-
Notifications
You must be signed in to change notification settings - Fork 33
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #248 from BitGo/feat/add-sol
feat: add solana to non-bitgo recovery dropdown
- Loading branch information
Showing
15 changed files
with
8,702 additions
and
6,593 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
# Obtain Durable Nonce Instructions | ||
|
||
Wallet Recovery Wizard allows you to provide a durable nonce when building Solana recoveries. A durable nonce allows you to extend the 60 second broadcast window of Solana transactions. After selecting "SOL" or "TSOL" from the coin dropdown, you will see two fields: Durable Nonce: Public Key and Durable Nonce: Secret Key. You may either enter the keys for a durable nonce you already have prepared or follow the steps below to create one (Note: if you receiver an "unknown signer" error, skip to step 3 of the instructions below): | ||
|
||
1. Open a terminal window, clone the repository, navigate to the cloned repository and install node modules: | ||
|
||
```bash | ||
git clone [email protected]:BitGo/wallet-recovery-wizard.git | ||
cd wallet-recovery-wizard | ||
npm i | ||
``` | ||
|
||
2. Run the script to build a durable nonce with the "create" command, and save your public key and secret key: | ||
|
||
```bash | ||
npm run durable-nonce:build -- create | ||
``` | ||
|
||
3. Run the script to build a durable nonce with the "import" command, and copy and paste the public key and secret key into Wallet Recovery Wizard. | ||
|
||
i. If on Devnet, set the -n flag to "devnet": | ||
|
||
```bash | ||
npm run durable-nonce:build -- import -n devnet | ||
``` | ||
|
||
ii. If on Mainnet Beta, set the -n flag to "mainnet-beta": | ||
|
||
```bash | ||
npm run durable-nonce:build -- import -n mainnet-beta | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
Version 4.5.0 of the Wallet Recovery Wizard supports building transactions to recover NEAR from your BitGo Hot and Self-Managed Cold wallets. | ||
|
||
Below is a list full node RPC endpoints that must be called to broadcast the transaction as there are no suitable explorers available for NEAR. | ||
|
||
Construct the API request to the full node: | ||
|
||
Testnet Request URL: https://api.devnet.solana.com | ||
|
||
Mainnet Request URL: https://api.mainnet-beta.solana.com | ||
|
||
Method: POST | ||
|
||
Request Body format (find "serializedTx" in your downloaded JSON): | ||
|
||
```json | ||
{ | ||
"id": 2, | ||
"jsonrpc": "2.0", | ||
"method": "sendTransaction", | ||
"params": [ | ||
"serializedTx", | ||
{ | ||
"encoding": "base64" | ||
} | ||
] | ||
} | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.