bitshares / bitshares/bitshares-ui
[3][fletchertyler914] Feature Request: Offline Signing
- Dominant language
- JavaScript
- Stars
- 520
- Forks
- 575
- Avg merge
- 12h 7m
- Merged PRs (30d)
- 5
Description
1. The online wallet generate a transaction, json format, need:
a. TaPoS header,
b. not-too-soon expiration time,
c. required keys / signed keys (optional)
d. serialized (optional)
2. user copy the json to offline wallet, add signature
3. user copy the signed transaction json to online wallet, broadcast
PoC:
* online part:
* src: https://github.com/zhangweis/bts-trx
* live: https://www.dexfree.com/bts-trx/#/
* offline part:
* src: https://github.com/zhangweis/cold-bts
Contributor guide
Research direction
Start by reviewing the online PoC at https://github.com/zhangweis/bts-trx and the offline PoC at https://github.com/zhangweis/cold-bts. Compare their transaction-generation and signing flows with the wallet's existing entry points. Done means an online wallet can produce the requested transaction JSON, an offline wallet can add a signature, and the online wallet can broadcast the signed JSON.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blockchain, javascript, react
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100