Assessment reportsPublic findings
Back to Zellic siteBack
↗
Assessment reports>Silo Staking>Threat Model>Message: ExecuteMsg::Vote
GeneralOverview
Findings
High (1)
Low (1)
Threat ModelWhat are threat models?
hub-execute.rsMessage: ExecuteMsg::BondMessage: execute::check_received_coin_msgMessage: ExecuteMsg::DonateMessage: ExecuteMsg::HarvestMessage: ExecuteMsg::RebalanceMessage: ExecuteMsg::ReconcileMessage: execute::reinvestMessage: ExecuteMsg::SubmitBatchMessage: ExecuteMsg::TuneDelegationsMessage: ExecuteMsg::AcceptOwnershipMessage: ExecuteMsg::AddValidatorMessage: ExecuteMsg::CallbackMessage: ExecuteMsg::DropOwnershipProposalMessage: ExecuteMsg::RemoveValidatorMessage: ExecuteMsg::TransferOwnershipMessage: ExecuteMsg::QueueUnbondMessage: ExecuteMsg::UpdateConfigMessage: ExecuteMsg::VoteMessage: ExecuteMsg::VoteWeightedMessage: ExecuteMsg::WithdrawUnbonded
token-execute.rs
Audit ResultsSummary

Message: ExecuteMsg::Vote

This message can only be invoked by the vote operator.

The following user parameters are expected:

proposal_id — The proposal ID to vote on. vote — The chosen vote option.

The function sends a message to the Cosmos governance module, with the chosen proposal ID and vote.

Zellic © 2025Back to top ↑