You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 21, 2023. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+17-27Lines changed: 17 additions & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,48 +10,38 @@ _This is the preferred solution for end-users, updates will be automatically ins
10
10
11
11
Developers working with dApps may also install directly from the release package, or by downloading the project and building it.
12
12
13
-
# `AlgoSigner.sign()` and `AlgoSigner.signMultisig()` have been officially deprecated.
13
+
##`AlgoSigner.sign()` and `AlgoSigner.signMultisig()` have been officially deprecated.
14
14
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
16
18
17
19
### 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.
21
21
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
22
26
23
27
## New Users
24
28
25
29
- 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)
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.
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.
Copy file name to clipboardExpand all lines: docs/dApp-guide.md
+3-7Lines changed: 3 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,13 +10,9 @@ DApp users can trust AlgoSigner to:
10
10
- Authorize transactions without giving dApps direct access to their keys
11
11
- Sign and approve transactions when using dApps
12
12
13
-
## v2 Signing
13
+
## Signing transactions with AlgoSigner
14
14
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).
16
16
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).
Copy file name to clipboardExpand all lines: docs/dApp-integration.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,8 +4,6 @@
4
4
5
5
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.**
6
6
7
-
This guide covers the new v2 Transactions Signing method, docs for the legacy v1 signing are [here](legacy-dApp-integration.md)
0 commit comments