Build a standalone read-only Ponder indexer in a NEW public GitHub repository for this public equipment-rental trial. Deliver source and deployment instructions only; we will review and host it later.

SOURCE AND ACTUAL DEPLOYMENTS

Reference: https://github.com/identity-md-launches/launch-1988-kkk

Commit: 6ce8023819f68d2b84f2151b24285af477f4d9c7

Robinhood Chain Testnet, chain ID 46630.

Public keyless RPC: https://rpc.testnet.chain.robinhood.com

MockPaymentToken: 0x31339619db548257cE09A76f189b0b1932f5c0cd, deployment/start block 138710650.

RentalEscrow: 0x06135FF9311eCa80a7484444A552f28fFC660F05, deployment/start block 138710790.

Both are non-proxy contracts. Derive exact ABIs from the pinned source/build artifacts; do not guess signatures. Check chain identity and deployed code. Preserve these deployment defaults while allowing explicit address/start-block/RPC overrides. Keep the reference repository and contracts unchanged. Its indexer/ and docs/RECONCILIATION-REPAIR.md are behavioral/test references, not packaging to copy.

PUBLIC EXAMPLE TO VERIFY

At block 138754466, hash 0x198390e8346394fda55e74abb43cce543aff5768667adbf14bfc1c873bf90bad (check canonicality), there is one policy, item and CANCELLED reservation, all ID 1. The administrator, renter and fee recipient are 0x0fF6617f72544f60802b72D752dA7490C304CdeE. Token decimals: 6. Policy deposit 50000000 base units, cancellation fee 5000000, reservation window 86400 seconds. Cumulative refunds paid: 45000000; cumulative fees paid: 5000000. Escrowed deposits, outstanding refund credits, accrued fees, liabilities and escrow token balance are all zero. Original fixed supply 1000000000000 base units is back in the test account. Item is available again; original reservation terms remain stored.

Booking clientRef: 0x0f3fcf2d397cb63077da241a2b9b0a8762d96b745c235f2e1993c749ba1aeaac

Completed fee request ID: 0xb5d4ba7e1b0d63f8be844a65244059d1f8808692685ecd0fd3778d676e543b78

Final fee-withdrawal transaction: 0x87911ffadb4882d59cf8cd1979c4e49f0598f3f38206a15eed55716b1c00faf4

Discover earlier events from the real deployment blocks and verify these values at that fixed block. Do not compare a fixed example to changing latest state. This example covers cancellation/refund/fee withdrawal only; it does not prove checkout/return, expiry, role separation or failure recovery.

DELIVER

• A normal Ponder 0.18 project at repository root, exact dependency pins, pnpm lockfile, Node >=22.12 and documented tool versions. Use supported public APIs and ordinary installation, without the old pruned archive, private bootstrap or single-JSON-row projection.
• Entity tables and documented queries for equipment availability, policies, reservations and accepted terms, renter credits/payment history, staff/admin state, completed fee-request IDs and accounting totals. Use exact integer amounts/IDs; preserve snapshotted terms after policy changes. Canonical event identities, ordered application and duplicate handling must prevent double counting and retain supported reorg rollback.
• Queries must answer: available equipment/current quote; reservation terms/status; renter credits/payments; fee-request outcome; accounting totals; sync status. Provide GraphQL and documented read-only examples. Report indexed block/hash, observed head, lag and RPC errors so callers can distinguish stale/catching-up data. Explain provisional results and reorg/finality limits. Readiness is not a guarantee of continuing freshness; never label observed head as indexed progress without evidence.
• Read-only reconciliation against one canonical block: use a coherent database snapshot/checkpoint and pin independent event scans and storage calls to it, checking block hashes before/after. Discover expected fee-request and staff identities from chain events independently of projected records. Retain missing/extra record detection, revoked-staff records, cumulative refundsPaid/feesPaid, accepted terms, credits/liabilities and token balance/donation checks from the repaired reference. Fail on mismatches or unavailable history without repairing data or substituting latest. Bound log ranges/timeouts/retries; document RPC-trust and completeness limits.
• Dockerfile, env.example, persistent PostgreSQL Compose setup, and beginner Railway instructions. Host-published local ports must bind explicitly to host loopback only; database ports stay internal. No Docker socket, privileged containers or broad host mounts. The Railway container must listen on its platform port/interface; use private database connectivity and require PostgreSQL in production. No signing keys or committed credentials.
• Stable schema on ordinary restart; a distinct schema for a changed deployment, with readiness-controlled serving and documented rebuild/rollback behavior. Document backup/restore and deliberate old-schema cleanup, preserving existing data by default. Include deployment settings, readiness endpoint, query/resource protection and known public-RPC limits. Do not provision Railway or claim its instructions were tested if they were not.
• INDEXER.md: ABI provenance, chain/contracts/start blocks, entities/keys/events, intentionally omitted events, configuration, exact commands/results and limitations for the next maintainer.

VERIFICATION AND BOUNDARIES

Run clean install, codegen, typecheck, unit tests and permitted read-only public RPC/backfill/query checks. Show actual results; mark unavailable or unrun checks NOT RUN. Respect worker access restrictions; never access our computer, private services or cloud metadata. Any local-network harness below is delivered for our subsequent execution, not a request to access our environment.

Deliver executable integration tests for lifecycle/term preservation, revoked staff, duplicate logs, refund/fee payments, restart preserving the database, RPC outage/catch-up, short reorg and fresh replay. Reconciliation tests must reject missing/extra fee and staff records, changed historical payment totals and bad/noncanonical RPC evidence; valid history must pass. Local transaction/fault fixtures must use disposable Anvil chain 31337 only, reject nonlocal endpoints and other chain IDs, and clean up only resources they created. Never transact on the public testnet or simulate its failures. The running indexer is read-only and holds no keys.

Only this public rental example. No private files, real-user data, browser UI, contract changes/deployments, tunnels, cloud accounts, paid hosting or extra jobs. Deliver reproducible code and honest evidence, not production approval.