diff options
| author | Luke Dashjr <luke-jr+git@utopios.org> | 2016-05-11 21:54:09 +0000 |
|---|---|---|
| committer | Luke Dashjr <luke-jr+git@utopios.org> | 2016-05-11 21:54:09 +0000 |
| commit | 5e6f3ba3bef783807191f8dccdf5bec1bcbfdabc (patch) | |
| tree | 53a24d555d5c6fcfae17e3894f7e056afa97d120 | |
| parent | 162e2e002568dc8f1b4a85180d903366f74f40c4 (diff) | |
| download | bips-5e6f3ba3bef783807191f8dccdf5bec1bcbfdabc.tar.xz | |
bip-0009: Remove n/a paragraph
| -rw-r--r-- | bip-0009.mediawiki | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/bip-0009.mediawiki b/bip-0009.mediawiki index 0e1d7bd..162b264 100644 --- a/bip-0009.mediawiki +++ b/bip-0009.mediawiki @@ -197,9 +197,6 @@ If a client does not understand a rule without the prefix, it may use it unmodif On the other hand, when this prefix is used, it indicates a more subtle change to the block structure or generation transaction; examples of this would be BIP 34 (because it modifies coinbase construction) and 141 (since it modifies the txid hashing and adds a commitment to the generation transaction). A client that does not understand a rule prefixed by '!' must not attempt to process the template, and must not attempt to use it for mining even unmodified. -Servers should only signal this mutation when they have verified a client behaving this way will not produce invalid blocks. -This includes verifying the client's supported rules (listed in the template request) are not lacking of a rule that would change serialisation. - ==Support for future changes== The mechanism described above is very generic, and variations are possible for future soft forks. Here are some ideas that can be taken into account. |