VigiRail
VigiRail is the institutional payment and financial-messaging layer of VigiChain — ISO 20022-compatible, post-quantum, and gasless for the sender. It is a protocol subsystem, not a separate chain. On the testnet it can be joined and used today: an institution is admitted under a quorum of named authorities, signs with a real post-quantum key, and carries a payment from initiation to settlement. The chain can also carry and commit the rail, and no network has switched that on yet — so the rail says of itself that it is not committed by consensus, and its signature backend is pinned but not independently approved for production. Mainnet stays locked.
01
A VigiRail sender transfers exactly the business amount. No native VIGI to hold, no gas to price, no blockchain nonce to manage — the protocol never subtracts network cost from the transfer. Resource control is institutional instead: every participant holds a contracted capacity, counted in messages per window of blocks, so the limit is measured by the chain's own clock rather than by a clock an operator can set.
02
VigiRail is specified against the ISO 20022 families — customer initiation, clearing and settlement, cash-management reporting and business headers. The schema registry and usage profiles are a committed slot in the design and are NOT built: no shipped code validates a message against a schema today, and the rail carries a payload commitment rather than a payload. What already holds is the property that made the design this shape — raw XML is never a consensus format, and the chain verifies commitments instead of running a parser.
Read live from a VigiChain node. Nothing here is illustrative — including the limits.
Asking the network…
Source: /api/vigirail/status
A VigiRail sender transfers exactly the business amount. No native VIGI to hold, no gas to price, no blockchain nonce to manage — the protocol never subtracts network cost from the transfer. Resource control is institutional instead: every participant holds a contracted capacity, counted in messages per window of blocks, so the limit is measured by the chain's own clock rather than by a clock an operator can set.
VigiRail is specified against the ISO 20022 families — customer initiation, clearing and settlement, cash-management reporting and business headers. The schema registry and usage profiles are a committed slot in the design and are NOT built: no shipped code validates a message against a schema today, and the rail carries a payload commitment rather than a payload. What already holds is the property that made the design this shape — raw XML is never a consensus format, and the chain verifies commitments instead of running a parser.
The envelope is specified and not yet running: a key encapsulation establishes a shared secret, a pinned key-derivation function produces the encryption keys, and authenticated encryption protects the payload. None of that is performed by this build — there is no key-encapsulation code in the node, and the rail says so when asked. What is real today is the part the chain depends on: the payload never reaches the public ledger in the first place. Names, account identifiers, amounts and compliance data are carried as commitments, and the institutional post-quantum signature that binds the message is checked on every one.
The design separates visibility from control: a viewing capability would let a regulated participant see a scoped set of payments without ever granting authority to spend or settle. None of it is built — the node contains no viewing-capability code at all — so nothing on this rail can be disclosed to a supervisor today except by the institutions themselves, outside it. The separation is a property of the design, stated here so it is not mistaken for a feature.
VigiRail separates messaging from irreversible settlement: a payment is validated, optionally reserves liquidity, then finalises. Before finality it can be cancelled; after finality it is never rewritten — a return is a new, linked compensating transfer. Idempotency keys, per-institution sequences and validity windows make the same instruction impossible to settle twice, even if it is resent through another gateway.
VigiRail refuses rather than guesses: an unavailable cryptographic backend, an unknown suite, an inactive institution, an exhausted quota or a failed signature all stop the message — no placeholder ever returns success. It stays disabled until independent cryptographic, consensus and banking-interoperability review passes. Throughput figures are engineering targets, not public performance claims until independently reproduced. Mainnet remains locked.
Sovereign post-quantum network for verified value.
Post-quantum cryptographic security software: a sovereign network that strengthens custody, settlement and identity. Testnet active; mainnet opens when independent validation supports it. Ten layers, each with its own page and its real state on it: three running, two half-built, five written but not yet on the network.
