Bitcoin Hopes and Desires > 커뮤니티 카카오소프트 홈페이지 방문을 환영합니다.

본문 바로가기

커뮤니티

커뮤니티 HOME


Bitcoin Hopes and Desires

페이지 정보

작성자 Fanny 댓글 0건 조회 11회 작성일 24-08-29 11:44

본문

So now we know the whole technique of bitcoin functioning and the way Bitcoins can be utilized for making all kinds of actual transactions. Bitcoins are exchangeable for fiat forex through cryptocurrency exchanges and can be used to make purchases from merchants and retailers that settle for them. Greg Sanders: Yeah, if I can leap in. Mark Erhardt: So I’m questioning, one in all the issues that seems to jump out after i hear you talking about that is, what if one aspect keeps making updates however not concluding it? And we’ve all the time gone back and forth between these, as a result of we don’t know if we should always do a easier model first and anticipate later to do a much more advanced model, or if we must always simply leap to the more complicated model proper now. Because we’ve at all times been discussing the truth that asserting, youtu.be having the channel announcement level to a particular onchain output, was quite bad for privateness and that we may most likely do higher. So, these are issues that we’ve at all times been simply hand-wavy about how we'd do this in the future. Read More: Amid worth drops and elevated regulation, what’s the future of cryptocurrency?


But I don’t think we’ll mean you can have any sort of multiplier, as a result of one in all the other ideas was that you could additionally just announce some UTXOs that you simply own, with the proof that you just own them, with a complete worth of, for example, 2 bitcoin, and then that might grant you the ability to announce as much as X occasions that in channels with out having to level to any particular onchain output. I didn’t suppose it was too bad, but the one key difference here is that for the payment channels with penalties as at the moment designed, it’s necessitating that you just store these secret nonces perpetually till channel close. These charts are cardinal a part of the entire affair as with them traders are ready to predict the movement close to accuracy. But, understanding that the markets never shut is a helpful safeguard to have. If in case you have one other Lightning-like channel specification that you coded up or a custom channel type, you may also include that in this channel announcement and it'll simply work. That’s why we’re not doing that right now, and that’s why most people will just keep asserting the output that actually corresponds to the channel so that when it gets spent, folks truly notice it and can take away it from that graph and know that they can't route through that channel anymore.


I think we’re going to stick with a simple version, where you enable pointing to any type of output to pay to your channel. PTLC fixes that by making sure that as an alternative of using the preimage of a SHA256 hash and its hash, we’re going to make use of elliptic curve factors and their private keys. This could appear unnecessary provided that BIP32 already gives prolonged personal keys (xprvs) that can be shared between signing wallets. Maybe we can begin with t-bast. Can the channel keep open when the UTXO gets spent? And on the other hand, how do you make sure that the same UTXO shouldn't be reused for the announcement; and what occurs if that UTXO will get spent? So, will we should be keeping monitor of the UTXO really not being moved while it's the stand-in to have announced the channel? Mike Schmidt: The taproot and MuSig2 channel discussion somewhat leads into the updated channel announcement dialogue and the way gossip protocol would have to be upgraded with a view to support shifting to P2TR outputs. So, we want to change that, as a result of we want to allow taproot, which suggests allowing also input, particularly if we use MuSig2; we don’t need to reveal the inner keys.


And proper now, it’s going to make use of the identical cost hash with all these nodes, which means that if someone owns two of the nodes in the trail, they are learning data, and this is unhealthy for privateness. Right now, whenever you send a cost, this payment is going to go through a number of nodes on the community. Bastien Teinturier: Sure. So proper now, once we announced the channel on the network, we explicitly announced node IDs and the Bitcoin keys that are contained in the multisig 2-of-2, and other people verified that the output that we're referencing is definitely locked with the script hash of multisig 2-of-2 of those two keys, so you may only use it with scripts that actually comply with the format of Lightning channels with out taproot. Mike Schmidt: Murch or t-bast, some other feedback on taproot and MuSig2 channels? Mike Schmidt: Go ahead, Murch. Mike Schmidt: Next section from the Summit discussed PTLCs and redundant overpayments. Bastien Teinturier: Okay, so PTLCs are a change that's allowed by taproot and adaptor signatures.


댓글목록

등록된 댓글이 없습니다.