Privy Integration
Privy owns user sign-in and wallet creation. Remlo uses it to keep Tempo wallet management out of the critical path for both employers and employees.Current chain configuration
| Property | Value |
|---|---|
| Chain name | Tempo Moderato |
| Chain ID | 42431 |
| Currency | USD, 6 decimals |
| RPC | https://rpc.moderato.tempo.xyz |
| Explorer | https://explore.tempo.xyz |
Login surface
| Mechanism | Current status |
|---|---|
| Enabled | |
| SMS | Enabled |
| External wallet | Enabled |
| Passkey | Enabled through the login screen action |
| Disabled | |
| Disabled | |
| Discord | Disabled |
| Farcaster | Disabled |
Embedded wallet behavior
embeddedWallets.createOnLogin is set to users-without-wallets. That means:
- A new user does not have to bring a wallet to start using Remlo.
- An employee invite can be accepted without any chain-specific setup.
- A wallet can still be linked later if the user prefers a self-custodied route.
Access model
- Middleware reads the Privy token from cookies for route protection.
- Internal APIs read the Privy JWT from the
Authorizationheader. - Product role is derived from Supabase, not from Privy alone.
WalletConnect
The current config can add WalletConnect support whenNEXT_PUBLIC_WALLETCONNECT_PROJECT_ID is present. That variable is optional in the current codebase.