Chain integration
EVM and native Tezos
Separate native implementations with explicit network identities, interfaces, wallets, storage, and receipt verification.
Network and contract identity
Key state by chain family, exact network identity, and contract address. Select the deployment profile explicitly.
EVM
Sepolia uses numeric chain ID 11155111, 0x addresses, Solidity ABI encoding, and Ethereum transaction receipts. Read calls use eth_call at a pinned block; writes require an approved wallet transaction.
Tezos
Shadownet uses NetXsqzbfFenSTS, KT1 originated contracts, Micheline entrypoints and storage, FA2 ownership, and native operation receipts. Preserve Base58 address casing. Use the native RPC schema, not an Ethereum ABI.
Find the native implementation
Each module reference links directly to its implementation, tests, compilation targets, entrypoints, and views.
Repository layout
Solidity lives in src/modules/<module>/. SmartPy lives in src/modules/<module>/tezos/. Module manifests declare deployable contracts and dependencies. Source coverage, tested behavior, originated addresses, and audited parity are separate records.
src/modules/keel-hold/KeelHold.sol
src/modules/keel-hold/tezos/keel_hold.py
src/modules/keel-hold/tezos/keel_hold_onchfs.py
modules/keel-hold/keel.module.json
modules/keel-hold/deployments/11155111.jsonNative publication and dependency resolution
Prepare unsigned native operations; confirm each origination and resolve its real dependencies before the next stage.
SDK publication adapter
tezos-publication.ts defines the native publication plan, exact network validation, operation details, object inscriptions, and confirmed dependency resolution. Placeholder addresses are preparation scaffolding, never deployment evidence.
Read back after publication
Verify the exact network, confirmed operation, originated address, entrypoint/storage types, object bytes, and decoded digest. Then run the resulting token viewer. A local compile or simulated plan does not establish a deployed native reader.