Addresses
Blast deploys to Sui mainnet only. Every publication is recorded under deployments/sui/mainnet in the contracts repository, with its package ID, shared object IDs, transaction digests, and post-deploy checks. That folder is the source of truth.
Current release
Section titled “Current release”| Object | ID |
|---|---|
blast_presale package |
0xf9c404c0368cf014b44cac79dc5037da2aa34e16952673433d1c87ae3d2f8ca4 |
FeePolicy |
0x3da5bfd3275991b70a445a2022e07925ce9a927dd47d7c3fd583563089a9afae |
CreationPolicy |
0x4ce001c53e9da536fc7d04a87383e90ca76e27492b3cad92cf9e167af0dc83d8 |
Blast ACL |
0xc9fbcfc4eda38626d7daad17902cc145b4008beb20470135438298aa7a005a6d |
VenueConfig |
0xebfd4e31f8fddf1b8d5b4a45835c7397156f6f62eeefef46b7b1b42aa29c6d39 |
PackageAdmin |
0xbea1b6227c157f3ffa9afa9925ae1bd0013692ca0c55d02558a2b18945c8f083 |
Clock |
0x6 |
VenueConfig is taken by cetus::new, cetus::migrate, bluefin::new, and bluefin::migrate.
The immutable blast_admin package is 0x726fb49b880faa89719b95c6ef3a91be794f771ed3560fe5894d0a605c8469f9. The immutable blast_partners package used by this publication is 0x50c4a1b68af8c4fa0438ad8b02e49d484d46ab38e85ac4d001ea13449aa20dbd.
Source: 11 October publication record and Published.toml. Use published-at for calls and original-id for types and event filters; they are equal for this version.
Venue and dependency objects
Section titled “Venue and dependency objects”Creation and migration also take objects outside this package:
| Object | Used by | Where to find it |
|---|---|---|
Cetus GlobalConfig, Pools |
cetus::new, cetus::migrate |
Cetus developer docs |
Cetus LP-burn BurnManager |
cetus::migrate, cetus::collect_fees, cetus::new_vault |
Cetus developer docs |
Bluefin GlobalConfig |
bluefin::migrate, bluefin::collect_fees |
Bluefin docs |
blast_partners package and each Partner |
set_partner, the partner pay calls |
Its record in deployments/sui/mainnet |
Currency<T> for a coin |
bluefin::new, finalize, bluefin::migrate |
The coin’s shared Currency object in Sui’s Coin Registry. Read its ID from the coin’s registration transaction |
Retired packages
Section titled “Retired packages”Earlier publications are sealed and will never gain the current logic. Do not build on them.
| Package | Status |
|---|---|
0x663012c11fd49ce0c833e2e33e2d0ebd6af8fc5e632c9807290426fdd47a7fdc |
Superseded before any sale could be created. |
0x76cb0508fc94234fddd910b5616248f8a42998048a28e55f5fe1cc89e7b98400 |
Superseded by the current release. |
Other earlier publications remain in the deployment history. Use the IDs above for this release; existing sales still belong to the package that created them.
Finding a sale’s objects
Section titled “Finding a sale’s objects”- A sale’s
PresaleID comes from itsPresaleCreatedevent or from the app that listed it. - A migrated sale’s
VaultID comes from theVaultCreatedevent whosepresale_idmatches. A vault locked without a presale has the zeropresale_id. - Vesting schedules are named by the
vesting_idfield inRaiseAllocated,RecipientAllocated, andClaimed.