Inside the technology
How a VERIDIS document proves itself
For the client’s auditor, IT team and legal counsel: the attestation process, the proof layers, how sensitive data is handled and what stays out of scope.
The common thread
From raw data to portable proof, in five steps
This is the process: what happens to your document. Data goes in, the calculation is done with declared assumptions and, when the client opts for attestation, which is optional, the result is sealed in a trusted execution environment and comes out verifiable by anyone, anywhere, independently of the issuer.
Input data
A measurement, inventory, technical report or manifest enters as declared input, with the origin trail preserved.
sha256(inputs)Seal in trusted hardware (optional)
The final document, or its hash, is sealed in a trusted execution environment (TEE), with the issuer key generated inside it. The calculation runs outside the enclave; attesting the calculation run itself is a planned layer.
document attestationPackage hash
A cryptographic hash binds the result into a tamper-evident package, where any later change is detectable. With attestation, the package can also get an RFC 3161 timestamp.
sha-256 + rfc 3161Public anchor
Optional layer, planned: the seal gets anchored in a public registry, so that no one can erase, backdate or omit it.
distributed ledger (optional)Cert + link + QR
The client carries the proof: a certificate verifiable by any third party, without depending on our platform.
portable verificationHonest boundary
We do not attest that the input data is true: that is the accredited verifier's role, and our work feeds their review, never competes with it. What we attest is that the delivered document is exactly what was sealed and by which issuer, with the date given by the timestamp when there is one, and that the proof package reveals any change. That discipline is what makes the proof hold up.
Open architecture
The verification envelope, no black box
If the thread is the process, the envelope is the anatomy of proof: what each layer guarantees, and before whom. The prover is pluggable: today the strongest layer is TEE attestation; if a stronger proof emerges tomorrow, the envelope incorporates it without changing the certificate format.
{
"envelope": "veridis.attestation/v1",
"document": {
"sha256": "9f2e…a1b4",
"type": "ghg_inventory"
},
"issuer": {
"key": "generated in the enclave",
"environment": "TEE"
},
"proofs": [
{ "type": "tee_attestation", "status": "verified" },
{ "type": "timestamp", "standard": "RFC 3161" },
{ "type": "public_registry", "status": "planned" }
],
"verification": {
"mode": "issuer_independent",
"bearer": "cert + link + qr"
}
// pluggable prover: new proofs fit without changing the format
}// illustrative structure of the VERIDIS attestation certificate
Want to see the envelope applied to a document of yours? Talk to engineering →
Confidentiality and LGPD
Your data comes in protected and leaves without exposure
An emissions inventory touches personal data: commuting by public servants and staff, business travel, invoices. Handling it carefully is part of the method, not an appendix.
Minimization before delivery
Personal data is removed or anonymized before a file leaves, with the method declared file by file and no third-party authorship metadata.
A cryptographic digest for every file
The delivery package carries the SHA-256 digests of the files received and delivered. With attestation, the digest list itself is sealed, and a later change becomes detectable.
Confidentiality set in the contract
Confidentiality and data processing under Brazil’s data protection law (LGPD, Law 13,709/2018) set in the contract, with a duty to report any incident.
Verify without publishing
TEE attestation is optional. When used, checking it takes only the file and the certificate: the document does not have to be published anywhere.
Technology
Four areas, one standard of proof
Everything that leaves VERIDIS can go through the same verification thread; TEE attestation is optional. The technology changes from area to area; the standard of proof never does.
AI with governance
Use case selection and deployment of agents and models with rules and assumptions declared before they run. We do not promise to explain the model: what it delivers is the result with the assumptions in plain view.
- Agents for licensing, MRV and regulatory monitoring
- Rules and assumptions declared before each run
- Final document with TEE attestation, if the client opts for it
Blockchain in service of proof
A public registry for verifiable dates and non-omission, with no jargon and no token. Blockchain is the planned optional registry layer of the verification envelope, in service of proof.
- Public integrity and time anchors
- An audit trail that outlives our own platform
- Designed to work alongside timestamping and qualified signatures
In-depth data analysis
Proprietary corpus built on public energy, environment and climate data, treated methodically: multicriteria analysis, sector benchmarking and probabilistic simulation.
- Multicriteria methodology published in an industry technical journal
- Benchmark of dozens of public decommissioning projects
- Monte Carlo simulation for risk and regulatory scenarios
The common thread of verifiable proof
Trusted execution environment available for deliverables: the record stands as auditable, portable proof. It is the core of the work, the subject of Brazilian Intellectual Property filings.
- Certificate, link and QR verifiable by third parties, independently of the issuer
- Applicable to any document of value: GHG, PDI, IHM, calculation reports
- Family of patents and software registrations: Brazilian Intellectual Property
Next step
Want to see the proof applied to a document of yours?
We take your deliverable through the whole process, from input to QR, in a technical demo.