From: martl.chris@proton•me
To: "bitcoin-dev@lists•linuxfoundation.org"
<bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Concern about "Inscriptions"
Date: Fri, 18 Aug 2023 20:43:13 +0000 [thread overview]
Message-ID: <ri0Obd5AcQ2or-gzsFQVqblzEJK7KtEsV3U-bItN8ZsRD47PvurPyR5Vl3CH0Xs-ndSWSxlaiQJ0xvbduTnwwD4dMtOxp-4MMCUyqBCbuZE=@proton.me> (raw)
[-- Attachment #1: Type: text/plain, Size: 1997 bytes --]
It is already more than a half year since the probably mayor Bitcoin script exploit started.
These exploits are nothing new in the Bitcoin history and mostly are due to the loose flexibility of the system in regards of processing predicatives (Bitcoin script). The very first mayor bug; if you wish, vulnerability, was the CVE-2010-5141, which still engages us without end even after 14 years.
Subsequent Bitcoin historical events let to build more “improvements” upon this wobbly basis exposing even more ground for exploits.
As long as this loose flexibility is not modified in a way its exposure for exploits is eliminated remains nothing else than to pursue other strategies; and ones which are compatible with the current status quo and furthermore, with a permission-less system.
Here a strategy proposal:
Let’s name it: #Ordisrespector and #Ordislow.
Why #Ordisrespector and #Ordislow are compatible with a permission-less system.
#Ordisrespector gives the option to a regular Bitcoin node operator to opt-in or not to a self-defense of his/her storage property (and thus of his/her integrity); by giving a signal of dissatisfaction with the current affairs of aggression via insertion of arbitrary data into the witness structure. This dissatisfaction signal is manifested by not taking into the mempool and relaying transactions with inserted arbitrary data in the witness structure.
#Ordislow gives the option to a regular Bitcoin node operator to opt-in or not to a self-defense of his/her storage property (and thus of his/her integrity); by increasing the coercion cost of mining-entities relative to the cooperation cost of mining-entities due to the current affairs of aggression via insertion of arbitrary data into the witness structure. This coercion cost increment is manifested by not propagating a found block, unless a configurable or maximum delay has elapsed, which contains at least a transaction with inserted arbitrary data in the witness structure.
Chris
[-- Attachment #2: Type: text/html, Size: 7151 bytes --]
next reply other threads:[~2023-08-18 20:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 20:43 martl.chris [this message]
2023-08-21 14:47 ` Russell O'Connor
2023-08-21 14:58 ` rot13maxi
2023-08-22 5:15 ` martl.chris
-- strict thread matches above, loose matches on Subject: below --
2023-09-06 8:00 vjudeu
2023-09-03 16:01 vjudeu
2023-09-05 17:49 ` Peter Todd
[not found] <mailman.11.1692705603.26941.bitcoin-dev@lists.linuxfoundation.org>
2023-08-22 14:18 ` GamedevAlice
[not found] <mailman.134025.1692632811.956.bitcoin-dev@lists.linuxfoundation.org>
2023-08-21 16:28 ` John Tromp
2023-08-21 22:34 ` symphonicbtc
2023-08-23 17:34 ` Erik Aronesty
2023-08-03 13:33 GamedevAlice
2023-08-03 16:03 ` leohaf
2023-08-02 11:07 GamedevAlice
2023-08-02 15:46 ` Luke Dashjr
2023-07-27 19:03 Léo Haf
2023-07-30 18:34 ` rot13maxi
2023-07-27 5:10 vjudeu
2023-07-26 5:30 vjudeu
2023-07-26 9:46 ` leohaf
2023-07-25 14:11 leohaf
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='ri0Obd5AcQ2or-gzsFQVqblzEJK7KtEsV3U-bItN8ZsRD47PvurPyR5Vl3CH0Xs-ndSWSxlaiQJ0xvbduTnwwD4dMtOxp-4MMCUyqBCbuZE=@proton.me' \
--to=martl.chris@proton$(echo .)me \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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