Overview
JSON ABIs for integrating applications with RISEx smart contracts
Contract ABIs
These artifacts are the Solidity JSON ABIs for the main RISEx protocol contracts. Use them with viem, ethers, or any library that accepts a standard Ethereum ABI array.
Contract addresses for RISE Testnet are listed on the Deployments page. Pair each address with the ABI for the matching contract before you encode calls or deploy integrations.
Full ABIs are served as static JSON under /risex/abis/ instead of being pasted into MDX. That keeps documentation pages fast to load and avoids build-time memory issues while remaining easy to copy into your own repo or pipeline.
Download all ABIs
Use the button below to fetch every ABI file in one step. Your browser downloads a single ZIP archive (risex-contract-abis.zip) containing the same JSON files as in this documentation tree.
Contracts
| Contract | Role | ABI (JSON) |
|---|---|---|
| AccountRegistry | Address-to-user registration and userId resolution | AccountRegistry.json |
| CollateralManager | Collateral balances, margin, and related accounting | CollateralManager.json |
| ERC20 | Fungible token interface (collateral and quoted assets) | ERC20.json |
| FeeManager | Fee parameters and fee-related flows | FeeManager.json |
| FundingRate | Funding settlement, premium index, and per-market funding clamps | FundingRate.json |
| OrdersManager | Order placement, updates, and coordination with matching | OrdersManager.json |
| PerpsManager | Perpetual positions, markets, and funding-related logic | PerpsManager.json |
| RISExAccessManagerUpgradeable | Role-based access control (upgradeable deployment) | RISExAccessManagerUpgradeable.json |
| RISExAuthorization | Permits, session keys, operator allowances, and permission checks | RISExAuthorization.json |
| RISExOracle | Price and oracle surface for the protocol | RISExOracle.json |
| RISExUniversalRouter | Composed execution and router entrypoints | RISExUniversalRouter.json |
Suggested workflow
- Confirm chain and contract addresses from Deployments.
- Add the matching ABI JSON to your project (copy from this site, use the ZIP above, or vendor the files from
public/risex/abis/in the docs repository). - Instantiate clients (for example
getContractin viem orContractin ethers) and encode calls with your library’s helpers.
For higher-level signing and session flows, see Contract interface and the rest of the RISEx documentation.