the checker/inside the enclave/the census
Verification only matters if something is being verified. This is the thing: a Flare compute extension that answers a question about money you don't want to show anyone.
Everything below is a real request and response, captured from the extension reading live Flare oracle prices. Nothing here is illustrative.
Stays inside the enclave. Never written to state, never sent to the chain.
The entire response. This is all anyone else ever sees.
Each row is one real instruction sent to the enclave.
Public data, published on purpose. The computation is private; it isn't unauditable. Every feed the enclave read is named in the response, so you can see it used real oracle values rather than numbers of its own choosing.
| Feed | Price the enclave used | Reading it now |
|---|---|---|
| Loading… | ||
Calls FTSO v2 on Coston2 from your browser. Prices move, so today's number will differ from the captured one. That the feed answers at all is the point.
It would be easier to let the caller pass prices in. It would also be worthless. Someone who supplies their own prices can claim any solvency they like, and the attestation would faithfully certify that the enclave correctly computed a lie. The code that reads the oracle has to be the code the attestation covers, which is why the read happens inside.
A contract can't hold a secret. Putting the portfolio on-chain to prove something about it discloses the portfolio, which was the thing you were avoiding. The alternative is a trusted third party, an auditor or an exchange vouching for you, which is exactly what this replaces.
git clone https://github.com/iamrobertmoore/glassbox cd glassbox/extension && ./run-demo.sh
Starts the extension and puts these same requests through it against live prices. No Docker, no tunnel, no chain transaction. Then check the attestation from the machine it runs on with the checker.
Feeds read from FTSO v2 at 0xC4e9c78EA53db782E28f28Fdf80BaF59336B304d on
Coston2 (chain 114). Open source, MIT.