- Status
Pot calling kettle black, while dashing our hopes that the first would be the last...
FYI:
1. MN upgrade progress
i.e. ~86% of all nodes or ~95% of active nodes are upgraded now.
2. It's almost 2 weeks since the 12.2 release and almost every active 12.1 masternode which was started more than 1 week ago was paid (see https://www.dashninja.pl/masternodes.html?mnregexp=70206, sort by "Last paid"), there are like 2 or 3 masternodes left to be paid and then the cycle is done.
3. Given the signaling for DIP0001 we have ~85-90% of the mining power upgraded to 12.2, miners on 12.1 have increased orphan rate due to inconsistency of winners list there (unlike for 12.2), so they have an incentive to upgrade ASAP too.
With all this in mind, please be aware that we are going to activate SPORK_10_MASTERNODE_PAY_UPDATED_NODES in few coming days. Note, that you are not going to be paid (as a MN) and you will most likely mine invalid/orphan blocks all the time (as a pool) if you are still going to run 12.1 after this spork is ON. Don't wait for this to happen, update to 12.2 NOW!
A small note for masternoders who updated to 12.2: as I already noted above https://www.dash.org/forum/threads/version-12-2-release.17807/page-5#post-146784 and as you can see on dashninja - there are quite a few 12.2 masternodes running on 70206 protocol. If your masternode is in this list - you have to re-activate it and make sure it's on 70208 protocol or it will NOT be paid otherwise.
1. MN upgrade progress
Code:
Total: 4715 (PS Compatible: 4095 / Enabled: 4295 / Qualify: 2064)2. It's almost 2 weeks since the 12.2 release and almost every active 12.1 masternode which was started more than 1 week ago was paid (see https://www.dashninja.pl/masternodes.html?mnregexp=70206, sort by "Last paid"), there are like 2 or 3 masternodes left to be paid and then the cycle is done.
3. Given the signaling for DIP0001 we have ~85-90% of the mining power upgraded to 12.2, miners on 12.1 have increased orphan rate due to inconsistency of winners list there (unlike for 12.2), so they have an incentive to upgrade ASAP too.
With all this in mind, please be aware that we are going to activate SPORK_10_MASTERNODE_PAY_UPDATED_NODES in few coming days. Note, that you are not going to be paid (as a MN) and you will most likely mine invalid/orphan blocks all the time (as a pool) if you are still going to run 12.1 after this spork is ON. Don't wait for this to happen, update to 12.2 NOW!
A small note for masternoders who updated to 12.2: as I already noted above https://www.dash.org/forum/threads/version-12-2-release.17807/page-5#post-146784 and as you can see on dashninja - there are quite a few 12.2 masternodes running on 70206 protocol. If your masternode is in this list - you have to re-activate it and make sure it's on 70208 protocol or it will NOT be paid otherwise.
Not everybody is equally mature in dash. Please understand that no coin is completely immune to bad actors.
But luckily the majority of voters (aka masternode owners). Is doing there very best do vote in a way that service dash best.
That being said, the 45% 45% 10% split will not change anytime soon, do further research into this will be done, to find the right mix, but that could be years before that actually changed if ever.
In the meantime try and tweak your miner as best as possible, just it has a heater in the winter, try using it in a way you can get taxbreak or something. That who you compete in this business
I just noticed something strange on a maternode payment, it shows in the blockchain but not on dash ninja.
https://www.dashninja.pl/blocks.html Block 774206 is missing. Curious.
The block looks fine, so I can only assume some kinda error / slip on dashninja.? Side note, this masternode was paid 5 day 0 hours after last payment. Quicker than normal
https://www.dashninja.pl/blocks.html Block 774206 is missing. Curious.
The block looks fine, so I can only assume some kinda error / slip on dashninja.? Side note, this masternode was paid 5 day 0 hours after last payment. Quicker than normal
Strange indeed. Block 774206 does show up on cryptoid (https://chainz.cryptoid.info/dash/block.dws?774206.htm), and i also noticed another masternode (on latest version) getting paid after 5 days.
Could be a case of lucky variance for those masternodes and a not totally synced Dashninja block explorer.
(although Dashninja does seem okay now, with correct balance showing at last and a nicely updated website)
Last edited:
Every active node started/paid before or 2 days after the release is paid again now, so payment cycle is complete and SPORK_10_MASTERNODE_PAY_UPDATED_NODES is ON meaning that only upgraded (12.2.x / 70208) nodes are going to be paid from now.
On another note, we are 250+ blocks into new DIP0001 voting period (4032 blocks, ~1 week). So far 90% of blocks are signaling DIP0001 and we need 80%+ support for this period in total at the block 778176. Looking good
On another note, we are 250+ blocks into new DIP0001 voting period (4032 blocks, ~1 week). So far 90% of blocks are signaling DIP0001 and we need 80%+ support for this period in total at the block 778176. Looking good
Code:
2017-11-22 05:04:42 CGovernanceObject::ProcessVote -- Masternode index not found
2017-11-22 05:04:42 CGovernanceObject::ProcessVote -- Masternode index not found
2017-11-22 05:04:42 CGovernanceObject::ProcessVote -- Masternode index not found
2017-11-22 05:04:42 CGovernanceObject::ProcessVote -- Masternode index not found
2017-11-22 05:04:42 CGovernanceObject::ProcessVote -- Masternode index not found
2017-11-22 05:04:42 CGovernanceObject::ProcessVote -- Masternode index not found
2017-11-22 05:04:42 CGovernanceObject::ProcessVote -- Masternode index not found
2017-11-22 05:04:42 CGovernanceObject::ProcessVote -- Masternode index not found
2017-11-22 05:04:43 receive version message: /bitcore:1.1.0/: version 70206, blocks=0, us=[::]:0, peer=142
2017-11-22 05:04:44 AdvertiseLocal: advertising address 75.91.99.153:9999
2017-11-22 05:04:49 SOCKS5 connected 82.196.1.234
2017-11-22 05:04:49 CPrivateSendClient::StartNewQueue -- connected, addr=82.196.1.234:9999
2017-11-22 05:04:49 ThreadSocketHandler -- removing node: peer=143 addr=82.196.1.234:9999 nRefCount=2 fNetworkNode=1 fInbound=0 fMasternode=1
2017-11-22 05:04:49 ERROR: Requesting unset send version for node: 143. Using 209
dash-qt: /home/ubuntu/build/dash/depends/x86_64-unknown-linux-gnu/share/../include/boost/thread/pthread/recursive_mutex.hpp:113: void boost::recursive_mutex::lock(): Assertion `!pthread_mutex_lock(&m)' failed.This occurs consistently across multiple hardware platforms, all linux64.
- Apr 8, 2014
- 1,971
- 1,339
- 1,283
Just go here: https://www.dash.org/wallets/#wallets
Find your operating system and download your wallet.
After you download it just start the program and done
To be sure, from top menu go to debug console and write 'getinfo' and execute you should see version: 12.2.1
You're in the wrong forums, you should try the litecoin and decred forums.
DIP0001 is locked in!
(you can check for yourself via getblockchaininfo rpc command)
We will wait few hours to make sure that winners list is stable and if everything is good we'll activate IS. Stay tuned!
(you can check for yourself via getblockchaininfo rpc command)
We will wait few hours to make sure that winners list is stable and if everything is good we'll activate IS. Stay tuned!
Code:
"SPORK_2_INSTANTSEND_ENABLED": true(rpc command: spork active)
is it actually working for you?
according to the docs [1]
a call to `gettransaction` is supposed to have confirmations and bconfirmations fields but it only has the former.
I see a field called `instantlock` thats not in the docs.
btw i did a tx with IX and confirmations was 0 (not 5)
whats going on?
[1]: https://dashpay.atlassian.net/wiki/spaces/DOC/pages/104823072/InstantSend+Receive
according to the docs [1]
a call to `gettransaction` is supposed to have confirmations and bconfirmations fields but it only has the former.
I see a field called `instantlock` thats not in the docs.
btw i did a tx with IX and confirmations was 0 (not 5)
whats going on?
[1]: https://dashpay.atlassian.net/wiki/spaces/DOC/pages/104823072/InstantSend+Receive
You are right.
The wiki is often out of date. The core team should install mediawiki, a much more advanced wiki software, where we can see in the history of the article, who edited the article, and when. That way you could see that this doc is outdated, and comment in the article's discussion the errors and the proposed changes. Even more, the MNOs should hire people responsible to update the wiki, and fire them in case the wiki is not updated.
This is yet another reasonable proposal, but who is gonna paid 3000$ to propose it in the budget?
Last edited:
Yay! Is 2mb happening now as well, and 10x fee reduction, or is that later?It's alive!Code:"SPORK_2_INSTANTSEND_ENABLED": true
(rpc command: spork active)
Dip0001 lock in only allows us to turn IS back on. 2mb block limit and 10x lower fees are going to activate automagically on block 782208 i.e. in ~1 week.
@UdjinM6 the link in the release notes is dead.
i.e.
https://github.com/dashpay/dash/doc/instantsend.md
Yay! A bug in docs!
Here is the correct one https://github.com/dashpay/dash/blob/master/doc/instantsend.md
EDIT: or even better https://github.com/dashpay/dash/blob/v0.12.2.x/doc/instantsend.md
- Status