Doichain/dapp

Modify REST-API call "verify" - provide interface for postfix smtp-filter

Open

#102 opened on Mar 29, 2019

View on GitHub
 (3 comments) (0 reactions) (1 assignee)JavaScript (13 forks)auto 404
A prioritybountyfeaturegood first issuehelp wanted

Repository metrics

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

Description

As described in #101 , the verify call needs to be extended and should check if the local dApp has verifiable local data which have a valid permission (correct signatures) inside the blockchain.

In case the local database doesn't hold nameId and or public_key of Alice, we must either purely rely on the local data or find a way to gather or save public_key of Alice in order to decrypt the signatures inside Doichain. Please lets further discuss this issue here!

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

Contributor guide

Research direction
Examine the existing verify endpoint implementation in the Meteor app. Understand how local data is stored and how to retrieve public keys from the blockchain or local database. Look at the referenced issue #101 for context. Identify where to integrate signature verification and permission checks.
Tech stack
javascript
Domain
backendapi
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
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
GitJavaScriptbasic blockchain concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40