marigold-dev / marigold-dev/decookies
Singning using different wallets
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 9
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
## Context
Following #13 and #15 several issues had been created on the different wallets supported by Beacon SDK:
- Temple ✅ with Temple mobile app => https://github.com/madfish-solutions/templewallet-extension/issues/736
- Kukai => https://github.com/kukai-wallet/kukai/issues/400
- Umami => https://gitlab.com/nomadic-labs/umami-wallet/umami/-/issues/720
- Galleo => https://github.com/Cryptonomic/Deployments/issues/76
- Stribe => Seems to work, since it is using AirGap wallet under the hood...
This issue is there to follow the resolution of each Wallet.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the related context in issues #13 and #15, then check the linked Temple, Kukai, Umami, and Galleo wallet issues. Compare the signing status for each wallet, including Stribe, and update this tracking issue as each wallet’s resolution is confirmed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100