Simplify witness request to `digestMultibase` and enable 1:1 service mapping
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
No files, tests, or entry points are named. Start by locating the witness request schema and service configuration handling, then clarify the intended request shape and 1:1 mapping behavior with maintainers. Done should include an agreed interface, implementation scope, and tests covering requests addressed to differently configured services.
Written by the indexing model from the issue text.
Description
Description
Consider simplifying the witness request payload to hold only the digestMultibase value. This establishes a strict 1:1 mapping between a service URL and a specific witness configuration, eliminating the need for out-of-band options and their discovery.
Motivation
-
Client-Side Simplicity - Clients can manage a plain list of witness service URLs without storing or processing additional out-of-band configuration options. A client constructs a single, identical request payload and sends it to the targeted set of service URLs.
-
Scalability and Resource Optimization - Different cryptographic algorithms exhibit distinct CPU and RAM footprints. e.g.,
ecdsa-jcs-2019requires minimal resources, whereas post-quantum algorithms like mldsa, or combinations involving RDFC and longer keys, have much higher requirements. A 1:1 URL-to-service mapping allows infrastructure auto-scaling and resource allocation to be tuned with fine granularity per endpoint. -
Security and Key Isolation - Restricting each service instance to a single configuration ensures that the environment only operates on the specific private key required for that endpoint. It prevents cross-access to other cryptographic keys, narrowing the attack surface and reducing the blast radius of a potential compromise.
-
Traceability and Auditing - Monitoring traffic, tracking usage metrics, and performing compliance audits is highly efficient with 1:1 mapping. It eliminates the operational complexity of decomposing and parsing logs from a 1:M (one endpoint to multiple configurations) setup.
-
Fault Isolation - If a specific cryptographic library, algorithm, or configuration encounters a runtime failure or vulnerability, the impact is isolated to that specific endpoint. The rest of the witness infrastructure remains unaffected, ensuring higher overall system availability.
- Dominant language
- JavaScript
- Stars
- 4
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from digitalbazaar/hmbd
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
digitalbazaar/hmbd#5 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
digitalbazaar/hmbd#3 ·
-
OSV
Difficulty 3/5 1-2 days Newbie friendliness 52/100
digitalbazaar/hmbd#2 ·
All issues in digitalbazaar/hmbd
Similar issues
-
Clinic sharing: fast sync refusal message suggests Delete Data, which only developer builds haveOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
avniproject/avni-client#2228 ·
-
bug confirmed issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
open-webui/open-webui#33196 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
fable-compiler/Fable#5157 ·
Maintainers usually reply within 1 day
-
New tool: PaperBananaPossibly taken @github-actions claimed this today. Opensubmission triage
Difficulty 1/5 Under an hour Newbie friendliness 75/100
kausalflow/tools#243 · 1 comment ·
Maintainers usually reply within 1 day
-
area: apple-music area: build-release bug effort: small priority: high
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
ChristianTabor/Argon#32 ·
Maintainers usually reply within 1 day