Orbofi
Orbofi: Tokenized vs Non-Tokenized AI Agents
Orbofi lets creators build agents without issuing a coin or connect an agent to an Autonomous Agentic Coin (AAC), a tradable ERC-20 token linked to its brain. Tokenization adds an on-chain asset; the agent still needs configured capabilities and a runtime to perform its tasks.
Tokenized and non-tokenized options
| Dimension | Non-tokenized agent | Tokenized agent |
|---|---|---|
| Agent form | A utility-only or entertainment agent without an associated agent coin. | An agent connected to an ERC-20 AAC. |
| On-chain trading | No agent coin is issued for trading as part of this form. | The associated AAC can be traded on-chain. |
| Functional capabilities | Depend on the selected models, knowledge, tools, and integrations. | Depend on the selected models, knowledge, tools, and integrations, with a separate token layer. |
Capabilities come from the agent configuration
Orbofi's modular framework combines AI models with custom tools and knowledge bases. Its configurable capabilities include on-chain and off-chain actions, so token issuance and the actions an agent performs are separate parts of the design.
Social behavior is another configurable capability. Orbofi describes agents that interact through clients including X, Telegram, Discord, and GitHub. Those connections support uses such as posting content and interacting with communities. A particular agent's ability to perform that work depends on its selected tools and connected services.
The coin's tradability does not establish the quality of an answer, the usefulness of generated content, or the presence of a particular tool.
The coin and the running agent
Orbofi's AAC design connects the token's on-chain record to a content-addressed agent brain. A compatible runtime can retrieve that brain, verify its contents cryptographically, and execute it.
The runtime supplies the computing environment in which the agent works. Trading the ERC-20 token and executing the agent are distinct operations: a token trade alone does not demonstrate that an agent has completed a task or started running in another environment.
Example: A community assistant with an optional coin
In this hypothetical example, a creator wants a community assistant to answer questions from a project knowledge base and publish updates through Telegram. Assume that the knowledge base and a working Telegram integration are configured, and that the assistant has no trading tools. The creator is deciding whether making the agent tradable would also make it capable of trading.
Orbofi's non-tokenized option matches the assistant-service requirement. Choosing the AAC form adds an ERC-20 agent coin that can be traded on-chain. With the hypothetical configuration unchanged, the assistant still has its knowledge and publishing capabilities, but no configured tool for placing trades.
Trade execution would require supported trading tools and configuration. The assistant's question-answering and publishing functions remain dependent on the configured knowledge base and working Telegram connection.
