Independent research collective/Est. 2023

Bonding Curve
Research Group

We design, simulate, and stress-test cryptoeconomic systems — turning parameter choices that would otherwise be argued from intuition into evidence a protocol team can act on.

Focus
Cryptoeconomic system design
Method
Simulation, calibration, parameter sweeps
Output
Decision-grade evidence for protocol teams
Partners
Avalanche Foundation, Web3 protocol teams
01Practice

Cryptoeconomic systems, treated as engineering rather than opinion.

Protocol parameters get chosen in forum threads and governance calls, often on the strength of whoever argues most confidently. Our work is the alternative: model the system, calibrate it to real data, sweep the choices, and hand the decision-makers a defensible answer with its uncertainty attached.

01

Mechanism & system design

Specifying how a protocol's incentives, issuance, and constraints fit together — and writing that specification down precisely enough to be simulated, tested, and argued with.

Mechanism designToken engineeringSpecification
02

Simulation & digital twins

Building executable models of live systems in cadCAD, so a proposed change can be run against years of synthetic history before it is run against real value.

cadCADAgent behaviourScenario design
03

Parameter selection under uncertainty

No single forecast survives contact with a market. We sweep the parameter space, score every candidate against explicit goals, and report which choices hold up across the scenarios that could plausibly happen.

PSUURobustnessSensitivity analysis
04

Empirical data analysis

On-chain and market data, ingested and reconciled, then used to calibrate models against what actually happened rather than what a whitepaper assumed would.

CalibrationOn-chain dataValidation
02Method

From an open question to a decision, in six steps we can show our work on.

Every engagement runs the same pipeline. It is deliberately boring: the value is that each stage produces an artefact the next stage — and any reviewer — can check.

  1. 01

    Specify

    State the goals the system has to meet, and the invariants it must never violate, as testable propositions.

  2. 02

    Model

    Encode the mechanism and the agents that respond to it as an executable cadCAD model.

  3. 03

    Calibrate

    Fit behavioural parameters against historical on-chain and market data, not against assumption.

  4. 04

    Sweep

    Run the model across a cartesian grid of candidate parameters and plausible market scenarios.

  5. 05

    Validate

    Put every run through automated gates that fail loudly when the model quietly stops meaning anything.

  6. 06

    Decide

    Report which choices are robust, which are fragile, and where the evidence runs out.

Validation gates

Every run must clear all four

Wiring gate

Asserts every swept parameter actually reaches the state-transition math. Catches the parameter that is being varied and silently ignored.

Variance gate

Asserts every swept axis moves at least one target metric. A parameter that changes nothing is either inert or misconnected.

Conservation gate

Asserts the physical invariants hold at every step — supply is conserved, stake cannot exceed it, nothing is created by an accounting slip.

Verification gate

Recomputes every number quoted in a memo directly from the result data. A claim that cannot be reproduced does not ship.

03Selected work

Research that ends in a decision someone has to make.

We work with protocol foundations and teams whose parameter choices carry real consequences. The current flagship is a multi-phase engagement with the Avalanche Foundation.

Avalanche Foundation
Status — Active

Avalanche Staking Economics — Phase II

Parameter Selection Under Uncertainty for staking robustness

A digital twin of the Avalanche staking subsystem, built to answer a governance question with evidence instead of argument: which validator and delegator yield parameters keep the network secure and the token sound across the market conditions that could plausibly occur — not just the one that was assumed.

Optimisation goals

  • G1Network securityHold the staked fraction of circulating AVAX high enough to preserve consensus security.
  • G2Sustainable issuanceKeep long-run issuance bounded so the reward schedule does not dilute holders into the ground.
  • G3Validator viabilityKeep validation profitable above hardware cost, and the validator set distributed rather than concentrated.

Specification

Engine
cadCAD digital twin, cartesian parameter sweeps
Reward curves
Status quo · ACP-285 (filed) · quadratic duration · convex APY
Staker response
Tanh · arctan (fat-tailed) · Gompertz (asymmetric) · piecewise linear
Data
Snowflake (Ava Labs), DeFiLlama, CoinGecko
Assurance
Wiring · variance · conservation · verification gates

Avalanche research — Phase I

The published research base for the Avalanche engagement: systems architecture, the Phase II proposal, and the supporting notes, kept as a linked knowledge graph rather than a stack of PDFs.

Systems architecturePublic

Threshold-based flow funding

Mechanism design and simulation for continuous funding that releases against thresholds rather than in lump-sum grant rounds.

Mechanism designPublic goods

Bonding curve shock absorber

A simulator for curve designs that damp volatility shocks instead of transmitting them straight through to the token price.

Market designSimulation

Public goods token comparison

Empirical comparison of public-goods token designs and their realised distribution outcomes, from on-chain data.

Data analysisPublic goods
04Open source

The tooling is public, because a result you cannot rerun is not a result.

Our models, libraries, and analysis code are open. If we claim a parameter choice is robust, the code that produced that claim should be sitting where you can run it yourself.

Reference library

A worked guide to modelling and simulating cryptoeconomic primitives

Methodology, worked examples, and the reasoning behind the tooling — written to be usable by someone building their own model, not only by someone reading ours.

pip install condingOpen the library