Manifest Trade exchange profile

Manifest Trade is a Solana exchange built around an on-chain central limit order book. Traders can interact through its application, wallet integrations or software that routes into the shared market. The protocol has separate core, wrapper and client components; an application’s convenient controls should not be confused with the entire protocol’s available instruction set.[1]

The official overview describes permissionless creation of token-pair markets, expandable account storage and distribution through wallets and aggregators. Availability of a market does not establish issuer quality or usable depth at a particular size. A token’s mint address and executable book matter more than a familiar display symbol.[2]

DefiLlama reported US$3,383,821,728 in rolling 30-day spot volume at 20:11:22 UTC on 20 October 2026. This protocol-level turnover includes routed activity and is not a count of users of Manifest’s own interface.[3]

Reverse orders are designed as continuing liquidity rather than expiring ordinary orders. The resting-order implementation disallows an expiry for these reversible types. Its price transformation is asymmetric: a bid filled at P becomes an ask at P divided by one minus the spread, while an ask becomes a bid at P multiplied by one minus the spread. Closing a browser does not stop that on-chain instruction.[5]

The portfolio interface permits exercise only before the option’s on-chain expiry. It also distinguishes an issuer’s settlement actions from a holder’s exercise. Closing a live series early requires ownership of its full option supply. Burning an expired token cleans up the token position; it does not retrospectively exercise the option.[13]

Manifest describes its core matching protocol as charging no trading fee. That statement has a narrow scope: wallet transactions still use Solana resources, integration layers can have their own economics, and token-specific transfer behaviour remains relevant. An advertised zero protocol fee should not be read as a guarantee that creating, funding and managing a position consumes no SOL.[6]

Global orders provide capital reuse rather than multiplied collateral. In a hypothetical example, one 100 USDC global balance backs quotes in three markets. If a fill consumes 80 USDC, only 20 USDC remains available for those quotes, before other movements. The three markets do not create 300 USDC of independent buying power.[4]

The rent assessment, taken on 29 September 2026, counted 3,717 allocated market accounts. It explicitly analysed storage and possible reclamation rather than measuring active trading pairs. Empty allocations, seats and reused trader records must not be converted into an estimate of registered customers.[10]

Defragmentation is a storage-maintenance mechanism, not a published inactivity fee. Re-expanding an account can require rent again. The documented wrapper implementation and the application’s actual deployment should also be distinguished; the presence of a developer maintenance instruction does not establish that an interface exposes it to every customer.[11]

For example, a hypothetical market balance of 100 quote tokens with 60 reserved in live orders has 40 available. Cancelling the orders can release the reservation, assuming no intervening fill; it does not add 60 new tokens to the account. The SDK separately reports withdrawable and open-order quantities in the token’s own units.[8]

The current client’s withdraw-all helper withdraws available base and quote balances. It does not implicitly cancel every order to make locked amounts available. The current cancellation helpers can inspect the core book as well as wrapper-tracked orders, but large books can need multiple instructions or transactions. Refreshing state before building cancellation matters because orders may fill between the read and submission.[7]

The SDK separates market readers, wrapper bookkeeping and transaction-building clients. Integrations must convert between human token quantities and the mint’s atomic units, then submit the resulting instruction with a suitable signer. This is crypto funding: no Manifest bank deposit, card-cash balance or fiat withdrawal timetable was established from the SDK documentation.[21]

Assets deposited into market contracts remain subject to those contracts’ withdrawal rules; they are not simply free tokens in the wallet. The repository documents a four-of-five Squads authority for program upgrades. User signing and an open source order book therefore coexist with an upgrade-control mechanism. A multisignature threshold limits unilateral changes but does not remove code or governance risk.[1]

The security material distinguishes the formally analysed matching program from surrounding software. The August 2026 whole-repository scan included analytics endpoints, SDK validation, routing adapters and release infrastructure. Those components can affect quotation, records or integration safety even when a core accounting property has been checked.[20]

