dartroom / signer Goto Github PK

Tasks:

• Login with Pera Wallet
• switch between Pera Wallet addresses
  - [ ] sing transactions with Pera Wallet moved to new issue

Source code: https://github.com/perawallet/connect

Creating the base interface for the signing package. The base system needs to ask for enough info from the signer to be able to integrate with all the services.

Tasks:

• create an interface for the signing functions
• create an interface for wallet address management

Signing interface

The signing interface might look something like this.

const signedTxns = await sign(context, 'Pera', 'Failed to sign transaction',[[
      { txn: txns[0], signers: [addr], doNotSign: false }
]])

Where transactions are passed in the most advanced format so that complex signers like the Pera Wallet can be supported. In the dart-signer system, the transactions get formatted to fits every signing package's different needs.

Integrate the various ways of signing from the different integrations into one interface.

Tasks:

• integrate MyAlgo
• integrate Pera
• integrate AlgoSigner
• integrate Exodus

Tasks:

• Login with Algosigner
• switch between Algosigner addresses
  - [ ] sing transactions with Algosigner moved to new issue

Source code: https://github.com/PureStake/algosigner

https://github.com/blockshake-io/defly-connect

Integrate MyAlgo connect.

Tasks:

• Login with MyAlgo
• switch between MyAlgo addresses
  - [ ] sing transactions with MyAlgo moved to new issue

Source code: https://github.com/randlabs/myalgo-connect

Pera wallet works in dev mode when installed in the Nuxt project. But after the build process, it fails to load when called.

Add a github action to publish the package to NPM and github

Tasks:

• Login with Exodus
• switch between Exodus addresses
  - [ ] sign transactions with Exodus moved to new issue

Docs: https://docs.exodus.com/api-reference/algorand-provider-api/

Test and rework the Pera and AlgoSigner transaction formats to properly support rekeyed accounts.

Algo Signer

https://github.com/PureStake/algosigner/blob/develop/docs/dApp-integration.md

The AlgoSigner seems to be able to figure out the correct singing account if no signer array is passed. But when we do specify the signers we might need to set the authAddr field as well to get the proper account to sign the transaction.

Pera

https://docs.perawallet.app/references/pera-connect/

Pera wallet behaviour has not been tested yet. Might be the case here as well that is few specify the optional signers array, it won't be able to figure out the signer anymore. However, the Pera wallet does not have an authAddr field to compensate, so the behaviour might be different.

Support base64 in addition to Uint8array for the input transaction format to bring the package in line with the supported output formats of the dartroom/contracts package.

Tasks:

• add module (.mjs) compile option to build command
• add linting
• add ci/cd