-
Notifications
You must be signed in to change notification settings - Fork 217
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 #363 from AleoHQ/fix/5-8-24-0
Rename `aleo.tools` to `provable.tools`
- Loading branch information
Showing
9 changed files
with
24 additions
and
24 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
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
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
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 |
---|---|---|
|
@@ -31,7 +31,7 @@ Make sure you have both Leo and snarkOS installed on your machine. | |
|
||
### 2. Generate your test keys and wallet address | ||
|
||
* In your favorite browser, navigate to [https://aleo.tools/](https://aleo.tools/) and click the **Generate** button | ||
* In your favorite browser, navigate to [https://provable.tools/](https://provable.tools/) and click the **Generate** button | ||
* Save your **Address**, **View Key**, and **Private Key** in a safe place, you'll need them later | ||
|
||
### 3a. Seeding your wallet with credits | ||
|
@@ -106,7 +106,7 @@ Alternatively, you can find your execute transaction confirmation by going to [t | |
|
||
### 5. Obtain your records plaintext | ||
|
||
* Navigate to [https://aleo.tools/](https://aleo.tools/) and click the **Record** tab in the nav bar at the top of the page | ||
* Navigate to [https://provable.tools/](https://provable.tools/) and click the **Record** tab in the nav bar at the top of the page | ||
* Place the record ciphertext you copied in the previous step in the `Record (Ciphertext)` field | ||
* Place your view key in the `View Key` field | ||
* Copy the plaintext record provided. If you do not see it, it's likely you copied the wrong ciphertext record in step 4. Consider revisiting or reach out to `[email protected]`. | ||
|
@@ -151,7 +151,7 @@ Finally, it is time to execute the application you just deployed! | |
|
||
* You'll need to update the `--record` flag with the latest transaction linked to your wallet balance. In this case, you can obtain that by going to the following URL: https://api.explorer.aleo.org/v1/testnet3/transaction/$DEPLOY_TX_ID but replace $DEPLOY_TX_ID with the transaction ID provided to you once your application was deployed (or from the most recent transaction linked to your wallet address). An example URL looks like so: https://api.explorer.aleo.org/v1/testnet3/transaction/at1rkkpqu5k4rt86zzccczw6cxeyvrl7hxydvvv7dhl7zr7p9w40c8s70kwm8 | ||
* In the JSON object provided at https://api.explorer.aleo.org/v1/testnet3/transaction/$DEPLOY_TX_ID, navigate to: `object.fee.transition.outputs[0].value` and copy the record ciphertext value. | ||
* Head to [aleo.tools](https://aleo.tools/) and navigate to the **Record** tab and paste the record ciphertext you just copied as well as your wallet's view key | ||
* Head to [provable.tools](https://provable.tools/) and navigate to the **Record** tab and paste the record ciphertext you just copied as well as your wallet's view key | ||
* Similar to the steps we followed for a deploy transaction, update your `RECORD` variable with the record plaintext you just decrypted by doing the following: | ||
|
||
<!-- markdown-link-check-enable --> | ||
|
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