The post-audit history records fixes to transfer-fee accounting and cancellation rounding, including work on verification rules. The follow-up security record also covers market-account validation and order-tracking issues. These disclosures are evidence of continuing maintenance, not a basis for calling all application paths exploit-proof or assuming that any future upgrade is already covered by an older audit.[18][19]

Manifest’s own risk disclosures warn that automated or manager-controlled vault logic, off-chain dependencies, depegs and market conditions can cause losses. Estimated rates can change and exits can be delayed by stressed liquidity. No policy wording establishing an insured customer limit or compensation entitlement was found in those disclosures.[15]

The terms require lawful use and local legal, tax and reporting compliance. They provide no verified country availability matrix. Permissionless protocol access does not establish eligibility for every interface or strategy.[16]

The privacy policy describes a wallet-based application without a conventional user account. Private keys and signing are handled by third-party wallets, while RPC providers and other infrastructure can receive technical request data. An interface support request cannot substitute for control of the wallet’s recovery material.[17]

The wallet integration guide identifies [email protected] for integration assistance, the project repository for issues and an explorer for inspecting activity. These are useful escalation and evidence routes, but they do not establish a staffed emergency dealing service with authority to cancel a user’s orders. A report should distinguish the market, transaction signature and observed state.[6]

The portfolio interface includes date-range export requests and states for requesting payment and waiting for an export. The inspected client did not establish a universal fixed export charge, so that operation should not be described as invariably free. Review its current quote and completion status before treating the requested report as delivered.[13]

Developer history functions also have scope limits. The release notes describe a wallet-only completeFills request without a starting slot as bounded to one day, with the effective slot range returned. That default is not lifetime account history. Explicit ranges and complete pagination are needed when reconciling fills with deposits, withdrawals and fees for records or tax work.[9]

No current firm-specific financial permission or compensation membership was established. The terms identify Bonasa Technologies Inc. as application operator without establishing its incorporation jurisdiction. Corporate naming and open source code do not establish financial authorization.[16]

The application terms date from 24 February 2026 and distinguish proprietary web/mobile interfaces from protocol licensing and third-party services. This profile concerns Manifest Trade at manifest.trade and its linked application.[16]

The official About page links the Bonasa-Tech codebase and protocol analytics. It presents liquidity as accessible through multiple wallets and aggregators. That distribution helps explain why protocol activity can exceed the traffic visible in one website, but does not support adding a separate user count for each interface that accesses the same book.[2]

Operator

Bonasa Technologies Inc.

Exchange model

Decentralised

Service scope

Solana spot book; separate collateralised options and vault interfaces.

Client types

Retail clients

Pricing publication

Public pricing

Other names

Manifest

Pricing scope

No core trading fee; network, storage and route costs remain.

Funding scope

Solana tokens, market deposits and shared global balances.

Custody and asset handling

Wallet signing; deposited assets follow market or strategy contracts.

Client eligibility

Use must be lawful in the customer’s jurisdiction.

Support

Developer email, repository issues and public transaction tools.

Authorisation and registration scope

No current firm-specific financial permission established.

Exchange metadata checked 20 Oct 2026Source 1Source 12Source 14Source 2Source 16Source 8Source 15Source 4Source 6

A vault position and a reverse order have different exit actions. Selling the vault share addresses participation in the managed strategy; cancelling the order addresses its continuing book instruction. Disconnecting a wallet from the website performs neither action. The vault risk disclosures expressly allow strategy control outside a single immutable on-chain rule.[15]

The privacy policy lists browser-stored RPC choices, chart settings, favourite markets, cached data and acknowledgements. Those preferences can disappear when browser storage is cleared, while submitted transactions remain public on Solana. A different device should not be assumed to reproduce local settings or to close positions created on the earlier device.[17]

The published integration skill favours returning instructions when the surrounding application will sign. A locally configured bot with a usable key is a different authority arrangement from a read-only assistant. Stopping the bot stops future software actions; existing reverse orders, outstanding limits and deposited vault interests still require their own on-chain exit steps.[22][5]