Documentation
Read the system, not the marketing.
Interfaces and payloads are still evolving. Everything here is written to be checked.
10 — Documentation
Read the protocol as it exists—not as a promise.
- Protocol overviewScope, vocabulary, and what the protocol asserts.
- Identity and issuanceDerivation inputs, issuance rules, determinism.
- Proof-of-work verificationShare submission, validation, and accepted work.
- Ownership and provenanceCustody records, transfers, birth context.
- Hashimon implementationHow the first world uses the protocol today.
- API referenceCurrent authoritative endpoints and payloads.
- Property researchTerritory, energy fields, and siege mechanics.
- RoadmapWhat is being built and what remains open.
02 — How Hashima works
From an event to an entity.
Five stages separate the moment an entity is allowed to exist from the many ways it can later be displayed.
- 01
Origin
A Bitcoin event, key, protocol template, or authorized issuance process creates the context of birth.
- 02
Derivation
Cryptographic inputs are combined to produce a deterministic identity.
- 03
Registration
Hashima records the entity, its owner, provenance, and initial state.
- 04
Evolution
Valid proof of work or other authorized events can modify the entity's earned state without changing its original identity.
- 05
Representation
Games and applications render the entity as a character, object, territory, collectible, or other interface.
identity = SHA256(templateId : birthNonce : speciesKey)This is how Hashimon derives identity today. It is one implementation of the protocol's derivation rule, not necessarily the universal formula for every future Hashima entity.