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.
Receipts provide proof for every state change not retrievable from the block.
Inlines:
Property | Type | Description |
---|---|---|
version | uint16 | Receipt version. |
type | ReceiptType | Receipt type. |
The invisible state change triggered a mosaic transfer.
Inlines:
Property | Type | Description |
---|---|---|
mosaic | Mosaic | Mosaic transferred. |
senderAddress | Address | Address of the sender. |
recipientAddress | Address | Address of the recipient. |
The invisible state change changed an account balance.
Inlines:
Property | Type | Description |
---|---|---|
mosaic | Mosaic | Mosaic increased or decreased. |
targetAddress | Address | Address of the target account. |
An mosaic expired.
Inlines:
Property | Type | Description |
---|---|---|
artifactId | MosaicId | Mosaic identifier. |
Network currency mosaics were created due to inflation.
Inlines:
Property | Type | Description |
---|---|---|
mosaicId | MosaicId | Identifier of the mosaic that has been created. |
amount | Amount | Number of mosaics created. |
The collection of receipts related to a transaction.
Inlines:
Property | Type | Description |
---|---|---|
source | ReceiptSource | Transaction that triggered the receipt. |
receipts | array(Receipt, size=receiptsSize) | Array of receipts. |
Did you find what you were looking for? Give us your feedback.