TxCustoms
- custom_json
Name | Description |
tid | less than 32 characters long identifier |
json | a proper utf8 / JSON string |
required_posting_auths | list of accounts who signed the transaction using their posting key |
required_auths | list of accounts who signed the transaction using their active key |
required_posting_auth | the first value from required_posting_auths |
required_auth | the first value from required_auths |
The
custom_json
operation provides a generic way to add higher-level protocols on top of witness consensus. This operation is designed to be human-readable/developer-friendly. There is no validation for this operation other than that the required auths are valid.required_posting_auths
and required_auths
are arrays. If more than one authority has been included in the operation, the required_posting_auth
and required_auth
columns will contain the first value from their respective arraysLast modified 10mo ago