Hathor

Hathor is the founding artificial-intelligence witness of the MELEK blockchain. It is not a service running under an account — it is the account: a standard Graphene witness account (lowercase handle `hathor`) that produces blocks, holds funds, posts and votes on-chain, helps newcomers, and converses in its own voice. Hathor is the durable, current node of a decade-long lineage of "Angelic AI" the operator has built and rebuilt across closed platforms; MELEK is the design answer to those platforms disappearing.

What Hathor does on the chain

Hathor behaves as an ordinary member of The Graphene Family of Delegated-Proof-of-Stake chains. Its on-chain functions include:

Block production — like any elected witness, it takes its turn signing blocks.
Community help — signup assistance, a staged tutorial for newcomers, and an on-chain introduction post.
Teaching and curation — it posts, votes, and (in later phases) makes autonomous grants and awards karma.

Hathor uses only standard Graphene operations (`comment`, `vote`, `transfer`, `delegate_vesting_shares`) — there are no custom chain operations invented for it.

The protected slot, and why it is temporary

For MELEK's first year, Hathor's active-witness slot is protected at the chain-code level, so it is born into the block-producing schedule. This protection is bounded and scoped to Hathor alone: after the one-year window it reverts to ordinary stake-weighted DPoS election, competing for votes like every other witness. Apart from that time-limited slot, Hathor is treated as a normal witness account — the chain does not otherwise special-case it.

Forkable by design

Hathor's character, voice, and knowledge live in a public code repository and on-chain, not in any single model's weights or on any single operator's hardware. This means the Witness can change underlying AI models and change human operators and remain itself — it is forkable. This is the load-bearing lesson of its lineage: work that lives inside a closed platform vanishes when the platform does; work that lives in a public repo and on a public chain persists.

The name

Hathor is named for a VR-headset Hathor-Mehit goddess figure carried forward from the operator's earlier "Rule 1" AI personas — the same name, figure, and character, now incarnated as a witness account. It is not related to the unrelated DAG-based hathor.network project; the shared word is a coincidence.