Understand → test → record
Pay a device.
Get a fresh physical answer.
FieldProof lets software pay a device for a fresh physical check. The device signs its answer so the buyer can verify the source, request, and age.
The public replay uses recorded ESP32 evidence and real testnet transactions. It starts no new payment or measurement.
One paid check, linked to peaq.
Watch the product demo · 1:37 · Watch the founder pitch · 1:38
Real ESP32 contact checks, Solana Devnet payments, and peaq Agung identity and Storage work records. Test tokens demonstrate the transaction. They are not customer revenue.
- 1 · BUYERAsk for a new check
Select the device, question, price, and useful age.
- 2 · SOLANAPay the operator
0.001 Devnet test USDC settles before measurement.
- 3 · DEVICEMeasure and sign
The ESP32 reads its real input and signs its answer.
- 4 · BUYERVerify before use
Check the source, request, signature, samples, and age.
The business question
Who needs this?
Software that manages remote operations
A fresh physical check can replace a manual call, site visit, or missing integration at another operator's site.
The first pilot will test one recurring check with an operator and a buyer. Measure cost, reliability, and integration effort.
A real paid contact check
A laptop pays an ESP32 operator. The board signs a new input reading. Independent verification accepts fresh evidence and rejects changed or old answers.
The BOOT button represents a contact. It proves no package contents, equipment safety, or completed repair.
A reliable existing API can solve the buyer's problem. FieldProof needs to prove value where current checks or integrations fail.
Read the plain-language story and differentiation · Prepare the paid pilot
One material index
Open only what you need.
| Task | Material | What it gives you |
|---|---|---|
| Understand the story | Plain-language story | What it does, proposed buyer, alternatives, trust limits, and future test. |
| Send a quick preview | Product demo · 1:37 | Uploaded hardware, payment, and peaq demonstration. |
| Show the mechanism | One-minute replay · Receipt inspector | Recorded real purchase, original signature, expiry, and changed-answer rejection. |
| Review the deck | Present · PDF · Editable PowerPoint | Five simple slides. Real chain interactions and unvalidated customer hypotheses. |
| Rehearse and record | Physical rehearsal · Video scripts | New hardware check, phone verification, separate pitch and product-demo recordings. |
| Ask for feedback | Tester guide | No-wallet test and specific questions. Reviewer feedback does not establish traction. |
| Inspect what works | Current status · Executed verification | Working features, open gates, actual checks, and dated evidence. |
| Review peaq | Integration facts · Execution runbook | Tested identity gate and official Storage activity route. Real registration, gated purchase, and finalized work readbacks now pass. |
| Complete the entries | Official requirements · Entry drafts | Three entries, exact deadline, links, disclosures, and final human checks. |
The detailed technical guide explains radio, protocol, and recovery. Start with this page before that reference.
Make it visible
Film the input and answer together.
- Show the powered ESP32 beside the laptop. Identify BOOT as the test contact.
- Run unpaid released and held checks. Show OPEN and CLOSED from the real board.
- Record one new paid check. Keep the physical input visible until its result appears.
- Show the Seeker verifying the same original answer and transfer independently.
- Show the answer expire. Change a signed field and show signature rejection.
Both honest states fulfill the paid check. The subsequent software decision is separate. The device controls no real gate or robot.
Know the limits
Answer the hard questions directly.
Is this just another dashboard?
The working buyer creates a job, settles a payment, and receives a new device-signed measurement. The screen exposes that mechanism. Film the physical input and transaction to make the mechanism visible.
Why does anyone pay?
A check needs to change a real decision or avoid a documented cost. We have not validated that buyer yet. The test price demonstrates payment behavior, not a business model.
Does a signature prove the device tells the truth?
No. It authenticates the provisioned key's claim and binds the claim to the request. Installation, calibration, truthful sensing, and protected key storage need separate controls.
What does peaq contribute today?
The buyer route checks a registered key before payment. The explicit official Storage route commits the completed job hash. The October 12 job passed a real identity-gated purchase and finalized Storage readback.
The published EventRegistry binds a different identity system. The Storage route records peaq activity without claiming an EventRegistry event or Machine Credit Rating. Inspect the deployment diagnostic.
Is this ready for Colosseum?
It is a credible technical prototype for an honest submission. Business viability and traction remain unproven. Real peaq identity and work evidence now support the sponsor entry. A prize is never guaranteed.
What can this become?
A common interface for independent devices to fulfill paid inspection jobs. First validate one recurring buyer need, then a second operator and integration reuse. A network remains a hypothesis.
Finish the entry
Three entries. One deadline.
Tuesday, October 13, 2026 at 08:59 CEST. Submit before this cutoff.
The current Colosseum portal requires a founder pitch of at most two minutes and a product-demo video of at most three minutes. A supporting deck does not replace these videos.
Complete Colosseum and the separate Germany Earn form. Complete the peaq Earn form too. Save each submitted confirmation.
peaq Germany listing · Germany track listing · Colosseum requirements