Merge your confidential inbox balance into your spending balance. This moves all funds from the inbox balance into the spending balance and resets the inbox to encrypted zero, ensuring that proofs reference only stable spending balances.
Note
Even if the inbox is already empty (contains encrypted zero), this transaction is valid and succeeds.
Requires the ConfidentialTransfer amendment. Loading...
{
"TransactionType": "ConfidentialMPTMergeInbox",
"Account": "rUUeVf9zJWfg7mxNCLhEXm9mfmeHBGb9w3",
"MPTokenIssuanceID": "003CE807D39D78123FFBDD9401BEC038D88BD328AC353B9C",
"Fee": "10",
"Sequence": 3991569
}In addition to the common fields, ConfidentialMPTMergeInbox transactions use the following fields:
| Field | JSON Type | Internal Type | Required? | Description |
|---|---|---|---|---|
MPTokenIssuanceID | String | UInt192 | Yes | The unique identifier for the MPT issuance. |
Besides errors that can occur for all transactions, ConfidentialMPTMergeInbox transactions can result in the following transaction result codes:
| Error Code | Description |
|---|---|
tecLOCKED | The MPT is locked for the account, or the issuance is globally locked. |
tecNO_AUTH | The issuance requires authorization and the account's MPToken is not authorized. |
tecNO_PERMISSION | The transaction lacks the required permissions. Common causes include: - The issuance does not have the Can Hold Confidential Balance flag enabled. - The account's MPToken is missing the ConfidentialBalanceInbox, ConfidentialBalanceSpending, or HolderEncryptionKey field. |
tecOBJECT_NOT_FOUND | The MPTokenIssuance or the account's MPToken does not exist. |
temDISABLED | The ConfidentialTransfer amendment is not enabled. |
temMALFORMED | The Account is the issuer of the MPTokenIssuanceID. |