Profiles & Accounts

Every æternity address has a profile page on Superhero, whether or not anyone has set it up. The page merges on-chain links, the API's account aggregate and trading statistics.

The two profile surfaces

The social profile is live at https://superhero.com/users/ followed by an ak_ address.

The header

The account aggregate from GET /api/accounts/{address} carries address, bio, chain_name, chain_name_updated_at, an embedded profile, public_name, holdings_count, and a links object keyed by the AddressLink provider ids: x, nostr, bio, site and prefaens. The links object is authoritative; the flat fields are fallbacks for older records.

If chain_name_updated_at is older than the staleness window, or has never been set, the endpoint re-reads the name from the middleware, returns the fresh value, and writes it back asynchronously. An hourly sweep covers accounts nobody is viewing, so a lapsed or transferred .chain name disappears from a profile within about an hour.

The tabs

/users/:address has four tabs, selected by a tab query parameter (feed is the default and omits the parameter):

All four datasets are prefetched when the page loads. The feed tab merges posts from GET /api/posts?account_address=… with trade and token-creation activity items.

On chain versus API

Every field a user controls is written behind their wallet signature; the transaction is submitted by Superhero's provider wallet. See AddressLink.

Editing your own profile

Open Edit SuperheroID on your own profile. It is one modal over several independent operations:

Each link has a matching unlink: /unclaim returns a message and nonce, you sign it, and /unclaim/submit relays the removal. The editor reloads its state after each operation.

Every claim reads the contract's own get_nonce(address), and the nonce advances on each link or unlink. If two devices claim at once, the second submit fails with a nonce mismatch and restarts from claim.

Fullname, avatar and the legacy username are read-only.

Leaderboards

/trends/leaderboard ranks accounts by portfolio performance from GET /api/accounts/leaderboard.

Each row carries address, chain_name, aum_usd, pnl_usd, roi_pct, mdd_pct, buy_count, sell_count, volume_usd, created_tokens_count, owned_trends_count and a portfolio_value_usd_sparkline of timestamp-value pairs.

The default sort direction is descending for every metric except maximum drawdown (mdd), which sorts ascending because a smaller drawdown is better.

The account index

/trends/accounts reads GET /api/accounts, which pages at 1 to 100 rows and accepts a search term matched against the address, chain_name, public_name, username and fullname. order_by takes exactly nine values, and anything else is a 400:

order_direction is ASC or DESC, defaulting to DESC. has_nostr=true returns only accounts that have linked a Nostr key, which is useful for a chat-contact suggester.

Both the account index and the leaderboard rank trading activity only; nothing ranks by posting, commenting, tipping or governance.

How public_name is computed

Server-side, by a fixed four-step ladder with no per-account preference:

prefered_aens_name   (links.prefaens — the AENS name the user explicitly linked)
chain_name           (resolved from the middleware)
username             (the legacy profile field)
address              (the ak_… itself)

See Names.

Related

• SuperheroID: what the profile is a view onto.
• Names: the name types and how one is resolved for display.
• AddressLink: the contract behind every editable field.
• Verifying Your X Account: the X link, and what its badge proves.
• Profile API: the endpoint-level reference.
• Portfolio: the holdings and performance numbers the profile surfaces.