When I see a dashboard quote the circulating supply of a tokenized asset, I want to know which block that figure came from.
If the dashboard and a smart contract are working from different snapshots, they can show different totals even when both calculations are correct.
That’s where Proof of SQL from @SpaceandTime gets practical for me. A table commitment acts like a fingerprint for a particular state of the data.
The SQL query can specify the block cutoff and how eligible mint and burn events are counted. The proof lets an application verify that the reported total came from running that query against the committed data.
For an app that checks a tokenized asset’s issuance cap, I’d want the block height alongside the proven total.
The proof tells me the calculation checks out. The block height tells me how current that answer is.
$SXT #SXT
If the dashboard and a smart contract are working from different snapshots, they can show different totals even when both calculations are correct.
That’s where Proof of SQL from @SpaceandTime gets practical for me. A table commitment acts like a fingerprint for a particular state of the data.
The SQL query can specify the block cutoff and how eligible mint and burn events are counted. The proof lets an application verify that the reported total came from running that query against the committed data.
For an app that checks a tokenized asset’s issuance cap, I’d want the block height alongside the proven total.
The proof tells me the calculation checks out. The block height tells me how current that answer is.
$SXT #SXT
