Developer guide
Start building with the design.
Hybla is a proposed, independent Hive-derived chain. This hub is the public design reference for the people who will build, test and use it.
A useful place to begin#
Start with the short white paper for the economic argument. The reward specification explains claims, mana, curation and cashouts. The decision register separates selected direction from parameters still under discussion.
These are design commitments, not a claim that a running network implements them. This site does not yet publish a Hybla chain ID, RPC endpoint or testnet release.
A familiar foundation#
The starting point is Hive’s account, permission, transaction, witness and social-content architecture. Hybla changes the economic rules on an independent ledger. Hive balances do not automatically become Hybla balances.
The Hive Developer Portal is the upstream reference for accounts, JSON-RPC, SDKs and node operations. Its endpoints access Hive. Hybla compatibility must be checked against a published release before using any wallet or library.
The development path#
- Understand the rules.Read the reward and monetary design. Identify each unresolved parameter before writing consensus code.
- Explore the upstream interfaces.Use the read-only Hive example to inspect the existing reward fund.
- Test the differences.Exercise weekly mana, equal curation, claim decay, downvotes and supply accounting on an isolated network.
- Publish the network contract.A testnet needs public source, a pinned build, genesis, chain ID, endpoints and reproducible tests.
Where contributions matter#
Consensus developers, economic modelers, witness operators, wallet and front-end builders all have a part to play. Useful work starts with an explicit assumption, a reproducible result and a failure case.