Roles and access
Five roles with real separation: Viewer, Maker, Checker, Compliance, and Examiner. Sign-in works with your existing single sign-on, so each person gets only the access their job requires.
Bitcoin QuayProduct
What you actually get
Running a Bitcoin node is a solved problem. Running one that survives an exam is not. The Operator Console is where your team approves actions, manages what the node connects to, and produces the record an examiner asks for. It is built for credit union and CDFI operators.
Dual-control approvals
Sensitive actions go into a queue where a second person has to approve them. Money movement is handled as a request tied to your payment vendor's decision, never a free-form send from the console.
Approved connections
An administrator maintains the list of systems Bitcoin Quay is allowed to talk to. In production, it connects only to what is on that list.
Evidence export
Actions are logged so you can export an evidence pack for an examiner. We will not claim SOC or PCI readiness we have not earned.
Bitcoin node management
See and manage your institution's node from one place. The underlying Bitcoin protocol code stays in sync with the open-source project, separate from this console.
Guardrails against scope creep
When an action would pull member data or new regulated activity into scope, Bitcoin Quay flags it and stops, rather than letting it through quietly.
This page describes intent, not shipped features. A capability goes live when its controls, vendor connections, and evidence trail actually work, not when the marketing page says so.