• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

Version 12.2 release

Status
Not open for further replies.
camosoul said:
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.
Tail of debug.log showing lastoutput before crash...

This occurs consistently across multiple hardware platforms, all linux64.
Click to expand...

I've just checked and I'm not seeing this or having any crashes.
 
@camosoul Do you use proxy ?
If , which proxy SW do you use ?

camosoul said:
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.
Tail of debug.log showing lastoutput before crash...

This occurs consistently across multiple hardware platforms, all linux64.
Click to expand...
 
Was DASH Core proxy functionality not tested? Not even with the pre-defined settings?

I realize that's not where your focus has been, but...
 
Dash News Network said:
The original announcement in August said an InstantSend hotfix was available, yet here we are still waiting and being strung along with yet another pre-announcement for an announcement.

Is Dash Core going to keep fixing InstantSend bugs and disabling InstantSend for months at a time, or bring Dash up to modern standards with segwit and Lightning?

Litecoin and Decred already have Lightning while Dash is getting left behind in the dust.
Click to expand...

You're in the wrong forums, you should try the litecoin and decred forums.
 
wal said:
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
Click to expand...

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:
wal said:
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
Click to expand...
This RPC has changed https://github.com/dashpay/dash/blob/master/doc/release-notes.md#rpc-changes pls follow the doc linked in the release notes.

@thephez ^^^
 
Status
Not open for further replies.
Back
Top