< bitcoin-git> [bitcoin] Empact opened pull request #13525: Report reason inputs are nonstandard from AreInputsStandard (master...are-inputs-standard-reason) https://github.com/bitcoin/bitcoin/pull/13525
< SkyHawk> I'm looking for work anyone hiring?
< MANDON> HELLOW
< MANDON> LS
< hardik_> Hello
< hardik_> I want exchange BTC to NEO by using API (not manually).
< hardik_> Is it possible ?
< zeib> hu
< zeib> hi
< zeib> i sent bitcoins to bitcoin core while it was syncing and i can't see my bitcoin and i can't sync please tell me how to get my bitcoins back
< zeib> i sent bitcoins to bitcoin core while it was syncing and i can't see my bitcoin and i can't sync please tell me how to get my bitcoins back
< zeib> please help
< zeib> help me
< zeib> i sent bitcoins to bitcoin core while it was syncing and i can't see my bitcoin and i can't sync please tell me how to get my bitcoins back
< mryandao> zeib: #bitcoin
< sipa> jonasschnelli: for correcting 7 characters, the checksum can be 26 characters when the data in it is restricted to 341 characters (so 315 data characters, 1575 data bits, or about 196 bytes of data)
< sipa> for length 1023, 27 characters are needed
< sipa> jonasschnelli: looking at it differently, and aiming for certain % of correctable characters (for 512 bits of data):
< sipa> * with 26 checksum characters you can correct 7 (5%)
< sipa> * with 62 checksum characters you can correct 17 (10%)
< sipa> * with 116 checksum characters you can correct 33 (15%)
< sipa> * with 195 checksum characters you can correct 60 (20%)
< sipa> or put otherwise: by increasing the total string length by 25% you can correct 5%, by increasing 60% you can correct 10%, by increasing 113% you can correct 15%, by increasing 189% you can correct 20%
< sipa> (the nonlinearity is because corrections include possible errors inside the checksum characters themselves)
< jonasschnelli> sipa: Thanks (also thanks for the ML post)
< jonasschnelli> I think 26 (5%), 62 (10%) and 195 (20%) would be a possible way to flex Bech32X
< jonasschnelli> I think 189% increase for 20% robustness is acceptable.
< sipa> so such a code could at most store 730 bits of information
< bitcoin-git> [bitcoin] MarcoFalke opened pull request #13527: policy: Remove promiscuousmempoolflags (master...Mf1806-NoPromiscuousmempool) https://github.com/bitcoin/bitcoin/pull/13527
< bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/000abbb6b074...3a4549301ab2
< bitcoin-git> bitcoin/master fa1eac9 MarcoFalke: [qa] mininode: Expose connection state through is_connected
< bitcoin-git> bitcoin/master 3a45493 MarcoFalke: Merge #13512: [qa] mininode: Expose connection state through is_connected...
< bitcoin-git> [bitcoin] MarcoFalke closed pull request #13512: [qa] mininode: Expose connection state through is_connected (master...Mf1806-qaMininodeState) https://github.com/bitcoin/bitcoin/pull/13512