Deployments
The contract addresses, the chains they are deployed on, and how to deploy them to another chain.
Assertions work on a chain once the four contracts are deployed there.
Addresses
Section titled “Addresses”The addresses are the same on every chain.
| Contract | Version | Address | Released in |
|---|---|---|---|
| Assertions | 2.0 | 0xa55e47C835ACD377da79D57162117D9B5Ecf3496 | Byakko |
| Operations | 2.0 | 0x09e4a7eF82674BaDD27a02E19f3D3e5a1903eA1f | Byakko |
| Collections | 2.0 | 0xc011ec7f6fAAaa37DE5923D2c6206C9597D16bc7 | Byakko |
| Expressions | 2.0 | 0xe5594e55aCa44ac271209612FA57866130edC9e5 | Byakko |
The builder uses them for you. If you build calls by hand, copy them from here.
Networks
Section titled “Networks”Each status is read live from the chain. Deployed opens the contract on the chain’s explorer. Pending deployment takes you to the steps below, where anyone can deploy the contracts.
Earlier versions
Section titled “Earlier versions”Earlier versions keep working at their own addresses.
| Contract | Version | Address | Released in |
|---|---|---|---|
| Assertions | 1.0 | 0xA55e4707A94Ce4Aa647517ed9aD4084e4E5D1f3F | Argos |
ENS names
Section titled “ENS names”Every contract has two ENS names. The release name is permanent: it keeps resolving to that release’s contract after a later one ships. The bare name always resolves to the newest release, so it moves when one ships.
| Contract | Version | Release name | Bare name |
|---|---|---|---|
| Assertions | 2.0 (Byakko) | byakko.assertions.eth | assertions.eth |
| Operations | 2.0 (Byakko) | operations.byakko.assertions.eth | operations.assertions.eth |
| Collections | 2.0 (Byakko) | collections.byakko.assertions.eth | collections.assertions.eth |
| Expressions | 2.0 (Byakko) | expressions.byakko.assertions.eth | expressions.assertions.eth |
| Assertions | 1.0 (Argos) | argos.assertions.eth | Moved to a later release |
Use a release name wherever the contract must never change under you.