Anybody staked yet?
That will be because someone had too muck stake money?
Topic: . - page 29. (Read 36731 times)
hey guys
whats going on here?
whats going on here?
if you can fix the coin.. maybe the original chain (the one that got stuck on block 1800)
it could be awesome
i think we are doing a swap, and swapping to something we will need to swap from again ..
So reading back, this is essentially an new Algo set of 23x sph hash , there have been multiple changes without forcing people to update so the old and new chain states are preserved... Is the dev still active? Does this need to be properly hard forked or a coin swap?
I can see that lots of people have invested time and probably money into mining this..
hey guys
whats going on here?
whats going on here?
if you can fix the coin.. maybe the original chain (the one that got stuck on block 1800)
it could be awesome
i think we are doing a swap, and swapping to something we will need to swap from again ..
Does anyone actually know what is going on? As far as I can work out the coin was added to Empoex because it was paid for, the dev doesn't quite know what he's doing regards the technicalities. And yes, wallet after wallet, with dev jusr randomly fixing/breaking/changing stuff.
IMHO the best thing to do is can the lot, and relaunch completely once the dev has got his act together.
IMHO the best thing to do is can the lot, and relaunch completely once the dev has got his act together.
What I can determine:
1. The "algorithm" that the dev made (ThiaMine) didn't work and caused the PoS break
2. The code base has been changed (and broken) three times
3. The current wallet does not properly compile on Linux (or Mac, probably)
4. In order to participate in Proof of Burn you need to (in order, otherwise you're screwed because you'll have the new blockchain):
- Use the 1.1.5 wallet to send your burn coins to XPAt4zq4Tyok91zjzfn4NPs6vwwQk7b2BM (presumably on the blockchain that stopped at 1800?)
- Take a screenshot of the transaction
- Make a backup copy of your .DeOxyRibose directory and keep it safe, then delete everything in it
- In your new conf file, use addnode=182.56.79.76
- Open the new wallet, version 2.0, and copy your new address
- Post your transaction screenshot, your old address, and your new address to http://forums.deoxyribose.cf/showthread.php?tid=2
6. I still have no idea what is going on
How to synchronize the old wallet for to send a coin on a burn? Nodes? Version?
We are all lab rats of an 11 year old kid. 
Ha haa. I know if I was 11, and crypto existed back then, I would be doing the same thing, trying to make this complete, functional, and successful, with all the cool features I could think of 
. So I'll continue being this kid's lab rat, as I owe it to those who were my lab rats in the past
Ha haa. I know if I was 11, and crypto existed back then, I would be doing the same thing, trying to make this complete, functional, and successful, with all the cool features I could think of . So I'll continue being this kid's lab rat, as I owe it to those who were my lab rats in the past
Does anyone actually know what is going on? As far as I can work out the coin was added to Empoex because it was paid for, the dev doesn't quite know what he's doing regards the technicalities. And yes, wallet after wallet, with dev jusr randomly fixing/breaking/changing stuff.
IMHO the best thing to do is can the lot, and relaunch completely once the dev has got his act together.
IMHO the best thing to do is can the lot, and relaunch completely once the dev has got his act together.
I have to agree, I've never come across such a confusing coin
It's great that the dev is active with development, and sometime it's best to engage the community with development and testing. but this should have been properly administered with with community, enforced hard forks, version updates etc…
IMHO the best thing to do now it stop, take a pause, fix all the issues so far. agree what rewards you want etc.. then fork on to a new chain, enforcing all clients to update… Then concentrate on making the network strong
It's great that the dev is active with development, and sometime it's best to engage the community with development and testing. but this should have been properly administered with with community, enforced hard forks, version updates etc…
IMHO the best thing to do now it stop, take a pause, fix all the issues so far. agree what rewards you want etc.. then fork on to a new chain, enforcing all clients to update… Then concentrate on making the network strong
How to synchronize the old wallet to send a coin on a burn?
This is a good question.
Niitassin, you should probably have posted the blockchain that you expect transactions on - there are at least three distinct blockchain forks from what I can tell, so very few clients are synced.
What do you mean? Because of mistakes developer(eбнyтoгo мaлoлeтки) I lost all my coins? Why was it necessary to create +100500 versions of the wallet?!
7000 XNA NEW BLOCK!!!!!!?? this is normal?
I think so:
http://i.imgur.com/0DUJcTV.png
What I'm curious about now is, the balance not changing/updating. Is this normal?
http://i.imgur.com/FobXIa4.png
Edit: Well, the balance does appear in the "Send Coins" section, so at least I know how much I've got. Would be nice if the "Overview" displayed the balance correctly though.
How to synchronize the old wallet to send a coin on a burn?
This is a good question.
Niitassin, you should probably have posted the blockchain that you expect transactions on - there are at least three distinct blockchain forks from what I can tell, so very few clients are synced.
niitassin-
Wallet wont compile because of your messing around with POW Reward amounts.
Please see PM to get it resolved so that I can get the community a Mac Wallet before POW ends breaks their blockchains, forcing them to have to resync the whole chain.
Wallet wont compile because of your messing around with POW Reward amounts.
Please see PM to get it resolved so that I can get the community a Mac Wallet before POW ends breaks their blockchains, forcing them to have to resync the whole chain.
1. I did not mess with the block rewards at all programmatically
2. I just changed it's apperance to be a lot lesser when it's a same by editing xnaunits.cpp
3. Right Now redownloading a Whole Chain is not really a Problem
4. The Error You PM'd Me, is for the XNA Apperance. I will fix it, thank you.
5. I love donuts!
I'm working on a fix for Linux (and probably OSX), at the moment. You should be able to pull it after I finish because it has a fix for LevelDB as well. I guess I'll pull whatever you fix with xnaunits.cpp, since I was just guessing at what you meant initially. Just make sure you take a look at DeOxyRiboseUnits::amountDigits(int unit) and DeOxyRiboseUnits::decimals(int unit) as well, because you changed XNA to equal what mmXNA equalled in DeOxyRiboseUnits::factor(int unit), but you didn't change the corresponding values in those functions.
(Also, XNA is just redeclared in xnaunits.cpp, but presumably you meant the return 1000000000; one, since it returns without ever reaching the other.)
No need of the XNA Units Problem, The LevelDB, I am interested, also you seem like a very nice guy/gal/bot (No Offence)!
Jump to: