Create V2 Pool for KBL/xKBL 0.15% + Default Listing of xKBL

Request for Comment
1

Title: Launch V2 Pool for KBL/xKBL (0.15%) and Request Default Listing of xKBL

Author(s): Kabila

SaucerSwap Voting Interface: N/A

Related Discussions: N/A

Submission Date: May 15, 2025

Summary:

We propose the creation of a V2 KBL/xKBL pool with a 0.15% fee tier on SaucerSwap, alongside the default listing of xKBL within the SaucerSwap platform. This initiative supports the recent rollout of xKBL (Kabila’s staked version of KBL) by improving trading depth, reducing slippage, and making the asset more accessible to users participating in KBL staking.

Abstract:

A V2 KBL/xKBL pool will enable users to swap between KBL and its staked counterpart with high capital efficiency and low slippage, leveraging concentrated liquidity mechanics. This setup is ideal for tightly pegged pairs and avoids the inefficiencies of a legacy V1 pool. In parallel, default listing of xKBL will ensure broader visibility and improved token discoverability and authority.

Motivation:

The creation of a V2 KBL/xKBL pool and the inclusion of xKBL in SaucerSwap’s token registry are key steps in supporting the adoption of staking mechanics within the Kabila ecosystem. These actions will:

  • Facilitate deeper liquidity around KBL/xKBL pairs.
  • Provide efficient infrastructure for users to enter or exit staking.
  • Promote trust and visibility around xKBL.
  • Align with the broader Hedera DeFi roadmap and unlock new strategies for liquidity providers and stakers alike.

Benefits (Pros):

  • Improved Trading Experience: Low slippage and optimized routing for swaps between KBL and xKBL.
  • Capital Efficiency: Concentrated liquidity ensures better use of treasury or community funds.
  • Stable Market Peg: Helps maintain the expected 1:1 peg between KBL and xKBL.
  • LP Incentives: Opportunity to earn fees with tighter liquidity bands and lower capital requirements.
  • Visibility: Listing xKBL by default simplifies onboarding and trust on SaucerSwap.

Downside (Cons):

  • Technical Overhead: Requires periodic monitoring or rebalancing if the peg drifts or activity spikes.
  • Smart Contract Risk: As with any DeFi deployment, users are exposed to protocol-level risks.
  • Education Required: New users may need guidance on xKBL staking, minting, and redeeming.

Voting Options:

  • For: Approve the creation of a V2 KBL/xKBL pool with a 0.15% fee and list xKBL as a default token in the SaucerSwap interface.
  • Against: Request further clarification, revision, or delay the implementation.
2

tokens which appear in the token select modal list by default, i.e. default listed, are based on aggregated TVL & volume and is updated monthly.

For more information see Partnership Inquiries | SaucerSwap

3

Thanks nube. Noted down :slight_smile:

4

Proposal is clear.
It wants to establish a V2 pool.
Specified the fee tier. 0.15%

Sentinel reports and audits would help.
Token IDs too.

How much liquidity does the proposer would commit to initiate the pool?

5

Thanks @H-Barbara

Here is the Sentinel Report for $KBL: Sentinel

And the Vesting and Staking Contract Audits for $KBL and $xKBL by Hacken: Kabila audit by Hacken

KBL Token ID: 0.0.5989978
xKBL Token ID: 0.0.8061363

In terms of liquidity, we are planning to start with a 50K-50K$ pool, and slowly increase it to 150K-150K$ approximately.

6

All my substantive questions been answered.
Be sure to add these info to the proposal whenever you are ready to make it.

Also, for your best chances to succeed, consider timing of when to establish your proposal (though I dont think there’s too many major holiday breaks to consider now) and giving communities a heads up (and reminders) for the proposals during to votings.

1 Like