Large-scale consensus screenups suggest disabling 64-byte transaction consensus for a variety of reasons. They have been non-standard for years and do not seem to serve a useful purpose.
In practice, even such transactions do not have a risk of forfeiture, as such transactions can be comfortable with different sizes. It was useful. I’m trying to understand this aspect better.
I was given UTXO A
already exists or just mined under current consensus rules (e.g. through non-standard transactions).
A 64-byte transaction is given T
It spends it (non-standard, by definition).
Without access to the secrets used to generate them (if any) T
(Private key, hash pre-image, etc.)
Is it possible to change it all the time? T
Consensus to effective transactions T'
It will cost A
?
Furthermore, if you understand it correctly, it is not possible in a 64-byte transaction. T
Send coins to destination B
This is a secure (i.e. >=20 bytes) public key (hash).
Anyway, for everything B
do you have malate? T'
It will be saved B
(You can still spend at least with private keys b
)?
If the latter is too difficult to prove, you can show it T
You can detour the coins away covered by attackers B
.
Discover more from Earlybirds Invest
Subscribe to get the latest posts sent to your email.