Verify EchoPortfolioContributorSecretUrlTest Echouser — Rec…
Verifies data from EchoPortfolioContributorSecretUrlTest (app.echo.xyz).
CANDIDATE FIX (still a throwaway — verify before wiring). EchoPortfolioContributorDirect (09e2c2b8) v1.0.1 with the two privacy leaks closed: (1) the url template variable is renamed URL_PARAM_GRD -> SECRET_URL_PARAM_GRD, so the raw portfolio uuid is routed into secretParams instead of the public claim. Mechanism, read from browser-extension-sdk 0.4.2-dev.1: params-extractor separateParams() puts any param whose name .toLowerCase().includes("secret") into secretParams, and claim-creator assigns only publicParams to params.paramValues. network-filter keeps greedy matching for names ending in G…
Primary data point: Echouser.
Reclaim Protocol generates a zero-knowledge proof that a user holds an active EchoPortfolioContributorSecretUrlTest session and exposes the following verifiable data points:
- Echouser
How it works
- Your user starts a verification session and signs in to EchoPortfolioContributorSecretUrlTest as they normally would.
- Reclaim Protocol observes the encrypted EchoPortfolioContributorSecretUrlTest session through a zero-knowledge proof system, with no credentials leaving the user's device.
- Your application receives a cryptographic proof of the user's data — verifiable on-chain or in your own backend.
Other providers
- Verify GitHub UserName data
- Verify Gmail Account data
- Verify LinkedIn - User Profile Details data
- Verify Twitter User Profile data
- Verify Binance KYC Level data
- Verify Uber UID data
- Verify Twitter Follow Check Finquarium data
- Verify Kaggle username data
- Verify identity_github00 data
- Verify LinkedIn - User Profile Details 2 data