Libre (@libredotorg) header
Libre (@libredotorg) profile picture

Keep your Bitcoin, get some $ or Loan some $ vs pristine Bitcoin collateral

Bitcoin
Joined January 2024
Photo by Libre (@libredotorg)Photo by Libre (@libredotorg)Photo by Libre (@libredotorg)Photo by Libre (@libredotorg)Photo by Libre (@libredotorg)Photo by Libre (@libredotorg)Photo by Libre (@libredotorg)Photo by Libre (@libredotorg)Photo by Libre (@libredotorg)Photo by Libre (@libredotorg)
You really only need 2 coins - USD to pay for things. - BTC to save.
182
126
21
1,869
92,856
Deep dive by Benobi on the intrinsic security or "Real L2"s vs Sidechains / Federated approaches to Scaling Bitcoin. From what I saw in Dubai, and per @DavidFBailey -- lots of hyper-activity here.
Bitcoin L2s have 2 levels of security: It’s important to understand how each solution deals with these 2 levels. Level 1 is the consensus / management of the “database” or chain. Where does the balances of users live and who can alter those? If it’s a database living on one computer that an admin can change, well that’s really easy to cheat. This is even true for an orderbook on a “decentralized exchange” - like the one I tested yesterday. Level 2 how are the reserves managed? What can cause a release of coins? What scenarios are there where the native asset gets depleted? For example - if the BTC is held in a single signature wallet on a bridge, that’s dangerous! Someone is going to say “but oh single sig could use MPC sharding” - and to that I would say that you still have the risks of how that key was generated and distributed in some sort of cryptographic ceremonial dance that could also make it very insecure. Now bridges can also use multisig - but that’s also not “trustless” because it ultimately relies on validators that *could* collude to steal coins. This is why zero-knowledge “bridge-less” / “trustless” is the holy grail for BTC. The way this works in theory is that a taproot script with “spend conditions” control how that a Bitcoin UTXO can be spent. So the trust lies in the production of a cryptographic proof from the first level - consensus/database. An example of this is “optimistic rollups” such as Arbitrum / ETH which use something called fraud proofs in order to keep participants in the network honest. There is a "challenge period" for these proofs to keep network participants honest. No one has figured out how to do this on Bitcoin yet!! But someone will likely figure this out in the next 12 months. We will have a “hello world” version of a zkBTC proof. @L2Ordinals and BitVM are interesting theories on ways that proofs could be implemented on BTC. It’s all theoretical still. I’m tracking this topic very closely now and I’ll continue testing L2s on video daily.
3
2
30
18,225