all collections · daily · marketplace overlay
weekly · real (teal) vs wash (rose)
counterparties · funders · clusters
Move packages this wallet published on-chain — what it shipped, not what it used.
This package defines a social token system. The primary object is `Global`, which stores configuration, a SUI vault, and a table of `Shares` objects indexed by address. `Shares` objects track the supply of a specific social token and who holds how much of it. Public functions allow an `AdminCap` holder to update configuration parameters like protocol and subject fees. Users can `buy_shares` and `sell_shares` for a given subject, which involves calculating prices, applying fees, updating share holdings, and transferring SUI from or to the `Global` vault. The `withdraw` function allows the `AdminCap` holder to empty the `Global` vault. The system uses dynamic fields (`Table`) to manage shares and holdings, and emits `TradeEvent`s for each buy/sell action.
This Sui package defines a social token system. The primary object is the `Global` object, which manages `Shares` for different subjects (addresses) and holds a `Config` for fees and a `vault` for SUI. The `club` module uses the `socialcoin` module to manage messages within clubs. The `socialcoin` module allows users to buy and sell shares associated with a specific address, affecting the `supply` of shares and the `holders` table within a `Shares` object. Fees are applied to trades, with a `protocol_fee_percent` going to a `protocol_fee_destination` and a `subject_fee_percent` going to the subject of the shares. An `AdminCap` is used to gate the `update_config` function, allowing only the administrator to change fee percentages and the protocol fee destination. The `club` module allows `socialcoin` holders to post and delete messages in clubs, with message deletion being possible by the original sender or the `Global` admin.
This Sui package defines a "club" system. The primary object types are `Global`, which acts as a singleton registry for all clubs, and `Club`, representing individual clubs. Public/entry functions allow users to create new clubs (paying a fee), add/remove club administrators (only by the club creator), and update various club details like name, logo, description, announcement, threshold, and channels (by the club creator or an administrator). The `Global` object stores `Club` IDs in tables indexed by club index, type, and owner, and is mutated during club creation. Clubs are shared objects. The package uses an authorization pattern where only the club creator or an existing admin can modify club information.
This package manages a singleton Global object, which contains a Table of Club objects keyed by address. Each Club object contains a TableVec of Message objects. The init function creates and shares the Global object, setting the deployer as its admin. The new_message entry function allows a socialcoin holder to create a new message within a specified club; if the club does not exist, it is created. The delete_message entry function allows the sender of a message to mark their own message as deleted and clear its content, provided the message exists and is not already deleted. The package uses dynamic fields (Table and TableVec) to store clubs and messages.
This package defines a social club system where users can send messages and manage "social coins." The primary object types are Global (a singleton holding all club data and social coin configurations), Club (representing a specific club with messages), Message (a message within a club), Shares (related to social coin holdings), AdminCap (for administrative control), and Config (social coin fee settings). Public/entry functions allow users to create new messages in a club (new_message), delete existing messages (delete_message), update social coin configuration (update_config), and buy/sell social coin shares (buy_shares, sell_shares). The new_message function requires the sender to be a holder of the social coin associated with the club's subject. The delete_message function allows either the message sender or the Global admin to delete a message, and it replaces the message content with an empty vector and marks it as deleted. Notable patterns include: an AdminCap for administrative functions (update_config), a Global singleton object that manages all clubs and social coin data, and the use of
casualRule-based labels, conservative precision.
area + brightness = call volume; hover for detail
{
"wallet": "0xd056f27d7cdf90b6546d27882d06a6fce2d9c7e9e3c16a032ad5096fa7804330",
"n_tx": 26,
"n_successful_tx": 17,
"n_distinct_epochs": 8,
"n_distinct_sponsors": 0,
"first_seen_cp": 23684145,
"last_seen_cp": 78597280,
"first_seen_ts_ms": 1705385430846,
"last_seen_ts_ms": 1731313567325,
"total_gas_spent_mist": -811667372,
"n_self_sponsored_tx": 26,
"n_sponsored_tx": 0,
"gas_price_p50": 750,
"gas_price_p95": 757,
"active_hours_top24": [
9,
8,
7,
11,
12,
6,
2
],
"primary_archetype": "casual",
"labels": [
"casual"
],
"label_confidence": [
0.7
],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely E. / SE Asia.