Crate govern

Expand description

Handles proposals, voting, and queueing of transactions into a Smart Wallet.

Re-exports§

accounts: An Anchor generated module, providing a set of structs mirroring the structs deriving Accounts, where each field is a Pubkey. This is useful for specifying accounts for a client.
govern: The govern program.
instruction: An Anchor generated module containing the program’s set of instructions, where each method handler in the #[program] mod is associated with a struct defining the input arguments to the method. These should be used directly, when one wants to serialize Anchor instruction data, for example, when speciying instructions on a client.
program: Module representing the program.
proposal: Proposal logic.

GovernanceParameters: Governance parameters.
Governor: A Governor is the “DAO”: it is the account that holds control over important protocol functions, including treasury, protocol parameters, and more.
GovernorCreateEvent: Event called in govern::create_governor.
GovernorSetElectorateEvent: Event called in govern::set_electorate.
GovernorSetParamsEvent: Event called in govern::set_governance_params.
Proposal: A Proposal is a pending transaction that may or may not be executed by the DAO.
ProposalAccountMeta: Account metadata used to define Instructions
ProposalActivateEvent: Event called in govern::cancel_proposal.
ProposalCancelEvent: Event called in govern::cancel_proposal.
ProposalCreateEvent: Event called in govern::create_proposal.
ProposalInstruction: Instruction.
ProposalMeta: Metadata about a proposal.
ProposalMetaCreateEvent: Event called in govern::create_proposal_meta.
ProposalQueueEvent: Event called in govern::queue_proposal.
Vote: A Vote is a vote made by a voter by an electorate.
VoteSetEvent: Event called in govern::set_vote.

check_id: Confirms that a given pubkey is equivalent to the program ID
entry: The Anchor codegen exposes a programming model where a user defines a set of methods inside of a #[program] module in a way similar to writing RPC request handlers. The macro then generates a bunch of code wrapping these user defined methods into something that can be executed on Solana.
entrypoint^⚠: Safety
id: Returns the program ID