• © Goverland Inc. 2026
  • v1.0.8
  • Privacy Policy
  • Terms of Use
TLXTLXby0xCA13326CC4072943bb2635b4691084F84a4FDA670xCA13…DA67

TIP 05: Update baseForAllTLX Bonding Config

Voting ended over 1 year agoSucceeded

Summary The proposal is to update the baseForAllTLX parameter from 38,000 to 20,000 .

Abstract Updating this parameter to 20,000 should make bonding more engaging and accessible by increasing the rate that the bonding discount increases so it is profitable to bond more frequently.

Motivation The Bonding contract has a parameter baseForAllTlx that can be updated through governance. The function of this parameter is detailed in the Bonding docs here: https://docs.tlx.fi/basics/tokenomics/bonding-for-usdtlx In short, it controls how frequently it is profitable to bond, and the maximum amount that can be bonded at once. Larger values of this parameter lead to less frequent bonding but of larger amounts. Smaller values lead to more frequent bonding of smaller amounts. Currently, this value is set to 38,000, you can see this value in the UI on the bond page: https://tlx.fi/bond

To be clear, this value does not modify in any way the inflation schedule for bonding.

Specification The baseForAllTLX parameter should be set to 20,000.

Rationale When the full amount is bonded currently, it results in bonding being unprofitable for a little over two days. This makes it harder for users who want to bond a small amount to find a profitable window to do so. Reducing the amount, and increasing the frequency of bonding should make bonding more faced past, engaging and accessible.

Test Cases When updating this parameter, the discount will increase after it is updated. For this reason, consideration needs to be taken to process this update only when the discount is significantly negative so it doesn't spike up into a positive discount. A test should be done at the time of executing this change to simulate the outcome of the change and ensure that the bonding discount is still negative after this change. A manual test should be done to ensure the value has been updated correctly in the contract and on the UI.

Off-Chain Vote

For
3 TC75%
Against
1 TC25%
Abstain
0 TC0%
Download mobile app to vote

Timeline

Jun 24, 2024Proposal created
Jun 24, 2024Proposal vote started
Jun 29, 2024Proposal vote ended
Jun 29, 2024Proposal updated