Reference
Security
How keys are kept, what Nectar will sign, and what needs your approval.
How keys are kept#
Each wallet's private key is sealed with AES-256-GCM under a server key before it is stored. A key is opened only to sign one of your transactions or for an export you approved, never for a suspended account, and only after checking it derives to that wallet's own address. Every read is scoped to your account.
What Nectar will sign#
Before anything is signed, the transaction is checked against a short allowlist. Anything else is refused.
| Transaction | Only when |
|---|---|
| A buy or sell | Through NectarRouter, paying out to the wallet itself |
| A token approval | With NectarRouter as the only spender |
| A HYPE withdrawal | From a funder, approved in Telegram for exactly that amount and recipient |
| An internal transfer | HYPE to another wallet of the same account |
What needs Telegram#
- Signing in
- Approve in Telegram, after matching the code
- Withdrawing HYPE out of Nectar
- Approve the exact amount and recipient
- Exporting a private key
- Approve, then see it once
- Trading, funding, consolidating
- No approval: nothing leaves your account
Exporting a key#
Tick that you understand what an exported key allows, then approve in Telegram. The key is shown once, for 60 seconds, and never again. You can ask at most 5 times a minute, and every export is recorded (the key itself never is). An archived wallet's key can still be exported.
Good habits#
- Keep only what you are trading in Nectar; withdraw the rest.
- An imported key also stays wherever you copied it from. Anyone holding it can move that wallet's HYPE.
- Check the code, the amount and the recipient in Telegram every time.