From: Prayank <prayank@tutanota.de>
To: Jeremy <jlrubin@mit.edu>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] [Bitcoin Advent Calendar] What's Smart about Smart Contracts
Date: Thu, 23 Dec 2021 10:42:02 +0100 (CET) [thread overview]
Message-ID: <MraenVQ--B-2@tutanota.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1812 bytes --]
Hi Jeremy,
> Here's the day 6 post: https://rubin.io/bitcoin/2021/12/03/advent-6/, the
topic is why smart contracts (in extended form) may be a critical precursor
to securing Bitcoin's future rather than something we should do after
making the base layer more robust.
There are few comparisons in this post and links that I consider misleading or incomplete. I had already tweeted this but such discussions are better archived here:
Difference between Bitcoin and Ethereum that is not mentioned on the website which should be considered while looking at fees: 1. Size of blocks added to chain everyday (600 MB) 2. Block limit (500 MB per 10 mins) 3. UTXO vs Account model 4. Failed transactions that pay fees (50k per day) 5. Will these fancy smart contracts work without nodes? No. Where are these nodes running? AWS and Infura has nice articles to highlight their importance 6. Who is paying the fees? Stablecoins, DEX, NFT platforms, CEX and VCs
There can be lot of other differences that affect the fee market including lot of users in Bitcoin obsessed with supply and hodling. Things that have changed in last few years: 1. Darknet markets using Monero 2. Stablecoins stopped using Omni and lot of alternatives exist right now 3. Most of the transactions are related to exchanges. They have started using their own tokens, less exchanges support layer 2 for Bitcoin and users are forced to withdraw some altcoin even if they need bitcoin. 4. Newbies are reading influencers like Elon Musk and happy with their doggy coins to get rich quick/rekt. 5. Bitcoin users or influencers declared DeFi a scam and even sidechains like Liquid, Rootstock do not qualify their purity tests. Projects like DLCs are still not used in any projects with good volume.
--
Prayank
A3B1 E430 2298 178F
[-- Attachment #2: Type: text/html, Size: 2410 bytes --]
next reply other threads:[~2021-12-23 9:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-23 9:42 Prayank [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-12-07 23:29 [bitcoin-dev] [Bitcoin Advent Calendar] What's Smart about Smart Contracts Jeremy
2021-12-08 0:32 ` ZmnSCPxj
2021-12-08 1:11 ` Jeremy
2021-12-08 23:23 ` ZmnSCPxj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=MraenVQ--B-2@tutanota.de \
--to=prayank@tutanota.de \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=jlrubin@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox