Doichain/dapp

Confirmation not immediately forwarded to Send dApp

Open

#112 opened on Jul 10, 2019

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (13 forks)auto 404
A prioritybountybuggood first issuehelp wantedtest

Repository metrics

Stars
 (6 stars)
PR merge metrics
 (PR metrics pending)

Description

As also described in #36 and #14 after a Doi-Request got confirmed in an email, the confirmation dApp doesn't seem to callback Alice (Send-dApp) immediately.

The confirmation is displayed as confirmed right now after a block was confirming the two transactions.

Please see https://bounties.doichain.org/ how to apply for Doichain bounties.

Contributor guide

Research direction
Investigate the callback mechanism from the confirmation dApp to the Send dApp after email confirmation. Trace the code path for forwarding confirmation and identify where the delay or missing callback occurs.
Tech stack
javascriptnodejs
Domain
frontendbackend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitJavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70