---
title: Global Addressing
tags: docs
---

# Global addressing

(or MultiAddressing)

1. we have a working proposal within metachains to globally address ethereum (sub-)state tries

    <originChainId><AnchorAddress><JUMP><ContractAddressOnMetachain>

published services on origin by validators of core
2. multiaddresses standardize networking protocol "endpoints"
/ipv4/127.0.0.1/tcp/6600/

extended threadsDB `/ipv4/127.0.0.1/tcp/80/log/jdklflksd`
/ip4/127.0.0.1/tcp/4006/p2p/12D3Koo......PbbdRME/log/12D3Koo...iHKfiMf

imagine:
/ipv4/127.0.0.1/tcp/6600/p2p/12D3Koo......PbbdRME/contract/CID_global_address_contract (3)

? solidity compiles metadata, should this be included in the global

3. IPLD node which contains global addressing informartion -> CID is the global address
counter point: who manages the availability of this IPLDnode?
whereas, if the multiaddress is resolvable in its own right

    {
        "multiAddress": "/ethereum/0x00000000000000001/metachain/0xaf2..28/contract/0xff4..33",
        "abi": "CID",
        ...? as Alice, what is helpful ?
    }

Examples of Ethereum/Blockchain multiaddresses
"/ethereum/0x00000000000000001/metachain/0xaf2..28/contract/0xff4..33/eip165/0xadf.."
"/cosmos/001/zone/0xaa2.."

"/ethereum/0x00000000000000001/contract/0xfd4..33"
"/ethereum/0x00000000000000002/contract/0xed4..21"

"/cosmos/001/zone/0xaa2.."

## Random Resources

- [Multiaddr](https://multiformats.io/multiaddr/)
- [Multiaddr Github](https://github.com/multiformats/multiaddr)
- [Multiaddr Protocols](https://github.com/multiformats/multiaddr#protocols)
- [Universal Chain Registry](https://github.com/UCRegistry/registry)
- [EIP-165](https://eips.ethereum.org/EIPS/eip-165)