video1.0<iframe src="https://www.loom.com/embed/e24f8cb61b47471d8973a6193f00e281" frameborder="0" width="1920" height="1440" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>14401920Loomhttps://www.loom.com14401920https://cdn.loom.com/sessions/thumbnails/e24f8cb61b47471d8973a6193f00e281-6050bbbe76fb5109.gif192.905Hi everyone, I'm Artem, co-founder of UZPROOF, and in this Loom I show how our project works. As a customer, I create a quest by pasting the contract address, set the quest schedule for seven days, and publish it as a Jupiter swap task with the minimum USDC value requirement. As a user, I open the quest, complete the swap to SOL, then click "Verify on-chain" and "Claim on-chain proof" to get the verified result in Solana Explorer. I also run scripts to read the attestation and submit the claim, showing that it works without an API key — payment is authentication via x402. No specific action is requested from viewers. Heads up on the Phantom warning at 1:36 — we've already filed an allowlist request with Phantom. The transaction calls the official Solana Attestation Service program (SAS, 22zoJMtdu4tQc2PzL74ZUT7FrwgB1Udec8DdW4yw4BdG) released by Solana Foundation, and our authority 49pihiqwqBb87qmYYdABxnBZQH6YovTZW1wxmFRQTPD9 has a clean tx history. Once Phantom processes the request the warning screen goes away and the flow becomes single-click.