Developer guide
Network & tooling
Use the Hive ecosystem to understand the foundation. Hybla network configuration will be published with a reproducible testnet release.
What is available#
- Public design
- Available on this site
- Hybla public testnet
- Not announced here
- Chain ID, RPC and faucet
- Pending testnet release
- Public Hybla consensus release
- Pending publication
- Mainnet and initial distribution
- Not launched through this site; design incomplete
No token sale or token-claim service is offered here. Joining the working group is a signature of interest in exploring the project.
Read the Hive reward fund#
This example reads Hive, the upstream network. It needs Node.js 22 or later and an internet connection. It sends no transaction and requires no keys.
// Run with Node.js 22 or later. Reads the existing Hive chain.
const response = await fetch('https://api.hive.blog', {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify({
jsonrpc: '2.0',
method: 'condenser_api.get_reward_fund',
params: ['post'],
id: 1
}),
signal: AbortSignal.timeout(10000)
});
if (!response.ok) throw new Error('HTTP ' + response.status);
const data = await response.json();
if (data.error) throw new Error(data.error.message);
console.log(data.result);Save as reward-fund.mjs and run node reward-fund.mjs. Inspect fields such as reward_balance, recent_claims and author_reward_curve. The response is Hive’s current state; it does not demonstrate Hybla’s proposed rules.
Public RPC services can be unavailable or rate-limited. A timeout or HTTP error is surfaced by the example.
Before connecting an application#
- Verify the Hybla chain ID, transaction serialization, address prefix and asset symbols from the eventual release.
- Check which APIs and SDKs the release actually supports.
- Make network selection explicit in the wallet and application.
- Use separate test credentials and verify transaction destinations before signing.
Wallet support, account migration, delegation behavior and cross-posting are integration work, not promises of automatic compatibility.
For node operators#
The testnet package must include a pinned source revision, build instructions, genesis and seed configuration, hardware measurements, replay procedure and witness setup. These details remain unpublished here rather than being replaced with speculative commands.