Tezos Domains for Developers
  • Introduction
  • Integrating Tezos Domains
    • Client Libraries
    • GraphQL
      • Mainnet
  • Smart Contract Design
    • Smart Contract Overview
    • Top-Level Domain Registrar
    • Ownership Scheme
    • Domain Data
  • Contract Interoperability
    • Proxy Contracts
    • Name Resolution
    • Buys & Renewals
    • Auction Operations
    • Domain Operations
    • .tez TLD
    • Domains as NFTs
    • Affiliated Buys & Renewals
  • Deployed Contracts
    • Mainnet
    • Ghostnet
  • Audits
    • Audit by Quantstamp
    • Audit by Inference
Powered by GitBook
On this page

Was this helpful?

  1. Contract Interoperability

Proxy Contracts

To ensure future upgradeability while allowing clients to rely on fixed contract addresses, we offer a set of proxy contracts. Any contract or off-chain client can interact with them directly - the transactions are automatically routed to the correct destination.

You can find the addresses of the proxy contracts in the Deployed Contracts section.

Finding the Underlying Contract

Off-chain clients will often need to read data from an underlying contract. They can retrieve the individual addresses of underlying contracts from the proxy contract's storage. The generic storage structure follows:

type proxy_storage = {
    contract: address;

    (* ... more fields outside of this interoperability spec *)
}
storage (pair
    (address %contract)
    (
        # ... more fields outside of this interoperability spec
    )
);

Off-chain clients must not rely on a particular storage layout. They should always use annotations to find the correct value.

PreviousDomain DataNextName Resolution

Last updated 4 years ago

Was this helpful?