The problem ChainRoute-Forge solves

Manufacturers, resource producers, luxury brands, regulators, and custodians of high-value assets all need tamper-evident, verifiable provenance -- without smart contracts or vendor lock-in. Current options are centralized, complex, or not permanently anchored. ChainRoute-Forge lets them build and verify provenance chains (Polygon + Arweave) in a no-code/low-code way.

Challenges we ran into

Hurdle: Chain viewer only showed genesis
After a user created genesis, added an event, and anchored it, the “View chain” link took them to /chain/[genesis], which only showed the genesis transaction. Judges (and users) couldn’t see the full chain (genesis + events) from that page, so the demo looked incomplete.
How it was fixed (from BUIDLATHON-EVALUATION.md):
The chain page was updated to accept an optional query param: ?txes=txHash1,txHash2,..., and to fetch and display genesis plus those event transactions.
The “View chain” link from the success step was changed to include the new event tx hash in that txes list, so clicking it opens the chain with both genesis and the new event visible.
When only genesis is known, the UI was updated with short helper copy and a link to the Verify page so users know how to get the full chain (e.g. paste tx hashes or use “Load Example Chain”).
So the hurdle was chain discovery/display on the chain page; the fix was explicit multi-tx support via ?txes= and wiring the success-step “View chain” link to pass the new event tx.

Use of AI tools and agents

Coding was essentially done entirely with Cursor set to Auto (for a few tough parts Opus 4.6) 1x with an Ultra subscription. Grok Heavy was extensively utilized for ideation, brainstorming, and image generation. Grok API is also used by the app to describe user input files.