These are the contracts running on Kortana mainnet, chain ID 9002. Every address below was read from the chain, not from a deployment record.
- Factory - 0x8f126a956c13cc9737347a08ff25085766248d3d
- Router - 0x2c0ea6fa405005b689a6d05da2c13eeef40b01ed
- Quoter - 0x4ac6feab19bf8839153b2c1a10a7085d63bd60f4
- Price oracle - 0x672016410905df75c57b68b8b844dcd39edb227b
- DNR/KUSX pool - 0x405947b02232eeb0667296677b2dff50772bb6f9
- Wrapped DNR - 0xf3ae219b8379311ec061c92da2bb34178b9da36d
- KUSX token - 0x12e923e9331bbb2a9f4c997a94c98298aa0af0f6
- KUSX supply controller - 0x6f95075af7ffadf866d4d95f199596be8f2d0ad9
- KUSX oracle adapter - 0xc6f78540927210482c36db1513163d7a8eba6ffa
- KUSX stability module - 0xb5922c61ef20aee79bdce021f177d014f7f66e4b
The bytecode deployed at each of these addresses was compared against a fresh build of the published source on 2026-09-22. All ten match. The only differences are the compiler metadata hash, which records build paths rather than logic, and the constructor values written into the code at deployment.
You do not have to take that on trust. Build the source with Solidity 0.8.26, EVM target cancun, then compare your deployed bytecode against the chain with eth_getCode, ignoring the trailing metadata section whose length is encoded in its final two bytes.
Source is not yet verified on a third-party service. Sourcify does not support chain 9002, and support there follows from the chain being listed in ethereum-lists/chains, which is in progress. Until then the reproduction steps above are the way to check, and they do not depend on trusting us or any explorer.