From: Prayank <prayank@tutanota.de>
To: erik@q32.com
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Drivechain: BIP 300 and 301
Date: Fri, 3 Sep 2021 12:07:55 +0200 (CEST) [thread overview]
Message-ID: <Mif7Fdk--3-2@tutanota.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 401 bytes --]
> of course stacks can do this even without drivechain, so not sure whatwe're hiding from there
Stacks is not a Bitcoin sidechain IMO. It has its own native token which isn't pegged to BTC. Premined. It uses Bitcoin as a storage and broadcast medium for recording all blocks. Marketing with lot of misinformation. None of these things really help Bitcoin.
--
Prayank
A3B1 E430 2298 178F
[-- Attachment #2: Type: text/html, Size: 671 bytes --]
next reply other threads:[~2021-09-03 10:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 10:07 Prayank [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-09-02 17:11 [bitcoin-dev] Drivechain: BIP 300 and 301 Prayank
2021-09-02 20:20 ` Erik Aronesty
2021-09-02 21:02 ` ZmnSCPxj
2021-09-03 9:47 ` Prayank
2021-09-07 9:37 ` 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=Mif7Fdk--3-2@tutanota.de \
--to=prayank@tutanota.de \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=erik@q32.com \
/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