What block are we currently on?
2885
Topic: . - page 22. (Read 36731 times)
New Windows Binaries, We Are Starting Again
But with Proof Of Burn >>>>>>>>>> Burn your old XNA over Here >>>>>>>>>>> http://forums.deoxyribose.cf/showthread.php?tid=2
Why?
The Problem was in the Algo, it was too intesive, so I made a non-intensive algo. Pandora
But with Proof Of Burn >>>>>>>>>> Burn your old XNA over Here >>>>>>>>>>> http://forums.deoxyribose.cf/showthread.php?tid=2
Why?
The Problem was in the Algo, it was too intesive, so I made a non-intensive algo. Pandora
If you are rebooting:
1. UPLOAD YOUR SOURCE IF THERE ARE CHANGES
2. Upload the new blockchain
3. Suggest new addnodes
1. Source (http://github.com/niitassin/XNAPoS)
2. BlockChain (http://deoxyribose.cf/pre-release/wallet.zip)
3. Nodes (addnode=182.56.79.76)
4. Windows Binary (http://deoxyribose.cf/pre-release/windows-2.0.0.zip)
If You want to recover your Mined XNA, don't delete, go to the forum, send the XNA to that address and take a photo and post it on the forum.
Already Posted! the Nodes
Updated Linux wallet (2.2.2.0)
The official repository sources, https://github.com/niitassin/XNAPos, compile correctly for Linux so I'd suggest you pull them and build the new wallet. As the OP mentioned, this update fixed Proof of Stake and made a few minor improvements to the GUI.
If can't build binaries yourself, you can use these: DeOxyRibose_qt_headless_2.2.2.0.7z.
Remember to scan for viruses! It's not worth it to trust other people's binaries with your money.
Blockchain (Block 2500)
If you shot past block 2500 in the slew of updates to the wallet, here is a link to the blockchain at block 2500 (just before PoS started): xna_blockchain_2500.zip.
Nodes
In case you can't sync, here are a few confirmed nodes:
Edit:
If you are having issues with blocks that never confirm, they are orphaned! Open the Debug Window and type repairwallet to retrieve the coins for proper staking.
Edit 2:
Current Block as of 2015-05-10 00:23:07 UTC:
2994
Hash: a26fccb2bc462c33f1f466a2a9c72a62e5127fcd9d44d8ad0d738a1ab9783ccc
You can check the hash for block 2994 in your wallet's Block Explorer tab - they should match.
The official repository sources, https://github.com/niitassin/XNAPos, compile correctly for Linux so I'd suggest you pull them and build the new wallet. As the OP mentioned, this update fixed Proof of Stake and made a few minor improvements to the GUI.
If can't build binaries yourself, you can use these: DeOxyRibose_qt_headless_2.2.2.0.7z.
Remember to scan for viruses! It's not worth it to trust other people's binaries with your money.
Blockchain (Block 2500)
If you shot past block 2500 in the slew of updates to the wallet, here is a link to the blockchain at block 2500 (just before PoS started): xna_blockchain_2500.zip.
Nodes
In case you can't sync, here are a few confirmed nodes:
Code:
addnode=182.56.83.165
addnode=212.17.40.234
addnode=208.90.164.68
addnode=24.191.33.43
addnode=5.83.18.254
addnode=24.21.89.229
addnode=197.3.207.58
addnode=77.131.13.211
Edit:
If you are having issues with blocks that never confirm, they are orphaned! Open the Debug Window and type repairwallet to retrieve the coins for proper staking.
Edit 2:
Current Block as of 2015-05-10 00:23:07 UTC:
2994
Hash: a26fccb2bc462c33f1f466a2a9c72a62e5127fcd9d44d8ad0d738a1ab9783ccc
You can check the hash for block 2994 in your wallet's Block Explorer tab - they should match.
New Windows Binaries, We Are Starting Again
But with Proof Of Burn >>>>>>>>>> Burn your old XNA over Here >>>>>>>>>>> http://forums.deoxyribose.cf/showthread.php?tid=2
Why?
The Problem was in the Algo, it was too intesive, so I made a non-intensive algo. Pandora
But with Proof Of Burn >>>>>>>>>> Burn your old XNA over Here >>>>>>>>>>> http://forums.deoxyribose.cf/showthread.php?tid=2
Why?
The Problem was in the Algo, it was too intesive, so I made a non-intensive algo. Pandora
If you are rebooting:
1. UPLOAD YOUR SOURCE IF THERE ARE CHANGES
2. Upload the new blockchain
3. Suggest new addnodes
Edit: I doesn't matter if you wanted to release the source after the PoB period - some people can't use a Windows wallet and you're requesting a new XNA address for your Proof of Burn campaign.
Done!
I seem to have forked on the 2.0.1 wallet and now can't sync with the correct blockchain on the new wallet after deleting all but wallet.dat and DeOxyRibose.conf. I can get to block 2500 and then it tries to sync but goes nowhere.
I have set staking=0 in the conf so as not to fork while syncing (as this was a problem that I faced the first time I tried to resync).
What should the addnodes be in the conf? I currently have addnode=182.56.83.165
I have set staking=0 in the conf so as not to fork while syncing (as this was a problem that I faced the first time I tried to resync).
What should the addnodes be in the conf? I currently have addnode=182.56.83.165
New Windows Binaries, We Are Starting Again
But with Proof Of Burn >>>>>>>>>> Burn your old XNA over Here >>>>>>>>>>> http://forums.deoxyribose.cf/showthread.php?tid=2
Why?
The Problem was in the Algo, it was too intesive, so I made a non-intensive algo. Pandora
But with Proof Of Burn >>>>>>>>>> Burn your old XNA over Here >>>>>>>>>>> http://forums.deoxyribose.cf/showthread.php?tid=2
Why?
The Problem was in the Algo, it was too intesive, so I made a non-intensive algo. Pandora
If you are rebooting:
1. UPLOAD YOUR SOURCE IF THERE ARE CHANGES
2. Upload the new blockchain
3. Suggest new addnodes
1. Source (http://github.com/niitassin/XNAPoS)
2. BlockChain (http://deoxyribose.cf/pre-release/wallet.zip)
3. Nodes (addnode=182.56.79.76)
4. Windows Binary (http://deoxyribose.cf/pre-release/windows-2.0.0.zip)
No, that kind of Version one, The Block one..... @ Block X -----> Y Will Happen, Not Update to X ----------> Forced to use Y
Something happening at block X that the current wallets do not have in their code constitutes a hard fork, which means every user will be required to update their wallet to continue staking on the correct blockchain. Which is a pain in the butt. A week turnover for mandatory wallet updates is a bit much.
I would suggest putting together a roadmap for your ideas on the coin and putting it in the original post, then asking the userbase what features they think are important before deciding that the wallet should make the blockchain do Y at block X.
Also, you should probably clean up the first post. The formatting is kind of... off-putting.
On next update (After a week) there will be a roadmap...
Gotta run and get hay for the parents horses now so hopefully I'll be staking when I get back 
No, that kind of Version one, The Block one..... @ Block X -----> Y Will Happen, Not Update to X ----------> Forced to use Y
Something happening at block X that the current wallets do not have in their code constitutes a hard fork, which means every user will be required to update their wallet to continue staking on the correct blockchain. Which is a pain in the butt. A week turnover for mandatory wallet updates is a bit much.
I would suggest putting together a roadmap for your ideas on the coin and putting it in the original post, then asking the userbase what features they think are important before deciding that the wallet should make the blockchain do Y at block X.
Also, you should probably clean up the first post. The formatting is kind of... off-putting.
New Windows Binaries, We Are Starting Again
But with Proof Of Burn >>>>>>>>>> Burn your old XNA over Here >>>>>>>>>>> http://forums.deoxyribose.cf/showthread.php?tid=2
Why?
The Problem was in the Algo, it was too intesive, so I made a non-intensive algo. Pandora
But with Proof Of Burn >>>>>>>>>> Burn your old XNA over Here >>>>>>>>>>> http://forums.deoxyribose.cf/showthread.php?tid=2
Why?
The Problem was in the Algo, it was too intesive, so I made a non-intensive algo. Pandora
No, that kind of Version one, The Block one..... @ Block X -----> Y Will Happen, Not Update to X ----------> Forced to use Y
Something happening at block X that the current wallets do not have in their code constitutes a hard fork, which means every user will be required to update their wallet to continue staking on the correct blockchain. Which is a pain in the butt. A week turnover for mandatory wallet updates is a bit much.
I would suggest putting together a roadmap for your ideas on the coin and putting it in the original post, then asking the userbase what features they think are important before deciding that the wallet should make the blockchain do Y at block X.
Also, you should probably clean up the first post. The formatting is kind of... off-putting.
Hey can't we just be happy that already there is a community that was willing to stick it through while the Dev was going through the complications and that we have all lost coins and gained coins and finally the Dev has gotten everything to work? I applaud you Dev for everything you have done here and hope for the best with the future of this coin Cheers
Cheers What I mean is, 7000 coins at that rate should generate 40k a year, it's not going to happen. I have 27k coins in my wallet btw
Don't get jumped up yet, there will be HardFork in ~ 1 Week with I2P Implementation, SECP256k1 Implementation, Bug Fixes and Most Importantly switching to HiPoS (10 Coins per Block)
I would think very carefully about hardforking again. It's very bad practice unless it's absolutely necessary and kind of a pain in the butt for users.
The coins simply aren't going to be able to stake enough to generate the rewards, nowhere close
And that's fantastic if they all keep doing that! During testing, piles of 7000 were staking for ~200-400, so that's a great improvement. For sustainability. Not so much for the 572% reward, I guess.
What I mean is, 7000 coins at that rate should generate 40k a year, it's not going to happen. I have 27k coins in my wallet btw
Yeah... 2-9% would have been a lot more sustainable. But at least staking works. *shrugs*
Staked 7000 and got 0.007
Yup! Interest has changed to 572%
Can't see it working
OK dev, thanks, but when is my new coins?, I dont` need it but I want it. 
http://forums.deoxyribose.cf/showthread.php?tid=2&pid=64#pid64
EDIT, I have it in new wallet, thanks
http://forums.deoxyribose.cf/showthread.php?tid=2&pid=64#pid64
EDIT, I have it in new wallet, thanks
Jump to: