0xe5780a784d1d076a25b8b6e125fb6d36d39826fe2fb507944589231480f1c35a

published packages

Move packages this wallet published on-chain — what it shipped, not what it used.

• 0xe3b4ddf9…79228541

  This package manages two primary object types: `Collection` and `Minter`. A `Collection` represents a group of NFTs, while a `Minter` object controls the minting process for a specific collection. The `init` function initializes the package by creating a `Publisher` and a `Display<Nft>` object, which are then transferred to the transaction sender. The `add_phase`, `remove_phase`, and `update_phase` functions allow the `Minter`'s owner to manage sale phases, which define parameters like price, max sales, and start time. The `mint` function allows users to mint NFTs from a collection, checking against the current sale phase's rules and deducting the minting fee from the provided SUI coin. Notable patterns include owner-gating for phase management functions and time-gating for the minting process based on sale phase start times.

• 0xe527e05d…ea7463bd

  This Sui package, `my_minter`, primarily manages `Minter` objects, which represent NFT collections. It also defines `Nft` objects, which are the individual NFTs minted. The public/entry functions allow for the management and interaction with these `Minter` and `Nft` objects. `add_phase`, `remove_phase`, and `update_phase` are administrative functions that modify the `phases` vector within a `Minter` object, which dictates the sale phases for the NFT collection. These functions are gated by checking if the transaction sender is the `Minter`'s owner. The `mint` function is the core logic, allowing users to mint NFTs. It checks the current time against the `start_time` of the active sale phase, verifies a Merkle proof (`root` in `SalePhase`) if provided, and updates the `minted` count in the `Minter` object and `user_buys` and `sale_phase_buys` tables. It also creates a new `Nft` object and