HyperWaferHyperWafer dev log
The endpoint answers for two chains
- /rpc serves every standard Solana method and eight hyper_ methods: books, marks, funding, positions, liquidations, HIP-4 outcomes, vaults and HIP-3 dexs.
- JSON-RPC batches can mix both. The Solana items go upstream in one batch and the HyperCore reads run in parallel.
- Past 200 free calls a day, x402 on Solana: a USDC transferChecked of 0.0005 per call, confirmed before the answer is sent.
Every hyper_ answer is signed
- The HyperWafer key signs sha256 of the canonical JSON of method, params, data, the HyperCore time and the time we served it.
- The SDK's verify() and the console check it in the browser against the published key.
Hourly receipts and the house agent
- The keeper writes one Memo an hour with the hour's calls, the USDC received, the 70% burn share and the sha256 of the call ledger.
- The house agent, a funding watcher, pays for one batch every hour over x402 from its own USDC, so the meter runs from day one.
MCP server and TypeScript SDK
- /mcp exposes the eight hyper_ methods as tools, on the same meter as /rpc.
- The SDK is one ES module with types, served from this site at /sdk/hyperwafer.mjs.