# Contract Addresses River is pre-launch; deployment addresses will be published here per network at release. Each deal deploys its own instance set. The table below is the shape integrators should expect — one row-group per deal, plus shared governance singletons. ## Per deal (example: first deal, Ethereum Mainnet) | Contract | Address | | --- | --- | | Structure | *TBD at deployment* | | Senior class token (`DistributingClassToken`) | *TBD* | | Junior class token (`DistributingClassToken`) | *TBD* | | Senior accumulating wrapper (`DistributingVault4626`) | *TBD* | | Exit queue (senior) | *TBD* | | Exit queue (junior) | *TBD* | | Waterfall | *TBD* | | Facility | *TBD* | | FacilityReporter | *TBD* | | Gate | *TBD* | ## Shared (governance) | Contract | Address | | --- | --- | | RiverAccessControls | *TBD* | | RiverGovAuthority (timelock) | *TBD* | | RiverPause | *TBD* | ## ABIs ABIs are generated from the audited source in the [river-contracts repository](https://github.com/river-one-eco/river-contracts); build artifacts ship with each tagged release. ## Verify before integrating Always verify that an address you integrate is the one published here (or announced through River's official channels) — per-deal deployments mean multiple legitimate instances will exist, and only published ones are covered by River's audits and operations.