Silex guide
Silex Profiles
Silex Profiles let users build a public identity around their Silex activity, progression, links, and achievements.
Private until you publish
Visiting Profile settings creates a private draft for your canonical Silex account. A profile becomes public only after you choose a unique username and explicitly select Public. Private profiles return an unavailable public page and are not included in public discovery.
What can be public
Your chosen display name, username, short bio, selected provider avatar, manually entered X, Discord and Telegram handles, structured links, up to 10 custom links, Silex achievement badges, public Level progress, Shard balance, daily Voting Power, account month, Watchlist count, cumulative Community Points allocated, and participation counts may appear.
What stays private
Exact total XP, today's individual Community Point allocations, actual Watchlist projects, reaction history, notifications, email, Google identity, OAuth Discord identity, provider subject IDs, roles, sessions, and authentication data are never part of the public profile projection.
Social handles and provider identity
Public X, Discord and Telegram handles are entered manually in Profile settings and are independent from sign-in providers. A linked Discord account is not published automatically. Google login remains authentication-only. Selecting a Discord or Google avatar is a separate, explicit public-profile choice and never publishes the provider name, email or subject ID.
Progression
Public profiles show an allowlisted progression summary. Owner settings additionally show exact XP, XP remaining, today's available Voting Power and the UTC reset. Read how XP, Levels, Shards and Voting Power work.
Independent from project intelligence
User profiles, links, activity counts, and achievement badges have no effect on Silex Project Verification, Watch state, Listing status, contract analysis, or organic Trending.