Chain Parameters

This page is the reference for every protocol number in these pages. Other pages may quote a number when it helps the reader, but they link here, and this page wins if the two disagree. When the chain changes, it is corrected here first.

Each row gives the value in upstream Hive, the value on the Pixa chain, the kind of number it is, and its source. Bold marks a Pixa value that differs from Hive. Numbered notes follow each table.

The Pixa code is cited at commit 48f75a2 of pixagram-blockchain/pixagram, the 1.29.0 release, for every rule hardfork 30 left unchanged, and at tag v1.30.0 for the rules it changed. Paths are relative to libraries/, and config.hpp means protocol/include/hive/protocol/config.hpp. Hive values come from hived 1.28.7, the release Pixa is built on (upstream config.hpp), or from the live Hive chain where marked. The live Pixa nodes report revision d986a23, the last commit of the hardfork-30 branch before the release was tagged.

Network identity

1. The ASCII bytes of pixagram, zero-padded to 32 bytes.
2. Pixa Supra. PXS promises no price; its rules are in Pixa Supra (PXS) and the price feed.
3. Called Pixa Power (PXP) in prose.
4. These are the symbol bytes in the legacy, pre-NAI wire format. Clients that hard-code Steem's bytes produce invalid signatures.
5. A new chain: no balances were carried over from Steem or Hive. What genesis created is in Genesis.
6. Hardforks 1–28 all applied at block 1; hardfork 29 at block 402,205 (2026-09-18 12:00 UTC); hardfork 30 at block 949,330 (2026-10-07 12:00 UTC). What each changed is on Protocol Upgrades.
7. 1.30.1, tagged on 2026-10-15, is a maintenance release without a hardfork: it merged upstream Hive 1.28.8, and every value in its config.hpp is that of 1.30.0 (v1.30.1). On 2026-11-03 all 21 scheduled witnesses ran it (get_witnesses_by_vote).

Genesis

1. 25,000,000 PIXA ÷ 102, the genesis feed of 102 PIXA per PXS. The accounts and their rules are on System Accounts.

Blocks and witnesses

1. A witness enters the schedule once accounts holding at least 1% of all outstanding VESTS approve it (Witnesses and DPoS).

Transaction and block size

1. The live maximum block size minus 256 bytes, checked when a node accepts a transaction.
2. Despite its name, this constant only sets the smallest block size witnesses may vote for (config.hpp:391, hive_operations.cpp:312-325). It does not cap transactions.
3. The body must be non-empty UTF-8; otherwise only the transaction limit applies. Artwork posts published from 2026-09-04 to 2026-10-04 had a median body of about 26 kB, and the largest so far is 497,479 bytes (block 65,406).
4. Larger requests are refused with HTTP 413.
5. Since hardfork 28, a transaction may name an expiry up to 24 hours ahead. A node drops a transaction that is still unconfirmed 1 hour after it first saw it.
6. Checked when a node receives a transaction, before any signature is verified; not a block-validity rule (Transaction Lifecycle).
7. The execution-time part of the Resource Credit cost is multiplied by 1 + payload bytes ÷ 8,192, so a 64 KiB payload costs nine times a small one in that part (Resource Credits).

Accounts and keys

1. The fee is burned: it is paid to null (hive_evaluator_account.cpp:193).
2. Tickets are claimed with Resource Credits instead of a fee.
3. Account recovery needs this history (hive_evaluator_account.cpp:578). Before hardfork 30 the chain recorded none, because the inherited start block, 3,186,477, lay in the future; since 2026-10-07 12:00 UTC every owner-key change is recorded, so a recovery can undo an owner change made after that moment, and none made before it (Keys and Recovery).

Posts and comments

1. The limit that nodes apply when accepting transactions. Consensus allows up to 127 beneficiaries and a reply depth of 65,535.
2. Votes are accepted until payout, but in the last 12 hours each vote's rshares, up or down, are multiplied by the time left ÷ 12 hours.

Voting and curation

