We just burned the 60k at block 279917.
If you look at the Total Coins in the previous block, you will see that this block is 60k less. The coins were sent as a network fee which are destroyed.
But why network fee was destroyed and not given to miner? Yes, at the change to PoS, network fees are now destroyed. Though it is fractional, it does help overtime with inflation, and now we can remove coins from the total coin cap if needed...  instead of having them just sit there at an address somewhere. Thats how burning coins should work.. |
|
|
|
What's next on the cards? We have some cleanup work and a few tweaks to do, then we will be concentrating on the Anon Transaction... |
|
|
|
If it is one MN per IP address, there might be no incentive to host MN's once phase X hits, and rewards are down to 5 DNET.
Not sure that will be an issue, less masternodes means larger masternode rewards, which encourages people to start a few masternodes. If everyone had a few masternodes, we would still have a significant amount of nodes on the network. The objective is to increase the value of DarkNet to offset the lower rewards without creating a high inflation situation. |
|
|
|
Is it better to have one big wallet or many smaller wallets for staking?
One wallet, many smaller inputs. 2k-5k are good input sizes |
|
|
|
How does the masternode payout system work? Is it at a set time daily? Every certain number of blocks?
every block a random masternode is rewarded, just like the staker receives their stake |
|
|
|
I also see a lot of people who are still running the old wallets/masternodes, might want to update soon..
Any tips for restarting current masternodes with the latest version so that one doesn't need to restart them from the controller. With things being stable with my masternodes I'd rather wait for the next mandatory update or significant drop in reward than have my masternodes wait for a 1-2 days for the next payments. the timeout period is approx 60 minutes, so as long as you have you masternode restarted and running from the masternode side you should be fine. |
|
|
|
|
I also see a lot of people who are still running the old wallets/masternodes, might want to update soon..
|
|
|
|
need more people to turn on Obfuscation please. 500 Dnet/ 2 Rounds for now. Will be working up the amounts and rounds as we go.. Thanks |
|
|
|
What zapwallettxes ?
-zapwallettxes will clear the wallet of orphans |
|
|
|
Been away and not paying attention for the last couple of weeks, so just upgraded. New wallet is syncing and working fine for me on Win10 64, FWIW. Thanks to everyone for working through the issues of the past little while!
Question, and apologies if this was addressed however many pages back: Just got my first MN payment after upgrading, and the text is grey and it has a little eye beside it. I'm assuming this means the payment is invisible in some way. Is this the new normal for all MN payouts now?
Also, is staking automatic or does it have to be configured (if it's even up and running at present)?
Cheers.
Needs to confirm and it won't be grey anymore |
|
|
|
|
did you delete the peers.dat file and restart the wallet?
|
|
|
|
just for info: so far non of my masternodes running with version 2.1.2.1 crashed some masternodes still running with 2.1.2.0 & just crashed again, so i guess the new version is a nice step ahead for masternodes  What addnodes are you using? I have been syncing for the past 3 hours with none in the masternode darknet.conf files and it's still less than 50% done on the first node. It was stated when we pushed the update before this past one, that you should not need any addnodes. Yes, coin-server.com is a good one to have, but again, you should not need any. If you have more than that one, i would remove them all and delete your peers.dat file and restart the daemon |
|
|
|
Contrary to you guys on my side everything is working perfectly. I have no problems, no crash. yesterday I started with fresh brand new wallet, wired coins, launch masternode... I am just waiting the first payement to be certain. However I have no crashes what's so ever win7 64 & debian 32...
Did you really use a wallet from before the switch to POS? maybe you should create a brand new clean wallet.dat and send your coins there from your current one... just and idea.
I hope your issues will be resolved.
Fresh resync. New wallet on nodes, controller is a wallet from may. Nothing to do with files it's the exe. I don't know what to tell you... win10? because on my side as I told you, it's crash proof. Do you have enough cpu and ram resources? others programs running? maybe it's the old wallet controller? everything full new? test my crash problem on yours. in debug masternode start-alias mn1 YOURPASSWORD and work you way up your nodes pressing up to bring up masternode start-alias mn1 YOURPASSWORD then just change the number. normal happens after activating about 5-6 might be that you just dont have enough nodes to see this crash and are only using limited functions in the wallet... If it crashes it will not say the masternode has been activated but you can still go through the menus. the mphosting/linux masternode is another problem in its own as that is just fresh install, new wallet, only things saved were conf file. I have tried to tell you before, that u need to use walletpassphrase <your pass phrase> 12000 Then do the masternode start-alias <masternode name> The repeat, one line at a time. Will work much better than doing masternode start-alias <masternode name> <wallet passphrase> |
|
|
|
Mine has been crashing. I don't run a master-node. Worked at first for about 14 hours then crashed. Been crashing everyday since, almost every 12 to 16 hours... Restarted almost everyway possible--fresh starts and partial deletes. Used two different backups for wallet.dat and got the same results... just crashed as I was typing this...
What OS? Have you used a wallet.dat backup from before v2.1.1.0?? |
|
|
|
|
We are trying to research the issue with corrupting and crashing wallets.
Is anyone having issues with Wallets crashing, that is NOT using that wallet to run a masternode (either local or remote masternodes). Just staking??
|
|
|
|
OK folks, we re moving again. We are having an issue with one of the sporks, that is what caused the chain to stall for a bit the other day. When I disabled it the other day I just entered a date to activate as a few days in the future. That time passed last night stalling the chain again. I just changed the date to a couple months from now. We will have the issue resolved by then. Sorry about that.
Hello StakeBox, I can confirm that the chain is moving moving again. I don't understand what sporks... and what they do? Could you please enlighten me a little on the subject? From what I get from your message it's something that you can control. Does it affect the decentralized nature of DNET? Sporks are a way of mitigating network confusion and disagreement when there are either either hard or soft forks. If you run "spork show" in the console you can see the current state of the various sporks. When we push new updates that have protocol level changes we disable sporks 8, 9, and 10. Those are the ones needed the most. The others have not been needed by us so far. Yes, I can control them, I am the only one with the associated private key needed to do so. That doesn't really effect decentralization, as beyond allowing older versions of a wallet to communicate with newer versions during transitional periods, they serve no other function. I can't use them to roll back the chain, disallow certain users, deny blocks, or any other type of thing. The only spork that could even be misconstrued as a decentralizing thing is spork 10, the pay updated nodes spork. It is used after a protocol level change, which is generally a mandatory update, to decide when to stop sending masternode payments to masternodes still running the older version of the wallet. It lets older versions of the wallet continue acting as masternodes and getting paid for it during the transition, preventing a situation where there were no masternodes, or even very few, weakening that side of the network. thank you very much for this clear information. Should you have at least another devs have access to the private key in case of need? redundancy can always be very useful... Smooth stacking now for me too. However I remarked that it isn't possible to have the same wallet run a masternode and have a separate stacking address on it. it breaks the masternode address once a staking payment is received. It divides the masternode coins address in 4 stash of around 2500 dnet but still on the same address. However the masternode refuses to launch after saying that the coins aren't good. Is that a normal and expected behavior? Are you running just a local masternode on that wallet (Using just the darknet.conf file) ?? or are you setting it up as a remote node (using a masternode.conf file)?? |
|
|
|
My problem with that script is that my wallet randomly crashes even when starting one MN at a time...
until the wallet crash has been fixed a script is going to just annoy you with the crashing. masternode start-missing just needs to be fixed. have you tried the work around i suggested and are still having your wallet crash?? - Wait until your masternodes are close the the amount on Crownings stats page - console command: walletpassphrase <yourpassphrase> 12000 [HIT ENTER] - console command: masternode start-alias <Name of masternode> [HIT ENTER] - arrow up key to re enter passphrase - arrow up key twice change the name etc etc?? This has been working without issue for me, zero wallet freezes. |
|
|
|
Can windows wallet get fixed plz. It lags out then crashes when you start nodes one after other. Start missing instantly crashes. It is getting stuck at a block/crashing out when staking.
I have used a wallet from may. Resynced from scratch. It is the program.
It's not the program, its the new chain that your old wallet is not even aware of. I am also on Win 10 64bit. Besides that fact, it works for me and others. Sure, there are still issues. We have good workarounds for most. If you use an old wallet, your nodes are at risk of not working. so what is the workaround? was just told to use a wallet pre 2.0.1.0 version. will this get fixed in an update? Here is a solid work around for the lagging issue in the console. walletpassphrase <yourwalletpassphrase> 12000 enter masternode start-alias <name of masternode> enter walletpassphrase <yourwalletpassphrase> 12000 enter masternode start-alias <name of masternode> enter etc etc.. we are looking into this issue... EDIT: Make sure you have synced all the masternodes in your list before you start this, depending on the peers you have, this may take awhile after all the data has been synced. Check you masternode totals from the information tab against the Crowning stats page. You may not see all, but should see most (All depends on the peers you are connected to) |
|
|
|
My wallet is fully synced and working except for POS. Is POS active?? I have my wallet unlocked but it says I'm not staking.
you have to unlock your wallet for staking, have an input which is either 1 hour old (standard input) or a previously staked input of 101 confirms then your wallet will stake |
|
|
|
|
Show Posts
