LastCrate

Inspiration

A recall notice begins a process. Somebody still needs to know which shop has responded and what happened to the stock. LastCrate focuses on the unanswered shop and the integrity of the record a distributor later shares.

What it will do

A regional distributor will import affected deliveries, freeze the original recipient list, collect authenticated stock reports and see unresolved work. Explicit corrections will preserve the original and revised scope. An authorized export will let a reviewer check the history against a public cryptographic commitment without using the distributor's application account.

If thirty of thirty-one shops respond, silently deleting the last shop must not produce a valid report claiming complete coverage. The record will still distinguish a response from physical removal. It will not certify that food is safe.

Proposed implementation

We propose Next.js and TypeScript, Supabase authentication and PostgreSQL, a transactional anchoring worker, and a minimal Solidity registry on Base Sepolia. Salted commitments go on-chain; business records remain private. A separately deployed verifier will check the expected deployment and case, reconstruct coverage and flag altered or outdated exports.

Implementation is reserved for the official 24-hour final. No application, contract deployment or executed software tests are claimed in this Phase 1 submission. The technology tags below describe the planned stack.

Why this can become a business

The initial buyer is an English regional food distributor serving 50–100 independent food sites. We will test £49/month for readiness drills and case evidence, while recipient staff participate free. The pilot must demonstrate enough measured time savings to cover that price. Existing tools already provide notifications and response tracking; our proposed distinction is independent verification of the declared scope and its revisions.

Validation status

The concept draws on published FDA and FSA evidence. We have not conducted customer interviews or pilots, secured partnerships, measured time savings or earned revenue. Our proposed pilot includes three distributors and explicit willingness-to-pay and usability gates.

Team and attribution

Project lead: Shivam Gupta. Proposed team name: Fieldproof. AI tools assisted research and drafting. This is a conceptual Phase 1 proposal.

Sources

• FDA: strengthening recall compliance and effectiveness
• FSA: Small and Micro Food Business Operator Tracking Survey, Wave 5
• Recall InfoLink
• FoodLogiQ Recall

Built With

• base
• cryptography
• next.js
• postgresql
• solidity
• supabase
• typescript
• viem
• web3