1. Since hardfork 28, the cost is a share of the full mana bar, whatever is left: 50 full-strength votes empty a full bar, and a vote's strength does not shrink as mana runs down.
2. Every vote loses this amount. On Pixa 1 VESTS ≈ 1 PIXA, against about 1,608 VESTS per HP on Hive, so Hive's 50,000,000 meant a full-strength vote needed more than 2,500 Pixa Power to count at all; hardfork 30 divided it by 1,000, and a full-strength vote now counts from more than 2.5 Pixa Power. On Hive the threshold is about 1.6 HP. Before hardfork 30 the deduction was Hive's (hive_evaluator_social.cpp:710-711).
3. Earlier votes earn more than later votes of equal weight.
4. Hardfork 29 lowered the reward fund's recent_claims to at most this value (database_hardfork.cpp:525-561). The value inherited from Hive had made early payouts too small to pay.

Pixa Power (staking)

1. 1 VESTS was worth 1 PIXA at genesis, and the ratio stays flat because nothing is added to the vesting fund without issuing VESTS (live: 1 VESTS = 1.0000000072 PIXA). On Hive the vesting reward adds HIVE to the fund without new VESTS, so each VESTS is worth more over time. The Hive figure is from 2026-10-05.

Issuance

New PIXA is created in every block. The yearly rate depends only on the block number h:

rate(h) = max( 9.78% − 0.01 percentage points × floor(h / 250,000) , 0.95% )

The constants are Hive's (config.hpp:260-262, database.cpp:1732-1737). Pixa counts h from its own genesis, so it restarted Hive's schedule at the top.

1. On Pixa: the PIXA supply plus the PXS outside the treasury, valued at the median feed.
2. Hive weights each block's witness pay so that 21 blocks' worth is spread over the scheduled witnesses; with fewer than 21, each block paid more, and on 2026-10-05 a block paid about 2.33 times the nominal share (0.329 PIXA). Since hardfork 30, while fewer than 21 witnesses are scheduled every block pays exactly the nominal share; a full schedule keeps Hive's weighting.
3. Hive converts each block's share to the debt token and rounds down to 0.001. At Pixa's scale one block's share is a few thousandths of a PXS, so the rounding cut the fund to about 74% of its share. Since hardfork 30 block n pays floor((n+1)x) − floor(nx) of the exact share x, which telescopes to the exact amount over consecutive blocks.
4. When an author's liquid half is converted to PXS, the PIXA that does not fit into a whole 0.001 PXS was burned; since hardfork 30 it is paid to the author as PIXA (Reward Examples).

What this means today. On 2026-10-08 a block's nominal issuance was about 0.936 PIXA (block 979,298):

• Content: about 0.655 PIXA to the reward fund.
• DPF: about 0.140 PIXA, which is 0.0027 PXS at the median; paid as 0.002 or 0.003 PXS a block so that the blocks together receive the exact share.
• Witnesses: about 0.141 PIXA, paid as Pixa Power to the block's producer, who also takes the split's rounding remainder (producer_reward 0.140999 VESTS a block after hardfork 30, against 0.328999 before).

The chain issues the nominal amount, about 9.75% a year at today's block height. Before hardfork 30 it issued about 1.16 times that, about 11.3%, because of the witness weighting and despite the DPF's rounding loss (Supply, Inflation and Yield).

Pixa Supra (PXS) and the price feed

PXS promises no price. It has no peg, cannot be redeemed for money and pays no interest, and no one stands behind its value. The rows below are the rules the chain applies to it.

