joshua/dash-docs
1
0
Fork 0
mirror of https://github.com/seigler/dash-docs synced 2025-07-28 18:26:13 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

P2P - Special tx payload size clarification

Browse source
This commit is contained in:
thephez 2018-12-17 16:59:47 -05:00
parent b32d7879b8
commit f5a3097aad
No known key found for this signature in database
GPG key ID: BBC8A06DBE236099
1 changed files with 3 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

4
_includes/devdoc/ref_transactions.md
View file

@ -414,7 +414,9 @@ flexibility to expand beyond the financial uses of classical transactions. DIP2
transactions modified classical transactions by: transactions modified classical transactions by:
1. Splitting the 32 bit `version` field into two 16 bit fields (`version` and `type`) 1. Splitting the 32 bit `version` field into two 16 bit fields (`version` and `type`)
2. Adding support for a generic extra payload following the `lock_time` field 2. Adding support for a generic extra payload following the `lock_time` field. The
maximum allowed size for a transaction version 3 extra payload is 10000 bytes
(`MAX_TX_EXTRA_PAYLOAD`).
Classical (financial) transactions have a `type` of 0 while special transactions Classical (financial) transactions have a `type` of 0 while special transactions
have a `type` defined in the DIP describing them. A list of current special have a `type` defined in the DIP describing them. A list of current special