This repository has been archived by the owner on Jun 21, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 58
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 #266 from PureStake/master
Release 1.6.0-b
- Loading branch information
Showing
71 changed files
with
2,051 additions
and
809 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 |
---|---|---|
|
@@ -5,4 +5,5 @@ | |
**/packages/dapp/lib | ||
.DS_Store | ||
test*.png | ||
**/coverage | ||
**/coverage | ||
**/test-project/results |
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,66 @@ | ||
# AlgoSigner Ledger Periphreral Hardware Actions | ||
|
||
## Overview:<hr /> | ||
Allow the AlgoSigner extension to work with the primary Ledger device account via HID for transaction signing on pay and asset transactions. This includes transactions originating in the extension and from DApps. | ||
|
||
It supports adding the account to your normal accounts tracking in the extension to supply both methods with the ability to sign. | ||
|
||
## Common Errors:<hr /> | ||
During any action the ledger device may prompt to connect. If the device is not connected then the screen may be blank. | ||
|
||
<br /><img src="./ledger_images/connect_err0.png" width="400" /><br /> | ||
|
||
If the device is connected, but the app is not open you may recieve a not supported error. | ||
|
||
<br /><img src="./ledger_images/connect_err1.png" width="400" /><br /> | ||
|
||
## Adding an address:<hr /> | ||
Open AlgoSigner and go to the default account overview. | ||
With the desired network selected click the "Add Account" button at the bottom of the page. | ||
Then choose "Link hardware device account" from the options. | ||
|
||
<br /><img src="./ledger_images/connect0.png" width="400" /><br /> | ||
|
||
The page will inform you that it must open AlgoSigner in a tab to connect to the device. Press "Continue". | ||
A new tab should open in the window where AlgoSigner is active. | ||
|
||
<br /><img src="./ledger_images/connect2.png" width="400" /><br /> | ||
|
||
Populate the Account name field with the value name of the new account. | ||
Verify the device is connected, unlocked and that the Algorand application is installed and active then press "Add Address". | ||
This will get the default account for the connected device. | ||
Once this address is obtained it will be added to your AlgoSigner account and you are free to close the tab. | ||
|
||
<br /><img src="./ledger_images/connect3.png" width="400" /><br /> | ||
|
||
## Signing with the extension:<hr /> | ||
First you must add an address to the appropriate network. | ||
With the proper network added you can select the account from the list of accounts. | ||
This will show you the normal account information and give you the option to "Send" as normal. | ||
After entering your transaction information and choosing to send you will be prompted for your password. | ||
Once your password is deemed correct and the address is internally determined to be a hardware account a new tab will automatically open. Here you will be presented with a similar transaction view to one seen from DApps in the extension. | ||
|
||
<br /><img src="./ledger_images/sign_extension0.png" width="400" /><br /> | ||
|
||
You can review here, but you should verify ALL data thoroughly from the Ledger device. | ||
Verify the device is connected, unlocked and that the Algorand application is installed and active then press "Send to device". | ||
After signing you will be presented with the transaction id and the transaction will be sent to the network. | ||
You are then free to close the tab. | ||
|
||
<br /><img src="./ledger_images/sign_extension1.png" width="400" /><br /> | ||
|
||
## Signing with a DApp:<hr /> | ||
First the user must add an address to the appropriate network. | ||
A transanction can be then be sent with the network and matching Ledger address. | ||
The user will be presented with the normal sign page. | ||
Once the password is deemed correct and the address is internally determined to be a hardware account a new tab will automatically open. | ||
The new tab will show the same information the user just seen on the normal sign screen. | ||
They are free to review here, but should verify ALL data thoroughly from the Ledger device. | ||
Verify the device is connected, unlocked and that the Algorand application is installed and active then press "Send to device". | ||
After signing the blob will be sent back to the DApp tab in the same way that a transaction sign normally does from AlgoSigner. | ||
|
||
<br /><img src="./ledger_images/sign_dapp0.png" width="800" /><br /> | ||
|
||
The blob will also be presented to the user indicating they are free to close the tab. | ||
|
||
<br /><img src="./ledger_images/sign_dapp1.png" width="400" /><br /> |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
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
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 |
---|---|---|
@@ -1,22 +1,24 @@ | ||
{ | ||
"name": "@algosigner/dapp", | ||
"version": "1.5.2", | ||
"version": "1.6.0", | ||
"author": "https://developer.purestake.io", | ||
"repository": "https://github.com/PureStake/algosigner", | ||
"license": "MIT", | ||
"description": "Sample DAPP for use with AlgoSigner.", | ||
"scripts": { | ||
"build": "npm run clean && webpack", | ||
"clean": "rm -rf ./dist/", | ||
"test": "jest" | ||
}, | ||
"devDependencies": { | ||
"jest": "^26.4.2", | ||
"jest": "27.0.0", | ||
"ts-loader": "^7.0.5", | ||
"typescript": "^3.9.7", | ||
"webpack": "^4.44.1", | ||
"webpack-cli": "^3.3.12" | ||
"webpack-cli": "^3.3.11" | ||
}, | ||
"dependencies": { | ||
"@types/jest": "^26.0.14", | ||
"ts-jest": "^26.3.0" | ||
"ts-jest": "^27.0.0" | ||
} | ||
} |
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
Oops, something went wrong.