How the pieces fit
Every box is a component you can run, install or read. Select one to see what it does and where its code lives.
Start here
Give your AI agent the chain
SKILL.md is a compact context file for Claude Code, Codex and similar agents: endpoints, token names, renamed fields, genesis accounts and the deltas from Hive. Drop it in ~/.claude/skills/pixagram/ and the agent knows Pixagram.
What Pixagram is
A social network on a chain
Pixagram looks like a photo app: a feed, profiles, likes, comments, communities. Underneath, every post and every vote is a transaction on Pixa, and the images themselves are stored on chain as base64 PNG, WebP or SVG — no hashes pointing at a server that may disappear. Posting is free through recharging resource credits, and authors and curators are paid from the chain's own inflation.
A Hive fork, tuned
Pixa tracks hived 1.28.7, the software behind Hive and, before it, Steem. Blocks close every three seconds and are signed by up to 21 elected witnesses. What changed: the tokens are PIXA (liquid), PXS (the stable unit, worth one Big Mac by convention) and VESTS (staked PIXA); keys start with PIX; transactions may be twice as large; and both of Hive's passive-yield levers are welded to zero, so holding earns nothing — only producing blocks, posting and curating does.
Pictures into pixel art
The one piece that is not a blockchain is the converter: an SDXL pipeline with a depth ControlNet, a pixel-art LoRA and InstantID face preservation, running as a Hugging Face Space. It turns any photo with a face into 4K pixel art that still looks like the person. Nothing uploaded is stored.
Who runs what
The chain is run by its witnesses, elected by stake-weighted vote; six produce today and the guide on this site explains how to become the seventh. The app is served by public API nodes in Warsaw, Singapore, France and Iowa. The code is developed under the pixagram-blockchain organisation on GitHub and published to npm under @pixagram and to Docker Hub under pixadock.
Repository index
Everything under github.com/pixagram-blockchain, grouped by what it is for. The activity page shows which of these changed recently.
Run the network
| Repository | What it is | Links |
|---|---|---|
| witnessShell, Docker Compose | Two-container witness stack: hived with the four plugins a producer needs, and the price feed. Joins the network at api.pixagram.com:2001. 2 vCPU, 4 GB, 50 GB. | Guide, step 5 |
| pixagram-nodeShell, Docker Compose | Full public API node: hived, HAF (hived + PostgreSQL), Hivemind, Jussi and Caddy for TLS. Nine containers, 4 vCPU, 16 GB, 100 GB. | Guide, step 8 |
| bigmac-feedGo | Price-feed publisher. Reads the US Big Mac price from The Economist's index, divides it by a PIXA/USD reference and broadcasts feed_publish through your own node every hour. | pixadock/bigmac-feed |
| pixagramC++, MIT | The chain itself: the hived fork tracking Hive 1.28.7, with Pixa's tokens, raised limits, restricted allocation accounts and zero-yield monetary policy. Shipped as the pixadock/pixagram image. | pixadock/pixagram |
| hafC++, PL/pgSQL | Hive Application Framework fork: a hived whose sql_serializer plugin pushes every block into PostgreSQL, with automatic undo of forked-out blocks, so applications index a database instead of polling a node. | pixadock/pixagram-haf |
| hivemindPython, SQL, MIT | Social-layer indexer and API on top of HAF: feeds, follows, reblogs, communities, notifications and reputation, served as bridge.*, follow_api.* and tags_api.*. | pixadock/hivemind |
| alphanetDocker Compose | The project's own deployment: the full stack — hived, HAF, Hivemind setup/sync/server, Jussi, TLS and the feed — in one Compose file, with the bootstrap settings that started the chain. Read it to see how the pieces are wired; to run a node, use pixagram-node or witness, which are the operator versions. | Guide |
Build on it
| Repository | What it is | Links |
|---|---|---|
| dpixaTypeScript | The chain client library for Node and the browser: database, blockchain, broadcast, resource-credit and social APIs, keys, assets, failover between nodes. | @pixagram/dpixa, docs |
| pixagram-skillMarkdown | The agent skill: one file that tells Claude Code or Codex how Pixa differs from Hive and which endpoints to use. | Download |
| face-to-pixelart-4KPython, GPL-3.0 | Source of the AI converter: SDXL, depth ControlNet, retro-art and VGA LoRAs, InstantID face preservation, tiled high-resolution generation. | Hugging Face Space |
| fourteen npm librariesJavaScript, Rust/WASM | Storage, serialisation, rendering, upscaling, content safety, perceptual hashing and a post-quantum vault — the pieces the app is built from, published under @pixagram. | npmjs.com/org/pixagram |
Watch it
| Repository | What it is | Links |
|---|---|---|
| witness-statusJavaScript, MIT | Live technical status of the witnesses, computed in the browser from the public node. Also a dependency-free CLI with exit codes for cron, and a status.json snapshot refreshed every ten minutes for bots. | Activity, dashboard |
Public endpoints
| Node | Location |
|---|---|
https://api.pixagram.com | Warsaw — also the P2P seed, port 2001 |
https://merlion.surf | Singapore |
https://blockforge.lol | France |
https://pixarex.net | Iowa, United States |
All four serve the same Hive-compatible JSON-RPC over HTTPS POST, batches included, with CORS open. There is no testnet: pixagram.dev is the app's canary build, and anything broadcast through it is real.