• 목록
• 답변
• 글쓰기
• 게시판 리스트 옵션
  • 수정
  • 삭제

Bitcoin shed a fifth of its value on Saturday as a combination of profit-taking and macro-economic concerns triggered nearly a billion dollars worth of selling across cryptocurrencies. Cryptocurrency Investment Funds Like 3AC, Celsius, and Others Wasted Nearly $6 Billion. BTC volume in the last 24 hours reached approximately $14.59 billion, a rise of 66.55%. Giottus Crypto Platform CEO Vikram Subburaj said, "Breaching key resistance at $32,400 will be the eventual target before a sustained rally is possible." Meanwhile, the global cryptocurrency market cap hit around $1.19tn, a rise of 1.45% in the last 24 hours, while the market cap of Bitcoin was at $593bn, and its dominance was sitting at 49.88%, a decline of 0.11% over the day, according to CoinMarketCap. 3. Select the cryptocurrency you want to deposit, such as BNB. If you want to get into trading, put aside some extra money when you have it, find a coin you'd be into trading, and buy some to play with. This is the main issue here, in my opinion, where you’re basically holding on extra key material. A sidechain is basically a separate blockchain connected to the main chain.

The main question that we had during the Summit is that there’s work when the current proposal spends the MuSig2 output for both commitment transactions and splices and mutual closes, which means that we have to manage nonce-state, MuSig2 nonce-state in many places, and it’s potentially dangerous because managing those nonces correctly is really important for security. For LN-Symmetry, I didn’t have to pull this around because there’s no penalties, so I just, in memory, hold these nonces and then complete signatures just in time. I didn’t think it was too bad, but the one key difference here is that for the payment channels with penalties as currently designed, it’s necessitating that you store these secret nonces forever until channel close. Mark Erhardt: Oh, maybe one. Bastien Teinturier: Yeah, I think also one of the reasons we don’t see pinning is that really, it’s harder to pin right now and make it work your while, because right now, commitment transactions do pay some fees. So, I would talk to Bastien quite a bit, I would talk to the statechains people. So, it’s really hard to figure out where to draw the line here. We had a great podcast out in the Chaincode podcast, where we talked to Elle Mouton and Oliver Gugger about simple taproot channels, which basically is this proposal.

Mike Schmidt: Murch or t-bast, any other comments on taproot and MuSig2 channels? All right. The second segment of the LN Summit notes that we highlighted was Taproot and MuSig2 channels. And this way, you don’t have to exchange nonces for the MuSig2 output and only the mutual closing and maybe the splices, probably the splices as well, would use the MuSig2 spend path. This way, it’s indistinguishable from any other taproot output, whereas right now, funding outputs are witness script hash of 2-of-2 multisig, which is really easy to distinguish onchain. So we’re only focusing on that funding output for now. I’m making sure that whatever we’re building would actually be useful by these projects, I think that’s very important. And I’m curious how Lightning engineers are thinking about taproot and MuSig2 related channels and how the audience should think about their nearer term uses in Lightning, in contrast to something that I think a lot of Bitcoin hopefuls are thinking about, which is Point Time Locked Contracts (PTLCs) involving schnorr signatures and adaptor signatures. Bastien Teinturier: Sure. So right now, when we announced the channel on the network, we explicitly announced node IDs and the Bitcoin keys that are inside the multisig 2-of-2, and people verified that the output that we are referencing is actually locked with the script hash of multisig 2-of-2 of those two keys, so you can only use it with scripts that really follow the format of Lightning channels without taproot.

I don’t know, maybe Bastien has another opinion on that. Bastien Teinturier: Okay, so for now, the first thing we are doing with taproot is just moving the funding transactions, the channel output to use the MuSig2 taproot output. And there was Youtu published an article idea that instead of using the MuSig2 output, the commitment transaction, actually, the funding output would have both a keypath spend that would be MuSig2, but also a scriptpath spend that would use a plain, normal 2-of-2 multisig, so that all the commitment transactions would use the scriptpath spend. So, just moving the funding transactions to use MuSig2 already has a very nice benefit for all users, and it’s a good way to start experimenting with taproot with MuSig2 before moving on to PTLC. 500 out of 500 of the 'Fortune 500' corporations use .Com, and all of the world's best salespeople and marketers; they aren’t going anywhere. And right now, it’s going to use the same payment hash with all these nodes, which means that if someone owns two of the nodes in the path, they are learning information, and this is bad for privacy.