Collateral Whitelist Addition Vote Executor
Free to download on every platform. Comes pre-installed on BotFone, BotPad and BotFlip — with extra free apps included.
About this app
WHAT IT DOES
Collateral Whitelist Addition Vote Executor enables governance participants and administrators to execute a passed proposal that adds a new asset to a protocol's collateral whitelist. The tool reads the governance contract state to verify the proposal status, vote counts, quorum requirements, and whether the proposal has passed and is ready for execution. It then constructs and submits the transaction to the whitelist contract, setting the asset's risk parameters—loan-to-value ratio, liquidation threshold, and collateral cap. The tool ensures that the proposal has met all governance requirements before allowing execution, preventing premature or unauthorized changes.
This tool is essential for DAOs and DeFi protocols that use governance to manage collateral assets—such as lending platforms, stablecoin issuers, and margin trading protocols. It streamlines the execution of whitelist addition proposals, reducing the risk of human error and ensuring that risk parameters are set correctly.
HOW TO USE
1. Connect your EVM wallet to the network where the governor and whitelist contracts are deployed.
2. Enter the governor contract address and the whitelist contract address.
3. Enter the proposal ID and the asset address to be whitelisted.
4. Set the risk parameters: LTV percentage (e.g., 75), liquidation threshold percentage (e.g., 80), and collateral cap (e.g., 1000000).
5. Click "Check Proposal" to verify the proposal status—the tool displays vote counts, quorum status, and whether the proposal can be executed.
6. Review the proposal status and risk parameters in the review panel.
7. If the proposal has passed and meets quorum, click "Execute" to submit the execution transaction.
8. Track progress via the status bar and confirmation of the transaction hash upon completion.
TECHNICAL MECHANISM
The tool reads the governance contract using view functions: state(proposalId) for proposal status, proposalVotes(proposalId) for vote counts, and quorum() for the required threshold. It validates that the proposal is in the "Succeeded" state and that the total votes meet the quorum requirement. For execution, the tool attempts multiple function signatures on the whitelist contract: addCollateral(asset, ltv, liquidationThreshold, cap), addCollateralWithOracle(asset, ltv, liquidationThreshold, cap, oracle), and executeProposal(proposalId). Gas estimation applies a 20% buffer, and actual gas costs are calculated from receipt.effectiveGasPrice. The tool validates that LTV is less than the liquidation threshold and that all risk parameters are positive integers.
WHAT IT CANNOT SEE
This tool cannot verify the risk parameters or oracle feeds for the new collateral asset—it relies on the user to input correct values and on the protocol's governance to have approved them. It cannot guarantee that the asset is safe or appropriate for the protocol; the tool does not assess token security, liquidity, or market risk. It cannot bypass governance requirements or execute a proposal that has not passed—the tool will reject execution if the proposal is not in the "Succeeded" state. It cannot recover funds if the new collateral causes protocol insolvency due to incorrect risk parameters or market conditions. It cannot assess the asset's liquidity or market depth off-chain; collateral assets with insufficient liquidity may lead to liquidation issues. It cannot validate that the asset's smart contract is secure or that it has been properly audited.
PLEASE NOTE
EVM chains only. This tool requires that the governor and whitelist contracts implement the standard interfaces used by the tool. Not all governance or whitelist contracts use the same ABI—the tool attempts multiple function signatures for compatibility. Always verify the risk parameters with protocol risk managers before executing. Setting LTV too high or liquidation threshold too low can lead to protocol insolvency. Test on testnet before using on mainnet.