From: Erik Aronesty <erik@q32•com>
To: Peter <dizzle@pointbiz•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Security problems with relying on transaction fees for security
Date: Tue, 12 Jul 2022 07:57:40 -0400 [thread overview]
Message-ID: <CAJowKgKM7B6UY-dNNTym7GAPS_dZ0dnMUPFJe-bSssKqt=zL5Q@mail.gmail.com> (raw)
In-Reply-To: <fJguYsLelZiEN8g25KZONgNp8qHvY3UkkEE7uUtI6O7MFgaNcKBVc5l5gCUlFSxQLE5Hzu3QobS8ZE4pzmTVqSG8wU5Y0Q3jHL3X6Wsye4c=@pointbiz.com>
[-- Attachment #1: Type: text/plain, Size: 805 bytes --]
>
> we can expect mining to transition to a public service from the current
> for-profit business model
>
I get it now
Game theory would predict all of the major players mining in the future
will be large holders
If you're holding a hundred Bitcoin you should take one, sell it for mining
equipment and use it to ensure the rest is stable
I guess that's perfectly reasonable
Yeah I'm on board with the idea that this is a non-issue
Interested parties will continue to maintain the security of the chain with
the same basic game theoretic stuff
Bitcoin doesn't need a security budget
Existing holders have the ability the means and the incentive to secure
their funds
Probably the only thing Bitcoiners should do is to advertise this rather
than to make it some sort of secret
>
[-- Attachment #2: Type: text/html, Size: 1999 bytes --]
next prev parent reply other threads:[~2022-07-12 11:57 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 3:56 Peter
2022-07-12 11:57 ` Erik Aronesty [this message]
2022-07-12 15:08 ` Peter
2022-07-12 17:46 ` Ryan Grant
[not found] <mailman.82083.1657699581.8511.bitcoin-dev@lists.linuxfoundation.org>
2022-07-13 9:43 ` John Tromp
2022-07-13 11:56 ` John Tromp
2022-07-13 12:11 ` Gino Pinuto
2022-07-13 13:29 ` Manuel Costa
2022-07-14 9:33 ` vjudeu
2022-07-14 9:57 ` Erik Aronesty
2022-07-14 11:42 ` Gino Pinuto
2022-07-14 16:01 ` Erik Aronesty
2022-07-14 16:27 ` Manuel Costa
2022-07-15 6:03 ` vjudeu
-- strict thread matches above, loose matches on Subject: below --
2022-07-11 18:12 Bram Cohen
2022-07-11 18:38 ` micaroni
2022-07-11 18:43 ` Erik Aronesty
2022-07-11 19:45 ` vjudeu
2022-07-11 20:35 ` Russell O'Connor
2022-07-11 20:52 ` Erik Aronesty
2022-07-11 21:36 ` Peter Todd
2022-07-11 21:56 ` Peter Todd
2022-07-12 0:21 ` Russell O'Connor
2022-07-12 0:37 ` Peter Todd
2022-07-14 0:54 ` Anthony Towns
2022-07-11 21:18 ` Pox
2022-07-11 21:53 ` Peter Todd
2022-07-12 2:47 ` Bram Cohen
2022-07-11 22:19 ` James MacWhyte
2022-07-11 22:26 ` Peter Todd
2022-07-12 0:01 ` James MacWhyte
2022-07-12 0:31 ` Peter Todd
2022-07-13 0:38 ` Tom Harding
2022-07-13 12:18 ` Erik Aronesty
2022-07-11 23:29 ` Anthony Towns
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='CAJowKgKM7B6UY-dNNTym7GAPS_dZ0dnMUPFJe-bSssKqt=zL5Q@mail.gmail.com' \
--to=erik@q32$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=dizzle@pointbiz$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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