Build on Hive without reading anyone else’s mind
json_metadata: { "openattribute.news": true }One key alongside the metadata your application already writes. No API keys, no telemetry, and nothing to install. Anyone can read the register, and anybody can add a name to it under their own Hive account. What each name means is written down where it can be looked up: the register, and the convention around it on the spec.
One chain. Everything anybody has ever published is already on it.
And an application for every taste, all of them writing to the same place.
Each invented its own name for the same few things, written into the metadata it already publishes.
Every one of those is readable by anybody. None of them is written down, so only the application that coined it knows what it means.
A second application can see the name. It cannot know what it stands for, or what shape the value takes.
So the meaning gets written down once, on the same chain, in the open: what the name means and what shape it takes.
Nothing passes through the middle. An application reads the definition once, then reads the other’s content directly.
Every name written down is one more thing the next application can already render.
What it does
01
Discover what exists
Before creating a new field, check whether another application already defined one. Every registration is on-chain, with a description of its meaning and, when needed, the structure of its values.
02
Write it, read it
Add one key to the metadata you already publish. Read definitions from other applications and build on them. Interoperability of content, not uniformity of experience. What you create stays yours.
03
Register your own
Create an attribute no one has defined yet and register it under your own account. Other applications can understand it without permission or coordination.