ApeBond

ApeBond (ABOND) — 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).

ApeBond — a DeFi / Bonds project: a decentralized “bonds” platform (discounted purchase of partner projects’ tokens with vesting) and the ABOND utility token for tier mechanics/real yield (official documentation). AI component is not described in Tier‑1, so per the DecAIHub methodology DecAI Fit = 0/6 (ai_score = 0).

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 “bonds” platform — purchasing tokens at a discount and with vesting.
Who it’s for: DeFi users who participate in bonds; partner projects that need liquidity/treasury.
Why onchain/token: the product and the ABOND token are onchain; at the same time, the project does not belong to Decentralized AI (AI is not confirmed).

How it works (very briefly)

The user does: buys a bond (partner tokens at a discount) and waits for/claims the unlock per the vesting.
The system does: manages the purchase/vesting via smart contracts and (claim) the ecosystem liquidity/treasury mechanics.
The user gets: partner tokens per the vesting schedule; additional utilities via ABOND (tier staking/real yield).
Where the blockchain is: smart contracts and the ABOND token (multi‑chain); addresses and Safe multisigs are published in the docs.
Token role (if any): ABOND is needed for tier points, discounts on bonds and real yield (docs).

Quick links: AI thesis fit

Project passport

Field	Value
Project name	ApeBond
Also known as (aliases)	ABOND, ApeBond DAO
Logo (logo)	—
Token symbol (ticker)	ABOND
Category	DeFi \| Bonds \| Infra
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	0x34294afabcbaffc616ac6614f6d2e17260b78bed (BNB Chain)
Token model (token_type)	utility (tier points + discounts + real yield)
Max supply	650,000,000 ABOND (BscScan Max Total Supply)
Issuance	fixed supply (per the explorer data)
Tokenomics (tokenomics, brief)	tokenomics (docs): Migration 39.1%, Ecosystem Fund 15%, Multiplier Buffer 14.9%, Fundraise 10%, Treasury 10%, Team 5% (3y linear vesting), Bonus Bucket 5%, Initial Liquidity 1%.
Governance	DAO (claim; governance upcoming)
Admins/keys	multisig (Safe), addresses published in the docs
Audit	yes (Paladin; Halborn; Sherlock — per the docs)
Bug bounty	—
Team (team)	—
Funding (investors/funding)	—
AI component (ai_component)	—
Use‑case (use_case)	bonds + tier staking rewards
DecAI Fit — AI thesis fit	0/6 — no AI reality and no AI intent (ai_score=0)
DecAI Fit component summary	0 / 3 / 1 / 2
Last verified	2026-02-11

Links (links_*)

Type	Link
Website	https://ape.bond/
Docs	https://docs.ape.bond/apebond
GitHub	https://github.com/ApeSwapFinance
Releases / Changelog	https://apebond.medium.com/
Whitepaper	https://docs.ape.bond/apebond
Roadmap	https://ape.bond/roadmap
Security advisories	—
Explorer (BSC)	https://bscscan.com/token/0x34294afabcbaffc616ac6614f6d2e17260b78bed
Explorer (ETH)	https://etherscan.io/token/0xe6828d65bf5023ae1851d90d8783cc821ba7eee1
X	https://twitter.com/ApeBond
Discord	https://discord.gg/g3A5T6VSFr
Telegram	https://t.me/ape_bond
Medium	https://apebond.medium.com/
Audit report(s)	https://docs.ape.bond/apebond/where-dev/security
Bug bounty	—
CoinGecko (profile, reference)	https://www.coingecko.com/en/coins/abond
CoinMarketCap (profile, reference)	https://coinmarketcap.com/currencies/apebond/

General project overview

ApeBond describes itself as a “decentralized platform” where users can buy partner projects’ tokens at a discount, but with a vesting period (usually 14–60 days), while projects receive long‑term liquidity/a treasury boost (official documentation). Within the ecosystem, the ABOND token is used: locking/staking it provides tier points and unlocks utilities such as additional discounts and real yield (docs).

Features/modules

Bonds: purchasing partner tokens at a discount + vesting (docs).
ABOND tier points: locking/staking ABOND for discounts/access to special bonds (docs).
Real Yield: staking ABOND and receiving rewards in WBNB (docs).
Multi‑chain: ABOND is present on BNB Chain, Ethereum, Polygon (docs).

Typical scenarios

Scenario 1 (bonds): a user buys a bond → waits for the vesting period → claims the partner tokens (docs).
Scenario 2 (tier staking): a user stakes/locks ABOND → receives tier points → receives additional discounts/real yield (docs).

Getting started (wallet/network)

