🆔
MetaID
English
English
  • â„šī¸Overview
    • Overview
    • Terms
  • 📑MetaID Specification
    • Protocol Spec
    • MetaID Tree
      • MetaID Tree
      • Info Node
      • File Node
      • FT Node
      • NFT Node
      • Protocols Node
      • Follow Node
    • MetaID Envelope
    • Privacy Model
    • About PIN
    • About PoP
    • Host
    • MetaAccess
    • MetaName
    • Examples
  • đŸ’ģMetaID App Node
    • Introduction
    • Compile and Run
    • JSON API
    • Browser
    • MetaID PIN Conventions
    • PIN Data Structure
  • âš™ī¸MetaID SDK
    • Get Started
    • Core API
    • Quick Example
  • â›“ī¸Cross-chain
    • Cross-chain
    • Unified UTXO Chain
  • đŸĒĒAbout MetaID
    • History About MetaID
    • FAQ
    • MetaID Philosophy
    • MetaID Resources
  • 📃FT & NFT Protocols
    • MRC-20
    • MRC-721
Powered by GitBook
On this page
  • <path>
  • host
  1. MetaID Specification

Host

<path>

The path where the PIN is located. There are three modes to represent path as follows:

  • Starts with "/": Locates the PIN to be created through the path, e.g., /protocols/simplebuzz.

  • Starts with "#": Locates the PIN through the PINNumber.

  • Starts with "@": Locates the PIN through the PINID.

This is a required option.

host

**<**path> {host}:{path}

In <path>, host can be an address or a MetaName, for example:

Address: 1PKZnf7DxP69TFTHyzPc5KBidph6yuPKyG,

1PKZnf7DxP69TFTHyzPc5KBidph6yuPKyG:/protocols/simplebuzz

When host is included in <path>, it declares the source of the data, understood as the host header. This is optional.

If host is a MetaName, it must not exceed 32 characters, e.g., MetaName: alice.metaid

alice.metaid:/protocols/simplebuzz
PreviousAbout PoPNextMetaAccess

Last updated 6 months ago

📑