Contracts
Smart contracts
The Sui Move packages behind Rare Marketplace, the launchpad, Rare Trophies, game items and device passes, with their mainnet package ids and status.
Rare has six Sui Move packages published on mainnet. Each one is its own package with its own upgrade path, so you can integrate with one without depending on the others. All of them are written in Move 2024 and work with the standard Sui kiosk and TransferPolicy model.
Packages
Each package page shows the full package id and its shared objects, with a copy button.
When a package is upgraded, its call target (the latest package id) changes, but its original id does not. Event types and object types always use the original id. Build calls against the latest id and filter events by the original id. Every package above is at its first version, so both ids are the same today.
An earlier market package (0x4657…4b03) was published on 2026-10-27, never used and paused the next day. Its Config is paused, so it takes no new orders. Use the id in the table.
Coming later
Fees
Rare charges 0.1% on marketplace trades and launchpad mints, and takes no share of creator royalties. See Fees and royalties.
Conventions shared by all packages
- Amounts are in base units of the coin: MIST for SUI (1 SUI = 10^9 MIST), 10^-6 for USDC.
- Shared objects are passed as normal object inputs. The TypeScript SDK resolves
initialSharedVersionfor you. - Pauses never lock funds. Admin pauses stop new orders, mints or unlocks. Cancels, refunds, withdrawals and payouts never take the pause switch.
- Upgrades are versioned. Shared objects carry a version. After an upgrade, a
migratecall retires the old code, and older code refuses newer objects. - Admin caps (fee changes, pauses, moderation) and upgrade caps are held by a single Rare address today. Fee changes on the marketplace and launchpad go through a 48 hour timelock on chain, so a new rate is visible in the
Configfor two days before it applies. - Events are stable: field order never changes. Decode them from BCS with the layouts on each page, since JSON rendering differs between RPC providers.
See Security for source availability and how to report a vulnerability.