What you need: an EVM wallet; access to the ApeBond interfaces.
Network/chain: ABOND is listed in the docs as multi‑chain (BSC/Ethereum/Polygon).
Fees: gas of the respective network for onchain operations.

Architecture/tech (non‑AI)

Components: bonds/vesting smart contracts (docs), the ABOND token, Safe multisigs for administration/treasury (security docs).
Participant roles: bonds users; partner projects; ABOND holders; administrators/multisig signers.
Where logic runs: the core logic — onchain (smart contracts); interfaces/content/some processes — offchain.
Dependencies: EVM networks (BSC/Ethereum/Polygon, etc.); Safe.

Token/economics (expanded, no forecasts)

Token utility: tier points via locking/staking, Discount Boost, Special Bonds, Real Yield; governance (upcoming) for emissions (docs).
Protocol necessity drivers: ABOND is needed for tier mechanics; the bonds product itself is onchain (docs).
Who pays fees: users pay network gas; the protocol fee flows are not consolidated into a single “fees” document in the extracted Tier‑1.
Where fees go: real yield is described as a distribution of revenue to users staking ABOND (docs).
Issuance/burn: max supply per the explorer; the tokenomics distribution is in the docs.
Security/incentive mechanisms: staking pools with lock periods/multipliers (docs).
Distribution and token issuance schedule: the tokenomics page (docs), including 3‑year team vesting.
Treasury: Safe multisigs for the treasury are published in the security docs.

Governance

Who makes decisions: governance is described as upcoming (emissions via on‑chain governance and also off‑chain governance) (ABOND token docs).
How protocol parameters change: — (no specific procedures in the extracted Tier‑1).
Where decisions are discussed/made: —.
Keys/multisig: Safe addresses are listed in the security docs.

Security and incidents

Audits: Paladin (regularly, claim), Halborn (Real Yield), Sherlock (Solana bonds) — per the security docs.
Bug bounty: —.
Incidents: —.
Threat model: the risk of errors in the bonds/vesting contracts; risks of administrative keys/multisigs; cross‑chain risks when bridging ABOND.

Project status and timeline

Current status: the docs are available; the product is functioning; a roadmap page exists.
Key releases/milestones: —.
Roadmap: https://ape.bond/roadmap

Ecosystem/integrations

Integrations: Safe (multisig), multi‑chain deployments of ABOND, partner bonds (docs).
Partners: — (we do not record logos as evidence without terms).
Where it’s actually used: the ABOND token is confirmed onchain; smart contracts/multisig addresses are published in the docs.

AI component of the project

What is real AI here? in the extracted Tier‑1 there are no AI models/agents/ML functions.
What is truly onchain? the bonds mechanics, the ABOND token and the published addresses of smart contracts/multisigs (docs).
Why is a token needed? tier points/discounts/real yield and (upcoming) governance of emissions (docs).
Red flags (based on the information found): the project is not about AI (ai_score=0); multi‑chain/bridges add risk; administrative powers require trust in the multisig.

DecAI Fit component summary

DecAI Fit: 0/6 — no AI reality and no AI intent (ai_score=0)

Component	Level	Score
AI reality	absent	0
Onchain necessity	high	3
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): in the extracted Tier‑1 there is no roadmap/declaration regarding an AI module.
Evidence: Tier‑1 — https://docs.ape.bond/apebond
Why sufficient / why not (one line): AI intent requires an explicit Tier‑1 item.
Conflict note (if any): —

AI_1 — what the AI does (1/0)

AI_1 (decision): 0
Claim (one line): AI features are not described.
Evidence: Tier‑1 — https://docs.ape.bond/apebond
Why sufficient / why not (one line): the project is described as a DeFi bonds platform.
Conflict note (if any): —

AI_2 — demos/examples (1/0)

AI_2 (decision): 0
Claim (one line): there is no demo of an AI component (the AI component is not described).
Evidence: Tier‑1 — https://docs.ape.bond/apebond
Why sufficient / why not (one line): not applicable.
Conflict note (if any): —

AI_3 — metrics/quality (1/0)

AI_3 (decision): 0
Metrics: —.
Context (version/date/how measured): —.
Evidence: Tier‑1 — https://docs.ape.bond/apebond
Why sufficient / why not (one line): not applicable.
Conflict note (if any): —

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

AI_4 (decision): 0
Claim (one line): there is no AI architecture.
Evidence: Tier‑1 — https://docs.ape.bond/apebond
Why sufficient / why not (one line): not applicable.
Conflict note (if any): —

Onchain necessity

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

