• © Goverland Inc. 2026
  • v1.0.3
  • Privacy Policy
  • Terms of Use
BasisCashBasisCashby0x7F9455D723d6Ea89393E360e9C11B7846f3903Ad0x7F94…03Ad

Whether to Lower Seignorage

Voting ended about 5 years agoSucceeded

BIP-5 Title: Lowering Seignorage TWAP Threshold Author: liquidity_king, @liquidity_king Category: Economic

Summary: Currently, Basis Cash only mints additional BAC to BAS/BAB holders when the TWAP for BAC is over 1.05 This proposal is to lower the seignorage threshold to a lower value voted on by the community.

Motivation: Early on in an algo coins lifecycle, investors are primarily speculators who are betting on continued expansion, while having confidence that the bond mechanism backstop will encourage buying below peg. BAC does not have a natural source of demand, with demand primarily coming from speculation that the network will expand.

Speculators rely on the seignorage dynamic to support BAS prices, which ultimately drive demand for BAC. They take comfort that the BAB mechanism will support them when prices fall below peg. However, with the current parameter of 1.05 there is a gap from 1.0-1.05 where investors are not supported by the protocols incentives. Speculators buying BAC at 1.04 are not supported by BAB demand for another 4 cents, and they are also not going to be receiving any seignorage income from their farmed BAS. The 1.05 parameter also effects BAB redemptions, meaning that BAB buyers need to have faith that TWAP will reach 1.05 in a reasonable time frame. Lowering this threshold gives BAB more potency which is the most critical incentive for the protocols long term survival. Finally in the very long term having a more narrow threshold should help us target a more narrow peg which is the ultimate value proposition of the project.

Voting Options for BAS/BAB Seignorage Threshold: *1.05 (current) *1.04 *1.03 *1.025 *1.02 *1.01 *1.0

Off-Chain Vote

1.05 (current)
0 0%
1.04
0 0%
1.03
0 0%
1.025
1.34K 20.6%
1.02
0 0%
1.01
5.18K 79.4%
1
0 0%
Download mobile app to vote

Timeline

Dec 21, 2020Proposal created
Dec 23, 2020Proposal vote started
Dec 25, 2020Proposal vote ended
Oct 26, 2023Proposal updated