menhir
on-chain memory commitments
The MemoryRegistry contracts and @limccn/menhir-core:
canonicalization (JCS RFC 8785), digests, and commitment hashing for
MemoryOverEth.
One hashing implementation is shared by the contract, the browser, the gateway and the CLI, so a hash drift fails a test instead of producing a commitment that only looks valid on chain.
Verify a commitment (longstone.app/verify)- Source github.com/limccn/menhir
- Getting started Getting-Started.md — endpoints, deployments, gas baseline
- Package @limccn/menhir-core on npm
- Contract contracts/ — MemoryRegistry (Base Sepolia)