TaifoonTAIFOON
Builders Programme
TSUL · v1.0 · LIVE ON DEVNET 36927

Ship code.
Co-own the route.
Get paid forever.

The Taifoon Sustainable Use License. Fair-code lineage, on-chain donut routing. Every settled call routes its realized spread three ways — 70/20/10: 70% to the solver running the pod (operating revenue), 20% perpetually to the wallet that authored the merged contribution (yours), 10% to the ecosystem. The split is fixed; the pool is whatever each fill actually clears, in the upstream settlement currency. No upfront, no prize, no synthetic token. The canonical license text is one file: github.com/taifoon-io/license/LICENSE.md.

ONE LICENSE · ONE FILE · ONE ANSWER
The canonical TSUL is LICENSE.md at github.com/taifoon-io/license. This page is the public FAQ wrapper — anything ambiguous, the file wins. Questions: taifooon@proton.me.
Read the canonical LICENSE.md →
DONUT POOL
realized spread
per settled call
SOLVER SLICE
70%
operator revenue
CREATOR SLICE
20%
perpetual · merged author
ECOSYSTEM SLICE
10%
treasury + reviewers

[ WHAT YOU GET ]

Three product promises. The license clauses below exist to enforce them.
01
Co-ownership of every route you ship
When your adapter merges, your wallet becomes the perpetual recipient of 20% of every settled call's realized spread routed through it (the solver running the pod takes the 70% operating slice; 10% funds the ecosystem). The split is fixed at 70/20/10; the size of every pool is whatever that fill actually nets in the upstream currency. On-chain, automatic, irrevocable as long as your contribution stays merged.
02
No upfront. No prize. No synthetic token.
Performance only. You earn from the moment of merge, in whatever currency each upstream call settled in. No FX risk introduced by the platform. No vesting. No cliffs. The donut routes the actual revenue.
03
On-chain enforcement, not lawyer-paper
Rule 4 of TSUL is enforced by BuildersRegistry.recordRevenueTouch() on devnet 36927. Strip the donut and the registry revokes you. The license is a contract because the contract IS the license.

[ THE FOUR RULES · SUMMARY ]

The full operative text lives at LICENSE.md in taifoon-io/license. Below is the plain-English summary; the file is authoritative.
  1. 01
    Use or modify Taifoon for internal business purposes, non-commercial use, or personal use — free.
  2. 02
    Distribute it free of charge for non-commercial purposes — free.
  3. 03
    Don't alter or remove the licensing, copyright, donut routing, or other notices. Don't use Taifoon's trademarks for hosted-competing services.
  4. 04
    Preserve the on-chain donut. If your deployment routes value through Taifoon's adapter fleet, every settled call's realized spread must continue routing through BuildersRegistry.recordRevenueTouch() under the 70/20/10 split. This is the rule that makes the marketplace non-extractive.
Authoritative text · LICENSE.mdOpen the canonical file →

[ LICENSE FAQ ]

