Skip to content
This repository was archived by the owner on Jun 21, 2023. It is now read-only.

Commit 6f2ec55

Browse files
authored
Merge pull request #415 from PureStake/master
Patch 1.9.1
2 parents ae81eea + fb7d9c7 commit 6f2ec55

38 files changed

Lines changed: 635 additions & 562 deletions

README.md

Lines changed: 17 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -10,48 +10,38 @@ _This is the preferred solution for end-users, updates will be automatically ins
1010

1111
Developers working with dApps may also install directly from the release package, or by downloading the project and building it.
1212

13-
# `AlgoSigner.sign()` and `AlgoSigner.signMultisig()` have been officially deprecated.
13+
## `AlgoSigner.sign()` and `AlgoSigner.signMultisig()` have been officially deprecated.
1414

15-
## 1.9.0 Release
15+
An interactive transition guide is available [here](https://purestake.github.io/algosigner-dapp-example/v1v2TransitionGuide.html).
16+
17+
## 1.9.1 Release
1618

1719
### Main updates
18-
This update adds supports for easier transfers with the new autocomplete feature. Start typing an account or contact name on the destination field when sending Algos or ASAs and you'll be able to select the desired address from a dropdown. This also marks the end of the support of the older signing methods that were previously available.
19-
- Autocomplete support for UI-made transfers
20-
- `AlgoSigner.sign()` and `AlgoSigner.signMultisig()` have been deprecated
20+
This update adds supports for easier transfers with the new autocomplete feature. Start typing an account, contact name or name service alias on the destination field when sending Algos or ASAs and you'll be able to select the desired address from a dropdown. This also marks the end of the support of the older signing methods that were previously available.
2121

22+
- Autocomplete feature for UI-made transfers, supporting:
23+
- Accounts and Contact names
24+
- External name services (NFDomains and Algorand Namespace Service)
25+
- `AlgoSigner.sign()` and `AlgoSigner.signMultisig()` have been deprecated
2226

2327
## New Users
2428

2529
- Watch [Getting Started with AlgoSigner](https://youtu.be/tG-xzG8r770)
26-
- [Ledger Readme](docs/ledger.md)
27-
28-
## Adding Custom Networks
29-
30-
AlgoSigner users may add their own networks to the extension, for example BetaNet or the sandbox private network - [Instructions](docs/add-network.md)
30+
- [Using a Ledger device](docs/ledger.md)
31+
- [Adding Custom Networks](docs/add-network.md) (such as BetaNet or a private network)
32+
- [Troubleshooting Connection issues](docs/connection-issues.md)
3133

3234
## dApp Developers
3335

3436
For teams looking to integrate AlgoSigner into a project:
3537

36-
Developing with v2 Transaction Signing
37-
38-
- [dApp development guide](docs/dApp-guide.md)
39-
- [v2 AlgoSigner methods](docs/dApp-integration.md)
40-
41-
Legacy v1 Transaction Signing is going to be deprecated soon and is available only for reference purposes.
42-
Please use v2 when developing new apps and migrate existing apps that are still using v1 to v2 as soon as possible.
43-
44-
- [v1 Guide](docs/legacy-signing.md)
45-
- [v1 AlgoSigner methods](docs/legacy-dApp-integration.md)
46-
47-
## Roadmap
48-
49-
- UI improvements
50-
- Contribution guidelines
38+
- [dApp Development guide](docs/dApp-guide.md)
39+
- [AlgoSigner dApp Integration Guide](docs/dApp-integration.md)
5140

52-
### AlgoSigner development
41+
## AlgoSigner development
5342

54-
For developers interested in working with AlgoSigner [Extension Guide](docs/extension-developers.md). A contribution guide is in development.
43+
For developers interested in working with AlgoSigner, an [Extension Development Guide](docs/extension-developers.md) is available.
44+
Pull requests we accept need to be narrow in scope and all contributors need to sign (once) our [CLA](https://github.com/PureStake/algosigner-cla/blob/main/CLA.md) after submitting one in order for it to be considered.
5545

5646
## License
5747

docs/connection-issues.md

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
# AlgoSigner Connection Issues
2+
3+
If you're having issues accessing a dApp using AlgoSigner, you can try the following steps in order to delete any old existing connection that you may have lingering on the browser/website.
4+
5+
## Connection Troubleshooting
6+
7+
Find and press any disconnect button present on the dApp.
8+
9+
<img src="./connection_images/disconnect.png" width="300" />
10+
<br />
11+
<br />
12+
13+
Open the config menu and log out of AlgoSigner.
14+
15+
<img src="./connection_images/open-config.png" height="400" />
16+
<img src="./connection_images/logout.png" height="400" />
17+
<br />
18+
<br />
19+
20+
Reload the tab/window where the dApp is open and attempt to connect again.
21+
22+
<img src="./connection_images/reload.png" height="80" />
23+
<img src="./connection_images/connect.png" height="80" />
24+
25+
<br />
26+
<hr />
27+
<br />
28+
29+
## Additional steps
30+
31+
If the issue persists, try deleting your local browser cache and cookies before attempting to connect to the dApp again.
32+
33+
[Steps for Chrome](https://support.google.com/accounts/answer/32050)
34+
35+
[Steps for Brave](https://support.brave.com/hc/en-us/articles/360048833872-How-Do-I-Clear-Cookies-And-Site-Data-In-Brave-)
36+

docs/connection_images/connect.png

3.68 KB
Loading
12.5 KB
Loading

docs/connection_images/logout.png

25.2 KB
Loading
31.2 KB
Loading

docs/connection_images/reload.png

4.32 KB
Loading

docs/dApp-guide.md

Lines changed: 3 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -10,13 +10,9 @@ DApp users can trust AlgoSigner to:
1010
- Authorize transactions without giving dApps direct access to their keys
1111
- Sign and approve transactions when using dApps
1212

13-
## v2 Signing
13+
## Signing transactions with AlgoSigner
1414

15-
With the release of v2 signing, developers coding to the standard will be able to use the same code with any Algorand Wallet.
15+
You can start by looking at examples of how to sign transactions with AlgoSigner in the [example dapp](https://purestake.github.io/algosigner-dapp-example/index.html).
1616

17-
- Examples of signing with v2 are available in the [dapp examples repo](https://purestake.github.io/algosigner-dapp-example/index.html).
18-
- An interactive transition guide that demonstrates the differences between v1 and v2 signing is available as a link from the dapp examples repo or directly access the [transition guide](https://purestake.github.io/algosigner-dapp-example/v1v2TransitionGuide.html).
17+
Also available to read is our [dApp integration guide](dApp-integration.md).
1918

20-
### Developing a dApp
21-
22-
- Read [v2 dApp Integration Guide](dApp-integration.md)

docs/dApp-integration.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,6 @@
44

55
AlgoSigner injects a JavaScript library into every web page the browser user visits, which allows the site to interact with the extension. The dApp can use the injected library to connect to the user's Wallet, discover account addresses it holds, query the Network (make calls to AlgoD v2 or the Indexer) and request AlgoSigner to request for the user to sign a transaction initiated by the application. **All methods of the injected library return a Promise that needs to be handled by the dApp.**
66

7-
This guide covers the new v2 Transactions Signing method, docs for the legacy v1 signing are [here](legacy-dApp-integration.md)
8-
97
## Methods
108

119
- [AlgoSigner.connect()](#algosignerconnect)

docs/extension-developers.md

Lines changed: 9 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -10,21 +10,20 @@ There are multiple packages in the project that combine to build the overall ext
1010

1111
*https://github.com/PureStake*
1212

13-
- algosigner-> // Base project folder
14-
- dist-> // Folder containing the combined distribution components, used to install the extension, created on build
15-
- packages-> // Folder for scripts components that support the extension
16-
- common-> // Contains core elements used in other packages
17-
- crypto-> // Wrapper for encrypting and decrypting account information
18-
- dapp-> // AlgoSigner library that gets injected in dApps
19-
- extension-> // Extension definition and core files
13+
- algosigner -> // Base project folder
14+
- dist -> // Folder containing the combined distribution components, used to install the extension, created on build
15+
- packages -> // Folder for scripts components that support the extension
16+
- common -> // Contains core elements used in other packages
17+
- crypto -> // Wrapper for encrypting and decrypting account information
18+
- dapp -> // AlgoSigner library that gets injected in dApps
19+
- extension -> // Extension definition and core files
2020
- storage -> // Handles saving and loading of account information
2121
- test-project -> // Test wrapper for the package files
22-
- ui-> // Front end application for interaction within the extension interface
22+
- ui -> // Front end application for interaction within the extension interface
2323
- manifest.json // Extension definition file
24-
- package.json // Algosigner package, required packages, and scripts to build the project
24+
- package.json // AlgoSigner package, required packages, and scripts to build the project
2525
- readme.md // Project overview
2626
- docs -> // Guides and how-to's
27-
- dApp-integration.md // Guide to integrating dApps with AlgoSigner
2827
- media -> // Supporting images for this repository
2928
- LICENSE.txt // License for this repository
3029

0 commit comments

Comments
 (0)