@whitequark @jm there are better solutions to the double spending problem then a lottery for completing a proof-of-work function first
-
-
Replying to @bascule
@bascule@whitequark Yeah the more I’ve learned about the algorithm behind btc, it seems a little suboptimal. :)2 replies 0 retweets 0 likes -
Replying to @jm
@jm@whitequark one alternative is to leak a user's private key if they double spend2 replies 1 retweet 6 likes -
Replying to @bascule1 reply 0 retweets 0 likes
-
Replying to @whitequark
@whitequark@jm make double spending nonce reuse with any *DSA, which Bitcoin already uses. It's catastrophic (see e.g. PS3 master key)1 reply 0 retweets 0 likes -
Replying to @whitequark
@whitequark@jm i.e. if double spending is detected, identify the culprit in the DAG and blacklist his whole spending history2 replies 0 retweets 0 likes -
Replying to @bascule1 reply 0 retweets 1 like
-
Replying to @whitequark
@whitequark@jm encouragement to get your money from a reputable source and not to launder your money! ;)3 replies 0 retweets 0 likes
@whitequark @jm I'm talking about topological analysis of the spending DAG in the client and guilt-by-association
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.