power_house

power_house is a Rust verification stack for deterministic sum-check proofs, portable proof provenance, commitment-bound sparse workloads, transcript anchoring, and optional quorum networking.

Power House Archive (.pha) and Rootprint are the primary provenance workflow. A .pha file binds core proof data and provenance to a deterministic phx_fingerprint. Rootprint adds verifiable navigation, forks, merges, and equivalence over those core identities.

External proof attachments are optional transport data. They never affect a Power House fingerprint, Rootprint branch ID, core verification, or branch equivalence.

Power House + Rootprint

use power_house::{prove_with_rootprint, provenance::PhaArtifact};
use serde_json::json;

let artifact = PhaArtifact::new(
    json!({"producer": "example"}),
    "power-house/example/v1",
    json!({"claim": 7}),
    json!({"accepted": true}),
)?;
let graph = prove_with_rootprint!(label: "main", artifact: artifact)?;
graph.verify()?;
# Ok::<(), Box<dyn std::error::Error>>(())

The julian rootprint workflow navigates, forks, merges, compares, and verifies portable graphs. julian attach-external-proof is deliberately separate from the core engine.

Verified Scale

The repository contains four reproducible proof modes:

Mode	Public domain	Verifier work	Command
Constant polynomial	`2^70` points	`O(70)`	`cargo run --release --example sextillion_verify`
Seeded affine polynomial	`2^4096` points	`O(4096)`	`cargo run --release --example hyperscale_affine`
Seeded sparse polynomial	`2^1,000,000` points	`O(n + I log n)`	`cargo run --release --example sparse_record`
External committed sparse polynomial	`2^1,000,000` points	`O(n + I log n)`	`cargo run --release --example committed_workload`

Here n is the number of variables and I is the number of nonzero variable incidences. None of these modes allocates the expanded Boolean hypercube.

The external workflow stores the polynomial and proof separately:

PHSMv1: canonical sparse polynomial
PHCPv1: proof containing a domain-separated BLAKE2b-256 commitment

Verification requires both files and rejects workload substitution.

Install

cargo add power_house
cargo install power_house --features net

Reproduce

cargo test --all-targets
cargo test --all-targets --features net

cargo run --release --example sextillion_verify
cargo run --release --example hyperscale_affine
cargo run --release --example sparse_record
cargo run --release --example committed_workload
cargo run --example rootprint_workflow
cargo run --example pha_conformance_vectors

python3 scripts/verify_sparse_certificate.py \
  target/power_house_sparse_record.phsp

python3 scripts/verify_sparse_certificate.py \
  target/external_interaction_model.phcp \
  --polynomial target/external_interaction_model.phsm

python3 scripts/test_sparse_verifier.py
python3 scripts/soundness_budget.py
PYTHONPATH=sdk/python python3 -m unittest discover -s sdk/python/tests -v

The full procedure, formats, expected outputs, and failure tests are in Verification Guide.

Small canonical files in conformance/v1 are checked by both languages. Every single-byte XOR mutation of each vector must reject.

Library

use power_house::{Field, GeneralSumProof};

let field = Field::new(1_000_000_007);
let proof = GeneralSumProof::prove_seeded_affine(
    4096,
    &field,
    b"public reproducible workload",
);

assert!(proof.verify_seeded_affine(
    &field,
    b"public reproducible workload",
));

Primary APIs:

GeneralSumProof: dense, streaming, constant, and seeded-affine sum-check
SeededSparseProof: stable PHSPv1 seeded sparse certificates
CommittedSparsePolynomial: canonical external sparse workloads
CommittedSparseProof: stable PHCPv1 commitment-bound certificates
PhaArtifact: portable core proof and provenance identity
Rootprint: deterministic proof-history branching and equivalence
prove_with_rootprint!: recommended provenance-aware construction interface
ProofLedger: transcript logs, anchors, and quorum reconciliation

Network

The net feature enables the julian CLI, libp2p transport, signed envelopes, data availability endpoints, governance policies, stake accounting, and token migration commands.

julian keygen ed25519://<seed> --out ./keys/node.identity

julian net start \
  --node-id <node_id> \
  --log-dir ./logs/<node_id> \
  --listen /ip4/0.0.0.0/tcp/0 \
  --bootstrap /dns4/mfenx.com/tcp/7002/p2p/<PEER_ID> \
  --quorum 2 \
  --key ed25519://<seed>

The native wallet lane accepts signed EIP-1559 transfers and exposes only quorum-finalized blocks, balances, nonces, transactions, and receipts:

julian net start \
  --node-id <node_id> \
  --log-dir ./logs/<node_id> \
  --blob-dir ./data/<node_id> \
  --listen /ip4/0.0.0.0/tcp/7001 \
  --policy ./config/native-validators.json \
  --quorum 2 \
  --evm-chain-id 177155 \
  --evm-rpc-listen 127.0.0.1:8545 \
  --key ed25519://<seed>

Run scripts/test_native_rpc_cluster.sh to verify three independent replicas produce the same finalized block hash, state root, balances, and receipt. Use scripts/generate_rpc_cluster.py to create a sealed quorum-2 production bundle for three validators. The production runbook provisions the validators and global HTTPS edge on DigitalOcean.

Operations and migration procedures are documented in Operations and Mainnet Launch.

Documentation

License

MIT OR BSD-2-Clause.

power_house 0.3.0