Public root
Marketing and trust
Homepage, security, supported assets, FAQ, backup, recovery and launch guides live on the public root.
How It Works
A wallet flow that explains itself.
The public launch surface exists so users can understand the path before they face the app shell. This is the basic operating model: create or unlock locally, verify the network, protect your recovery data and test before scaling up.
Core sequence
Setup, review, protect, then send.
WEB4 Wallet is easier to trust when the steps are explicit. The point is not to rush through the app. The point is to understand the path.
- Open the wallet app at /app/ and create or unlock access locally.
- Review supported networks, balances and address views before you attempt a transfer.
- Read and complete the backup guide so you know how recovery will work if the device changes.
- When sending, verify recipient, network, asset and fee context, then start with a small amount.
Why the public site matters
The app and the acquisition surface now do different jobs.
The wallet app is intentionally privacy-focused. The public site is now built for explanation, trust and launch distribution.
Wallet app
Separate app shell
The wallet interface lives at /app/ and remains isolated from the crawler-facing acquisition surface.
Launch outcome
Better for search and paid traffic
Visitors now land on explanations and trust signals first instead of a generic app shell.
The shortest safe path is still not a blind path.
If you want the fastest route into the product, start by understanding the supported networks and the recovery story.