1. The feed software sets what a feed means. bigmac-feed v1.3.0, which the witness repository ships since 2026-10-30, prices one Big Mac in the local currency of the witness's country, or at a price the witness declares, and divides it by the fair value of PIXA's order book converted into that currency, so no currency is privileged (Oracle and Price Feed, Become a Witness). The feed software is not part of consensus.
2. The chain takes no sample in an hour when too few witnesses have a current feed; the median in force then stays as it was. get_config still prints HIVE_MIN_FEEDS: 7; the runtime check differs.
3. On 2026-11-03, at block 1,722,911; 51.833 on 2026-10-08. See the note below.
4. Witnesses cannot publish any other value (hive_operations.hpp:432).
5. The debt ratio is the value of the PXS outside the treasury as a share of that PXS plus all PIXA. While it is under 20%, part of each author reward is paid in PXS. At or above 20%, that part is paid in PIXA (database.cpp:2943-2964).
6. Above 30%, one PXS converts to at most 3P ÷ 7S PIXA, where P is the PIXA supply and S the PXS outside the treasury (database.cpp:2500-2528).
7. Refused if PXS would pass 20% (hive_evaluator_transfer.cpp:579-580).

The live median still rests on the placeholder. On 2026-10-08 every witness published 6.22 USD (a US Big Mac) ÷ 0.12 USD, an agreed placeholder price for PIXA. PIXA has traded on one market since 2026-10-15, and on 2026-11-03 the 21 scheduled witnesses published ten different feeds, from 31.731 to 70.792 PIXA per PXS: fourteen read the market, each with its own country's Big Mac, and seven still published the placeholder values 51.833 or 51.000. The seven sat in the middle of the feeds, so the hour's sample was 51.833, and 76 of the 84 samples behind the median of 51.000 were placeholder values (what the feeds read).

The same thresholds as collateral ratios. Let R be the value of all PIXA divided by the value of the PXS outside the treasury, both at the median feed. The debt ratio d and R are linked by R = 1/d − 1. This gives:

• PXS printing stops at R ≤ 4×.
• The haircut starts at R < 2.33×. Below that, a PXS settles for the factor min(1, 3R ÷ 7) of its feed value.
• On 2026-10-08, R was about 1,145×: 100,780,034 PIXA against 1,699 PXS outside the treasury, at 51.833. On 2026-11-03, about 155×: 100,931,814 PIXA against 12,771 PXS, at 51.000.
• The protocol has no upper threshold.

The PXS design notes describe a corridor of "roughly 3× to 10×"; the numbers on this page are the ones the chain enforces (the two compared).

Decentralized Pixa Fund (DPF)

1. On both chains steem.dao also counts as treasury. On Pixa, pixa.omnibus has no keys.
2. PIXA transferred to the treasury is converted at once, at the median. Any PIXA balance it holds converts at 0.05% per day (config.hpp:497, dhf_processor.cpp:342).
3. A proposal id is chain data, not a constant.
4. Each hour pays the difference between two running totals measured from the proposal's start, so the part below 0.001 PXS carries over instead of being discarded; before hardfork 30 a proposal paying less than 0.024 PXS a day received nothing.

Resource Credits

Reading live values

Every call below works against any public node; api.pixagram.com is the default. That endpoint renames Hive's hbd_* fields to pxs_* (for example pxs_balance and current_pxs_supply); hived itself keeps Hive's field names.

Shellrpc() { curl -s -X POST https://api.pixagram.com -H 'Content-Type: application/json' \
  -d "{\"jsonrpc\":\"2.0\",\"method\":\"$1\",\"params\":$2,\"id\":1}"; }

rpc condenser_api.get_dynamic_global_properties '[]'   # supply, issuance split, block size, fund ledger
rpc database_api.get_config '{}'                        # compiled constants
rpc condenser_api.get_chain_properties '[]'             # witness medians: account fee, block size
rpc condenser_api.get_witness_schedule '[]'             # scheduled witnesses, hardfork quorum
rpc condenser_api.get_feed_history '[]'                 # 84 hourly samples and the median in force
rpc condenser_api.get_reward_fund '["post"]'            # curation share, curves, recent_claims
rpc database_api.get_hardfork_properties '{}'           # last and next hardfork
rpc database_api.list_proposals '{"start":[""],"limit":50,"order":"by_creator","order_direction":"ascending","status":"all"}'

Figures you may meet elsewhere