ProofPay — The verified marketplace for real-world actions.

The company appears to be a self-contained prototype for a marketplace that verifies real-world actions using mobile sensors and evidence fusion. The author describes ProofPay as an end-to-end system built around a mobile app and backend API, designed to support two-sided marketplace workflows where users can either offer or accept payments for completing tasks. It uses smartphone telemetry (GPS, motion sensors) to generate a confidence score for submitted proof of task completion.

The project is described as a prototype, not a product with customers or revenue. The author states that the system includes role-based access control, escrow modeling, dispute resolution, and moderation tools, but does not indicate any live marketplace or user base. There is no evidence of funding rounds, headcount, or commercial traction.

The single most important open question is: What is the actual commercial viability of this verification model?

The description implies a trust-based marketplace for real-world actions, but lacks evidence that such a model has been proven at scale or with users. The author notes that financial and trust integrations are unfinished, which raises questions about whether the system can be monetized.

Confidence: Low. This is a self-reported prototype built by one person, with no independent verification of claims or traction.

The description states that ProofPay is a verified marketplace for real-world actions, implemented as a mobile app and backend API. It supports two complementary marketplace modes:

• "Pay Me To": A performer proposes an action and price to complete it.
• "Pay You To": A sponsor posts an action and offers a reward.

The system records sensor data (GPS, motion, accelerometer) during task execution and combines this with media proof (photos/videos) into a task-specific evidence package. It generates a confidence score based on the submitted evidence against a defined "proof recipe".

The backend evaluates evidence using a scoring model that includes duration, GPS, motion, continuity, and media elements, with penalties for poor data quality or implausible activity.

The system also includes:

• Escrow modeling
• Dispute resolution
• Ratings
• Notifications
• Moderation tools

Not evidenced: No mention of actual users, customers, revenue, pricing, or commercial adoption. The product is described as a prototype built by one person.

The author states that ProofPay was inspired by the question: "How can two strangers confidently exchange money for a real-world action?"

It positions itself as a solution to trust problems in gig work where traditional platforms do not fit non-standardized tasks. It claims to address limitations of:

• Photo reuse
• GPS alone (does not prove activity)
• Manual review (slow, subjective)

The system is described as "explainable", meaning that verification results show why a submission passed or failed.

Inference: The positioning suggests ProofPay is trying to build a trust layer for decentralized or community-driven task exchanges. It may be positioned as a platform for fitness challenges, location-based tasks, or creative activities.

Not evidenced: No claims about market size, target segments, or competitive differentiation beyond "modern phone as verification instrument".

The description states that ProofPay supports two types of users:

• Performers: Propose actions and prices to complete them.
• Sponsors: Post actions and offer rewards.

It also mentions that tasks can include:

• Fitness challenges
• Walking routes
• Location visits
• Activity durations
• Unique experiences

Inference: The ICP appears to be individuals or organizations looking to incentivize real-world behavior, possibly in communities, fitness groups, or event-based activities. It may target niche markets where traditional gig platforms do not apply.

Not evidenced: No evidence of actual customers, user personas, or market segmentation beyond the author’s own description.

The description states that ProofPay supports a two-sided marketplace, where:

• Sponsors post tasks and offer rewards.
• Performers complete them and get paid.

It includes escrow modeling in its design, suggesting a transactional model with funds held until verification is complete.

However, the author notes that financial integrations are unfinished. Specifically, they mention:

• Stripe Connect integration
• WebRTC live verification
• Push delivery
• Deeper geofence/route/dwell validation

There is no evidence of pricing tiers, revenue streams, or monetization strategy beyond the idea of a marketplace.

Not evidenced: No pricing data, revenue model, or commercial traction.

The system is built as a shared TypeScript monorepo, using:

• React 19 (web)
• Expo 54 + React Native (mobile)
• Express 5 (backend)
• PostgreSQL/Supabase
• Drizzle ORM
• OpenAPI + Orval for API contracts
• Zod validation

Mobile app features include:

• Background location tracking
• Sensor data sampling (accelerometer, gyroscope, pedometer)
• Motion cycle detection
• GPS continuity monitoring
• Media capture and storage via Supabase

The backend uses a rule-based scoring model that fuses multiple evidence types into a confidence score.

Inference: The system is technically sophisticated for a prototype, with cross-platform mobile support, background execution, and sensor fusion. It shows an understanding of mobile OS constraints and data summarization trade-offs.

Not evidenced: No information on scalability, performance metrics, or production deployment.

The author states that ProofPay is a prototype, built by one person (smoke14cu). It was submitted to the OpenAI 2026 hackathon, indicating it is not yet a commercial product.

There is no evidence of:

• Revenue
• Customers
• User base
• Product-market fit
• Commercial traction

The author explicitly states that financial and trust integrations are unfinished and that the system includes "exception paths" like disputes and moderation, but does not indicate these have been tested or used in practice.

Not evidenced: No data on adoption, usage, or commercial viability.

The description does not mention competitors directly. However, it implies a space that overlaps with:

• Gig economy platforms (e.g., TaskRabbit, Upwork)
• Fitness and activity tracking apps
• Location-based services
• Trust and verification systems for remote work or community tasks

It positions itself as solving trust problems in non-standardized gig work, where traditional platforms do not apply.

Inference: The competitive landscape likely includes platforms that offer task-based payments but lack robust verification of real-world actions. It may compete with niche activity-tracking or reward-based apps.

Not evidenced: No mention of existing competitors, market share, or competitive positioning.

1. Prototype-only status: The system is described as a prototype built by one person and submitted to a hackathon — no commercial product or traction.
2. Unfinished financial integrations: Stripe Connect, escrow, live verification, and payment release are noted as "next-stage work", not implemented.
3. No user base or revenue: No evidence of customers, users, or monetization.
4. Trust model unproven at scale: The system includes moderation, disputes, and escrow, but no indication these have been tested in real-world use.
5. Technical complexity vs. commercial viability: While the technical implementation is advanced, there’s no evidence that this complexity translates into a viable business.

Not evidenced: No data on risk mitigation, market validation, or scalability concerns.

1. What specific real-world tasks are you targeting, and how do you plan to validate demand?
2. How do you intend to monetize the platform beyond the initial marketplace model?
3. What is your plan for integrating financial services (e.g., Stripe Connect, escrow)?
4. Have you tested the verification system with actual users or in real-world conditions?
5. What are the key assumptions about trust and fraud that underpin this system?
6. How do you plan to scale beyond a single developer prototype?
7. Are there any legal or regulatory risks associated with verifying user behavior via mobile sensors?