Bitbond: asset tokenization suite — Token Tool, Offering Manager, Solana SPL/Token-2022

Bitbond: asset tokenization suite — Token Tool for deploying compliant tokens (including Solana SPL and Token-2022), and Offering Manager for the full primary-market workflow banks and asset managers actually run.

Docs hub: docs.bitbond.com/asset-tokenization-suite (llms.txt). Product: bitbond.com. Token Tool app: tokentool.bitbond.com. Offering Manager: om.bitbond.com. X: @Bitbond.

Click to zoom

What the suite is

Bitbond positions itself as the tokenization stack for banks, asset managers, and corporate issuers. The docs split cleanly into two products:

1. Token Tool — no-code studio (and API/MCP) for deploying tokens and NFTs, running on-chain sales, lockers, airdrops, payment automation, and portfolio tracking across 11+ chains.
2. Offering Manager — end-to-end primary issuance: investor onboarding, KYC, multi-payment rails, white-label invest pages, order/allocation management, and post-issuance servicing.

Rule of thumb: use Token Tool when you need the on-chain instrument fast (or programmatically). Use Offering Manager when you need the regulated distribution desk around that instrument.

Token Tool: deploy without writing the contract

From the Token Tool intro: connect a Web3 wallet, configure the token in the UI (or API), and deploy audited factory contracts. Token Tool is non-custodial — the creator wallet owns the deployed contracts. Contracts are CertiK-audited (token sale contracts also AuditOne).

Feature surface builders care about:

• Create / manage tokens (utility + “asset token” compliance knobs)
• Token sales (presale-style on-chain sales)
• Airdrops (custom + autofill; NFTs too)
• Token lockers
• Automate payments — streams, vesting, delivery-vs-payment (DvP)
• NFT create/manage
• Portfolio tracking, chain records, testnet faucets

Chains — and where Solana sits

Supported networks include Ethereum (+ Sepolia), Polygon, Avalanche, Arbitrum, Optimism, BNB Chain, Base (+ Base Sepolia), peaq, Solana (+ Devnet), Stellar, and XRPL (limited but evolving).

On Solana specifically, Token Tool targets SPL and Token-2022 (transfer hooks, interest-bearing tokens, access control — as Bitbond documents them). Login via Phantom and other WalletConnect-capable wallets. Factory / whitelist address published in docs:

Solana mainnet + devnet factory:
Ee3hNRX7Gkway5xrcRzoPw9QHDAMpLKegbwX87kXeo14

Whitelist this if your custody only allows outbound to known programs.

EVM still dominates the compliance-token feature matrix (ERC-20 + ERC-1400-family flags: pause, blacklist, force transfer, whitelist, document URI, per-address caps, transfer tax/burn fees). On Solana, treat feature parity as evolving — verify the exact toggles for SPL vs Token-2022 in the live Token Tool UI before you promise a client MiCA- or STO-grade controls on-chain.

Token Tool API

The Token Tool API is custody-agnostic and API-first: your wallet receives a contract-call transaction (calldata against the Token Tool factory) and signs it. Lifecycle actions after deploy (mint, burn, transfer, sales, payment automation, NFTs) hit the deployed contracts the same way — UI or code.

Official examples (ethers.js + custody variants): github.com/bitbond/token-tool-api-example. Use case they emphasize: many tokens created automatically in a short window (platforms, white-label issuers, batch RWA programs).

TokenTool MCP — agents on the issuance path

Bitbond exposes Token Tool through MCP:

User / app
   → AI agent (MCP client)
   → Token Tool MCP server
   → Token Tool API
   → on-chain contracts

Documented capabilities via MCP: create tokens (ERC-20, SPL Token-2022), lifecycle (mint/burn/pause/transfer ownership), NFTs, sales config, interact with deployed contracts. Repo: github.com/bitbond/token-tool-mcp.

Same non-custodial rule as the UI: the agent does not hold keys; a wallet/custody provider must sign. Pair this mentally with PayBox / Avici / x402-style agent money stacks — Bitbond is the issuance side, not the spend card.

Offering Manager: the primary market desk

Offering Manager is for issuers running STOs/ICOs with real investors:

• Multiple concurrent offerings (pricing, caps, dates, rules)
• Payments: SEPA/wire, Checkout.com cards, Coinbase Commerce, on-chain stablecoins
• KYC via Sumsub or Blockpass; country blocks; document agreements
• Investor wallet policy: byo_only, investor_choice, or custodial_only (Tangany — EVM today per docs)
• Invest page builder, embeddable checkout/portfolio widgets, audit trail, team + partners
• Export funded investor addresses for distribution (EVM, Solana, other supported chains) — often into Token Tool airdrops

Plans: Free (sandbox limits), Professional, Enterprise. API base: https://om.bitbond.com/api/public; interactive OpenAPI at om.bitbond.com/api/docs. Investor-protected routes use a Privy bearer token; issuer admin APIs use tenant API key (Enterprise) or session JWT.

Builder mental model

Offering Manager                    Token Tool
─────────────────                   ─────────────────
KYC / payments / invest UX          Deploy SPL / Token-2022 / ERC-20
Orders & allocations                Sales, lockers, vesting, DvP
Export investor wallets    ──CSV──► Airdrop / distribute
Compliance narrative                On-chain controls (chain-dependent)

Agents: TokenTool MCP  →  sign with custody  →  chain finality

When to reach for Bitbond vs pure Solana DIY

• Bitbond — need audited no-code issuance, multi-chain parity, primary-market KYC rails, or agent MCP without standing up your own factory.
• DIY Solana (Token-2022 + Streamflow + your KYC) — full control, custom transfer hooks, tighter program UX, no Bitbond fee surface.
• Hybrid — Offering Manager for capital formation; distribute on Solana via Token Tool or your own programs from the export CSV.

Practical start

1. Read overview.md and pick Token Tool vs Offering Manager.
2. Solana path: Token Tool → select Solana / Devnet → Phantom → create SPL or Token-2022; whitelist factory if custody-restricted.
3. Automate: clone token-tool-api-example or wire token-tool-mcp.
4. Full offering: om.bitbond.com → KYC + payments → invest page → export wallets → distribute.

Resources

• Asset Tokenization Suite docs
• Token Tool intro · API · MCP
• Offering Manager intro · OpenAPI
• API examples · MCP server
• Streamflow (vesting/locks on Solana) · Token-2022 field guide
• Bitbond on DevRels

Bottom line

Bitbond is a practical RWA/issuance stack: Token Tool for multi-chain token factories (Solana SPL/Token-2022 included), Offering Manager for KYC’d primary markets, plus API and MCP so backends and agents can issue without re-implementing factories. Use it when speed and compliance packaging matter; drop to native Solana programs when you need full Token-2022 surface area and no intermediary fee path.