Bandwidth growth may not be *precisely* predictable, but there are reasonable expectations. Demand for transactions should not be a factor in such limits at all.
-
This Tweet is unavailable
-
This Tweet is unavailable
-
Masternodes have a collateral requirement, since a MN sybil attack would compromise the extra services MNs provide. What kind of harm could a person cloning their non-MN full node do? Miners don't depend on non-MN full nodes, and network votes are done by masternodes.
Seems a bit like a "house of proof-of-stake" operating alongside a "senate-of-miners". But how is it secured? Are @LukeDashjr's and @fluffypony's critiques (for example, that the important functions of a node are not actually verified) accurate, and if not how specifically not?
-
-
SPV risk for standard txs in Dash is comparable to BTC/BCH: personal full node is still best. Full and SPV clients can prevent double spends with InstantSend, which relies on a quorum of masternodes, whose participation is now monitored w/ proof-of-service https://docs.dash.org/en/stable/masternodes/understanding.html#proof-of-service …
-
In the upcoming version, proof of service (PoSe) includes a bunch of neat DKG stuff. Currently it's based on things like whether a masternode handles instantsend locks properly -- here is an instance where a good masternode votes to ban a bad one:https://github.com/dashpay/dash/blob/master/src/instantx.cpp#L472 …
-
Oh cool, so instead of a cabal of MasterNodes taking one offline via DoS to increase their proportional payout, all they have to do is just vote them offline for bad behaviour. Much, much easier!
-
I appreciate your attempts to help with these kinds of edge cases; maybe you can give us more insights? Here is some of the code that deals most with proof-of-service bans in the current version: https://github.com/dashpay/dash/blob/v0.13.x/src/masternodeman.cpp …
-
Pointing out an obvious flaw doesn't mean I'm available for free work :)
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.