Yep, i understand things are forming, so better wait and let the system mature first.I had proposed a DGbB tab, like the MN tab, but in a brief exchange with Evan over at the #Dev channel he mentioned he didn't want to see this implemented in the QT right now.
I think it would be cool to have a simple ballot tracking tab, but there seems to be magic happening in the background, so best wait to see whats in store...
.
sentinels is pushed back to 12.2 as far as I knowAh cool. Now I just need to wrap my head around Sentinel.
Pablo.
Currently though, even if they are stored in cold wallets, they still need to be a hot wallet temporarily in order to vote and activate don't they? Is there any way to sign an offline masternode transaction for later broadcast, without using a trezor? Like if I have a computer that is *never* connected to the internet, any way to use that to sign a masternode command, either presently or in 12.1? Thanks in advance if anyone can help answer --Presently, masternodes are run from cold wallets, which are already quite secure. This new feature will allow our masternode operators an even higher security environment for their masternode collateral and infrastructure.
Can't reproduce this on Mac. Can you try again?After creating a new wallet the first automatically created receiving address got incomplete / incorrect.
The second receiving address i created manually was normal.
![]()
Not sure about thatsentinels is pushed back to 12.2 as far as I know
Yes, that's exactly what was done here https://github.com/dashpay/dash/pull/741 and improved here https://github.com/dashpay/dash/pull/744Currently though, even if they are stored in cold wallets, they still need to be a hot wallet temporarily in order to vote and activate don't they? Is there any way to sign an offline masternode transaction for later broadcast, without using a trezor? Like if I have a computer that is *never* connected to the internet, any way to use that to sign a masternode command, either presently or in 12.1? Thanks in advance if anyone can help answer --
Great, thanks! Curious, what is the reason for the time limit on the broadcast txn?Yes, that's exactly what was done here https://github.com/dashpay/dash/pull/741 and improved here https://github.com/dashpay/dash/pull/744
Message will be legit for the next hour after signing.
That's also the way electrum-dash(-server) will use to sign MN start messages.
We need to drop inactive masternodes. And if you signed your MN more than an hour ago but never activated it, it should go down right when you try to activate it because if there were no pings from any MN for more than ~1 hour we treat it as an inactive one.Great, thanks! Curious, what is the reason for the time limit on the broadcast txn?
So far it only happened to one of my six windows wallets and i cant seem to reproduce it.Can't reproduce this on Mac. Can you try again?
Can anyone else confirm this also pls?
Yep, could be helpful. You know where to send itSo far it only happened to one of my six windows wallets and i cant seem to reproduce it.
I have debug.log available if needed.
I will sent it your way.Yep, could be helpful. You know where to send it
Thanks!
Can't reproduce this on Mac. Can you try again?
Can anyone else confirm this also pls?
Testnet 12.0 wallet.dat is incompatible with Testnet 12.1 wallet, we have reset the blockchain and changed the address version of the addresses. You'll need to delete your old (testnet3) wallet.dat to avoid these errors.![]()
It happen when migrate from 0.12.0.56 to 0.12.1 - invalid addresses was old, last address - generated in new version.
I found that this builds include update protocol version to 70200 , Hot-Cold masternode setup will need to start masternode from cold wallet again.Latest builds (git-16671cd) of v0.12.1.x branch
Linux --> https://dashpay.atlassian.net/builds/browse/DASHL-DEV-539/artifact/JOB1/gitian-linux-dash-dist/
Windows --> https://dashpay.atlassian.net/builds/browse/DASHW-DEV-488/artifact/JOB1/gitian-win-dash-dist/
MacOS X --> https://dashpay.atlassian.net/builds/browse/DASHM-DEV-496/artifact/JOB1/gitian-osx-dash-dist/
Raspberry --> https://dashpay.atlassian.net/builds/browse/DASHP-DEV-492/artifact/JOB1/gitian-RPi2-dash-dist/
Changelog:
- Mixing: fix RelayTransaction to relay correct message: https://github.com/dashpay/dash/pull/797
- Mixing: Fix final dstx signing: https://github.com/dashpay/dash/pull/798
- Masternodes: Optimize processing of new MN: https://github.com/dashpay/dash/pull/800
- QT: Move DS qt options to options dialog: https://github.com/dashpay/dash/pull/801
- QT: various fixes for masternode tab: https://github.com/dashpay/dash/pull/799
Testnet tools (explorers, faucets, pools) --> https://www.dash.org/forum/threads/testnet-tools-resources.1768/
[email protected]:~# ./dash-cli masternode status
{
"vin": "CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase )",
"service": "[::]:0",
"status": "Not capable masternode: Hot node, waiting for remote activation."
masternode start-many
10:13:30

{
"overall": "Successfully started 4 masternodes, failed to start 0, total 4",
"detail": {
"status": {
"alias": "MN1",
"result": "successful"
},
"status": {
"alias": "MN2",
"result": "successful"
},
"status": {
"alias": "MN3",
"result": "successful"
},
"status": {
"alias": "MN4",
"result": "successful"
}
}
}
You need to wait 60mins for your old 70103 entries to expire and then start with 70200 wallet - i had the same issue, and after this "timeout" it worked.hmmm ... so I was brushing up on my CLI ... Main QT is happy to report start-many is successful, but all of my nodes spit back this message.
I did stop and start again, to check if it's the 'ol cosmetic bug, but it isn't ...Code:[email protected]:~# ./dash-cli masternode status { "vin": "CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase )", "service": "[::]:0", "status": "Not capable masternode: Hot node, waiting for remote activation."
that totally sounded like star wars talk loooolYou need to wait 60mins for your old 70103 entries to expire
Yes, as @flare already mentioned old addresses are invalid now. The thing to reproduce is "After creating a new wallet"![]()
It happen when migrate from 0.12.0.56 to 0.12.1 - invalid addresses was old, last address - generated in new version.
After ~8 hours of mixing it show:
Last PrivateSend message:
No compatible Masternode found
Got new PrivateSent Denominate tx.
On testnet masternodes require 1 confirmation instead of 15 for now https://github.com/dashpay/dash/blob/v0.12.1.x/src/chainparams.cpp#L188, mainnet still requires 15 though https://github.com/dashpay/dash/blob/v0.12.1.x/src/chainparams.cpp#L83Masternodes become ENABLED when the collateral has less than 6 confirmations. Is this new behaviour intended?