# HOW TO USE

### Defining Your Standard Visualizer with Time Protocol

As the owner of a unique standard inscription, represented as "0.STANDARD", you have the privilege of selecting which visualizer should be employed for your standard text.&#x20;

This process is simple as posting a JSON object directly on-chain with the "0" owner's address.

This JSON object must include 4 **essential** variables:

1. **`standardName (sn)`**: This could be 'time', 'Hz', 'ovo', or any unique identifier for your standard.
2. **`standardInput (si)`**: This is the specific type of data your standard will work with. Examples could include 'frequencyInput', 'timeInput', 'standardInput', ... among others.
3. **`standardVisualizer (sv)`**: This is the URL to your HTML file that serves to visualize or decoder for your standard.
4. **`protocol`**: the protocol to apply to your text, "**btctime**" to use time protocol.

Below is a template for the JSON object to be submitted:

```json
{ 
  "protocol": "btctime",
  "sn": "",
  "si": "",
  "sv": ""
}
```

These fields should be filled out with your specific data. For example:

```json
// Bitcoin .time v2
{ 
  "protocol": "btctime",
  "sn": "time",
  "si": "textStandard",
  "sv": "/content/22a2f576b26b16b8d1b948cde408f5edcb023f843f5bb588e169be866fff9180i0"
}


// inscribed by "0.time" owner.
```

Upon successfully submitting this JSON on-chain through the owner's address, the defined visualizer becomes associated with your standard text.

Consequently, your standard is empowered to use this visualizer for interpretation or visualization of its inscriptions, granting you greater control over how your standard is interpreted and displayed.
