Proof of Ship on NEAR

Problem: funders want to pay builders for shipping, but proof of shipping is usually a screenshot or a promise, and someone has to be trusted to decide.

Product: Proof of Ship on NEAR is an escrow contract that pays a builder only when Hey Research Lab's signed count of their ships meets the bounty's target. A funder opens a bounty for one project with create(builder, slug, min_ships, deadline, payout) and funds it in USDC with ft_transfer_call. The builder ships: releases, contract deployments, code. Hey Research Lab, the public record of building on Robinhood Chain, counts those ships from public sources with the same rule it uses on every project page and signs the count as EIP-712 typed data. Anyone submits that signature with claim() and the contract pays the builder. If the target is not met by the deadline plus a 3-day grace, each funder refunds exactly what they put in.

How NEAR fits: the contract verifies HEY's signature on chain with env::ecrecover and env::keccak256 against an attester fixed at init, so no bridge, relayer or oracle sits between the count and the payout. The signing domain uses chain id 397 and a salt of the escrow's account id, so a signature for the Robinhood Chain escrow, NEAR testnet or another escrow never verifies. The builder is paid at the eth-implicit NEAR account their EVM key controls, or through NEAR Intents (intents.near), from where they can withdraw to any chain Intents supports.

Status: live on NEAR mainnet at escrow.heyresearch.near with two test bounties, a full paid claim on testnet, and refusal tests for replay, wrong chain, wrong escrow and tampered counts. The Robinhood Chain version has already paid a builder 4,900 WIF.