When masternode ?
Hey man do you have a synced working wallet with connections? And if you do could you pretty please post your .conf file for me or PM it to me because no matter what I do I can't get the proper connections and I've tried everything See below 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. NodesIn case you can't sync, here are a few confirmed nodes: 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=208.90.164.68
addnode=197.3.207.58
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 your wallet's Block Explorer tab - they should match. |
|
|
|
What block are we currently on?
2885 |
|
|
|
[...] you do see my point where now there will be more than the 750 million coin supply when POS starts right? And I mean if they can be deposited into the new wallet then I would think that someone would buy as much of them as they could up so they could stake all of them and turn their supply into an outrageous amount no?
The blockchains are different, so the coins there are as good as dead - they can't be transferred to new wallets because the 2.x blockchain does not agree with whatever transfers were made to the exchange. Aye, what is being mined atm should be consider DeOxyRibose v2. Totally different coins and blockchian |
|
|
|
So just out of curiousity are all those sell orders for hundreds of thousands of coins still on EmpoEx? Because wouldn't those coins have to have been burned along with the rest when you made us start mining all over again? I'm just asking for piece of mind  Peace Of Mine. Delivered.... Well, the current data is EmpoEX's Fault... So those coins will still be accepted in the newer wallet? Not to sound rude but that doesn't seem very fair does it? I mean I had 525000 coins in the first wallet that I sent to EmpoEx that just vanished in thin air so why didn't EmpoEx destroy all the coins? I know that it's not really on you totally because you don't run the exchange but you do see my point where now there will be more than the 750 million coin supply when POS starts right? And I mean if they can be deposited into the new wallet then I would think that someone would buy as much of them as they could up so they could stake all of them and turn their supply into an outrageous amount no? Might be an idea to tell them to delist. |
|
|
|
3 days worked fx8350 = 2942000 xna turned into 2942000/500=5884 xna . it's just a laugh!!!!!! the price on the exchange=0. shit  Think they need to remove the coin from the exchange.. Its not the right chain AND Coin anymore. Also needs to be removed from the OP |
|
|
|
No because the second that I put the wallet.dat back into the roaming folder it automatically does the runtime error thing and says the wallet.dat is salvaged and can't be repaired or some shit and it's the wallet.dat from the latest wallet update I made a copy in case some shit like me having to reboot my computer happened then I knew I didn't lose my coins but I guess I was wrong lmao
Okay. 1. Keep you backup wallet. 2. Clean out blockchain folder. Delete everything. 3. Download and Put the wallet data from OP in the blockchain folder. 4. Put your wallet back into folder. 5. Reboot 6. Start up client again |
|
|
|
|
I found I had to reboot the PC to get it running again. Possible a case of the QT library binaries not compiled statically. (I have had problems like that in the past)
|
|
|
|
|
He seems to working flat out at this and are making good progress.
But should really get the changes under control and ONLY do hardforks at set block heights..
Update code with conditions.. Mandatory Client Update
Under block 1000 do normal.. Over 1000 changes kicks in
And if you are no using the new wallet, you will be on fork after block height 1000..
I like the dev though.. Seems like a nice guy. Hope this will go somewhere with a bit of support
|
|
|
|
Yeah that's what I've done. Just waiting for it to connect to some nodes and sync, guess I'll need a little patience
Make sure you have added .conf file. It should insta connect. |
|
|
|
|
Just to be clear in case somebody wants to mine this on windows.
1. Download client, run it. then close it.
2. Download the BlockChain zip file. Extract it to %USERPROFILE%\AppData\Roaming\DeOxyRibose
3. Create the DeOxyRibose.conf config file in the folder above (Use settings in OP)
4. Launch client. Let it sync. You are now mining.
(To confirm Help/Debug window. Type in getmininginfo. it should list your hashrate under hashespersec)
|
|
|
|
So which is the current wallet for windows then?
The one in OP. |
|
|
|
....
From where did you get 32 Cores?
DeOxyRibose Client 1.1.0 Changes (In Progress)
- Decrease in Algo Harshness
- Advanced PoS Features
- IRC Chat
- Less Crappy Look
- Hardcoded Nodes
Nice to see a Dev really working hard. |
|
|
|
something fishy with the Blockchain, i mined some blocks in the morning, but looks like there was a fork already. Still there is also a Problem with the nodes, have 0 Connections now too.  If reward is 1, you are not on the right chain before last night fix. Clean out everything. (download the blockchain data in OP as well and use that conf) |
|
|
|
Dammit.. Thought when he said tomorrow he meant tomorrow.. So went to bed and was just up for a cup of water..
See peps are already finding blocks and high diff
meh
You aren't missing anything, most people have been trying for 4 hours to get ANY connection to the network. Dev's config does not work. The original win wallet and config worked before the fork, now nothing. If anyone can post a working conf file for windows, please do. Here's what I've got in my .conf file and I've been synced since block 3 and have found 2 blocks myself addnode=52.28.61.59 addnode=182.56.90.144 server=1 daemon=1 rpcuser=whateveryouwant rpcpassword=whateveryouwant rpcport=22192 rpcconnect=127.0.0.1 gen=1 allowreceivebyip=1 Hope this helps some people out Odd, still doesn't connect for me, yet the first wallet with fork connected no problem  Oh well on to the next coin. peers.dat + conf.. works for me XZMtGVWDKLckhkuMp8V4Mgj1ZfFzAETeui . If you make a killing on it |
|
|
|
|
And now it looks like cloud cpu miners just hit.. meh
|
|
|
|
The real question I would like to ask though is has anyone figured out a way to mine this thing besides the wallet? because I don't get that much hashing power out of mine and wouldn't mind snagging some more stacks of coins From looking at the hashrate nope not yet. |
|
|
|
|
Dammit.. Thought when he said tomorrow he meant tomorrow.. So went to bed and was just up for a cup of water..
See peps are already finding blocks and high diff
meh
|
|
|
|
|
Show Posts
And how is it to understand where the coins at a solo production ?
