default for datacarriersize is 40, not 80

billdirks · Mar 5, 2015 · 14a25a6 · 14a25a6
1 parent 957efa4
commit 14a25a6
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/ch05.asciidoc b/ch05.asciidoc
@@ -473,7 +473,7 @@ Keep in mind that there is no "unlocking script" that corresponds to +OP_RETURN+
 
 A standard transaction (one that conforms to the +isStandard()+ checks) can have only one +OP_RETURN+ output. However, a single +OP_RETURN+ output can be combined in a transaction with outputs of any other type. 
 
-Two new command-line options have been added in Bitcoin Core as of version 0.10. The option +datacarrier+ controls relay and mining of OP_RETURN transactions, with the default set to "1" to allow them. The option +datacarriersize+ takes a numeric argument specifying the maximum size in bytes of the OP_RETURN data, 80 bytes by default.
+Two new command-line options have been added in Bitcoin Core as of version 0.10. The option +datacarrier+ controls relay and mining of OP_RETURN transactions, with the default set to "1" to allow them. The option +datacarriersize+ takes a numeric argument specifying the maximum size in bytes of the OP_RETURN data, 40 bytes by default.
 
 [NOTE]
 ====