jogeshwar01 / jogeshwar01/tesior-web
store signature in db before sending to blockchain
Open
bounty $
bug
good first issue
- Dominant language
- TypeScript
- Stars
- 9
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
- Currently we are storing after sending and confirming txn
- Ideally we should first store the signature in the payment/escrow db with status `Processing` before sending it to the blockchain
- After confirming txn on the blockchain, mark the status as `Success`
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the payment or escrow database write and the blockchain transaction send and confirmation flow. Change the sequence so the signature is stored with status `Processing` before sending, then mark it `Success` after confirmation; verify both status transitions and failure behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, typescript
- Domain
- backend, blockchain, database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100