What Pro actually trades
Bluefin’s Pro API describes a decentralized perpetual futures exchange on Sui. Its reference explains that the new architecture uses a trusted execution environment for order handling with on-chain trade execution. It supports cross and isolated margin. These are product and mechanism claims from the operator’s documentation, not an independent throughput or security audit.
The API separates order acknowledgements from final WebSocket confirmation. This matters for an activity collector: accepted HTTP requests are not executed fills. The official Pro SDK and API reference provide an integration starting point, but the present PerpsAtlas review has not audited historical fill pagination or all current market definitions.
Sources: Bluefin Pro API introduction ↗ · Bluefin Pro official SDK ↗
Classic balances do not become Pro history
Bluefin’s migration guide says Pro is live and gives users a path from Bluefin Classic. It describes withdrawing bridged wUSDC from Classic, swapping to native USDC and depositing into Pro. Classic’s older isolated-margin documentation should not be quoted as if it defined Pro’s cross-margin product.
A one-click movement of funds does not make Classic and Pro the same metric series. An adapter should retain the market and version ID for each fill and separately identify any period when both products accepted trades. A parent-level Bluefin provider value may combine or switch products; the open-interest directory cannot settle that scope.
Sources: Bluefin Classic to Pro migration ↗ · Bluefin Classic contract specifications ↗ · Bluefin Pro API introduction ↗
The BLUE token is a separate record
Bluefin’s official token page identifies BLUE as a governance token. That source establishes token identity, but it is not a dated ledger of fees, repurchases or cash distributions. Incentive rewards to traders, if measured, would also have a different recipient and basis from holder flow.
This article makes no token valuation or yield claim. Before any token economics panel, a reviewer needs current governing terms, the exact recipients and required actions, plus observed transactions tied to a defined period. Perp volume alone cannot establish a token holder right.
Sources: Bluefin BLUE token documentation ↗
What can enter a comparable series
The eligible cohort is filled Pro perpetual trades on specified Sui markets. It excludes Classic fills, spot swaps, lending transfers, unfilled orders and account migration. Native USDC collateral does not remove the need to state the quote asset and conversion convention for every market and day.
A reproducible adapter should archive source bytes and hash, specify completed UTC boundaries, the API version, market lifecycle and handling of corrections. It should reconcile fill counts or notionals to an independent official or on-chain path before any 30-day ranking number. Bluefin Pro remains in the expansion catalog while volume, OI, fees and holder flow are unknown for this comparable cohort.
Sources: Bluefin Pro API introduction ↗ · Bluefin Classic to Pro migration ↗ · Bluefin Pro official SDK ↗
What we monitor next
- Pin the current Pro contract and API versions and list eligible perpetual instruments.
- Reconcile completed Pro fills to an on-chain or independently reproducible source.
- Map Classic and Pro overlap before a parent-level volume or OI claim.
Frequently asked questions
Compare the evidence
Related research
Source register
- Bluefin Pro API introduction · checked 2026-10-07
- Bluefin Classic to Pro migration · checked 2026-10-07
- Bluefin Classic contract specifications · checked 2026-10-07
- Bluefin Pro official SDK · checked 2026-10-07
- Bluefin BLUE token documentation · checked 2026-10-07
Research revisions
- 2026-10-07 — Initial independently reviewed product and metric-scope audit.
AI-assisted research checked against cited sources. Facts, assumptions and interpretation are distinguished; this is not a financial audit or a recommendation tailored to you. Editorial standards.
Compare protocols →