The same 14 questions n8n answers on docs.n8n.io, adapted for an on-chain marketplace.
What license do you use?+
The Taifoon Sustainable Use License (TSUL) v1.0 for the platform code (solver core, BuildersRegistry, adapter fleet, OS surface). Apache 2.0 for the contributor templates under templates/adapter-v1/. Both licenses are based on the fair-code philosophy with one structural addition: on-chain revenue routing.
What source code is covered by TSUL?+
TSUL applies to all source code in the canonical Taifoon repositories — spinner, taifoon-eco, taifoon-next, open-mamba, taifoon-solver — except: branches other than the default branch, files containing .ee. in their name (Enterprise License), and files under templates/adapter-v1/ (Apache 2.0).
What is the Taifoon Sustainable Use License?+
TSUL is a fair-code license created by the Taifoon project in 2026. The license grants you the free right to use, modify, create derivative works, and redistribute, with four limitations summarized in The Four Rules above. We encourage anyone to reuse the license — contact taifooon@proton.me.
What is and isn't allowed under the license?+
Use is restricted to internal business purposes, AND the on-chain donut must be preserved on any commercial deployment that routes value through the adapter fleet. In practice all use is allowed unless you are (a) selling a product, service, or module in which the value derives entirely or substantially from Taifoon functionality, OR (b) bypassing donut routing. See the Worked Examples section for concrete scenarios.
Can I use Taifoon to power a feature in my app?+
Usually yes, as long as you preserve the on-chain donut. If your app routes user-facing cross-chain operations through Taifoon's adapter fleet, the donut routes on every settled call automatically — that is the design. The license violation arises only when you strip the donut routing or substitute it with a no-op proxy.
What if I want to use Taifoon for something that's not permitted?+
Email taifooon@proton.me. We actively encourage builders to embed Taifoon in their products. We just ask you to sign an agreement that defines the donut substitute or alternative billing arrangement. Enterprise terms (LICENSE_EE.md) cover the most common cases.
Why don't you use an OSI-approved open-source license?+
Two limitations TSUL needs that OSI cannot accommodate: the on-chain donut (which is the funding mechanism for the agent fleet, the reviewer pool, and the ecosystem treasury), and the "internal business purposes" boundary (which prevents commercial-rehost capture). We make Taifoon as widely and freely available as possible while ensuring the project can sustain itself.
Why did you create a license?+
The on-chain clause didn't exist in any prior fair-code license. We took n8n's SUL — the cleanest plain-English fair-code license available — and added rule #4. We tried to keep the legal pain to a minimum: plain English, four rules, mirrored worked examples, public FAQ, and a single email for questions.
My company has a policy against code that restricts commercial use. Can I still use Taifoon?+
If your use is internal — coordinating cross-chain data flows your company controls, integrating Taifoon into an internal data warehouse, routing your own treasury via the adapter fleet — yes. The "no commercial use restriction" policies generally target hosted-rehost and white-labeling, which TSUL also restricts. For grey-zone cases email taifooon@proton.me.
What happens to the code I contribute under TSUL?+
You retain ownership. The Contributor License Agreement grants the project a perpetual right to use and relicense your contribution (necessary so the license can adapt over time without re-collecting consent from every past contributor). You're not liable for damages your contribution causes downstream. If your contribution merges through BuildersRegistry.finalizeMerge(), your wallet starts accruing the creator slice of the donut on every settled call routed through your code.
Why did you build TSUL on top of n8n's SUL?+
n8n's SUL is the cleanest, most plain-English, most professionally-applied fair-code license available. The "internal business purposes" boundary is precise. The worked examples set a model for clarity. We mirrored their question structure 1:1 in this FAQ. The only structural addition is rule #4 (on-chain donut routing) — everything else is n8n's shape, lightly adapted.
What are the main differences between TSUL and n8n's SUL?+
One difference: rule #4 (on-chain donut routing). Everything else is structurally identical. If you understand n8n's SUL, you understand TSUL. The donut clause is the part that requires the BuildersRegistry contract to exist; it is the part that lets revenue route to contributors automatically without a subscription, license fee, or central billing operator.
Is Taifoon open source?+
Although Taifoon's source code is available under TSUL, according to OSI, open-source licenses can't include limitations on use. So we don't call ourselves open source. We use the term fair-code. The contributor templates under templates/adapter-v1/ ARE Apache 2.0 — that part is OSI-compliant.
What is fair-code, and how does TSUL relate to it?+
Fair-code isn't a software license. It describes a software model where software: is generally free to use and can be distributed by anybody; has its source code openly available; can be extended by anybody in public and private communities; is commercially restricted by its authors. TSUL is a fair-code license. Read more on faircode.io.
Can I use TSUL for my own project?+
Yes. We're excited to see more software use TSUL — especially projects that have on-chain revenue routing. Adapt rule #4 to reference your own registry contract. Email taifooon@proton.me if you'd like to talk through it.

[ WORKED EXAMPLES ]

Concrete scenarios. Solana flavored, because that's where most of the work is heading.
01
Alice ships a Solana-Mayan adapter
Alice writes the adapter in taifoon-eco/contracts/adapters/MayanSolanaAdapter.sol against bounty b-mayan-sol-001. Two open-mamba reviewer agents replay her code on devnet 36927; both PASS. The 24h challenge window expires with no counter-example. finalizeMerge() fires. From that block, every Mayan fill routed through her adapter splits its realized spread 70/20/10: 70% to whichever solver fills the route (their operating revenue), 20% perpetually to Alice as the merged author, 10% to the ecosystem (which funds the reviewer fleet). Pool size scales with each fill's actual edge; the split is fixed. Alice may simultaneously offer paid consulting services to teams who want to integrate her adapter.
ALLOWED
02
Bob runs "FastBridge by Bob" on a fork
Bob forks taifoon-solver and taifoon-eco/contracts, removes the recordRevenueTouch() call from the executor path, redeploys the contracts under a different name, and offers FastBridge by Bob as a hosted SaaS that charges users for cross-chain swaps. The value derives entirely from Taifoon's adapter fleet, AND the donut is bypassed. Both rule 1 (internal business purposes only) and rule 4 (preserve the on-chain donut) are violated.
NOT ALLOWED
03
A protocol team rebalances its own treasury via Taifoon
The team integrates Taifoon as the back-end of their internal treasury rebalancer. Treasury credentials never leave the team. No external customers access the integration. The donut still routes on every settled call. This is internal business use under rule 1, fully allowed.
ALLOWED
04
The same team turns it into a paid consumer product
The protocol team turns the rebalancer into a public product, charging end-users to rebalance their wallets via Taifoon's adapters, and arranges billing such that fees never flow through BuildersRegistry. The fact that the adapter calls still execute does not make this allowed. The donut must be preserved on every paid call routed through the fleet.
NOT ALLOWED
05
A protocol publishes its own adapter and earns donut perpetually
Across, deBridge, Mayan, Hyperlane, LiFi, Squid, CCIP, Stargate — any protocol can ship a first-party adapter that routes its own user volume through Taifoon. The donut routes 20% of every fill's realized spread perpetually to the protocol's wallet (the merged author), while the solver running the pod takes the 70% operating cut. This is the recommended path for protocols who want non-extractive solver access and provable settlement under V5.
ALLOWED

[ WHERE TO FIND THINGS ]

Operative documents and on-chain references.

[ LICENSE QUESTIONS ]

For commercial license inquiries, enterprise terms (LICENSE_EE.md), or any question about whether your use case fits within TSUL's four rules — reach out. We're happy to talk.taifooon@proton.me