Search results

I have not concluded about it yet. If the basic income is the same everywhere, this will attract residents from the poor countries. If the basic income varies among local communities and is proportional to the purchasing power of the people, this will preserve the inequality. So, as always...

https://forum.encointer.org/t/scaling-encointer-fast-and-globally-through-staked-social-vouches/95

Lets vote the numbers about it. https://mnowatch.org/votethenumbers/votethenumbers3/ https://mnowatch.org/votethenumbers/ https://mnowatch.org/votethenumbers/prepnumvote3

You are all claiming that it was a BLS error that caused the blockchain halt (I am still not conviced 100% about it, when I read the code of the bug fix), but lets we suppose it was solely a BLS bug. Why do you assume that BLS is a good thing when used in order to make all the masternodes...

It depends on how you define compelling. I like the encointer community. https://explorer.encointer.org/

Exactly. The narrative that the blockchain halt had nothing to do with DashPlatform is an ostrich-like behavior. It reminds me of the reaction of the ostrich trying to hide when in danger.

Dash is certainly a dying coin/community. I agree with you. But on the other hand, there is no cryptocurrency community that is not a dying one. All of them are dying, with different dying speeds. So the dying speed is that matters, and I am still here to reduce that speed.

More detailed info for the above. https://github.com/dashpay/dash/tree/v0.13.0.0-rc1/src/evo the deterministicmns.cpp file is used to allow reusing of external collaterals in DIP3. In DIP3 (a specification that is supposedly written mainly by @QuantumExplorer aka Samuel) it is written ...

The bug occured in the file https://github.com/dashpay/dash/blob/v19.0.0/src/evo/deterministicmns.cpp as @QuantumExplorer recently admitted. Since it being asked of me sure part of the code at issue is here if (dmn->pdmnState->pubKeyOperator.Get().IsValid() && !DeleteUniqueProperty(*dmn...

Yes...shut down your service, this is the correct thing to do. But on the other hand, help us reveal the government agents that are hiding behind the crowdnodes, those filthy agents who always vote against anything may help the Dash community to succeed. I invite you to join the mnowatch...

10 NO votes? Look again, the NO votes of crowdnode are 23.

Below the 35 masternodes who voted against the dashtip proposal. https://mnowatch.org/the_results_dashd_2023-05-24-15-30-22.uniqueHashVotes.116.html?4=tip MOST OF THEM (23 masternodes) ARE CROWDNODERS!!! I suspect that the agents are now hiding into the crowd, dont you think @xkcd ? We have...

I tottaly agree with the above. The Dash protocol should be first voted by the members of the Dash community. Thats why organized governance, and cheep governance questions are desperately needed. After deciding the dash protocol, then various code implementations of the protocol should be...

And what is the usage of BLS signatures? Do we need them for the 4k HCMNs or not? You should first point to the code that caused the blockchain halt, and then we will discover whether it is related or not to the HCMN.

"High Collateral Masternodes". The DCG misleadingly names them "High Performance Masternodes" Read here. https://www.dash.org/forum/index.php?threads/should-platform-run-on-all-nodes-or-should-platform-run-only-on-high-performance-nodes.53374/

No impact on the markets? The stupid Evo decision about 4K High Collateral Masternodes=HCMN (stupidly named by DCG as HPMN=High Performance Masternodes) is taken, 9 Jan 2023 https://www.dashcentral.org/p/EVO-DECISION-4K-HPMN 15 Jan 2023, Dash is coin number 70...

I think they didnt lose money (correct me if wrong). They were just unable to do transactions during the halt time. But the issue is , this is the FIRST time such an incident occurs in Dash cryptocurrency, since its initial start up 9 years ago. The High Colateral Masternodes, introduced in...

If you consider the hard forking path as a problem, what solution do you suggest? What do you think of polkadot parachains?

So the bug has been discovered, the fix has not been discovered. Thats not a good thing, it reminds me of my pathetic self. I can discover too many bugs in my everyday life, but I am unable to discover their fix, or discover their fix the correct time.

I suspect that the problem has not been resolved by passing from v19.0 to v19.1, they just swept it under the rug. As far as I understand the code, the DCG just delayed the hard fork until june 14, hoping they will discover the bug of 19 version until that date...