Maintained Smart Contracts
We declare & maintain Smart Contracts for the community so they can be used as library calls.
Those contracts:
Are declared both Starknet Sepolia and Mainnet.
Those contracts are re-deployed at each release, so their code correspond to the release commit.
The source code is always available in the main garaga repository under
src/contractsThe contracts are only declared and not deployed, their expected usage is through library syscalls., so their usage is done through their class hashes and not their contract address (which don't exist unless you deploy them yourself)
Class hashes for Garaga v1.0.1.
0x312d1dd5f967eaf6f86965e3fa7acbc9d0fbd979066a17721dd913736af2f5e
A contract allowing to compute elliptic curve multi scalar multiplication for all supported curve identifiers
0x1367d4ed2f58cfaaeda8cb18a8fb108d77c33b847e9beced89351adece9fd5a
A verifier for RiscZero Groth16-wrapped proofs.
0x59d24936725776758dc34d74b254d15f74b26683018470b6357d23dcab6b4bd
A contract to verify Drand signatures. Soon with timelock encryption utilities.
0x4b22453df42037dd61390736454e8390910adfbbc1fa9d85613e6f375f4de22
A verifier for SP1 Groth16-wrapped proofs.
Version Compatibility: When generating calldata for these contracts, use the same Garaga SDK version as the release that declared the class hashes. For v1.0.1 contracts above, use garaga==1.0.1 (pip), garaga_rs tag v1.0.1, or garaga@1.0.1 (npm).
The SDK generates hints that are specific to each contract version. Mismatched versions will cause verification to fail.
Last updated
Was this helpful?