Author

Topic: [ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN - page 333. (Read 782375 times)

full member
Activity: 165
Merit: 100
DEV UPDATE

Mandatory v2.1.2.2 wallet update has been released today by Stakebox that has fixed some core bugs and include many frontend improvements.

https://github.com/Darknet-Crypto/Darknet/releases/tag/v2.1.2.2

Change Log
- Incorrect math for the max budget, the block rewards, and the seesaw mechanism were corrected.
- Issue with masternode payment enforcement has been addressed.
- Unconfirmed staking and masternode rewards will no longer be shown in coin control.
- Masternode rewards will be marked as such in the transactions tab, and will no longer show as confirmed prematurely.
- Staking and masternode rewards will also show in the immature row on the main overview page of the wallet.
- Transactions sent using Obfuscation were showing as Darksent in the transactions page before, they will show as Obfuscated now.
- 2 new RPC calls created. setstakesplitthreshold & getstakesplitthreshold. This will allow people to experiment with stake split sizes.
- Few other minor changes to the Qt

As with any wallet upgrades, please backup first then test with 1 or few of your wallets and masternodes first before upgrading all wallets.

Nice update, this has the kind of information I like to see.

Building now.. testing soon...
hero member
Activity: 728
Merit: 500
Does this fix masternode start-missing?
full member
Activity: 236
Merit: 100
Mac Wallet updated
works like a charm
back to staking  Wink
legendary
Activity: 1148
Merit: 1001
DEV UPDATE

Mandatory v2.1.2.2 wallet update has been released today by Stakebox that has fixed some core bugs and include many frontend improvements.

https://github.com/Darknet-Crypto/Darknet/releases/tag/v2.1.2.2

Change Log
- Incorrect math for the max budget, the block rewards, and the seesaw mechanism were corrected.
- Issue with masternode payment enforcement has been addressed.
- Unconfirmed staking and masternode rewards will no longer be shown in coin control.
- Masternode rewards will be marked as such in the transactions tab, and will no longer show as confirmed prematurely.
- Staking and masternode rewards will also show in the immature row on the main overview page of the wallet.
- Transactions sent using Obfuscation were showing as Darksent in the transactions page before, they will show as Obfuscated now.
- 2 new RPC calls created. setstakesplitthreshold & getstakesplitthreshold. This will allow people to experiment with stake split sizes.
- Few other minor changes to the Qt

As with any wallet upgrades, please backup first then test with 1 or few of your wallets and masternodes first before upgrading all wallets.

ok updating 5 nodes for test
is there a block or timeframe until the update must be done
legendary
Activity: 1638
Merit: 1011
jakiman is back!
DEV UPDATE

Mandatory v2.1.2.2 wallet update has been released today by Stakebox that has fixed some core bugs and include many frontend improvements.

https://github.com/Darknet-Crypto/Darknet/releases/tag/v2.1.2.2

Change Log
- Incorrect math for the max budget, the block rewards, and the seesaw mechanism were corrected.
- Issue with masternode payment enforcement has been addressed.
- Unconfirmed staking and masternode rewards will no longer be shown in coin control.
- Masternode rewards will be marked as such in the transactions tab, and will no longer show as confirmed prematurely.
- Staking and masternode rewards will also show in the immature row on the main overview page of the wallet.
- Transactions sent using Obfuscation were showing as Darksent in the transactions page before, they will show as Obfuscated now.
- 2 new RPC calls created. setstakesplitthreshold & getstakesplitthreshold. This will allow people to experiment with stake split sizes.
- Few other minor changes to the Qt

As with any wallet upgrades, please backup first then test with 1 or few of your wallets and masternodes first before upgrading all wallets.
full member
Activity: 236
Merit: 100
Mac Wallet still disconnecting (while staking) somewhere between the 24 h
have to restart once a day

My Transactions are all messed up
in overview it only shows very old once
 
full member
Activity: 226
Merit: 100
member
Activity: 109
Merit: 10
That isn't too bad. How good is the staking  or is that included in the MN calculations?

hero member
Activity: 525
Merit: 500
how often do masternodes get payments

60 Second block time = 1440 blocks per day.
973 Masternodes online.

1440 / 973 = 1.48 times per day on average.

That would make the current average daily revenue per each masternode, about $0.18, or $5.47 per month.
full member
Activity: 226
Merit: 100
how often do masternodes get payments
Right now it takes around 48 hours to begin receiving masternode payments. Once you start getting them you can calculate the number of expected payments per day with the following formula.

number of blocks per day/number of masternodes=number of daily payments per masternode

So, right now you can expect 1440/974~1.47 payments per day. With the current number of masternodes on the network masternode payments are 29.25 DNET, so you are looking at about 43 DNET per day per masternode, on average.

These numbers reflect as things stand right now, and could change daily, or even hourly, if the number of masternodes changes.
member
Activity: 109
Merit: 10
how often do masternodes get payments
legendary
Activity: 1792
Merit: 1010
collecting like an aggressive landlord collects rents

missing a transaction though.. anyone knows if we have block explorer ? thanks

Yep, right here: http://lmgtfy.com/?q=darknet+block+explorer

pretty funny, .. great block explorer btw.., ok.. span off and activated 68th master node , thanks all and God speed
member
Activity: 109
Merit: 10
Running masternode start via the debug console yields the following error:

Not capable masternode: can't detect external address. Please use the masternodeaddr configuration option. Nothing is mentioned in the initial post about having to do this, only using the default 127 / local loop address at least for a single master node.
It is not usually needed. I should just have s3v3n modify the instructions to include it, and, upon further review, I see that the start command is incorrect there, which is why you were entering it like that. I will let him know to fix that as well.

To use the masternodeaddr configuration option add masternodeaddr= in darknet.conf.

edit: appears to be working. It didnt like using the nat address apparently.
full member
Activity: 226
Merit: 100
Running masternode start via the debug console yields the following error:

Not capable masternode: can't detect external address. Please use the masternodeaddr configuration option. Nothing is mentioned in the initial post about having to do this, only using the default 127 / local loop address at least for a single master node.
It is not usually needed. I should just have s3v3n modify the instructions to include it, and, upon further review, I see that the start command is incorrect there, which is why you were entering it like that. I will let him know to fix that as well.

To use the masternodeaddr configuration option add masternodeaddr= in darknet.conf.
hero member
Activity: 525
Merit: 500
collecting like an aggressive landlord collects rents

missing a transaction though.. anyone knows if we have block explorer ? thanks

Yep, right here: http://lmgtfy.com/?q=darknet+block+explorer
legendary
Activity: 1792
Merit: 1010
collecting like an aggressive landlord collects rents

missing a transaction though.. anyone knows if we have block explorer ? thanks

never mind ,nothing is missing, network is operating great, spinning yet another master node as per indication (slack) things will move big time in months to come, I call it a "sleeper" in the crypto world
hero member
Activity: 525
Merit: 500
Is the new vultr MN script out yet?
member
Activity: 109
Merit: 10
Running masternode start via the debug console yields the following error:

Not capable masternode: can't detect external address. Please use the masternodeaddr configuration option. Nothing is mentioned in the initial post about having to do this, only using the default 127 / local loop address at least for a single master node.

Follow my guide in op. Step by step with pics.

https://github.com/Darknet-Crypto/Darknet/releases/download/v1.1.0.0/Windows.Setup.for.Darknet.Masternodes.pdf


I have followed the guide, created the address, created the key modified the conf, restarted the wallet, deposited the 10k and run masternode start. The port is open in the firewall, username / passwords are set for rpc, and have added the provided nodes in that document. Still get the same message.
hero member
Activity: 728
Merit: 500
Running masternode start via the debug console yields the following error:

Not capable masternode: can't detect external address. Please use the masternodeaddr configuration option. Nothing is mentioned in the initial post about having to do this, only using the default 127 / local loop address at least for a single master node.

Follow my guide in op. Step by step with pics.

https://github.com/Darknet-Crypto/Darknet/releases/download/v1.1.0.0/Windows.Setup.for.Darknet.Masternodes.pdf
member
Activity: 109
Merit: 10
Running masternode start via the debug console yields the following error:

Not capable masternode: can't detect external address. Please use the masternodeaddr configuration option. Nothing is mentioned in the initial post about having to do this, only using the default 127 / local loop address at least for a single master node.
Jump to: