Increasing Deposits

If the proposal you previously created didn't meet the MinDeposit requirement, you can still increase the total amount deposited to activate it.
Note: Proposals not meeting this requirement will be deleted after MaxDepositPeriod is reached.
Once the minimum deposit is reached, the proposal enters voting period:
secretcli tx gov
[proposal-id] \
[deposit] \
Note: The regular flags for the tx command are applicable to gov deposit (--fees, --gas, --account-number --ledger, --node, etc...)

Returning Deposits

The only ways deposits won't be returned to their owners is:
  1. 1.
    If in the voting period the proposal gets 1/3 NoWithVeto out of all votes, excluding Abstain votes (So NoWithVeto needs to be 1/3 out of all Yes, No & NoWithVeto ).
  2. 2.
    If in the voting period less than 1/3 of voting power votes (== The proposal won't reach a quorum).
Anyone can deposit for a proposal, even if you have 0 SCRT tokens staked/delegated/bonded.

Querying Deposits

Once a new proposal is created, you can query all the deposits submitted to it:
secretcli query gov deposits \
[proposal-id] \
You can also query a deposit submitted by a specific address:
secretcli query gov deposit \
[proposal_id] \


There are several flags to use with secretcli query gov deposit:
count total number of records in deposits to query for
--height int
Use a specific height to query state at (this can error if the node is pruning state)
-h, --help
help for deposits
--limit uint
pagination limit of deposits to query for (default 100)
--node string
<host>:<port> to Tendermint RPC interface for this chain (default "tcp://localhost:26657")
--offset uint
pagination offset of deposits to query for
--page uint
pagination page of deposits to query for. This sets offset to a multiple of limit (default 1)
--page-key string
pagination page-key of deposits to query for
results are sorted in descending order
Export as PDF
Copy link
Edit on GitHub
On this page
Increasing Deposits
Returning Deposits
Querying Deposits