Verification process

How SecureSaaS sequences cold wallet fieldwork — from kickoff inventory through dual-control checks, draft binders, and optional transfer observation.

Kickoff and scope lock

We confirm wallet and device count, dual-control roles, review deadline, and whether historical ceremonies need reconstruction. You designate an operations contact. Engagement letter and deposit follow.

Device inventory fieldwork

On-site or via sealed photo evidence, we record hardware serials, custody locations, and firmware notes. Purchase invoices and RMA paperwork are matched where available. Gaps are logged, not guessed.

Dual-control and procedure drafting

Role matrices and access procedures are written against how your team actually operates. Emergency access paths are described without embedding secret material in our files.

Chain-of-custody and ceremony index

We populate a chain-of-custody log for the agreed period and index multi-sig ceremony evidence. Missing witness names or dates become remediation items, not silent omissions.

Draft binder review

Your operations contact receives a draft package. Comments focus on factual corrections. A second SecureSaaS reviewer checks internal consistency before finalization.

Optional transfer verification window

When a large withdrawal is planned, we schedule an observation session against the completed checklist: approvals, device identity, destination controls, and a written memorandum for your file.

Team reviewing documents in a meeting

What you keep; what we keep

Seed phrases and private keys never leave your control. Our working files hold serial numbers, role names, procedure text, and hashed references you approve. Printed binders can be produced for vault storage; digital copies are delivered over channels you designate.

Browse engagements Plan a kickoff