From: Erik Aronesty <erik@q32.com>
To: Billy Tetrud <billy.tetrud@gmail.com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Reducing block reward via soft fork
Date: Mon, 24 May 2021 17:55:14 -0400 [thread overview]
Message-ID: <CAJowKg+MX=Tt5HBL4HXwTP1R191qqiQ23qJ2Ot0yr4M0hEcU1g@mail.gmail.com> (raw)
In-Reply-To: <CAGpPWDYJHP1WsJA9Rymb3GwMomCipVV7UV_eSVb_g-DbBkw32w@mail.gmail.com>
> > I don't think 99% of transactions need that level of security
> Well you can't get security for the 1% of transactions that need it without giving that security to all transactions on the chain. Also, the blockchain security created by miners isn't really a per transaction thing anyway. An attack would affect all bitcoins regardless of what transactions they do or do not take part in.
yes, and this is what lightning is for. to secure the 99% of
transactions that *don't* need billions of dollars and years in lead
time of security.
at current prices, and even with the current known issues, lightning
is perfectly acceptable for small transactions.
next prev parent reply other threads:[~2021-05-24 21:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-23 1:00 [bitcoin-dev] Reducing block reward via soft fork James Lu
2021-05-23 10:42 ` Anton Ragin
[not found] ` <CANQHGB2pD57cZzcuTqr25Pg-Bvon_=G=_5901to2esrcumk-GA@mail.gmail.com>
2021-05-23 14:40 ` [bitcoin-dev] Fwd: " James Lu
2021-05-23 11:26 ` [bitcoin-dev] " ZmnSCPxj
2021-05-23 12:08 ` Karl
2021-05-23 13:35 ` ZmnSCPxj
2021-05-23 19:44 ` Karl
2021-05-24 20:28 ` Billy Tetrud
2021-05-24 21:55 ` Erik Aronesty [this message]
2021-05-25 0:55 ` Karl
2021-05-25 8:01 ` Billy Tetrud
2021-05-25 8:35 ` Jorge Timón
2021-05-25 8:53 ` Melvin Carvalho
2021-05-25 19:40 ` Billy Tetrud
2021-05-24 22:03 ` Phuoc Do
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='CAJowKg+MX=Tt5HBL4HXwTP1R191qqiQ23qJ2Ot0yr4M0hEcU1g@mail.gmail.com' \
--to=erik@q32.com \
--cc=billy.tetrud@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/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