BORG’s price behavior is engineered around liquidity events, not emissions

SwissBorg’s BORG token sits in an unusual spot for a large-cap utility asset. The supply story is mostly static. The float is not. Most of the interesting price action risk comes from how SwissBorg channels user activity into market buybacks, then forces a meaningful share of the resulting BORG into time-delayed states via in-app locking and governance pools. That’s market microstructure, not “tokenomics-as-a-pie-chart.”

At the product level, SwissBorg positions BORG as the utility token inside its wealth app. It’s used to (1) earn trading-fee cashback through the Loyalty Ranks system, (2) boost yields on Earn strategies, (3) participate in governance votes and receive governance rewards, and (4) access “exclusive deals” tied to rank/locking.

The token itself is the successor to CHSB. SwissBorg began the 1:1 migration from CHSB to BORG on October 17, 2023 via its migration process. BORG is an ERC-20 on Ethereum, and SwissBorg also supports BORG on Solana.

Supply and float: fixed cap, variable tradable reality

On CoinGecko, BORG is presented with a max supply of 1,000,000,000 and a total supply of 981,852,443 (CoinGecko snapshot as crawled). The market implication is simple: FDV is close to spot market cap because there is not a large “yet-to-mint” inflation overhang.

SwissBorg’s own dashboard reframes the same supply into buckets that matter for liquidity. It breaks “circulating supply” into unlocked, locked, burned, and a buyback pool; the liquidity bucket breakdown shown on SwissBorg’s site includes 563.28M unlocked, 410.92M locked (41.09%), 18.147M burned, and 5.6377M in the buyback pool.

That split is more predictive of short-term price behavior than “circulating supply” on an aggregator. A token can be “circulating” in the accounting sense while being practically unavailable to hit bids because it is locked behind app mechanics and cooldown windows. SwissBorg is explicit that rewards are accumulated into a locked account, which is a direct float-suppression lever.

On the contract side, SwissBorg’s docs describe BORG as an OpenZeppelin-based ERC-20 with ERC20Burnable support, meaning burns can reduce totalSupply() on-chain. They also note an important supply nuance: CHSB was hardcoded to 1 billion, while BORG’s initial supply “will take into account the tokens sent to address(0) to not mint tokens that can't be migrated.”

Original allocation (from CHSB genesis, carried through the 1:1 migration)

One caveat from a modelability standpoint: the 2017 allocation framing is supply-side. The 2024-2026 market reality is dominated by where tokens sit today (locked vs unlocked, pools vs user wallets), and by how fast they can transition between those states. SwissBorg publishes the state split, but that split is endogenous to user incentives and company program parameters.

Fee flows into buybacks: cadence is the mechanism

SwissBorg currently describes two buyback programs tied to activity and company performance. First is a “Buyback / Cashback” tied to app trading activity. SwissBorg states that app fees are collected in the destination currencies, converted into USDC, and used to execute BORG buybacks on the market (with the explicit note that fees taken in BORG are not converted).

Second is a quarterly “Governance allocation” buyback. SwissBorg links this to an internal metric called the “Sustainability Score,” described as measuring user activity and engagement, and it notes the company may adjust buyback amounts depending on operational burden or market conditions.

The microstructure detail that matters is the conversion throttle. SwissBorg states cashback is calculated based on exchange fees at the time of each transaction, then fees are converted daily into BORG over a 7-day period and distributed weekly. They also publish a market-impact constraint: under “normal market conditions,” the daily conversion into BORG will not exceed 25% of the previous day’s trading volume as reported by CoinMarketCap (24-hour volume data).

That is a deliberate anti-shock design. It reduces the chance the buyback becomes the dominant marginal buyer on low-volume days. It also means the program’s realized buy pressure can downshift precisely when liquidity is thin. That trade-off is rational for execution quality, but it weakens the “always-on bid” narrative during drawdowns.

There is also a control-plane risk. SwissBorg explicitly states it retains full discretion over the timing and execution of program purchases.

Locking mechanics: SwissBorg compresses float, then reintroduces it on a timer

The current Loyalty Ranks system is the primary float management layer. SwissBorg says it replaced the prior Premium and Borger Journey programs, and it sets one unified exchange fee of 0.99% while paying users BORG “cashback” for trading if they lock BORG and reach a rank.

