BlockchainCommons / BlockchainCommons/Gordian

Requirements for next version of QuickConnect

Open
#66 6 comments 0 reactions 0 assignees View on GitHub
Dominant language
Shell
Stars
120
Forks
26
PR merge metrics
No merged PRs in 30d

Description

[QuickConnect](https://github.com/BlockchainCommons/Bitcoin-Standup/blob/master/Docs/Quick-Connect-API.md) is currently offered by BitcoinStandup (both Mac and Linux), BTCPayServer, Nodl, MyNode, RaspiBlitz full node tools and hardware, and is used currently by FullyNoded, FullyNoded2, and a couple of other experimental apps to allow secure connection via Tor v3 from a remote to your own personal full node. 

However, we know that QuickConnect needs another major iteration, and welcome contributions to requirements and/or proposals for the next version.

We invite you to share your thoughts here.

-- Christopher Allen

Contributor guide

Open the contributing guide

Research direction

Start by reading Docs/Quick-Connect-API.md and review the current QuickConnect deployments and users listed in the issue. Gather concrete requirements or a proposal for the next major version; done means a sufficiently detailed next-version direction is documented for discussion.

Written by the indexing model from the issue text.

Assessment

Domain
api, networking, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.