Pixa
GitHub

Pixagram wiki

Proven tech. New canvas. Pixagram is a social network for pixel art. It runs on the Pixa chain, a blockchain built from the code of Steem and Hive, and every artwork published there is written into the chain itself.

Status: Live

Mainnet has run since 2026-09-04. Hardfork 30 has been active since 2026-10-07, and nodes run hived 1.30.1, a release without a hardfork, since 2026-10-15. Buying and selling artworks on chain is planned for 2027. Titles in plain text in the contents below are planned pages, not yet written.

Nothing here is financial, investment or legal advice. PIXA, Pixa Power and PXS carry risk, and PXS promises no price.

At a glance

3 seconds
per block
Few fees
Most operations draw on Resource Credits, which recharge from your stake. Opening an account, creating a proposal and converting PIXA to PXS cost a fee.
In the block
Each artwork is stored inside its post, not linked from elsewhere.
Proof-of-Brain
Stake-weighted votes decide which authors and curators are paid.
No passive yield
Holding PIXA, Pixa Power or PXS earns nothing by itself. Publishing, curating and producing blocks do.
100 million PIXA
at genesis, all of it staked

Every figure, with its source in the code, is on Chain Parameters.

Where to start

New to Pixagram

What Is Pixagram, then the FAQ.

Tokens and rewards

Tokens at a Glance and Proof-of-Brain. For PXS, PXS at a Glance.

Governance

Witnesses and DPoS, and how far the network is decentralized today: Decentralization and Safeguards.

Building an app

Developer Quickstart and Differences from Hive. The chain speaks Hive's JSON-RPC:

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

Run a Node and Become a Witness.

Checking a number or a name

Chain Parameters and the Glossary.

Contents

The pages are grouped in six parts, and each folder has its own index.

Understand

Concepts, written precisely

01

Start here

New to Pixagram? These pages say what it is, where it comes from, what it stands for, who does what and what is planned.

02

Social layer

How publishing, voting and communities work on the Pixa chain, and how rewards are decided.

03

Art on chain

How an artwork is stored in the chain itself, how long it lasts and what it proves.

04

Tokens and economy

PIXA, Pixa Power and PXS: what each is for, how new tokens are issued and destroyed, and where the stake came from.

05

Pixa Supra (PXS)

PXS promises no price: nothing defends it, and no one owes its holder anything.

06

Economic cybernetics

PXS promises no price. Its design notes describe it with terms from cybernetics; these pages explain those terms and say where each one meets the code and where it is only a metaphor.

07

Governance

Who produces blocks, who decides what the community fund pays, how the rules change, and how concentrated these powers are today.

Use and build

Guides step by step; exact commands, pinned versions

08

Guides

Step-by-step guides to using Pixagram at pixagram.com.

09

Developers

Exact, tested instructions for building on the Pixa chain, with pinned versions and expected output.

10

Node operators

Running the Pixa chain's software: a node that follows the chain, an API node that serves apps, and a witness that produces blocks.

Protocol, API and security

Specification: every rule with its source

11

Protocol reference

What the Pixa chain accepts and what it does with it: every operation, the path a transaction takes from a wallet to the index, and the data the chain holds against the data that apps and indexers derive from it.

12

API reference

How to talk to the public nodes. The API is Hive's JSON-RPC, so Hive's method documentation applies; these pages record the public nodes, the gateway's behaviour and every Pixa difference.

  • JSON-RPC Surface
  • condenser_api · database_api · bridge_api · account_history_api · rc_api, planned
  • Search API, planned
  • WebSocket and Streaming, planned
13

Security

Where the security material lives today, and the pages planned for this section.

  • Threat Model, planned
  • Key Security · Account Compromise, planned
  • Transaction Signing, planned
  • Malicious Content · Permanent Data Risks, planned
  • Node Security · API Security, planned
  • Oracle Security, planned
  • Incident Response, planned

The application

The product as it works, and which layer each behaviour belongs to

14

Pixagram product

The application at pixagram.com as a product: what each screen does, which of it is a rule of the chain, which is the indexer's, and which is the app's own.

15

Search and indexing

The components that find things: the app's search as it works today (Search), and PAPH, the perceptual hash published for pixel art.

  • PAPH
  • Indexing Architecture · Content, Artwork, Account, Community and Temporal Indexes · Geometric and Palette Screening · Similarity Search · Ranking Pipeline · Semantic Search · Question Answering · Caching · Benchmarks, planned
16

AI and knowledge

