Library

dpixa, the chain client

@pixagram/dpixa is a fork of dhive, Hive's TypeScript client, with Pixa's chain ID, key prefix and asset symbols built in. It runs in Node and in the browser, speaks JSON-RPC over HTTPS with failover between nodes, and covers the whole surface: reading state and blocks, signing and broadcasting operations, resource credits, and the social API served by Hivemind.

v1.5.4   npm   GitHub   Full API reference

Install and connect

npm install @pixagram/dpixa

Node, ES modules

import { Client } from "@pixagram/dpixa";

const client = new Client(["https://api.pixagram.com", "https://merlion.surf", "https://blockforge.lol", "https://pixarex.net"]);

const props = await client.database.getDynamicGlobalProperties();
console.log(`head block ${props.head_block_number}, signed by ${props.current_witness}`);

Node, CommonJS

The prebuilt bundle is the path used by the registration script in the node guide; it needs no bundler and no polyfills.

const { Client, PrivateKey } = require("@pixagram/dpixa/dist/dpixa.js");

const client = new Client(["https://api.pixagram.com"]);
const key = PrivateKey.fromString(process.env.POSTING_WIF);   // never write a key into a file

client.broadcast.vote({ voter: "you", author: "author", permlink: "permlink", weight: 10000 }, key)
  .then(r => console.log("included in block", r.block_num));

Browser, no build step

<script src="https://unpkg.com/@pixagram/dpixa@1.5.4/dist/dpixa.js"></script>
<script>
  const client = new dpixa.Client(["https://api.pixagram.com"]);
  client.pixamind.getRankedPosts({ sort: "trending", tag: "", limit: 5 })
    .then(posts => posts.forEach(p => console.log(p.title, "by", p.author)));
</script>

Give the client several nodes: it retries the next one when a request fails, and consoleOnFailover: true in the options logs when it does. All four public endpoints answer identically and allow browser requests from any origin.

What the client exposes

Pixa specifics

The client already carries the chain ID (706978616772616d…, the ASCII string pixagram padded to 32 bytes) and the PIX key prefix as defaults. What you still need to know:

The complete list of deltas from Hive — genesis allocations, reward-curve tuning, the feed quorum — is the SKILL.md file, written for AI agents but just as useful to a person.

All packages

Versions are read live from the npm registry when the page can reach it; otherwise the figures are those of 5 September 2026.

Storage and dataRenderingContent safetySimilarityKey protection

Storage and data

Rendering

Content safety

Everything read from the chain is treated as untrusted, and all checks run on the device — no content leaves the browser to be classified.

Similarity

Key protection

Other languages, other tools

Pixa is a Hive fork, so every Hive client that lets you set the chain ID and the key prefix can talk to it: pass the chain ID above, PIX as the prefix, and one of the four endpoints. Legacy-format asset strings must read PIXA and PXS; the HF26 numeric asset identifiers work unchanged. Everything the Hive developer portal documents about operations and API methods applies, with PIXA for HIVE and PXS for HBD.

Without any library, one curl is enough:

curl -s -X POST https://api.pixagram.com -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","method":"condenser_api.get_accounts","params":[["account"]],"id":1}'

The witness-status project ships a dependency-free command-line tool that runs the whole health pipeline: npx github:pixagram-blockchain/witness-status --check exits 0, 1 or 2 like a monitoring plugin, and --format json prints the full model. The AGENT.md file documents every formula it uses.

Docker images

The node software is published to Docker Hub under pixadock, for amd64. Both Compose stacks in the node guide pull from here.

Without a config.ini in the bind-mounted data directory, hived starts in isolation — no seed node, no witness, default plugins only. The witness stack is the shortest path to a node that joins the live network.