Module constraint

Collection of rule constraints.

A constraint is a test that must be met in order for a rule to be valid. These are intended to be used in conjunction with the RuleV2 type.

Structs

AdditionalSigner

Constraint representing the requirement that An additional signer must be present.

All

Constraint representing a group AND, where every rule contained must pass.

Amount

Constraint representing a comparison against the amount of tokens being transferred.

Any

Constraint representing a group OR, where at least one rule contained must pass.

Frequency

Constraint representing a comparison based on time between operations.

IsWallet

Constraint that represents a test on whether a pubkey can be signed from a client and therefore is a true wallet account or not.

Namespace

A constraint that tells the operation finder to use the default namespace rule.

Not

Constraint representing a negation, where the contained rule must fail.

PDAMatch

Constraint representing a test where a resulting PDA derivation of seeds must prove the account is a PDA.

Pass

Constraint representing an operation that always succeeds.

ProgramOwned

Constraint representing a test where a Pubkey must be owned by a given program.

ProgramOwnedList

Constraint representing a test where the Pubkey must be owned by a program in the list of Pubkeys.

ProgramOwnedTree

Constraint representing a test where the Pubkey must be owned by a member of the Merkle tree in the rule.

PubkeyListMatch

Constraint representing a test where a Pubkey must be in the list of Pubkeys.

PubkeyMatch

Constraint representing a direct comparison between Pubkeys.

PubkeyTreeMatch

Constraing representing a test where a Pubkey must be a member of the Merkle tree in the rule.