Skip to main content

These are saved CoinGecko ranks, not live market-cap ranks. No common collection time is recorded, so they are not verified as one snapshot; duplicate values may appear.

CoinYQ Dossier

Magma built market makers before its token vote was visible

Magma Finance developed three market-making designs on Sui before its published configuration established a working MAGMA vote. After one billion tokens were minted, the TreasuryCap carrying mint authority became immutable. Fees, upgrades, rewards and price publication remained separate powers held through capability objects and contract roles; freezing token issuance did not transfer those powers to token holders.

Before MAGMA, there were ranges and bins

Magma's first concrete identity was a Sui exchange. Its CLMM let liquidity providers select a price interval instead of spreading capital across every possible price. Fees accrue while that interval is active; when price leaves it, the position can become idle and change its asset mix.

ALMM divided the curve into bins. Each bin quoted one discrete price until a reserve side depleted, then trading advanced to the next. Volatility could raise the variable portion of fees. The mechanism made liquidity placement granular, but it did not remove impermanent loss, range management or smart-contract risk.

The code assigned administrators before token holders received a ballot

The public SDK's current map names CLMM package 0x4a35d3dfef55ed3631b7158544c6322a23bc434fe4fca1234cb680ce0505f82d and ALMM package 0x532bf64e6f0bf702353387d53a28a3239249f47c39d58954f2c0a1f9f4436c20. CLMM's GlobalConfig carries protocol fees, fee tiers, an allowed-role list and package version. Its roles cover pool, fee-tier, partner, reward and protocol-fee-claim management.

An AdminCap can alter membership, and business functions reject an outdated package version. Sui upgrades can preserve a published-at identity while moving execution to a newer package. This is deliberate maintenance machinery, not governance by every liquidity provider.

Audits reviewed this wider distribution and gauge architecture and found issues in reward math, cap verification and administrative state. Fixes and acknowledgments reduce specific defects; an audit is a bounded code review, not proof that every audited module is the live mainnet version.

One billion tokens arrived after an unlimited mint warning

On 11 December 2025 the MAGMA module created its TreasuryCap. Hashlock's audit warned that whoever held it could mint without limit. The team answered that the capability would be destroyed after minting. Current coin state shows one billion units and an immutable capability, resolving the standard supply path but not who received each allocation wallet.

Four days later the whitepaper fixed the economic table: 510 million ecosystem reserve over 48 months; 100 million community units unlocked at TGE; 150 million each for contributors and investors after 12 months then over 24 months; 70 million for foundation and marketing as needed; and 20 million for launch liquidity. “As needed” is discretion, not a vesting clock.

Magma 2.0 moved price discovery outside the pool

The PropAMM integration guide published in 2026 shifts attention from where LPs place ranges to who publishes the reference price. Its SUI/USDC example consumes an external multiplier. The guide sets a default price lifetime of 30 seconds, rejecting prices at least that old, and describes automatic locking when virtual Y liquidity falls more than 5% below its high-water mark. These are documented integration conditions; they are not a fresh measurement of every deployed pool’s configuration.

Publisher and LiquidityProviderCap holders can unlock. A circuit breaker can halt damage, while privileged recovery also concentrates operational judgment. The separate fanout feed is API-keyed, best-effort and has no replay, so observers do not receive the same guarantees as the onchain state.

The repository identifies a mainnet package and pool, while the Magma 2.0 announcement describes staged integration and public launch. Those sources document a deployment target but do not consistently establish unrestricted public access, supported pairs, a successor to the price feeder or a service commitment.

A governance token appeared without a governance package

The whitepaper says MAGMA will reward activity and let holders propose or vote on features, upgrades and parameters. The token page adds loyalty tiers and selected product access. These are explicit intended utilities, and the paper limits votes to protocol features rather than Foundation management.

But the July 2026 SDK config leaves both ve33 and distribution package IDs empty. No reviewed mainnet interface shows a MAGMA balance becoming voting power, choosing gauges, changing an upgrade cap or enforcing emissions. Staking language and a 51% incentive reserve do not themselves create a live vote.

Named entities, but no complete control map

The whitepaper names Magma Labs Foundation, a Distributor and project contributors. It does not provide the Foundation's jurisdiction, registration number, directors, the Distributor's legal identity, treasury addresses or a map from those entities to Sui capability owners. The GitHub organization lists no public members.

That opacity matters because the document also says separate Terms and Conditions or a Token Distribution Agreement govern distribution and continued holding. The reviewed public sources did not surface that agreement, so its counterparty and remedies cannot be assumed from the paper.

