diff options
| -rw-r--r-- | bip-0085.mediawiki | 2 | ||||
| -rw-r--r-- | bip-0118.mediawiki | 2 | ||||
| -rw-r--r-- | bip-0174.mediawiki | 6 |
3 files changed, 5 insertions, 5 deletions
diff --git a/bip-0085.mediawiki b/bip-0085.mediawiki index 182404f..efbc268 100644 --- a/bip-0085.mediawiki +++ b/bip-0085.mediawiki @@ -102,6 +102,8 @@ OUTPUT * Coldcard Firmware: [https://github.com/Coldcard/firmware/pull/39] +* Ian Coleman's Mnemonic Code Converter: [https://github.com/iancoleman/bip39] and [https://iancoleman.io/bip39/] + ==Applications== The Application number defines how entropy will be used post processing. Some basic examples follow: diff --git a/bip-0118.mediawiki b/bip-0118.mediawiki index 1b2f27c..afbfde6 100644 --- a/bip-0118.mediawiki +++ b/bip-0118.mediawiki @@ -92,7 +92,7 @@ Any participant can take a transaction and rewrite it by changing the hash reference to the previous output, without invalidating the signatures. This allows transactions to be bound to any output that matches the -value committed to in the <tt>witness</tt> and whose <tt>witnessProgram</tt>, +value committed to in the signature and whose <tt>witnessProgram</tt>, combined with the spending transaction's <tt>witness</tt> returns <tt>true</tt>. Previously, all information in the transaction was committed in the diff --git a/bip-0174.mediawiki b/bip-0174.mediawiki index 8551d3c..9434ce6 100644 --- a/bip-0174.mediawiki +++ b/bip-0174.mediawiki @@ -74,13 +74,11 @@ Where: : Magic bytes which are ASCII for psbt <ref>'''Why use 4 bytes for psbt?''' The transaction format needed to start with a 5 byte header which uniquely identifies it. The first bytes were chosen to be the ASCII for psbt because that stands for -Partially Signed Bitcoin Transaction. </ref> followed by a separator of <tt>0xFF</tt> -<ref>'''Why Use a separator after the magic bytes?''' The separator +Partially Signed Bitcoin Transaction. </ref> followed by a separator of <tt>0xFF</tt><ref>'''Why Use a separator after the magic bytes?''' The separator is part of the 5 byte header for PSBT. This byte is a separator of <tt>0xff</tt> because this will cause any non-PSBT unserializer to fail to properly unserialize the PSBT as a normal transaction. Likewise, since the 5 byte header is fixed, no transaction -in the non-PSBT format will be able to be unserialized by a PSBT unserializer.</ref>. This integer must be serialized -in most significant byte order. +in the non-PSBT format will be able to be unserialized by a PSBT unserializer.</ref>. This integer must be serialized in most significant byte order. The currently defined global types are as follows: |