Strongly agree. My suggestion 2MB now, then 4MB in 2 years and 8MB in 4years then re-asses. (Similar to BIP 102)https://twitter.com/jgarzik/status/635857060626718720 …
-
-
@billbarhydt@adam3us@gavinandresen How fast should $4B assets stray into uncharted waters without good models of security there? -
@NickSzabo4@adam3us@gavinandresen slowly. But that's qualitative. Now translate that into the quantitative. -
@billbarhydt@adam3us@gavinandresen Without good models getting too quantitative is false precision.
End of conversation
New conversation -
-
-
@NickSzabo4@adam3us@gavinandresen agreed, might sound dumb but maybe incrementing by few kb per week is better then single big jump?? -
@billbarhydt BIP101 increases the limit a few bytes every block, no big increases -
@gavinandresen@billbarhydt BIP101 never stays in one place long enough to explore whether it's safe there: just keeps piling on risk. -
.
@NickSzabo4@gavinandresen Ɐ ε>0 ∃ ẟ>0 st risk(blocksize+ẟ, time_at_blocksize-ẟ)<ε. Finding ẟ & ε will be ½ art, ½ science; risk fn unknown
End of conversation
New conversation -
-
-
@NickSzabo4@billbarhydt@adam3us@gavinandresen Small incremental change is standard how to change large projects. Jumping and rushing not.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.