What the paper does state is unusually direct: MAGMA is non-refundable and non-redeemable and supplies no equity, dividends, revenue, Foundation vote, reserve ownership or intellectual-property claim. A future protocol ballot would be a software power, not ownership of the people or entities behind it.

How the project changed

  1. 2025-01-31
    CLMM audit closes

    Zellic reports on the concentrated-liquidity code before the token exists.

  2. 2025-03-20
    ve(3,3) is presented

    Magma describes locks, gauges, emissions and fee sharing as its Sui governance design.

  3. 2025-12-11
    MAGMA is created

    The Sui coin mints one billion units after an audit flags TreasuryCap centralization.

  4. 2025-12-15
    Allocation and rights paper is published

    The whitepaper sets six allocation tranches, vesting and extensive legal exclusions.

  5. 2025-12-21
    Audit archive is assembled

    The official repository collects token, CLMM and ALMM assessments.

  6. 2026-04-28
    PropAMM deployment is documented

    The integration guide names mainnet package 0x56f72145f18db9709dc328f3e016d84cb775877527d1b3da2d8e740d60537795 and pool 0xa4225bc3466f8be9f7c8e81c922e833e7d37bf198a5769f68e1cb4ce4fc34996.

  7. 2026-06-09
    CLMM source becomes public

    The public repository exposes current config, roles, pools, positions and reward logic.

  8. 2026-07-31
    Mainnet SDK shows a split rollout

    CLMM and ALMM addresses are populated while ve33 and distribution remain blank.

Evidence and primary sources

Last evidence review: 2026-09-05

What is Magma Finance?

Magma Finance is a Sui liquidity protocol with several market-making designs. Its CLMM lets liquidity providers choose price ranges; its ALMM divides liquidity into fixed-price bins and varies fees with volatility. A later PropAMM uses an external price feeder rather than a reserve-derived price. The canonical token is the Sui coin 0x9f854b3ad20f8161ec0886f15f4a1752bf75d22261556f14cc8d3a1c5d50e529::magma::MAGMA, created with nine decimals and 1,000,000,000 units.

This identity excludes MagmaFi's 2023 Mantle DEX, its oMAGMA/veMAGMA design, a Magma stablecoin project, and older BNB or Algorand MAGMA tokens. The Sui project's official organization is MagmaFinanceIO and its website is magmafinance.io.

What problem does Magma Finance solve?

Concentrated-liquidity pools can leave capital outside the active trading range. Magma's products try to place liquidity more efficiently: CLMM gives LPs ranges, ALMM uses discrete bins and volatility-sensitive fees, and PropAMM anchors a concentrated curve to an offchain price. These designs may improve quotes, but they add position, oracle, administrator and upgrade dependencies.

The token story goes further. MAGMA is described as an incentive, loyalty and governance asset whose voters can influence upgrades and parameters. Yet the July 2026 mainnet SDK config fills CLMM and ALMM package IDs while leaving ve33 and distribution IDs empty. Public claims about voting, staking and emissions therefore outrun the reviewed production configuration.

How does Magma Finance work?

The published mainnet SDK identifies CLMM package 0x4a35d3dfef55ed3631b7158544c6322a23bc434fe4fca1234cb680ce0505f82d and ALMM package 0x532bf64e6f0bf702353387d53a28a3239249f47c39d58954f2c0a1f9f4436c20. CLMM positions concentrate assets in selected ticks; only in-range liquidity earns fees and rewards. ALMM bins quote at discrete prices, move the active bin as one side depletes and add variable fees as volatility rises. Protocol code gives capability holders and ACL roles power to manage fee tiers, partners, pools, rewards and protocol-fee claims, while a package-version gate directs users to the current implementation.

PropAMM is separately documented at package 0x56f72145f18db9709dc328f3e016d84cb775877527d1b3da2d8e740d60537795 with pool 0xa4225bc3466f8be9f7c8e81c922e833e7d37bf198a5769f68e1cb4ce4fc34996. An external publisher updates the price, the guide specifies a default price lifetime of 30 seconds and rejection at that age or older, a greater-than-5% virtual-liquidity deviation locks the pool, and a Publisher or LiquidityProviderCap can unlock it. The public repository identifies a mainnet package and pool; the official Magma 2.0 article still frames integration and public launch as a rollout, so availability is treated as partly conflicting.

All 1 billion MAGMA were created on 2025-12-11. The token audit warned that the TreasuryCap initially allowed unlimited minting; the team said it would destroy the cap after minting. The current Sui object is immutable, consistent with a frozen TreasuryCap and no standard later mint. Allocation is 51% ecosystem reserve vested linearly over 48 months, 10% community unlocked at TGE, 15% contributors and 15% investors each after a 12-month lock then 24-month linear vesting, 7% foundation/marketing as needed, and 2% launch liquidity. No separate onchain emission controller or live veMAGMA ballot was found in the current public SDK.