The app already runs two small models on the user's device, for sensitive images and for harsh wording (Account Settings), and its search sends artwork and post queries to a service that fuses text and image signals (Search).

  • AI Search · Natural-Language Queries · Question Answering · Retrieval Architecture · Evidence and Citations · Model Selection · Hallucination Control · Temporal Questions · Ranking with AI · Privacy and Data, planned

Marketplace, infrastructure and economics

What exists, what is planned, and worked numbers

17

Marketplace

Buying and selling artworks on chain is planned for 2027.

  • NFTs and Marketplace
  • Marketplace Protocol · Artwork Ownership · Minting and Tokenization · Transfers · Listings · Purchases · Auctions · Escrow · Fees and Burns · Royalties · Licensing · Disputes and Reversals · Marketplace Security · Marketplace Economics, planned
18

Infrastructure

The network as it is run: which programs sit between a reader's browser and the chain, where the public nodes are, and how data flows between them.

  • Architecture
  • Node Types · API Stack · HAF and Hivemind · Jussi and Gateway, planned
  • Indexers · Data Flow · Backups and Recovery · Monitoring · Observability · Capacity and Performance · Disaster Recovery, planned
19

Economics lab

Worked examples that follow the chain's own arithmetic step by step, each checked against a real payout.

  • Reward Examples
  • Voting Examples · Inflation Scenarios · Pixa Power Examples · PXS Scenarios · Haircut Simulations · Oracle Failure Scenarios · Economic Simulation, planned

History, reference and about

Tables, sources, dated records, signed essays

20

History and design

Where Pixagram comes from, read against the record; what the network has changed since genesis; and the essays its authors have signed.

21

Reference

The tables the other pages rely on. Chain Parameters is the reference for every protocol number.

22

About these pages

How these pages are written, and the legal notices that apply to them.

About the project

This repository holds Pixagram's documentation: what the network is, how to use it, how to build on it, and the figures behind it. Every page is a Markdown file that you can read here on GitHub.

Pixagram's aim is simple: artists should own their work and be paid for it directly. They are paid through other members' votes (Proof-of-Brain) and through tips. The chain started from a new genesis, with no airdrop and no mining (Genesis and Distribution).

Three legal entities, in three jurisdictions, share the work (Who Does What):

  • Pixagram SA (Switzerland) develops the protocol.
  • The Pixa Omnibus Foundation (Cayman Islands) stewards it.
  • Pixa Rex S.A. (Panama) operates the app.

How the pages are written

Part Folders Voice
Understand 01-start-here to 07-governance concepts, written precisely
Use and build 08-guides · 09-developers · 10-node-operators guides step by step; exact commands, pinned versions
Protocol, API and security 11-protocol-reference · 12-api-reference · 13-security specification: every rule with its source
The application 14-product · 15-search-and-indexing · 16-ai-and-knowledge the product as it works, and which layer each behaviour belongs to
Marketplace, infrastructure and economics 17-marketplace · 18-infrastructure · 19-economics-lab what exists, what is planned, and worked numbers
History, reference and about 20-history-and-design · 21-reference · 22-about tables, sources, dated records, signed essays

One question organises the pages: for every behaviour, is it a rule of the chain, a property of the indexer, or a choice of the Pixagram app? Each page says which. Three rules hold them together:

  • One reference for every number. Every protocol value is on Chain Parameters; other pages that quote one link there.
  • A status line on every page. Each page opens with one of Live, Planned (date), Proposed or Historical.
  • Inherited → changed. Every concept page ends with a table of what Steem or Hive did and what Pixa does instead.

The Style Guide has the rest.

Editing

Contributing has the full process, including how to report a security problem privately. In short:

  1. Follow the Style Guide.

  2. Name files in lowercase with hyphens, and list every new page in its folder's README.md and in the contents above.

  3. Link between pages with relative paths ending in .md, for example ../21-reference/glossary.md#haircut.

  4. Before opening a pull request, run the checks:

    Shellpython3 .github/scripts/check_docs.py

    They verify that every link and anchor resolves, that every page has a status line and is listed in its folder's index, and they warn about retired terms. They need only Python 3, and they run on every pull request.

Review

.github/CODEOWNERS routes each change to its reviewers. The pages on PXS, distribution, the legal entities and legal text need the owner's approval; chain facts are also checked by the chain maintainer. To make that approval binding, protect main with Require a pull request before merging and Require review from Code Owners.

Licence

Text published under the MIT License. The Pixagram® name and logo are not covered by it.