The Taifoon Sustainable Use License.
You can play with Taifoon’s toys for your own work, for free. You can share them with friends for free. Keep our name on them. If you build a new piece and people use it to move value, a small slice comes back to you. The one thing you can’t do is take our box, scratch off our name and sell it.
Version 1.1 is in force from 2026-10-20: rule 9 (preserve the meter), rule 10 (resale under a key), and three new documents: the Access Terms, the Enterprise License and the Vault Grant. All four are made with Interop FZCA, Dubai, United Arab Emirates.
Four rules.
Quoted from the license file. Where this page and the file differ, the file wins.
- 01You may use or modify the software only for your own internal business purposes or for non-commercial or personal use.
- 02You may distribute the software or provide it to others only if you do so free of charge for non-commercial purposes.
- 03You may not alter, remove, or obscure any licensing, copyright, donut routing, or other notices of the licensor in the software. Any use of the licensor’s trademarks ("Taifoon", the orbital trace, the singularity glow) is subject to applicable law.
- 04Any deployment that routes value through Taifoon’s adapter fleet must preserve the on-chain donut. A 49 bps skim of every settled call is routed through BuildersRegistry.recordRevenueTouch() and split: 70% to the contributor whose adapter routed the value, 20% to the reviewer agents that certified it, 10% to the ecosystem treasury. Removing, circumventing, or substituting donut routing — including via fork-and-rehost, calldata pre-processing that bypasses the registry, or proxy patterns that hide the adapter call — constitutes a license violation.
The slice comes back.
49 bps of every settled call that routes through an adapter, split three ways. The registry that enforces it on chain is not deployed yet; until it is, the split is applied in the platform’s own code and the license is enforced as a license.
What is allowed, and what is not.
All use is allowed unless you sell something whose value comes from Taifoon, or you bypass the donut.
- Coordinating cross-chain data flows your own organization controls.
- Building a Taifoon adapter for your protocol.
- Consulting: building adapters, reviewer agents, integrations, operations.
- Running mirrors and maintaining Taifoon on your own infrastructure.
- Contributing back, and earning your slice on every settled call your contribution routes.
- White-labeling Taifoon and selling it to your customers.
- Hosting the solver core or adapter fleet for a fee without the on-chain donut.
- Forking the registry, removing the donut clause, and running it as a competing marketplace.
- Replacing recordRevenueTouch() with a no-op, or stripping the registry call.
- Using "Taifoon" or a confusable mark in the name of a hosted competing service.
Need something else? Ask.
A commercial agreement covers what the four rules do not.