Key facts

  • Canonical coin type: 0x9f854b3ad20f8161ec0886f15f4a1752bf75d22261556f14cc8d3a1c5d50e529::magma::MAGMA on Sui.
  • MAGMA has nine decimals and total supply of 1,000,000,000.
  • The TreasuryCap was made immutable after minting; no DenyCap was identified in the reviewed coin state.
  • 51% (510,000,000) is assigned to ecosystem reserve with no lock and 48-month linear vesting.
  • 10% (100,000,000) community incentives/airdrop is listed as 100% unlocked at TGE.
  • 15% (150,000,000) contributors and 15% investors each have a 12-month lock plus 24-month linear vesting.
  • 7% (70,000,000) foundation/marketing is released as needed; 2% (20,000,000) liquidity is 100% unlocked at TGE.
  • The July 2026 SDK identifies CLMM package 0x4a35d3dfef55ed3631b7158544c6322a23bc434fe4fca1234cb680ce0505f82d.
  • The same SDK identifies ALMM package 0x532bf64e6f0bf702353387d53a28a3239249f47c39d58954f2c0a1f9f4436c20.
  • The SDK leaves ve33 and distribution package IDs empty, so live token voting and emission distribution are not established there.
  • CLMM ACL roles cover pool, fee tier, protocol-fee claim, partner and reward management.
  • The public CLMM config sets a package version and rejects calls through deprecated versions.
  • PropAMM documentation names mainnet package 0x56f72145f18db9709dc328f3e016d84cb775877527d1b3da2d8e740d60537795 and pool 0xa4225bc3466f8be9f7c8e81c922e833e7d37bf198a5769f68e1cb4ce4fc34996.
  • The PropAMM guide specifies a default 30-second price lifetime and an automatic lock when virtual Y liquidity falls more than 5% below its high-water mark.
  • The whitepaper calls Magma Labs Foundation and an unspecified Distributor separate actors but does not state jurisdiction, directors or a public operating-company identity.
  • The whitepaper denies refunds, redemption, equity, dividends, revenue rights, Foundation votes, asset ownership and intellectual-property rights.

Official links

Categories

Related coins

Frequently asked questions

Which Magma Finance does this page cover?

The Sui DEX at magmafinance.io and MAGMA coin type 0x9f854b3ad20f8161ec0886f15f4a1752bf75d22261556f14cc8d3a1c5d50e529::magma::MAGMA. It excludes MagmaFi on Mantle, its oMAGMA design, and unrelated stablecoin, BNB and Algorand assets.

Can more MAGMA be minted?

The token audit found the original TreasuryCap could mint without a cap, and the team promised to destroy it after the one-billion mint. Current state marks the capability immutable, blocking the reviewed standard mint path. Protocol packages and admin capabilities remain separate risks.

How is the one-billion supply allocated?

51% ecosystem reserve, 10% community, 15% contributors, 15% investors, 7% foundation/marketing and 2% liquidity. Contributor and investor tranches lock for 12 months then vest over 24 months; ecosystem reserve vests over 48 months.

Are CLMM and ALMM live?

The official July 2026 SDK publishes mainnet CLMM and ALMM package and object IDs, and user documentation exposes swap and liquidity flows. Upgrade, fee and reward controls remain capability- or role-gated.

Is Magma 2.0 PropAMM live?

The public repository lists mainnet package 0x56f72145f18db9709dc328f3e016d84cb775877527d1b3da2d8e740d60537795 and pool 0xa4225bc3466f8be9f7c8e81c922e833e7d37bf198a5769f68e1cb4ce4fc34996, while the launch article describes integration and public release as a rollout. A deployment is visible, but unrestricted production availability and operating guarantees are not consistently established.

Can MAGMA holders vote today?

Official prose says holders may propose and vote, but the reviewed mainnet SDK leaves ve33 and distribution package IDs blank. No live proposal executor, vote interface or MAGMA-controlled package upgrade was verified.

Who controls protocol parameters?

CLMM AdminCap and ACL roles can manage package version, fee tiers, pool/partner/reward permissions and protocol-fee claims. PropAMM relies on publisher and liquidity-provider capabilities for oracle updates and unlocking. Public docs do not map every current cap owner.

What legal rights come with MAGMA?

The whitepaper expressly denies refunds, redemption, equity, dividends, revenue, Foundation governance, asset ownership and intellectual-property rights. Protocol use or a future vote is distinct from rights against Magma Labs Foundation, the Distributor or contributors.

External trackers

Choose a tracking site for Magma Finance: