ShipStamp

ShipStamp creates wallet-signed software build receipts on Monad. A builder verifies a real public GitHub commit, publishes a versioned manifest at the live deployment, and confirms that the manifest names the same repository, commit, deployment origin, project, and connected wallet. ShipStamp canonicalizes those values and records the manifest hash, milestone, builder, proof version, and chain timestamp in ShipStampRegistry on Monad Testnet. Public receipts and chronological project timelines read from the contract without an account or application database. Anyone can inspect the transaction and contract record, then recheck whether the currently served manifest still matches the onchain hash. I built ShipStamp because, as an indie builder, a current repository or polished deployment does not show which specific build was intentionally shipped when. The project taught me to keep onchain proof narrow and honest: ShipStamp does not prove every deployed file came from the commit or that a wallet owns the repository. It proves the public commit existed, the live deployment served a matching manifest, and the named wallet recorded that manifest hash on Monad. ShipStamp used itself: receipt #1 records the release of live deployment manifest verification.