DOCS / DEVELOPERS
DESIGN DOCUMENT · PRE-RELEASE
Integration checklist
Build against verified artifacts and explicit compatibility guarantees.
Protocol behavior is proposed. This release is an interface preview; no funds or wallet signatures are accepted.
Before connecting a wallet
- Obtain the official release manifest and verify its origin.
- Check the virtual network ID against the intended base chain.
- Verify pool, registry, router, and verifier addresses.
- Inspect the exact message used for privacy-key derivation.
- Confirm the asset allowlist and supported transaction selectors.
Engineering workstreams
| Layer | Required artifacts |
|---|---|
| Circuits | Constraint source, test vectors, reproducible proving artifacts |
| Contracts | Solidity source, ABI, deployment scripts, invariant tests |
| RPC & indexer | Method specification, reorg recovery, key isolation |
| Relayer | Fee policy, submission lifecycle, availability controls |
| Wallet UI | Clear transaction intent, network selection, status handling |
Candidate tooling
The reference ecosystem uses Noir and Barretenberg for proving, Solidity and Hardhat for settlement, TypeScript services, and viem/wagmi for wallet integration. Jammer’s exact dependency versions and monorepo layout remain implementation decisions.
No clone URL or installation command is supplied because a Jammer protocol SDK has not been released. Invented package names and placeholder deployment scripts would not be safe integration guidance.
Validation matrix
- Reproduce key derivation on each target signer.
- Test unauthorized balance and history reads.
- Test double spends, replay attempts, invalid roots, and malformed outputs.
- Exercise failed swaps, pending-deposit refunds, and scanner reorgs.
- Measure proof latency and gas on the intended release build.
TECHNICAL REFERENCESDeveloper stack reference
JAMMER / DOCUMENTATION DESIGN REVISION 0.1