Something went wrong. Please try again.
Please confirm that you want to (auto) launch this application by explicitly clicking the button below. You need to keep this tab open, if you close this page or navigate away, the launched app will be closed.
Recovering wallet, confirming vault status:
... if there are no errors and the Channel IDs line up, you're good.
We will need two things: a 'strongpin' and a 'passphrase'.
You can sort of think of the 'strongpin' as a debit card number or an email address, and the 'passphrase' as the PIN or a password. It's fine to write down the strongpin or store it on your computer, but the passphrase should only be written down in a safe place, or (ideally) memorized.
The strongpin will be generated once you hit 'Create Wallet', but you can override the passphrase we generated if you'd like.
You can also hit "Add Word" if you want greater security. We recommend 3-5 words for most purposes. And if you don't like any of the generated words, you can reload the page - your storage token has NOT yet been used.
Once you are satisfied, you can hit "Create Wallet". The storage token will not be consumed until after the NEXT step, which is to register / authorized your wallet on the server - at which point we call it a "Vault".
... generating new wallet ... please wait ... 10M PBKDF2 iterations ...
Wallet created. Here is the full wallet object. However note that you only need to keep track of the 'strongpin' and 'passphrase'. The private key shown is derived from those.
As a technical FYI, the above wallet uniquely gives ownership of this channel. But again, this is derived from the above.
To turn a wallet into a vault, you need to register it with the server. Once you hit the button below, your storage token will be consumed and the budget it carries used to initialize your vault.
Here's the full channel handle. Registering it on the server ...
... again, this is derived from the wallet's strongpin and passphrase. But if you're doing development, sometimes you want to copy-paste the above - if you have the above 'handle' you can programmatically connect to the channel ... now we're just confirming from the server ...
... if all has gone well we should now have a vault. Below are 'channel keys' reflected back by the server.
Notably, it should confirm that your public key (above) is the owner of the channel. If they line up, then that's it.
You do not need to login above, you are "logged in".