We cheered Gensler when he became SEC Chairman because he taught about Bitcoin and blockchain at MIT.
Turns out, he’s never even owned it.
This guy is a sham.
@Justin_Bons And 5% can effectively censor transactions in PoW mining via feather forking (which makes it a gamble for any miner to include txs that these 5% wish to censor).
“There is no simple solution to the problem of privacy, because privacy itself is a solution to societal challenges that are in constant flux.” https://t.co/9PgSRNexkZ
Today the security halvening will take place over BTC
The amount of value protecting the network will be cut in half, drasticly reducing the security of the network
Another step down the path of a doomed security model
The halvening is a fundemental crisis, not a bullish event
@el33th4xor Double spend probability is also function of the *time waited for those confirmations*
6 confirmations in 20 minutes is stronger than 6 confirmations in 4 hours
Accepting after a fixed number of confirmations discards timing info. There are other types of acceptance policies
I like Bitcoin Cash for its purity of vision. Hardware trends tell us that, if you were happy with Bitcoin at 1MB in 2015, you should be just as happy with much larger blocks today. BCH is exploring how far one can ride these trends. Godspeed!
7. Satoshi did foresee, but was wrong on, what happens when transaction fees exceed block rewards. He indicated that the system would operate as normal. This is incorrect, as miners have an incentive to snipe each other's transactions instead of collaboratively building a chain.
If you are still building your product on top of BTC, you are guaranteeing that your customers will have a horrible user experience the next time the BTC blocks become full.
@el33th4xor There are policies for accepting transactions beyond "wait for N confirmations." Specifically, the transactions are accepted as a function of time since transaction broadcast as well as confirmations. First presented by @hashdag and further analyzed here:
https://t.co/bpAoMqlS9r
@el33th4xor Double spend probability also depends on the timing of block arrivals. 6 confirmations in 3 hours is not as strong as 6 confirmations in 20 minutes.
https://t.co/bpAoMqlS9r
@PeterRizun I also Bitcoin-related double spending probability questions. I am specifically interested in how the timing of block arrival affects the probability of double spend. I would appreciate any feedback you have on this e-Print paper on the topic: https://t.co/bpAoMq4gKR
@el33th4xor@PeterRizun Always seemed strange to require a fixed number of confirmations to accept a transaction given the stochastic nature of block arrivals. Doesn't the probability of double spend at acceptance depend both on number of confirms as well as the amount of time since trans broadcast?
@killerstorm@pakoconka1@PeterRizun From Satoshi's paper: "assuming the honest blocks took the average expected time per block." Satoshi discarded the stochastic behavior of block arrivals, and so his equations are approximations. The answer to the quiz is 20.83%. Block timing information affects the 2x spend prob.
@killerstorm@pakoconka1@PeterRizun Unfortunately it is not that simple. Using n=2 implies accepting a transaction after exactly two confirmations, only after which may the attacker double spend. The attacker waiting for two confirmations instead of just one to release his chain affects the double spend calculation
@PeterRizun Double spend probability depends on how long the one confirmation took to arrive. This timing information is public and available that the receiving party should not discard. Blocks can take a long time to arrive. https://t.co/BFaMFzF4ZZ (90+ min --> 70%+ 2x spend probability)
@PeterRizun Block timing information is required to answer this question. If the single confirmation took 90 minutes to arrive, the 2x spend probability is quite high. If the single confirmation arrived in only 2 minutes, probability is drastically lower. See: https://t.co/bpAoMq4gKR
@AdditiveLab These blocks can be made as big as you want, right? If so, I think you just solved the Bitcoin scaling issue!
Also, how much work/time goes into each block?