Skip to main content

Orizon

Orizon (ORI) — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).

Orizon — an AI/Other / DeFi project on BNB Smart Chain (EVM) that claims a “DeFAI” model: revenue from AI services (chatbots/image generation/APIs) is directed into an onchain treasury/mechanism and distributed as yield to stakers of the ORI token.

Disclaimer

Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.

TL;DR (for readers who are not into AI)

  • What it is: a DeFi protocol/token mechanism that promises to distribute yield to stakers from the revenue of AI services.
  • Who it’s for: ORI holders/stakers; users of the AI services (in theory — the source of revenue).
  • Why onchain/token: ORI is used for staking/rebase/referral and “contribution” rewards; some of the mechanics are described as onchain contracts.

How it works (very briefly)

  1. The user does: uses ORI and (per the docs) stakes the token to receive “rebase yield”.
  2. The system does: calculates and distributes rewards (including the referral and contribution model); burn conditions for the continuation of rewards are possible.
  3. The user gets: accruals of yield/rewards in the ORI token (per the protocol rules).
  4. Where the blockchain is: ORI is a BEP‑20 on BNB Smart Chain; the docs describe contracts for staking/vesting/referral reward mechanics.
  5. Token role (if any): ORI is the base asset of the protocol (staking/rebase/fees on sales).

Quick links: AI thesis fit

Project passport

Field Value
Project name Orizon
Also known as (aliases) Orizon DeFAI; ORI; @orizon_defai
Logo (logo) ../assets/155_orizon_logo.png
Token symbol (ticker) ORI
Category AI/Other | DeFi
Primary chain (chain) BNB Smart Chain
Type EVM
Network status mainnet
Consensus (consensus) PoSA (BNB Smart Chain; 21 validators)
Launch date (launch_date) —
Project status (status) active
Token (standard) BEP-20
Token contract 0xDA033999bB6165e64DB01Bd9be14B40f5653092E
Token model (token_type) utility (fee-mechanism)
Max supply “No fixed total supply” (per the docs); the current onchain “Max Total Supply” on BscScan: 265,007.3136 ORI (may change).
Issuance minting‑based (variable) + burn conditions for the continuation of rewards (per the docs).
Tokenomics (tokenomics, brief) 0% fee on purchases and 5% on sales; fee allocations: 2% DAO ops/dev, 1.5% community, 1.5% marketing.
Governance — (Tier‑1 contains no description of a governance process; “DAO operation” appears as a budget item)
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI services as a revenue source
Use‑case (use_case) yield for stakers from "AI productivity"
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 1 / 2 / 1 / 2
Last verified 2026-02-11

General project overview

In its documentation, Orizon describes the concept of “DeFAI” (Decentralized Finance + Artificial Intelligence): a set of AI services (chatbots, image generation, developer APIs) generates revenue, and this revenue is then “channeled” into an onchain treasury/reserve and distributed as yield to ORI holders/stakers. This is more of an economic model and token mechanism around “AI‑utility revenue” than a technical AI protocol with described models.

Features/modules

  • DeFAI positioning: an “AI‑powered financial reserve system” and the promise of yield “from real AI productivity”.
  • ORI token mechanics: minting‑based issuance, trading fee rules (sell tax) and fee allocation.
  • Staking / rebase yield: the operating mechanism section mentions rebase issuance, vesting and accrual rules.
  • Contribution / referral model: formulas for “contribution value yield” and direct referral yield in the docs.
  • Burn conditions: a mechanism is described where burning ORI may be required to continue receiving contribution rewards.

Typical scenarios

  • Scenario 1 (staker): stakes ORI → receives rebase/yield (per the protocol’s terms).
  • Scenario 2 (referrals): invites others to stake → receives a share of the yield from the referrals’ staking (per the docs).
  • Scenario 3 (contribution): participates in the “community computing power”/structure → receives contribution rewards; upon reaching a threshold, a burn of tokens may be required.

Getting started (wallet/network)

  • What you need: an EVM wallet (BNB Smart Chain).
  • Network/chain: BNB Smart Chain (BSC).
  • Fees: BSC network fees; per the docs — 0% on purchases and 5% on sales (sell tax), plus the protocol’s onchain fees (if applicable).

