Available Guards
Third Party Signer
Overview
The Third Party Signer guard requires a predefined address to sign each mint transaction. The signer will need to be passed within the mint settings of this guard.
This allows for more centralized mints where every single mint transaction has to go through a specific signer.
Guard Settings
The Third Party Signer guard contains the following settings:
- Signer Key: The address of the signer that will need to sign each mint transaction.
Set up a Candy Machine using the Third Pary Signer Guard
const myConfiguredSigner = generateSigner(umi);
create(umi, {
// ...
guards: {
thirdPartySigner: some({ signerKey: myConfiguredSigner.publicKey }),
},
});
API References: create, ThirdPartySigner
Mint Settings
The Third Party Signer guard contains the following Mint Settings:
- Signer: The required third-party signer. The address of this signer must match the Signer Key in the guard settings.
Mint with the Third Party Signer Guard
When minting via the Umi library, simply provide the third-party signer via the signer
attribute like so.
create(umi, {
// ...
guards: {
thirdPartySigner: some({ signer: myConfiguredSigner }),
},
});
Remember to also sign the transaction with the myConfiguredSigner keypair.
Route Instruction
The Third Party Signer guard does not support the route instruction.