Internal validation proves a report is internally coherent. It cannot prove the
filer controls what the report declares. That gap is where LodgeiT Labs anchors.
LodgeiT Labs · October 2026 · draft v1
A disclosure pipeline that validates an XBRL document — structural completeness against the taxonomy, arithmetic, compliance against a rule set — answers one question well: is this report internally consistent? It cannot answer a different and harder one: does the entity filing it actually control the assets, contracts and nodes it claims?
This limit is not a bug in any one implementation. It is structural, and it has a name. Internal validation is omission-invariant: a silently-omitted entity, wallet or liability leaves the validated report perfectly consistent with itself. The validator sees a clean document because it only ever sees the document. Auditchain’s own lead architect co-authored the paper that proves this (Rutgers CARLab & Meyers, September 2026), and its conclusion is the one we build on: internal validation must be paired with an external anchor.
Entity-level identity infrastructure anchors one edge of this. GLEIF Level 2 (the “who owns whom” relationship data behind the LEI) anchors the entity perimeter — which legal entities exist and how they relate. But a validated disclosure still asserts facts below that perimeter: that this filer controls these on-chain reserves, these smart contracts, these validator nodes. GLEIF tells you the entity is real. It does not tell you the entity holds the key.
Proof-of-control binds a disclosed on-chain address or position to an independently verifiable control attestation — a signature the filer can only produce if it holds the controlling key, verifiable by anyone, bound to the specific disclosure it supports.
LodgeiT builds this as remote signing over Nostr, using NIP-46. The signing key never leaves the holder’s control: the disclosure system requests a signature over a challenge that names the disclosure and the claimed address; the holder’s remote signer (a bunker, held by the filer, not by us and not by the validator) returns a signature; the signature is published to Nostr relays and is independently verifiable against the holder’s public key. We have proven this end to end — external signing across independent relays, with per-relay signatures verified — so it is a working mechanism, not a design sketch.
The result is an attestation with three properties a disclosure consumer can check without trusting us, the filer, or any single relay:
Proof-of-control is a reality anchor that attaches to a disclosure after the internal validator has done its job. It is complementary, not competitive — it answers the question the validator structurally cannot. Concrete attachment points:
| Disclosure context | What proof-of-control anchors |
|---|---|
| Proof-of-reserves state conditions | That the reserve addresses in the report are controlled by the filer at attestation time — the control half of a reserves claim the validator cannot otherwise establish. |
| MiCAR white papers & crypto-asset disclosures | That declared wallets, treasury positions and contract addresses are under the issuer’s control, bound to the published document. |
| Wallet & validator schedules (e.g. a GENIUS Act BNP-style framework) | That each scheduled wallet or validator node is controlled by the declaring entity, node by node, address by address. |
| Verified working-papers / event capture | A control attestation sits alongside verified operational events as part of the working-papers trail a reviewer walks — the on-chain-control line item in the evidence file. |
LodgeiT Labs builds open-source infrastructure for financial truth: deterministic engines, content-hashed provenance, and a settlement layer (L402 over Lightning) designed to be called by agents without a human in the loop. Proof-of-control is the reality-anchor edge of that same discipline — the same refusal to let a plausible-looking claim pass without a check a third party can reproduce. It carries downstream, too: a disclosure whose on-chain control is anchored can feed statutory resolution and lodgement with the control question already settled.
The mechanism is live today. If you run a disclosure or validation pipeline and want the control half anchored, we can demonstrate proof-of-control end to end against a disclosure of your choosing.
— Andrew Noble, LodgeiT Labs
andrew@lodgeit.net.au