The locking constraint is lighter than legacy “membership staking” designs. SwissBorg states locking “only lasts 2 weeks,” and after that users can keep tokens locked to maintain rank or unlock them.

Unlocking is not instantaneous. SwissBorg’s unlock cooldown rules state a 14-day cooldown after you unlock, during which voting power is lost on the unlocked amount until funds return, and rank benefits can drop if your locked balance decreases.

From a market-structure lens, this creates a two-step liquidity release process. “Sell pressure” is not just “do holders want to sell.” It becomes “did they start the cooldown two weeks ago.” That can smooth reflexive panics. It can also produce visible unlock waves if many users react to the same narrative catalyst at the same time.

SwissBorg’s legal terms also describe Premium accounts that require locking BORG for 12 months to upgrade tiers, and notes the required amounts can vary at the company’s discretion. Practically, the ecosystem has run multiple “locking regimes” over time. That history matters because legacy cohorts can behave differently from new cohorts, and their unlock behavior will not be synchronized.

Governance and burns: community votes, company rails

SwissBorg’s current framing is “Protect & Choose,” which evolved from “Protect & Burn.” The original description is straightforward: SwissBorg reserved 20% of exchange fees generated in the app and used them to buy tokens on the market and permanently remove them from supply.

On June 27, 2022, SwissBorg described the “Protect & Choose” evolution: the same fee stream was used to build a pool, buy back tokens through the quarter without announcing timing, then put the pool to a token-holder vote at quarter end. The pool itself was described as being converted into USDC and placed into a yield wallet to grow over time.

In the current BORG dashboard wording, SwissBorg states: every quarter, it burns an amount of BORG voted upon by the community, and the amount to vote on is based on the Sustainability Score.

The important structural point is that this is not a pure on-chain, unstoppable burn policy. It is a governance process inside a platform that also controls program execution and disclosure cadence. SwissBorg’s blog emphasizes that governance has been allocating a “multi-million euro” BORG pool and cites outcomes including 10 million BORG repurchased and 2 million BORG permanently burned.

Voting power is explicitly tied to locked BORG. SwissBorg states 1 Voting Power per 10 BORG locked. Guardians rewards are distributed in BORG at the end of each quarterly session, and are “maximised” by locked BORG at the time of voting and by participating in all votes within the quarter.

On-chain governance optionality exists at the token level. SwissBorg’s token contract documentation says BORG includes OpenZeppelin’s ERC20Votes extension, which tracks historical balances and supports delegation for on-chain voting. Today’s governance described by SwissBorg is still largely an app-centric process, which is a different trust and execution model than pure DAO governance.

BorgPad turns BORG into on-chain collateral, with burn paths tied to LP outcomes

SwissBorg’s on-chain expansion for BORG is most clearly expressed through BorgPad, positioned as a Liquidity Bootstrapping Protocol (LBP) ecosystem where BORG is the “currency of investment.” SwissBorg describes a flow where contributed BORG is paired with a project’s token to create a liquidity pool on a DEX like Raydium, providing liquidity for on-chain traders and SwissBorg app users.

The mechanism SwissBorg highlights is deflation through liquidity behaviors, not fixed-schedule burns. They describe two key effects: (1) BORG in the LP is locked until unpaired, and if the LP is burned the BORG remains locked permanently, effectively removing it from circulation; (2) swaps on the TOKEN/BORG LP accrue fees captured in TOKEN or BORG, and if the LP is burned, the collected fees are also burned.

BorgPad’s own docs make the LBP lock terms variability explicit. LBPs can include locking periods “up to 18 months” and a parameter that up to 50% of the LP can be burned, depending on the deal structure.

For market structure, this matters because it introduces new, episodic sinks for BORG liquidity that are external to the SwissBorg app. It also introduces event risk. Every new BorgPad deal can create a burst of BORG acquisition demand. The unwind is trickier. If positions are locked, the unwind is delayed. If LP is burned, the BORG is gone from float, but the market still has to reprice around a smaller effective circulating set.

Risk register: the dominant risk is float shock from synchronized unlock behavior

