Docs · Products
Bengar Wallet PREVIEW
A personal wallet whose key stays in the browser — with its current limits.
What it does
| Page | What it does |
|---|---|
| /onboarding | Create a new account or import an existing one. |
| /home | Balances. |
| /send | Build, review and sign a transfer. |
| /receive | Your address. |
| /assets | Issued assets you hold. |
| /history | Past transactions. |
| /staking | Delegate and view rewards. |
| /governance | Read proposals and vote. |
Key handling, stated plainly
- The private key is generated and used in the browser. It is never sent to a Bengar server.
- Bengar does not generate, receive, store or recover anybody's mnemonic. If you lose it, we cannot help — and that is the design, not a gap in support.
- What you see is what you sign: the review screen is rendered from the transaction that will be signed.
Current limit: key material lives in memory for the session. There is no encrypted at-rest wallet store yet, so a reload asks for your key again. Do not read “wallet” here as “encrypted persistent wallet” — it is not one yet.
- There is no dApp connector. Nothing external can ask this wallet for a signature.
- A passkey is not used as a chain key. Different domains, different keys.
- Holding an account grants no Trust authority.