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

Spellcheck

Browse Source
This commit is contained in:
TomZ
2024-03-11 13:50:18 +01:00
parent eb59f8c157
commit 8b80eb7865
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
readme.md
+4 -4
View File
@@ -254,7 +254,7 @@ goes into some detail on this topic.
The introspection opcodes should be able to dictate which of the two
representations of value they want to use. Notice, however, that such a
choice should only ever happen once per scriptsince changing
choice should only ever happen once per script since changing
mid-calculation is bound to cause problems.
We introduce `OP_SET_VALUE_MODE` a new opcode with code-point `0xTODO` that switches between Values with 8 digits behind the full unit and 11 digits.
@@ -271,11 +271,11 @@ quick overview of technical changes:
* TX version would tell parsers they need to decode the TX differently.
* OPcode would maintain past & future contracts consistent:
* if executed then OP_*VALUE introspection opcodes would return
milisats instead of sats (irrespective of TX version)
millisats instead of sats (irrespective of TX version)
* if not executed then OP_*VALUE introspection would return sats
irrespective of TX version, and if underlying prevout/output used
milisats then they are truncated e.g. returned value will be:
milisats / 1000, where / is integer division.
millisats then they are truncated e.g. returned value will be:
millisats / 1000, where / is integer division.
# Feedback & Reviews