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
_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

Reply via email to