OC_1 (decision): 1
Chain: BNB Smart Chain (primary), also Ethereum/Polygon (multi‑chain ABOND)
Addresses/identifiers: ABOND (BNB): 0x34294afabcbaffc616ac6614f6d2e17260b78bed; ABOND (Ethereum): 0xe6828d65bf5023ae1851d90d8783cc821ba7eee1 (docs).
Evidence: Tier‑1 — https://docs.ape.bond/apebond/products-and-features/abond ; https://bscscan.com/token/0x34294afabcbaffc616ac6614f6d2e17260b78bed ; https://etherscan.io/token/0xe6828d65bf5023ae1851d90d8783cc821ba7eee1
Why sufficient / why not (one line): the docs and explorers confirm the token addresses.
Conflict note (if any): —

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

OC_2 (decision): 1
What useful logic is onchain: bonds/vesting contracts and the published Safe addresses for administration/treasury (security + smart contracts docs).
Evidence: Tier‑1 — https://docs.ape.bond/apebond/where-dev/smart-contracts ; https://docs.ape.bond/apebond/where-dev/security
Why sufficient / why not (one line): addresses of contracts and multisig wallets are provided.
Conflict note (if any): —

OC_3 — onchain is critical (1/0)

OC_3 (decision): 1
“Replace the blockchain” test: bonds with vesting and the tokenized discount/staking logic require smart contracts; without onchain, enforceability and verifiability are lost.
Evidence: Tier‑1 — https://docs.ape.bond/apebond ; https://docs.ape.bond/apebond/products-and-features/tier-staking-and-real-yield
Why sufficient / why not (one line): the core product is described as a DeFi smart contract platform.
Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

TK_0 (decision): 0
Claim (one line): the project has a token, ABOND.
Evidence: Tier‑1 — https://docs.ape.bond/apebond/products-and-features/abond ; https://bscscan.com/token/0x34294afabcbaffc616ac6614f6d2e17260b78bed
Why sufficient / why not (one line): the token is confirmed by the docs + explorer.
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): in the extracted Tier‑1, ABOND is not described as a mandatory means of payment for access to the product.
Evidence: Tier‑1 — https://docs.ape.bond/apebond/products-and-features/abond
Why sufficient / why not (one line): the utility is described via tier/discounts/yield, not as “payment for the service”.
Conflict note (if any): —

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

TK_2 (decision): 1
Claim (one line): staking/locking ABOND provides tier points and real yield (WBNB), with multipliers by term.
Evidence: Tier‑1 — https://docs.ape.bond/apebond/products-and-features/tier-staking-and-real-yield ; https://docs.ape.bond/apebond/products-and-features/abond
Why sufficient / why not (one line): staking pools and the yield mechanics are described.
Conflict note (if any): —

TK_3 — governance (1/0)

TK_3 (decision): 1
Claim (one line): governance utility is claimed as upcoming: decisions on emissions via on‑chain governance (votes/bribes) and also off‑chain governance.
Evidence: Tier‑1 — https://docs.ape.bond/apebond/products-and-features/abond
Why sufficient / why not (one line): the governance role is explicitly described as an upcoming utility.
Conflict note (if any): —

TK_4 — token is replaceable (1/0)

TK_4 (decision): 1
Claim (one line): discounts/tiers/yield could be implemented via another token/accounting/LP positions; the strict irreplaceability of ABOND is not proven per Tier‑1.
Evidence: Tier‑1 — https://docs.ape.bond/apebond/products-and-features/abond
Why sufficient / why not (one line): the utility describes the advantages for holders, but does not prove that ABOND specifically is mandatory as the only possible asset.
Conflict note (if any): —

Evidence (table)

Tier	Source	What it proves
Tier‑1	https://docs.ape.bond/apebond	What ApeBond is and how bonds work (discount + vesting).
Tier‑1	https://docs.ape.bond/apebond/products-and-features/abond	ABOND: contracts (BSC/ETH/Polygon) and utility (tiers/discounts/yield/governance upcoming).
Tier‑1	https://docs.ape.bond/apebond/products-and-features/abond/tokenomics	Tokenomics distribution of ABOND and team vesting.
Tier‑1	https://docs.ape.bond/apebond/products-and-features/tier-staking-and-real-yield	Tier staking & real yield: pools, multipliers and WBNB rewards.
Tier‑1	https://docs.ape.bond/apebond/where-dev/security	Audits (Paladin/Halborn/Sherlock claim) and Safe multisigs (addresses).
Tier‑1	https://docs.ape.bond/apebond/where-dev/smart-contracts	List of onchain contracts and the ABOND token address (BSC).
Tier‑1	https://bscscan.com/token/0x34294afabcbaffc616ac6614f6d2e17260b78bed	The onchain ABOND token on BSC (max total supply).
Tier‑1	https://etherscan.io/token/0xe6828d65bf5023ae1851d90d8783cc821ba7eee1	Onchain representation of ABOND on Ethereum.