···21212222Keytrace evolves this model:
23232424-- Data isn't stored on Keytrace's servers, so, no risk of me getting bored and stopping the project
2525-- Data can be posted by other people's systems, anyone can verify or check other people's verifications
2626-- Keytrace's system for the proof verification is open-source and available for others to use on [npm](https://npmx.dev/package/@keytrace/runner)
2424+- Data isn't stored on Keytrace's servers, so, no risk of me stopping the project
2525+- Data can be posted by other people's systems, anyone can verify a proof and create a claim
2626+- Keytrace's system for the proof verification is open-source and you can get it [npm](https://npmx.dev/package/@keytrace/runner)
2727- The data is structured so that Keytrace can offer an API which only requires GET requests and the capacity to handle some web standards to prove that the data was 100% verified by Keytrace, and hasn't been touched since
28282929That said, I make a pretty big breaking change though: