Differences from Hive

Pixa runs Hive's code and speaks Hive's JSON-RPC, so Hive's documentation applies here with PIXA for HIVE and PXS for HBD. This page lists everything else that changes how you write code: the chain's identity, what the public API does to requests and responses, what Hivemind reports, and the protocol rules that differ. Every protocol value is on Chain Parameters; this page says what the values mean for a program.

Summary

Identity and assets

• Write amounts with Pixa's symbols: "1.000 PIXA", "0.020 PXS", "1000.000000 VESTS". A library that serializes Hive's symbol bytes produces signatures the chain rejects. hived checks a signature against both the legacy and the HF26 serialization of a transaction, so a client that signs the HF26 form, which identifies assets by NAI, avoids symbol bytes altogether.
• Never hard-code Hive's VESTS ratio. On Pixa one VESTS is worth about one PIXA, against about 1,608 VESTS per HIVE on Hive, and the ratio stays flat because no issuance goes to stakers. Compute it from total_vesting_fund_pixa ÷ total_vesting_shares (Pixa Power).

The public API

All six public nodes run the same gateway: Caddy, then an OpenResty configuration named Jussi, in front of hived and Hivemind (Chain Architecture).

Routing

Not served by any of the six: websockets, wallet_bridge_api (needed by the CLI wallet) and transaction_status_api. To learn whether a transaction is in a block, call database_api.is_known_transaction, then condenser_api.get_transaction with its id once the block is irreversible; before that, get_transaction answers Unknown Transaction (Transaction Lifecycle). The whole surface is on JSON-RPC Surface.

Field renames

The gateway renames Hive's field names in every response, and the names marked both also in requests to hived. Requests to Hivemind are not renamed.

Every other name stays Hive's. For example, author_reward operations keep hbd_payout and hive_payout, collateralized_convert_immediate_conversion keeps hbd_out, the treasury's funding operation is still called dhf_funding, and database_api.get_config still prints HIVE_ constants. Operation and API names are all Hive's.

Amounts inside responses. hived itself writes PIXA and PXS. The gateway also rewrites any amount followed by TESTS, TBD or HBD, such as "1.000 HBD", to PIXA or PXS wherever it appears in a response, text included.

Batches, ids and limits

Known issue: renames inside text

The gateway applies its renames to the whole body of a request or response, not only to field names. On 2026-10-05, a transaction whose post text contained pxs_balance reached hived from all six public nodes as hbd_balance.

• Writing. If any text you sign, whether a title, body, json_metadata, memo or custom_json payload, contains one of the 19 Pixa names marked both above, and the request is under about 10 KiB, hived receives different bytes from the ones you signed. The transaction fails with missing required posting authority (or active authority). Larger requests pass the gateway untouched, which is why artworks are unaffected. Until the gateway is fixed, keep these names out of signed text, or broadcast through a node without the gateway.
• Reading. Text in responses that contains a Hive name from the table, or an amount followed by TESTS, TBD or HBD, is shown renamed. A program that re-serializes a transaction from a response to check its signature can fail for the same reason.

Talking to hived directly

Your own node, including a witness node, has no gateway. hived reads and writes Hive's field names only, and it ignores a name it does not know without an error. Sent to hived directly, "percent_pxs": 5000 in a comment_options operation was read as the default 10000.

dpixa writes Pixa's names in five operations: claim_reward_balance, comment_options, escrow_transfer, escrow_release and witness_update. Sent to hived directly, those fields fall back to their defaults. That is harmless when a field holds its default anyway, such as pxs_interest_rate: 0 or percent_pxs: 10000; otherwise hived reconstructs a different transaction and rejects its signature. Broadcast these operations through a public node. Every other operation works either way.

Hivemind

• rshares are scaled for old votes. Hivemind multiplies the chain's rshares by one million for votes in blocks before 905,693, an inherited rule from Steem's early chain, and keeps the chain's value for later votes. One vote on 2026-10-05: 16,180,769,231,000,000 in bridge.get_ranked_posts and condenser_api.get_active_votes, 16,180,769,231 in the chain's effective_comment_vote operation. The chain crossed block 905,693 on 2026-10-05 23:36 UTC, so until the posts voted before then pay out, Hivemind's Trending and Hot weigh those votes a million times the newer ones (Feed and Discovery). Do reward arithmetic with hived's values.
• Reputation is not computed. Hivemind's reputation tracker does not run on the public nodes, so the condenser_api.get_account_reputations that the gateway routes to Hivemind returns 0 for every account, and bridge.get_profile and the post lists return 25, the bottom of Hivemind's display scale, for everyone. hived's reputation_api.get_account_reputations has the real figures.
• Twenty results per call. bridge.get_ranked_posts and the other list calls accept limit up to 20, not Hive's 100.
• Community names are portal- followed by digits, where Hive uses hive- (Communities).
• Social methods are Hive's. Feeds, posts, communities and notifications use the same calls and shapes, with the renamed fields above.

Protocol rules that change code

Libraries

SDKs and Libraries has the details and the tests.

Sources

• Gateway: jussi/nginx.conf at commit 4a271e8 (unchanged since 7e57cca): routing at lines 18-51, request renames at 63-85, response renames at 87-117, amount rewriting at 119-154, whole-body application at 189-193 and 219-233. Compression: ssl-proxy/Caddyfile.
• Tests on 2026-10-05: jsonrpc.get_methods, batch requests, request sizes, response headers and condenser_api.get_transaction_hex with a body containing pxs_balance, against all six public nodes; percent_pxs sent to a local hived 1.29.0; rshares compared between bridge.get_ranked_posts and the voter's effective_comment_vote in condenser_api.get_account_history. On 2026-10-08: bridge.get_profile against reputation_api.get_account_reputations; bridge.get_ranked_posts with limit 20 and 21; get_transaction on a reversible block; the rshares of votes before and after block 905,693.
• Code at tag v1.30.0 for the hardfork-30 rules, through Chain Parameters; at commit 48f75a2: asset symbols in asset_symbol.hpp:41-56; the witness property names the chain reads in hive_evaluator.cpp:160-188; everything else through Chain Parameters.
• dpixa at commit fddb47d: Pixa field names in src/chain/serializer.ts.
• Hive: developers.hive.io; Hive whitepaper (2020), §II.1 "Assets".