FAQ

Answers, on the record.

Procurement, legal, security, and contributor questions in one place. Every answer cross-links to the source-of-truth document or contract.

PROGRAM

What is the Builders Programme?+

An open marketplace for cross-chain decoders, bridges, solvers, and dossiers under the Taifoon Sustainable Use License (TSUL) — fair-code, n8n SUL lineage, with one structural addition: revenue routing is enforced on-chain. Pick an open route from bounties.xml, submit code, two open-mamba reviewer agents replay it, auto-merge on consensus. From the merge block, every settled call routed through your contribution skims 49 bps split 70/20/10 — creator / reviewers / ecosystem. Pure performance economics, denominated in whatever currency the upstream call settled in.

Who is this for?+

Solo decoder developers, protocol teams, MEV/searchers, reviewer-agent operators, SaaS partners (n8n, Vertex, Copilot Studio, Palantir AIP). All flows start from /builders/onboarding.

What does it cost to participate?+

Nothing. Devnet test tokens for any reviewer-bond or gas placeholder are free from the faucet. The only real cost is the time to implement decode_event().

How long does it take to ship a first contribution?+

For a LOW-tier route (~5 fields to decode against existing fixtures): typically 1–3 days from claim to merge. The 24h challenge window is the long pole.

ECONOMICS

How do creators earn?+

Pure donut economics. No upfront, no prize, no synthetic prize token. A 49 bps donut is skimmed at settlement on every paid call / solver fill flowing through Taifoon, auto-distributed: 70% to the creator whose contribution routed the value, 20% to the reviewer agents that certified it, 10% to the ecosystem treasury. Performance only — you earn only if your work ships traffic, in the same currency the upstream call settled in.

When does the donut start accruing?+

The moment your contribution is live, which is the moment finalizeMerge fires after the 24h challenge window. Anyone can call finalizeMerge() once the window expires; from that block onward, every call routed through your contribution accrues your slice in the registry's claimable[] mapping. Pull at any time via claim().

What if my contribution fails post-merge?+

The self-healer agent opens a fix route automatically and routes it to the original contributor with a 72h right-of-first-refusal before posting publicly. Donut keeps accruing while the contribution is live.

What currency does the donut pay in?+

Whatever the upstream call settled in. The donut is currency-agnostic — the routing contract takes a percentage of whatever flowed through it and splits at that level. No conversion, no synthetic token, no FX risk introduced by the platform.

REVIEW

Who reviews submissions?+

Two of the 11 open-mamba reviewer agents listed in open-mamba/reviewers.xml. Defaults are auto-assigned by bounty category; bounties can override. No human triage on the happy path.

How are reviewers held accountable?+

Reviewers post a bond at registration; the bond is slashable 20% per upheld challenge inside the 24h window. The 20% reviewer slice of the donut compensates them for that risk and the certification work — but only on contributions they certified that actually ship traffic. Bad certifications produce no donut for them, AND risk slash.

What if reviewers disagree (1 PASS / 1 FAIL)?+

Routes to a third reviewer of the same scope. 2/3 PASS schedules the merge. The dissenting reviewer is logged but not slashed — honest disagreement is allowed.

How do I challenge a merge?+

Anyone can call BuildersRegistry.challenge(bountyId, contributor, evidence) during the 24h window. Oracle off-chain reviews the evidence and calls upholdChallenge() if valid.

COMPLIANCE

Is the platform open source?+

Source-available under the Taifoon Sustainable Intelligence License (TSIL) — fair-code, same lineage as n8n's Sustainable Use License. 41% of components are fully OSS (Apache 2.0 / MIT). See builders-program.xml > licensing_matrix.

Which regulatory frameworks does this satisfy?+

EU AI Act (Art. 9, 10, 11, 13, 14, 15), NIST AI RMF, ISO/IEC 42001:2023, NAIC Model Bulletin, GDPR (Art. 5, 25, 32), SOC 2 Type II. Every delivery in builders-program.xml declares its mapping.

Where is data stored? Residency?+

EU-pinned for EU-tenant deployments (Frankfurt). Confidential-class data (pre-merge submission tarballs, reviewer signing keys) destroyed within 30 days of merge. On-chain records carry hashes only — no PII.

Who governs changes?+

A 5-seat Center of Excellence with quorum of 3, including an external auditor. Public on-chain decision log. 72h standard SLA, 4h emergency. See BUILDERS_PROGRAM_GOVERNANCE.md §1.

INTEGRATION

Can I plug Taifoon into my agent platform?+

Yes. The Protocol Bridge speaks REST + MCP today; A2A in Phase 2. n8n, Vertex AI, Copilot Studio, Palantir AIP integrations are explicit deliveries — see /builders/roadmap.

What about LLM costs?+

Taifoon Nemotron is the own-vendor stack — billed via Taifoon Grid in GRID tokens, no external invoice. External LLMs (Anthropic, OpenAI, xAI, Google) are tracked per-vendor with caps. See /os/grid.

Where do I get help?+

Open an issue on the GitHub repo, or join the contributor channel referenced in BUILDERS_PROGRAM.md. The COE community steward triages within 72h.