The name of your guard. This should match the name provided in the
availableGuards
array of your registered CandyGuardProgram
.
The total amount of bytes required to serialize your guard's settings. Contratry to the usual Borsh serialization, this size is fixed and should represent the maximum space required for your guard's settings.
The serializer used to serialize and deserialize your guard's settings.
Optional
mintIf your guard requires additional accounts or arguments to be passed
to the mint
instruction, this function parses the predefined mintSettings
of your guards into the required arguments and remaining accounts.
The serialized arguments to pass to the mint instruction.
A remain account to push to the mint or route instruction.
When isSigner
is true, the address
attribute must be Signer
and it will be pushed to the signers
array of the transaction.
Optional
routeIf your guard support the "route" instruction which allows you to execute
a custom instruction on the guard, this function parses the predefined
routeSettings
of your guards into the required arguments and remaining accounts.
The serialized arguments to pass to the route instruction.
A remain account to push to the mint or route instruction.
When isSigner
is true, the address
attribute must be Signer
and it will be pushed to the signers
array of the transaction.
Generated using TypeDoc
When creating your own custom guards, you will need to register them with the JS SDK by creating a
CandyGuardManifest
which lets the SDK know how to interact with your guard.