Review, Remediation et Upgrades

Review

Évaluation technique et sécurité centrale

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.

Le client reçoit :

• Executive Summary (état global du système, risques clés, priorités immédiates, readiness pour l’objectif déclaré)
• Findings / Risk Register (problème, composant affecté, impact technique, impact sécurité/fiabilité, sévérité, preuves, conditions d’exploitation/échec, remediation recommandée)
• Prioritized Remediation Roadmap (feuille de route de remédiation priorisée)
• Architecture / Engineering Recommendations (recommandations d’architecture / d’ingénierie)
• Validation Plan (tests, validation sécurité, checks de configuration, checks de régression, re-review si nécessaire)

Remediation

Remédiation d’issues techniques et de sécurité

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.

Le client reçoit :

• Scoped Fix Plan (liste d’issues convenue, priorité, critères d’acceptation et risque de changement)
• Implemented Fixes (changements de code, configuration, architecture et ops selon besoin)
• Verification Evidence (tests, checks sécurité, checks de configuration et résultats de régression)
• Change Documentation (ce qui a changé, pourquoi, comment l’opérer, residual risk s’il y en a)
• Handoff for Follow-up (prochaines étapes claires, y compris re-check ou re-review ciblé si nécessaire)

Upgrades

Développement de features et amélioration produit

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

Le client reçoit :

• Feature Scope & Design (exigences, interfaces, contraintes et considérations Bitcoin/sécurité)
• Implementation on the Existing Product (features livrées dans le codebase existant)
• Tests & Validation (couverture unit/integration, checks sécurité pertinents et protection de régression)
• Documentation & Handoff (fonctionnement, opération et extension de la feature)
• Upgrade Path Notes (rollout, compatibilité et readiness de production du changement)

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.