mirror of
https://github.com/seigler/dash-docs
synced 2025-07-27 01:36:13 +00:00
Several Corrections & Clarifications Suggested On IRC
**Suggested by @cbeams:** _includes/ref_block_chain.md: * Mention that coinbase is the first transaction in a block. **Suggested by @gmaxwell:** _includes/ref_core_rpcs-abcdefg.md: * Mention that you need to unlock your wallet when you run out of keys in the keypool. * Remove erroneous assertion that txindex=1 would allow `getreceivedbyaddress` to check balances of addresses not belonging to this wallet. _includes/ref_transactions.md: * Clarify that OP_RETURN scripts aren't usually executed because they always return false. en/developer-reference.md * Add a warning about using block chain or mempool data in executable context.
This commit is contained in:
parent
c1e61199a1
commit
68cd5b6ff9
4 changed files with 17 additions and 7 deletions
|
@ -47,9 +47,9 @@ The op codes used in standard transactions are,
|
|||
error in the Bitcoin Core implementation. This value is not used, so
|
||||
scriptSigs prefix the signatures with a single OP_0 (0x00).
|
||||
|
||||
* [`OP_RETURN`][op_return]{:#term-op-return}{:.term} terminates the script in failure. However, this will not
|
||||
invalidate a null data transaction which contains no more than 40
|
||||
bytes following `OP_RETURN` no more than once per transaction.
|
||||
* [`OP_RETURN`][op_return]{:#term-op-return}{:.term} terminates the script in failure,
|
||||
rendering the output unspendable and allowing a miner to claim the
|
||||
satoshis sent to that OP_RETURN output as an additional transaction fee.
|
||||
|
||||
A complete list of OP codes can be found on the Bitcoin Wiki [Script
|
||||
Page][wiki script], with an authoritative list in the `opcodetype` enum
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue