BitcoinCash/CHIP-MilliSatoshi
1
Fork 0
Code Issues Pull Requests Releases Activity

Fix word

Browse Source
This commit is contained in:
TomZ
2024-03-11 10:56:11 +01:00
parent 692797c8c6
commit c3e75b8683
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
readme.md
+1 -1
View File
@@ -171,7 +171,7 @@ The rationale there is based on the total issued supply of sats, however. Which
It is fair to say that 1% of all coins will never be on a single input or output and as a result we could be mostly safe about adding an additional 2 digits for nearly free. It fits in the same 8 byte number, as long as no more than 1% of total issuable supply never ends up on a single UTXO. It is fair to say that 1% of all coins will never be on a single input or output and as a result we could be mostly safe about adding an additional 2 digits for nearly free. It fits in the same 8 byte number, as long as no more than 1% of total issuable supply never ends up on a single UTXO.
The owners personal opinion is that in the far future if this is deemed needed and safe, we can simply do it then. Same trick with a new transaction version, but 50 years from now. We'd even be able to reuse the opcode and simply add an extra enum value. The author's personal opinion is that in the far future if this is deemed needed and safe, we can simply do it then. Same trick with a new transaction version, but 50 years from now. We'd even be able to reuse the opcode and simply add an extra enum value.
## Why not wait? ## Why not wait?