0x0d66d7ac45c1d011fdd21c5d4d193913c8c40d5f1e1e62e33f72ffa0f2b86e2a

published packages · 5 of 50

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

• 0x056464ae…8c7b6afb

  This package, `bluemove_router`, facilitates token swaps with integrated fees. It manages two primary object types: `FeeObject`, which stores buy and sell fees and an admin address, and `AdminCap`, a capability object for administrative actions. The `init` function creates and shares a `FeeObject` with initial fees and an admin, and transfers an `AdminCap` to the deployer. The `change_admin` entry function allows the holder of an `AdminCap` to update the admin address within a `FeeObject`. The `buy_exact_in` and `sell_exact_in` entry functions execute token swaps (SUI to generic token, or generic token to SUI, respectively) through an external `router` module, deducting a fee from the transaction which is sent to the `FeeObject`'s admin. These swap functions emit `BuyEvent`, `SellEvent`, `FeeCollectedEvent`, and `OrderCompletedEvent` to record transaction details and fee collection. The `utils` module provides a helper function `send_coin`

• 0x08153eae…b70d708b

  This package, `moonbags_router`, facilitates trading of generic tokens (Ty0) against SUI. It manages `Configuration`, `BurnManager`, `Pools`, and `GlobalConfig` objects, which are mutated during trades. The `buy_exact_out` entry function allows users to buy a specified amount of Ty0 tokens using SUI, emitting a `BuyEvent` and an `OrderCompletedEvent`. The `sell_exact_in` entry function allows users to sell a specified amount of Ty0 tokens for SUI, ensuring a minimum SUI output, and emits a `SellEvent` and an `OrderCompletedEvent`. Both functions transfer the resulting coins to the transaction sender and utilize a helper function `utils::send_coin` to handle coin transfers or destruction if the value is zero.

• 0x0986fa2d…1696c6ba

  This package manages two primary object types: `FeeObject` for collecting fees in SUAI tokens and `AdminCap` for administrative privileges. The `init` function creates and shares a `FeeObject` and transfers an `AdminCap` to the deployer. Public functions allow the `AdminCap` holder to change the `FeeObject`'s admin and for the admin to `collect_fees` from the `FeeObject`'s balance. Users can `buy_exact_in` or `sell_exact_in` using SUAI tokens and another generic token type through an external `suiai_v2` module, and these actions emit `BuyEvent` or `SellEvent` respectively. A `pay_fee` function allows users to deposit SUAI tokens into the `FeeObject`'s balance, emitting a `FeeCollectedEvent`. The `utils` module provides a helper function to safely transfer coins or destroy zero-value coins.

• 0x0ddf38bd…70e4dd1f

  This package facilitates token swaps, specifically between SUI and other fungible tokens (Ty0). The primary objects it manages are `Coin<SUI>` and `Coin<Ty0>`. The `buy_exact_out` entry function allows a user to buy a specified amount of `Ty0` tokens using SUI, emitting `BuyEvent` and `OrderCompletedEvent`. The `sell_exact_in` entry function allows a user to sell a specified amount of `Ty0` tokens for SUI, ensuring a minimum SUI output, and emits `SellEvent` and `OrderCompletedEvent`. Both functions interact with external modules for configuration, burning, and liquidity pools, and transfer the resulting coins to the transaction sender. A notable pattern is the use of generic types (`Ty0`) for fungible tokens, allowing the router to handle various token types.

• 0x1398f7fd…e6df7925

  This package manages a `Referral` object, which tracks referral rewards and their distribution. Public/entry functions allow an `AdminCap` holder to initialize the `Referral` object, pause/unpause reward claims, change the operator, and add whitelisted tokens. The `claim` function allows the `Referral` operator to claim rewards for users, transferring coins and updating records. The `withdraw` function allows the `AdminCap` holder to withdraw funds from the `Referral` object, while `deposit` allows anyone to deposit funds. Notable patterns include the use of an `AdminCap` for administrative actions, dynamic fields to store balances for different token types within the `Referral` object, and a `Table` to track referral records and processed request IDs.