Skip to content

Milestones

List view

  • ### **Goals for Initial Web Proofs Launch** - Payload Size - At least 1.5KB (500 bytes per request and 1 kilobyte per response) - Do the proofs need combined? No, we are okay with either 1 or 2 separate proofs - Speed - Deliver a proof of the above payload size in less than 60s - This includes download time for artifacts on a reasonable internet connection (100Mb) - Memory usage - <2gb would be ideal (4gb is ceiling on web, we need to measure mobile) - Arbitrary Domain Support - Definition ~90% of top 1,000 domains can successfully be called through our proxy - Works on the top 10 most requested domains - Coinbase - Spotify - Delta points - LinkedIn - Uber - Amazon - Venmo - Wells Fargo - Ticketmaster - WSJ - Problems: [bug example](https://github.com/pluto/web-prover/issues/186) - Platforms - At least one platform either iOS or WASM - WASM has oddball issues: - Deserialization of `AuxParams` is very slow (>60s itself) - `CompressedProof` generation is very slow (>60s?) - Attestation Modes - Origo hits the above goals. - TLSN remains operable (with the occasional network timeout), but without full support for manifests. - TEE’s - Verification - Support for “API” verification - Circuits: Take ciphertext hash as `z0` input. - Support for on chain verification, but via a signature is acceptable - Target Chains: testnet on op, base? - Manifests & Predicates - Devex: Developers have the ability to lock headers, url, status and json keys/values. We won’t support more full features Response Data Predicates or Data Scopes. This screenshot shows what the Response Manifest section looks like. ![image.png](https://prod-files-secure.s3.us-west-2.amazonaws.com/4b224148-c78b-4c13-b63f-c88002c8c6ad/a17ca300-d0cb-44a8-ba73-0a3996ca3f22/image.png) - Proof: Acceptable to not fully enforce all conditions at initial launch, as long as we can fast follow. We’ve done a lot of pre-work on this already. - Docs - SDK can be integrated by a solo developer without knowledge of cryptography. - Ability to read documentation and within 1 day create a web proof embedded inside of an application. - Required Download - <1gb feels like an acceptable ship goal, ideally <500mb. - Combination of r1cs files, wasm files - Hosted circuit artifacts (where?) / bake into binary?

    No due date
    6/7 issues closed