Architecture/tech (non‑AI)

  • Components: the ORI token (BEP‑20), “staking/yield vesting” and reward contracts (per the description in the Gitbook), the offchain part of the AI services as the source of revenue.
  • Participant roles: stakers, referrals, participants in the “contribution” scheme; the operator/team (as the managing party of the AI services and the distribution of revenue — by implication, without disclosure of the structure).
  • Where logic runs: the token and the accrual/accounting of yield — onchain; the AI services themselves and the revenue — offchain.
  • Dependencies: BSC infrastructure (RPC), integrations with offchain AI services (not described technically).

Token/economics (expanded, no forecasts)

  • Token utility: ORI is used in the staking/rebase/reward mechanics (referral + contribution), as well as in the trading rules (sell tax).
  • Fees: 0% on purchases and 5% on sales; fee allocations in the docs: 2% DAO ops/dev, 1.5% community, 1.5% marketing.
  • Issuance: the token overview states that ORI is “minting‑based” and has no fixed total supply; BscScan shows the current max total supply on BSC at the time of the check.
  • Burn: a mechanism is described whereby, upon reaching a “fivefold” threshold of contribution rewards, the destruction of an equivalent amount of ORI is required to continue receiving yield.
  • Incentives: referral yield (10% of the referrals’ rebase yield in each round), contribution yield and bond‑sharing reward — described by formulas in the Gitbook.
  • Treasury: an “on-chain treasury/DAO operation budget” is mentioned at the conceptual level; the addresses/rules of treasury management are not disclosed in Tier‑1.

Governance

  • Who makes decisions: not disclosed in Tier‑1 (“DAO operation” appears as the purpose of part of the fee).
  • Keys/multisig: — (no data).

Security and incidents

  • Audits / bug bounty: not found in the Tier‑1 sources used.
  • Threat model: correctness risks of the token mechanics (rebase/vesting/burn), centralization risks of decision‑making, the risk of a mismatch between “AI revenue” and the onchain distribution.

Project status and timeline

  • Current status: active (there are docs and a token on BSC).
  • Roadmap: the Gitbook has a section “ORIZON Development and Expansion Plan”.

Ecosystem/integrations

  • Integrations/cases: not compiled while filling in this card (a separate list of actual clients/AI services and onchain contracts is needed).

AI component of the project

  • What is real AI here? The whitepaper claims AI services (chatbots, image generation, developer APIs) as a source of “real-world AI productivity”, but without a technical description of the models/quality.
  • What is truly onchain? The ORI token on BSC and the contracts/mechanics described in the docs for staking/rebase/vesting/referrals and burn conditions.
  • Why is a token needed? ORI is the unit of account for staking and the distribution of yield/rewards; a 5% fee on sales with the specified allocation is also applied.
  • Red flags (based on the information found): AI‑washing — AI is described as “services/revenue”, but without proof of quality/implementation; onchain‑washing — there are no addresses of the protocol’s key contracts other than the token; token‑washing — the “no fixed supply” model conflicts with the supply displayed in the explorer; reconciliation is needed.

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality low 1
Onchain necessity medium 2
Token necessity low 1
Evidence Tier‑1 present 2
Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

  • AI_0 (decision): 0
  • Claim (one line): — (there is AI_1: AI services are described as a source of revenue).
  • Evidence: Tier‑1 — https://orizon-4.gitbook.io/orizon-defai
  • Why sufficient / why not (one line): AI_0 is set only if AI_1..AI_4 = 0.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): AI services (chatbots, image generation, developer APIs) are claimed that generate revenue for the yield model.
  • Evidence: Tier‑1 — https://orizon-4.gitbook.io/orizon-defai
  • Why sufficient / why not (one line): The whitepaper page lists the AI services as part of the product/economy.
  • Conflict note (if any): No technical details/quality verification (AI_4=0, AI_3=0).

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): No public Tier‑1 demos of the AI services in operation were found in the docs.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is a description, but without a demonstration of results.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Quality metrics/benchmarks of the AI services are not provided.
  • Conflict note (if any): —

AI_4 — tech description/architecture/versions (1/0)

  • AI_4 (decision): 0
  • Claim (one line): A technical description of the models/pipelines of the AI services is not disclosed.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is a product list of AI services, but without architecture/versions/implementation.
  • Conflict note (if any): —

Onchain necessity

OC_1 — contracts/addresses/chain (1/0)

  • OC_1 (decision): 1
  • Chain: BNB Smart Chain (BSC)
  • Addresses/identifiers: ORI token contract 0xDA033999bB6165e64DB01Bd9be14B40f5653092E
  • Evidence: Tier‑1 — https://bscscan.com/token/0xDA033999bB6165e64DB01Bd9be14B40f5653092E ; https://orizon-4.gitbook.io/orizon-defai/ori-token-overview
  • Why sufficient / why not (one line): The contract and the network are confirmed by the explorer and repeated in the docs.
  • Conflict note (if any): The docs say “no fixed total supply”, while the explorer shows the current max total supply (may change).

OC_2 — onchain beyond just a token (1/0)

  • OC_2 (decision): 1
  • What useful logic is onchain: The docs describe onchain contracts/mechanics for staking yield vesting and contribution/referral reward distributions (rebase output, vesting, burn conditions).
  • Evidence: Tier‑1 — https://orizon-4.gitbook.io/orizon-defai/operating-mechanism-of-the-protocol/contribution-value-algorithm-contract
  • Why sufficient / why not (one line): The Gitbook has a section “Operating Mechanism … Contract” with formulas and accrual/issuance rules.
  • Conflict note (if any): The addresses of these contracts are not specified in Tier‑1.

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: without a blockchain, the economic model can be implemented with centralized accounting; the necessity of trustless properties is not substantiated in Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no explicit argumentation that “without onchain a key property breaks down”.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, ORI (BEP‑20 on BSC).
  • Evidence: Tier‑1 — https://bscscan.com/token/0xDA033999bB6165e64DB01Bd9be14B40f5653092E
  • Why sufficient / why not (one line): The explorer confirms the token contract.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 0
  • Claim (one line): No statement was found in Tier‑1 that ORI is a mandatory payment for the AI services.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): The docs focus on staking/yield; a payment role for the service is not described.
  • Conflict note (if any): —

TK_2 — incentives/collateral/penalties (1/0)

  • TK_2 (decision): 1
  • Claim (one line): Staking/rebase yield and additional reward mechanics (referral/contribution), including burn conditions for the continuation of rewards.
  • Evidence: Tier‑1 — https://orizon-4.gitbook.io/orizon-defai/operating-mechanism-of-the-protocol/contribution-value-algorithm-contract
  • Why sufficient / why not (one line): The docs describe the reward pool, rebase output and burn‑related conditions.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): Governance mechanics via the token are not described.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Tier‑1 has “DAO operation and development” as the purpose of part of the fee, but without voting/processes.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): The claimed economic model is built around ORI (staking/rebase/rewards), i.e. the token is embedded in the protocol mechanism.
  • Evidence: Tier‑1 — https://orizon-4.gitbook.io/orizon-defai/operating-mechanism-of-the-protocol/contribution-value-algorithm-contract
  • Why sufficient / why not (one line): The described reward formulas are denominated in ORI and depend on the ORI stake.
  • Conflict note (if any): In the absence of contract addresses, the risk of a “marketing” formulation remains.

Evidence (table)

Tier Source What it proves
Tier‑1 https://orizon-4.gitbook.io/orizon-defai AI services as a source of revenue and the general DeFAI concept.
Tier‑1 https://orizon-4.gitbook.io/orizon-defai/ori-token-overview Statements about issuance/trading rules (sell fee 5%) and the ORI contract address.
Tier‑1 https://orizon-4.gitbook.io/orizon-defai/operating-mechanism-of-the-protocol/contribution-value-algorithm-contract Reward mechanics (rebase output, contribution/referral, burn conditions).
Tier‑1 https://bscscan.com/token/0xDA033999bB6165e64DB01Bd9be14B40f5653092E Onchain confirmation of the ORI token on BSC and of the current max total supply.
Tier‑2 — —
Tier‑3 — —

No comments to display

Back to top