Creator profiles and links
What you can do.
Give fans one place to find your profile and links. Choose your page theme and set up an alert view for your stream.
- Profile and link management
- Page themes
- Stream alert view
What’s been built
- Profiles, links and page styles in one placeReady
- OBS alerts for live streamsReady
- Fan support paymentsComing soon
Technology & architectureCreator pages with a Web3 support path.Explore the architecture
How it works, in three steps
Verify the creator account, confirm the fan's approved USDC transfer, then pass the result to the broadcast.
The server verifies both the Privy access token and current user record. It binds the verified primary wallet to the account used to manage profiles, links and broadcast themes.
Authorization binds sender, recipient, amount, validity and nonce. The mainnet candidate checks JGas fee-support readiness before sending USDC directly from the fan to the creator.
Verification checks the official USDC contract, amount, recipient and bound JGas final status. Azure Web PubSub delivers the recorded result, with retries for failed alerts.
The server verifies both the Privy access token and current user record. It binds the verified primary wallet to the account used to manage profiles, links and broadcast themes.
Security & design principles
Limit the authorization
0.01 USDC · Integer units · NonceThe transfer amount is checked as 10,000 integer base units. Expiry and nonce checks keep authorization bound to the approved amount and recipient.
Persist verified state
PostgreSQL · Row lock · IdempotencyTransactions and row locks protect order updates, and retries stay linked to the original order. Raw signatures are not persisted.
Share only broadcast details
Anonymous event · Receive-only grantOBS receives limited fields such as an anonymous label and amount. Wallet addresses, email and transaction hashes stay outside public events.