Finally, there is a link to the Binance peer-to-peer trading platform, where you are able to make deals directly with other Binance users to exchange cryptocurrencies and pay using your bank account or a number of online e-wallet services. You explored BNB Burn and what are the factors to consider before investing in Binance. You can now start to deposit your cryptocurrency coins or tokens into your Binance account. You’ll hear the expression “old soul” now and again to describe someone who seems like they’ve maybe lived through all of this before and have a wisdom and patience that is beyond their apparent years. If the new opcode, for example, removed an element of the stack, nodes that followed the new rules per the soft fork, well, in that case hard fork, would have a different stack after executing the opcode than old nodes, because old nodes would not interact with the stack at all. Mike Schmidt: Next question from the Stack Exchange is, “Why are there 17 native segwit versions? All the transactions are recorded into blocks, and the transactions remain transparent. He stressed that without effective scaling infrastructure to make transactions affordable, Ethereum essentially “fails”. There is a complete record of all transactions on the bitcoin network and everyone can view it.
Why are there 17 native segwit versions? This would be a huge advantage for larger multisig constructions which are very expensive and large right now in Bitcoin. But as well, I mean, the biggest one is requirements for something like anyprevout, right? Mike Schmidt: Okay, Murch, so 1,500 hours is too much for you, but Poelstra mentioned in his answer, “If we could reduce this to one month, 160 hours of work, I think this would be a reasonable thing to do for a certain kind of super-paranoid Bitcoin user who only transacted every several years”. ” And Andrew Poelstra answered this, providing some background, some other hand-calculation verification techniques that he’s used previously, including Codex32, and he estimates that it would take, even using some tricks and some helper lookup tables, that it would take about 1,500 hours to do that, 36 weeks of a full-time job, even using some of those tricks that he outlined in his answer. Mark Erhardt: Yeah, I was also surprised on how much Andrew had to write about that, but yeah, it turns out that humans are not computers, and while computers are good at some things, they are not great at other things, and while humans are good at some things, they’re not very good at calculating hashes and doing elliptic curve math on paper.
And on trampoline, I think that, again, people expressed interest in implementing trampoline, but I’m still waiting to see if this actually catches on, because many people are interested, but it still doesn’t seem to meet the bar for implementation in the short term. NOPS are not allowed to change the stack because previously no operation meant that it does nothing. But the current LN as of today is 100% penalty-based, and it doesn’t seem like it’s going to change much. So, yeah, it’s just because we can express the number 0 through 16 with a single byte, and that’s why we have 17 native segwit versions defined in, I think it’s BIP141, yeah. So, from that perspective, it’s kind of done. So, this could sound like, I guess from a priority perspective, I don’t think it’s quite there. So, it turns out that we have constants for some numbers in Bitcoin script, and there are single-byte opcodes that can express these constants. And so, yeah, this, it just stuck out as odd to me how this is not a power of 2, as almost all numbers that appear in the context of any computer protocols are.
So, having an output that includes the 0 CSV forces replaceability. CSV force the spending transaction to signal BIP125 replaceability? So, by requiring a 0 CSV, you do force replaceability even though there is no wait time, because a wait time of 0 means that it can be included in the same block. So, I don’t know if there’s much to talk about there. So, the stack has to be the same before and after, or it wouldn’t be a soft fork. We have Stack Exchange questions we’re going to go through. And then async payments and trampoline, this is a longer-term effort, because it requires a lot of things that we’re working on but are not complete yet, before we can actually really do async payments. The remaining piece would be things like the mempool policy work, which we’re continuing to work on as a necessary precondition. Otherwise, if you have things you’ve got to do, got to drop, understandable. And now with taproot, we also have a v1 witness program, which is also 32 bytes. There’s the P2WSH program, which is preceded by a v0 and then a 32-byte witness program. There’s the P2WPKH witness program, which is a v0 witness program of 20 bytes.
