Sophon Home
Sophon Home brings app discovery, digital identity, and wallet activity into one place. At Sophon, I worked across username reservation and claiming, smart-account transactions, ecosystem discovery, and participation features, connecting interfaces with backend services and smart contracts.
My work spanned interfaces, application logic, and integrations with backend services and smart contracts, with a focus on making complex interactions feel clear and responsive.
- my role
- Software engineer · Frontend & product engineering
- focus
- Onchain identity, smart-account transactions & ecosystem discovery
Sophon Home was built as a starting point for exploring the Sophon ecosystem: discovering apps, establishing an identity, managing assets, and accessing experiences connected to participation.
The challenge was bringing those pieces together. Someone discovering an app, reserving a username, or transferring an asset needed to understand the available actions and see their progress. The interface had to support those journeys across desktop and mobile, while coordinating backend services and smart contracts.
Identity and usernames. Onboarding, profiles, and reservation and claiming flows for Sophon usernames, represented onchain as NFTs. This connected name availability, eligibility checks, and ownership with the interface.
Wallets and smart-account transactions. Token and network selection, asset transfers, transaction history, and smart-account integration, including sponsored transactions and confirmation states.
Ecosystem discovery and participation. App discovery, search, profile activity, and integrations for challenges, badges, and reward claims.
Interaction details. Shared components, dialogs, loading states, animations, and responsive layouts across desktop and mobile.
The following example explores one part of that work: connecting username reservation and claiming to onchain ownership.
A Sophon username was more than a profile field. The name service represented names as NFTs using the ERC-721 standard, with ownership recorded by a smart contract. Reservation and claiming were separate steps, so the interface needed to show both the name’s state and what the user still needed to do.
I connected the claiming flow to eligibility checks and different verification routes, including social-account verification and ownership of a Guardian NFT. The flow checked ownership of the reserved name and used the appropriate contract call, with a signed proof from the backend for the social route.
This also depended on the wallet integration. I worked on shared transaction handling for smart accounts, including paymaster integration to sponsor gas fees so users could complete supported transactions without funding those fees themselves. The flow waited for transaction confirmation before continuing, guiding users from checking requirements through submitting the transaction and seeing the result.
