Pi Ecosystem Summit / #PiHackathon — CoreGuard submission kit

Event window: Nov 17–19, 2026. Check the official Pi Network / hackathon page for the exact submission form, track names and judging criteria, and adjust the fields below to fit them.

1. Project name & one-liner

CoreGuard Pi Commerce Shield — every Pi payment gets a receipt anyone can verify, and every dispute gets an evidence pack anyone can replay.

عربي: درع CoreGuard لتجارة Pi — كل دفعة Pi ليها إيصال أي حد يتحقق منه، وكل نزاع ليه حزمة أدلة أي حد يعيدها.

2. Short description (≈100 words)

Pi's next chapter is real commerce, and commerce runs on trust. Today a Pi buyer and merchant have no shared, verifiable record of what was agreed and what was paid. CoreGuard adds one: the buyer's intent is signed, the payment is checked against that intent by the Execution Firewall (ALLOW / DENY / HOLD), and the result becomes a deterministic receipt. If something goes wrong, DDE/1 produces an offline evidence package any arbitrator can replay. The verification engine is already live on Core Mainnet (Proof Artifact #1, L1 VERIFIED); this hackathon brings it to Pi.

3. Problem

• Pi merchants and buyers rely on screenshots and chat messages to settle disputes.
• Pi Browser DApps can ask the wallet to sign without any policy check between intent and execution.
• Trust badges on stores are marketing, not evidence.

4. Solution (what we demo)

1. Buyer creates an order in a sample Pi Browser DApp → a signed CoreGuard intent.
2. Execution Firewall checks amount, recipient and deadline → ALLOW (or HOLD if anything is UNKNOWN).
3. Pi payment completes → CoreGuard receipt generated and shown to both sides.
4. Merchant store shows a Verified Merchant badge rendered only from verified receipts.
5. Simulated dispute → DDE/1 evidence pack downloaded and replayed offline.

5. What already exists (honest status)

Never claim Pi integration is live before step 4 of the checklist below is done.

6. 90-second video script

• 0–10s: "A Pi payment went through. But did it do what the buyer agreed to? Today, nobody can prove it."
• 10–30s: Show the order screen, then the signed intent appearing.
• 30–50s: Firewall decision ALLOW, payment, then the receipt card with hashes.
• 50–70s: Store page with the Verified Merchant badge; flip one value and the badge fails closed.
• 70–85s: Dispute: download the evidence pack, run npm run verify offline, verdict shown.
• 85–90s: "CoreGuard. Proof, not logs. Already verified on Core Mainnet — now for Pi."

7. Team

• EslaM-X — founder, protocol & engineering (github.com/EslaM-X)
• Add any teammates, with roles, before submitting.

8. Submission checklist

• Register the team on the official hackathon page
• Create the Pi app in the Pi Developer Portal (App Studio) and get sandbox access
• Build the sample DApp order → payment flow with the Pi SDK
• Wire the Pi payment result into the CoreGuard receipt (packages/pi-network)
• Badge page + fail-closed demo
• Record the 90s video (script above)
• Public repo link + README section "CoreGuard × Pi"
• Post on X with #PiHackathon and tag @PiCoreTeam

9. 14-day schedule (Nov 3 → Nov 17)