SwissBorg has done real work to dampen reflexive sell pressure. Cashback rewards are paid in BORG and credited into a locked account. Buybacks are throttled versus market volume. Governance burns are quarterly rather than hyper-frequent, which reduces the constant “burn front-run” game.

Those are narrative-stabilizing choices. They also concentrate risk into specific windows and control points.

Top 3 risks

  1. Float shock via synchronized unlocks. Trigger: a drawdown, regulation headline, or program change that causes many users to start unlocking at once. Mechanism: BORG transitions from “locked” to “sellable” after the stated cooldown windows, lifting available float and deepening order-book imbalance into thin liquidity. Who bears it: spot holders and liquidity providers, especially on venues where BORG depth is shallow. Measurable indicators: SwissBorg’s “locked BORG” and “unlocked circulating” breakdown moving rapidly, plus elevated exchange outflows from custodial/app-associated wallets when unlock windows mature.
  2. Discretion risk in buyback execution. Trigger: operational constraints, market stress, or policy changes that alter the timing/size of buybacks. Mechanism: buyback demand is not a smart-contract obligation, and SwissBorg states it retains discretion over timing and execution. If market participants price in an “always-on bid,” a deviation can create sharp repricing. Who bears it: traders running mean-reversion or buyback-following strategies, and long-only holders relying on program continuity. Measurable indicators: changes in published buyback cadence/size, deviations from the stated conversion limits, and governance communications signaling parameter adjustments.
  3. Cross-chain / bridge surface area. Trigger: bridge exploits, transceiver or manager contract issues, or operational pauses. Mechanism: BORG’s multi-chain presence relies on bridging infrastructure (SwissBorg’s docs reference Wormhole-related components and NTT manager contracts). Bridge stress can fragment liquidity across chains and impair price discovery. Who bears it: Solana-side and Ethereum-side LPs, and users moving BORG cross-chain for BorgPad participation or trading. Measurable indicators: bridge transfer volumes dropping abruptly, on-chain error/incident reports, or contract-level pausing/guard-rail changes.

Dominant risk: float shock from synchronized unlock behavior

The biggest structural risk to BORG’s price is not “inflation” in the classic sense. BORG is not designed with a perpetual emissions schedule, and the max supply framing is stable. The risk is that a large portion of the token supply is sitting in semi-liquid states that can become liquid on a timer, and those timers can align around shared stimuli.

SwissBorg’s own breakdown shows hundreds of millions of BORG in a locked bucket at any moment. That is a float suppressant until it is not. The unlocking path includes cooldown mechanics (14 days stated in FAQs), which reduces instantaneous panic selling. But cooldowns also create something markets are very bad at pricing: a delayed supply wave.

When holders respond to a negative catalyst, they do not sell immediately. They initiate unlock. Two weeks later, many of those tokens can become sellable around the same time. If this coincides with low spot liquidity, the sell pressure can gap the market rather than clear smoothly. That is exactly the kind of discontinuity that makes “circulating supply” narratives feel wrong in practice.

SwissBorg’s buyback throttle helps prevent the program from overpaying into illiquid conditions, which is good execution. It also means buybacks may be least able to offset sell waves when liquidity is already thin. That’s the trade-off: narrative stability from controlled execution versus vulnerability to liquidity shocks when the float regime flips.

The monitoring approach is therefore mechanical. Track SwissBorg’s locked vs unlocked split. Track governance periods and reward distributions because those can change locking incentives and user behavior. Track BorgPad deal calendars and lock terms because they can create additional episodic sinks and later unlocks. If these three layers line up, BORG’s price can move far more on liquidity conditions than on “fundamentals.”

If you’re doing token economy design work internally, the BORG case is a useful reference for how buybacks, delayed unlocks, and governance pools can be composed into a single system. For teams hiring tokenomics consulting support, our tokenomics design services typically start by mapping the liquidity timetable across the main design components, not just the static supply chart.

For a contrasting “utility token in a consumer app” baseline, you can compare BORG’s mechanics with Trust Wallet (TWT). For a non-crypto, NAV-anchored supply-and-float lens, see Spiko USTBL.

If you’re building a model or writing an investment memo, it can help to formalize your assumptions up front; our tokenomics FAQ covers the core terms teams tend to mix together when discussing supply versus float.



This article is part of our Tokenomics Deep Dive series.