This repo holds Create Protocol scenarios for the kcolbchain/token-simulator engine. Contributions here are typically new scenario YAMLs, parameter sweeps, or corrections to existing assumptions.
- Every number has a source. Either a citation (doc link, on-chain
query, vendor quote) or an explicit
TODO:marking it as a placeholder. "Looks about right" is not a source. - No engine code here. Engine bugs, new math, Monte Carlo primitives — those go to kcolbchain/token-simulator. If you need a new engine feature to express your scenario, open an issue there and link it from your scenario PR.
- Scenarios are immutable once released. If you want to change
assumptions, copy the file and bump the version (
v1→v2) so past analyses remain reproducible.
- Browse issues labeled
good first issueorhelp wanted. - Comment on the issue to claim it.
- Open a draft PR with your YAML + a short description of what it models and where the numbers came from.
Every scenario file lives under scenarios/ and must include:
scenario.id— unique slug, matches the filenamescenario.version— integer, bumped on every breaking changescenario.horizon_months— simulation horizontoken.fixed_supply— even if token isn't active, keep the constantrevenue_streams[]— at least one, each with atake_rate_bpsand a growth modelcosts— at minimum infra + teamoutputs.track— list of metrics the engine should emit
If the engine adds a new top-level key, document it here.
Until the engine publishes validation:
python -c "import yaml; yaml.safe_load(open('scenarios/YOUR_FILE.yaml'))"feat(scenario): add Phase 2 compute-stream preset
fix(burn-toll): correct toll destination to treasury burn
docs(readme): clarify engine/scenario split