Review, Remediation und Upgrades

Review

Kern-Technik- und Security-Bewertung

GreyBound Review is a technical and security assessment of a Bitcoin system that already exists: wallet, signing path, node, backend, indexer, or side chain. Do this before mainnet funds or a public launch. The client gets an executive summary, a risk register, a remediation roadmap, and a validation plan. This is not a public contest report.

Review is for architecture and trust boundaries. Remediation is for issues already named. Upgrade is for new features in a product that already runs.

Der Client erhält:

• Executive Summary (Gesamtzustand des Systems, Schlüsselrisiken, unmittelbare Prioritäten, Readiness für das genannte Ziel)
• Findings / Risk Register (Problem, betroffene Komponente, technischer Impact, Security-/Reliability-Impact, Severity, Evidence, Bedingungen für Exploitation/Failure, empfohlene Remediation)
• Prioritized Remediation Roadmap (priorisierte Behebungs-Roadmap)
• Architecture / Engineering Recommendations (Architektur- / Engineering-Empfehlungen)
• Validation Plan (Tests, Security-Validation, Configuration Checks, Regression Checks, Re-Review falls nötig)

Remediation

Behebung technischer und Security-Issues

GreyBound Remediation fixes Bitcoin infrastructure issues the client already knows or that Review found. The work is code, configuration, architecture, and operations on the running system, then checks and handoff.

Der Client erhält:

• Scoped Fix Plan (vereinbarte Issue-Liste, Priorität, Acceptance Criteria und Change Risk)
• Implemented Fixes (Code-, Config-, Architektur- und Ops-Änderungen nach Bedarf)
• Verification Evidence (Tests, Security Checks, Configuration Checks und Regression Results)
• Change Documentation (was sich geändert hat, warum, Betrieb und Residual Risk falls vorhanden)
• Handoff for Follow-up (klare nächste Schritte inkl. gezieltem Re-Check oder Re-Review falls nötig)

Upgrades

Feature-Entwicklung und Produktverbesserung

GreyBound adds features to a Bitcoin wallet or signing stack that already ships. The work goes into the live codebase: descriptors, PSBT flows, multisig, hardware-signer paths, fee and coin selection, and the backend or indexer the wallet uses.

This is for

• a mobile, desktop, or extension Bitcoin wallet that already exists
• a signing service or non-custodial payments path that already exists
• Bitcoin or a side chain the client already runs

This is not for

• building a new wallet from nothing
• a template wallet for many chains

Der Client erhält:

• Feature Scope & Design (Requirements, Interfaces, Constraints und Bitcoin-/Security-Überlegungen)
• Implementation on the Existing Product (Features im bestehenden Codebase)
• Tests & Validation (Unit/Integration Coverage, security-relevante Checks und Regressionsschutz)
• Documentation & Handoff (Funktion, Betrieb und Erweiterung)
• Upgrade Path Notes (Rollout, Kompatibilität und Production Readiness der Änderung)

What we need from you

To start, we need the running system:

• what is live today
• what must not break
• what you want changed or proved
• who can answer questions on the repo

If the system signs or moves bitcoin, we need enough of the signing path to trace one transaction from screen to bytes. If you cannot share that yet, say so. We will say what we can still do.

What the work is

A Review maps trust boundaries and names what can lose funds.

Remediation changes the running code or config and shows the check.

An Upgrade adds a feature in that same codebase.

What we decline

We do not produce a public audit PDF meant only for a launch page.

We do not take a chain we do not operate.

We do not build a new wallet from nothing for every network.

Email contact@greybound.tech. We reply in 1–2 business days.