Maxim Orlovsky Profile picture
Jul 8, 2022 9 tweets 3 min read Read on X
An analysis which problems #Bitcoin solves as of today, in the order of adoption 🧵

1. instrument of Investment: long-term (5+ yrs) high-risk high-reward investing in censorship-resistant & trustless way: anybody can buy it (=short fiat/gold/assets) as a “forex” market bet

2. Long-term (5+ yrs) store of value (#SoV) with the same risk profile as gold, but cheaper vaulting and better unconfiscatability (still high chances of loosing due to vault mismanagement).

#MoE use-cases which are seriously undermined by bitcoin price volatility:

3. Simple payments for unbanked (paying with BTC is simpler than opening account + costs less and sometimes faster if done with LN).
4. International private remittances - frequently simple & cheaper

#MoE use-cases undermined by both price volatility & poor privacy (they cant’t run LN due to liquidity problems):

5. International capital movements.
6. Dark market deals (benefits from #Bitcoin PoW extreme censorship-resistant properties).

No 3-4 are better solved by stablecoins. These cases usually do not require censorship resistance, and this leaks users to non-bitcoin ecosystems.

No 5-6 frequently prefer more private alternatives like Monero as MoE - another adoption leak here.

Potential cases include programability and micropayments, but bitcoin is very poor on the first (leaking users again) and while the second works well with LN, it does not have the market yet.

#RGB fixes many #Bitcoin adoption issues. First, stable coins can work on LN in bitcoin ecosystem, much cheaper than anywhere else. We’ve for no.3-4 unlocked. Second, we get onchain privacy exceeding Monero - 5-6 unlocked again.

Finally we have programmability of full smart contracts - but scalable with LN. Again, beating all other smart contract platforms - in scalability, privacy & censorship-resistance.

#RGB - client-side-validation and LN combined - fixes #Bitcoin, such that now it will be able to fix the rest.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Maxim Orlovsky

Maxim Orlovsky Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @dr_orlovsky

Nov 7, 2021
Continuing #Taproot series.

#2, pt 1/6. Taproot introduces new “common signature function” for signing tx with BIP-340 Schnorr signature. This function may be re-used in a future soft-forks (simplifying implementation/code review). It provides two ways of changing signing algo:
#2, pt 2/6. First, for incremental updates, where we do not change the order of data signed, but append new data to the end, we can use so-called *ext flag* - a value in range 0-127 passed as a parameter to the common signing function.
#2, pt 3/6. Tapscript (BIP-342) already uses this mechanism to add to the signed data commitment to a specific key serialization algo (which may change with future updates), script branch version & code (via tapleaf_hash) and code separator.
Read 6 tweets
Nov 6, 2021
#Taproot is coming. Each day before taproot activation I will publish mostly unknown tech insights into what taproot brings.

#1, pt 1/5. Taproot introduces new versioning for bitcoin script (as many know). But do you know that each taproot branch may have a different script?
#1, pt 2/5. Moreover, taproot separates script versioning from witness versioning. I.e. in witness v5 we may have something like three script versions - or today v1 P2TR output may have a script condition for future versions of script
#1, pt 3/5. The new script versioning system is named *leaf version*. Current leaf version is 0xC0, meaning BIP-341, aka “Tapscript”. Yes, taproot can work not only with tapscript/BIP-341, but other future standards!
Read 5 tweets
Mar 9, 2021
1/ With #RGB one needs to change a mindset from “ethereum smart contracts” to normal understanding of what smart contract is. And first, this is a _contract_ between parties. Well-defined parties. Not some record in a global registry, like this concept was distorted in ethereum.
2/ RGB is _bearer rights_ smart contracts, returning the world what was lost of the true free market because of regulations and requirements for centralized censorhip with global registries (even when they are on blockchain, decentralization does not make them less global).
3/ Next, after shifting the point of view, you understand that as an owner of something you are responsible for your own self to keep the data required for securing and ensuring your actual ownership
Read 13 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

:(