Hardware Lab

Where money and approvals touch hardware: card terminals that emit ISO 8583 / EMV data into the graph, a security key that signs the evidence an approval rests on, an enclave that holds the consortium's blinding key, and private set intersection between banks. The devices are simulated at $0; signatures, hashes and key exchange are real.

simulated devices · real cryptographyVerified on real tools

Recent card taps

–

0 alertedPOS and ATM twin, last 20

From the Wokwi ESP32

–

source = wokwitaps posted by the simulated board

Enclave

–

PCR0 · SHA-384attesting…

Bank sync links

–

–bank graphs through the enclave

API /hardware/* · connecting…

Loading terminals…

Verified on real tools

Screen recordings of public third-party tools reading BankWeave's own output: the Wokwi simulator running our sketch, EMVLab decoding our TLV, webauthn.me decoding our assertion, and FalkorDB Cloud showing the node the signature writes.

wokwi.com/projects/new/esp32
The ESP32 terminal running in WokwiLoading recording…

The ESP32 terminal running in Wokwi

hardware/wokwi/sketch.ino on a simulated ESP32-DevKitC. Each button press is an HTTPS POST to /hardware/pos-tap; the OLED shows the response and the serial monitor prints the card, the ISO 8583 response and EMV field 55.

emvlab.org/tlvutils
EMVLab.org decodes our field 55Loading recording…

EMVLab.org decodes our field 55

The EMV TLV from a live terminal tap pasted into EMVLab's BER-TLV decoder: amount 9F02, IFD serial 9F1E, application transaction counter 9F36 and cryptogram information data 9F27 = 80 parse cleanly.

webauthn.me/debugger
webauthn.me inspects our FIDO2 assertionLoading recording…

webauthn.me inspects our FIDO2 assertion

A passkey assertion from an approval signature, decoded by Auth0's WebAuthn debugger: the clientDataJSON challenge is the case Merkle root, the origin is the BankWeave site, and authenticatorData carries the flags and signature counter.

browser.falkordb.com
The taps are edges in FalkorDB CloudLoading recording…

The taps are edges in FalkorDB Cloud

FalkorDB's own browser on our Cloud instance: the cross-bank ring, algo.pageRank, the (:Account)-[:CARD_TXN]->(:Terminal) edges the terminals (and the Wokwi ESP32) write, a SAR's provenance chain and vector KNN. Read-only queries; hostname cropped.

Also used as an external check: OpenSanctions ↗ for sanctions matches on case pages, and Chrome's virtual authenticator ↗ for WebAuthn without a physical key.

What is real and what is simulated

PieceRealSimulated
Card terminalsBER-TLV encoding (decodes on EMVLab), ISO 8583 field layout, CARD_TXN and USES_DEVICE writes to FalkorDB, alerts the agents triage, impossible-travel and ATC-replay detectionthe terminals and cards; 9F26 is an HMAC, not a chip's 3DES/AES MAC
ESP32 on Wokwithe circuit runs in the Wokwi simulator and makes real HTTPS posts to this APIthe board is a simulator
Security keyWebAuthn ES256 verification, signature counter, Merkle root over claims, evidence and sentences, seal break on revocationVaultKey is a WebCrypto key in this tab (WebAuthn can use a real key)
Enclave / HSMHMAC-SHA256 blinding, SHA-384 PCRs, ES384-signed Nitro-style document, EnclaveAttestation nodes, ingestion refused with 423 while quarantinedno TEE hardware or AWS Nitro PKI chain
PSIX25519 scalar multiplication, commutative blindingboth banks run in one process