Skip to main content
WesoForge

About

Hi, I’m Aurélien Mora (Eal on Discord), creator of WesoForge. The purpose of this project is to help compactify the Chia blockchain by converting “proof of time” (VDF) proofs into their compact (one‑witness / normalized-to-identity) form.

In Chia, blocks contain several VDF proofs. Those proofs are verifiable, but not always stored in their smallest representation. Chia’s “bluebox” concept exists to recompute these proofs into the compact form (using chiavdf) so the chain data becomes smaller and cheaper to store/serve.

What WesoForge is (at a glance)

It’s a distributed compaction pipeline made of a few cooperating components:

1) WesoForge client (CLI + GUI)

  • A worker application that leases compaction work from the backend, computes compact VDF witnesses, then submits results back
  • It embeds/relies on a slightly modified chiavdf to improve throughput for bluebox compaction (notably: better parallelism and reduced memory footprint during compact proof computation)
  • The UX goal is “one‑click compaction”: set a backend URL, choose CPU/RAM budget, run

2) Backend server (coordination + accounting)

  • A standalone HTTP API used by workers and the website
  • Responsibilities include:
    • create time‑limited leases so many workers can share a large backlog without stepping on each other
    • accept worker submissions
    • apply basic anti‑abuse rules (timeouts → reduced lease capacity, etc.) so one client can’t reserve everything and never return work
    • keep progress/stats/leaderboards for users and operators

The backend does not “blindly trust” clients: accepted results are validated through a local full node.

3) Modified full node (verification + storage)

  • A Chia full node extended with a local-only compactor API designed for high-throughput scanning + submission
  • Provides:
    • fast “what needs compacting?” scans (compaction targets)
    • robust submission with per-item reason codes (accepted / already compact / too recent / invalid proof / etc.)
    • a replayable event feed for reconciliation (so the backend can mark some jobs obsolete if they were compacted elsewhere)
  • When a compact proof is accepted, the node verifies it and replaces the proof in its local chain data so the block becomes compactified

4) Gossip node (wide P2P propagation)

  • A dedicated announcer process meant to connect to many peers and spread compact-proof announcements reliably while staying under Chia’s rate limits
  • On Chia’s P2P network, propagation is essentially:
    1. announce “a compact proof exists” (small)
    2. peers who want it request the bytes on demand (larger)
  • The gossip node focuses on step (1) at scale, so “compaction knowledge” spreads widely and other nodes can fetch proofs on demand

(The full node can also announce, but operationally a dedicated gossip node is used for broad coverage.)

5) Payer service (reward distribution)

  • A continuous payout service for a Chia CAT (“Weso coin”)
  • Watches the backend’s “work completed” records and pays any rewards that are due, then marks them as paid

6) Website

  • Shows progress/status (rates, totals, leaderboards) and helps communicate project activity

The “happy path” end‑to‑end flow

  1. The backend identifies compaction targets (VDF proofs that are still not compact)
  2. Workers (WesoForge clients) request leases (time‑limited batches of jobs)
  3. Each worker computes compact proofs locally using the modified chiavdf
  4. Workers submit results back to the backend
  5. The backend forwards results to the local modified full node, which verifies and applies them to its local chain data
  6. The backend marks jobs as accepted/done, updates rewards/stats, and the payer later issues CAT payouts
  7. In parallel, compactifications are announced to the wider network via the gossip node, so other nodes learn they can fetch those compact proofs too
  8. The website/dashboard shows progress and live metrics