Note
The catbuffer schemas repository defines how each transaction type should be serialized. In combination with the catbuffer-generators project, developers can generate builder classes for a given set of programming languages.
Serialization of a transaction.
Inlines:
| Property | Type | Description |
|---|---|---|
| max_fee | Amount | Maximum fee allowed to spend for the transaction. |
| deadline | Timestamp | Number of milliseconds elapsed since the creation of the nemesis block. If a transaction does not get included in a block before the deadline is reached, it is deleted. Deadlines are only allowed to lie up to 24 hours ahead. |
Binary layout for an embedded transaction header.
Inlines:
| Property | Type | Description |
|---|---|---|
| embeddedTransactionHeader_Reserved1 | uint32 | Reserved padding to align end of EmbeddedTransactionHeader on 8-byte boundary. |
Did you find what you were looking for? Give us your feedback.