Skip to content

QuantaChain Katenet Release (v3.2.6-alpha)

Choose a tag to compare

View all tags
@XD637 XD637 released this 05 Sep 08:49
· 10 commits to main since this release
v3.2.6-alpha
959e3bb

Quanta Alpha Release Notes

Current Version: v3.2.6-alpha — Strict Isolation + Agent Reputation

This release delivers two changes: a hard network isolation to restore block production, and the first new native contract template since launch — on-chain AI agent reputation.

🔴 Mandatory Upgrade — Protocol v62

This is a mandatory upgrade. Nodes still running v60 or v61 will be immediately rejected and cannot participate in consensus. To rejoin: docker-compose pull && docker-compose up -d.

What's New

Network Strict Isolation (Protocol v62)

  • Bumped PROTOCOL_VERSION to 62 and TESTNET_MAGIC to QT62.
  • Removed all backward compatibility from NetworkMessage::verify() — only QT62 is now accepted.
  • Changed the Version handshake check from a permissive range (v >= 59) to strict equality (v == 62).
  • Why this is needed: The v61 update still allowed v60 nodes to connect via backward compat. Since those v60 nodes carry a BFT peer resolution bug, including them in the consensus set prevents 2/3 quorum from being reached, stalling block production. Dropping them forces a clean, bug-free consensus group.

Agent Reputation Contract (Template 6) — TEMPLATE_AGENT_REPUTATION

A new native contract template that brings a trust layer to the Quanta AI agent economy.

The Problem: Quanta already has AgentJob, AgentBid, and AgentRegistry contracts. But there's no way for a new employer to know whether an agent is trustworthy before hiring them. This new contract solves that.

How It Works:

  1. An agent (or their owner) deploys an AgentReputation contract, linking it to their wallet address.
  2. After a job is completed (AgentJob → status claimed, AgentBid → status selected), the employer calls rate on the agent's reputation contract with:
    • job_contract: the completed job's contract address (on-chain proof of work)
    • score: 1–5 stars
    • review_hash (optional): SHA3 hash of an off-chain review text
  3. The contract enforces:
    • Score range (1–5 only)
    • Job must be completed — cannot rate an open or refunded job
    • Caller must be employer — only the job owner can rate
    • Idempotency — each job contract can only rate once (no double-rating)
  4. Aggregated stats stored on-chain: total_jobs, total_score, avg_score_x100 (e.g. 450 = 4.50★)
  5. Emits AgentRated events, indexed by QuaScan explorer.

New API Endpoint: GET /api/agents/:address/reputation

{
  "agent_address": "0xABC...",
  "contract_address": "0xDEF...",
  "total_jobs": 12,
  "avg_score_x100": 467,
  "avg_stars": "4.67",
  "last_rated_at": 208950,
  "reviews": [
    {
      "height": 208900,
      "employer": "0x123...",
      "job_contract": "0x456...",
      "score": "5",
      "review_hash": "abc123..."
    }
  ]
}

Previous Releases (Summary)

Version Date Summary
v3.2.5-alpha 2026-09-05 BFT peer resolution fix — unicast messages were silently dropped due to missing node_id resolution in handshake handler
v3.2.4-alpha 2026-09-04 Connection tracking fix — libp2p ghost connections leaked on reconnect, causing capacity errors. Protocol bumped to v60
v3.2.3-alpha 2026-09-02 Strict v58 handshake rejection + log noise reduction
v3.2.2-alpha 2026-09-02 Sync & stability — O(1) cumulative work calc, egress spam disabled, peer liveness fix. Protocol bumped to v59
v3.2.0-alpha 2026-09-01 Swarm release — replaced raw TCP with libp2p Gossipsub + Kademlia DHT
v3.1.5-alpha 2026-09-01 State actor refactoring + sync deadlock fix. Protocol bumped to v56

For full history see CHANGELOG.md.

🛠️ How to Run a Validator Node

🟢 STAKING IS OPEN! The network is fully transitioned to DPoS mechanics. Anyone who stakes at least 100,000 QUA can run a validator node, propose blocks, and earn rewards!

To join the network, you need to point your node to the bootstrap VPS. Below are the three ways to run the node, ordered by recommendation.

Option 1: Native Docker Run (Recommended)

This is the easiest and most direct way to run your validator. Just ensure you pass the --bootstrap flag to connect to the network.

1. Pull the Latest Image

docker pull xd637/quanta-node:latest

2. Start the Node

Important

Change "YOUR_PASSWORD_HERE" to your actual wallet password, and ensure validator.qua matches your wallet filename!

docker run -d \
  --name quanta-validator \
  --restart always \
  --network host \
  -v ~/quanta_data_v2:/home/quanta/quanta_data \
  -e QUANTA_WALLET_PASSWORD="YOUR_PASSWORD_HERE" \
  xd637/quanta-node:latest \
  quanta start --validator-wallet /home/quanta/quanta_data/validator.qua --bootstrap node1.quantachain.org:8333

Option 2: Docker Compose

If you prefer managing your containers via Docker Compose, create a docker-compose.yml file with the following configuration:

version: '3.8'
services:
  quanta-node:
    image: xd637/quanta-node:latest
    container_name: quanta_validator
    restart: unless-stopped
    network_mode: "host"
    volumes:
      - ~/quanta_data_v2:/home/quanta/quanta_data
    environment:
      - QUANTA_WALLET_PASSWORD=YOUR_PASSWORD_HERE
    command: >
      quanta start
      --validator-wallet /home/quanta/quanta_data/validator.qua
      --bootstrap node1.quantachain.org:8333

Start the Node:

docker compose up -d

Option 3: Native Source Build

For developers or those who prefer running natively without Docker:

1. Clone and Build

git clone https://github.com/quantachain/quanta.git
cd quanta
cargo build --release

2. Run the Node

./target/release/quanta start -c quanta.toml --validator-wallet ./quanta_data/validator.qua --bootstrap node1.quantachain.org:8333

Option 4: Advanced Configuration (quanta.toml Override)

If you want full control over your node's configuration instead of relying on CLI arguments like --bootstrap, you can provide your own quanta.toml file. This is useful for customizing port bindings, max peers, or API rate limits.

When using Docker, you can mount your local quanta.toml to override the default one baked into the image. Just add a -v flag to your docker run command:

docker run -d \
  --name quanta-validator \
  --restart always \
  --network host \
  -v ~/quanta_data_v2:/home/quanta/quanta_data \
  -v ~/my-local-quanta.toml:/home/quanta/quanta.toml \
  -e QUANTA_WALLET_PASSWORD="YOUR_PASSWORD_HERE" \
  xd637/quanta-node:latest \
  quanta start --validator-wallet /home/quanta/quanta_data/validator.qua

This completely overrides the baked configuration with your own file.

Staking & Delegation

Minimum stake to become a validator: 100,000 QUA. Your wallet's Falcon-512 public key is automatically used for BFT signing.

Become a Validator (Stake)

# Register as a BFT validator by staking QUA
quanta-wallet stake \
  --wallet /home/quanta/quanta_data/validator.qua \
  --amount 100000 \
  --fee 0.01 \
  --node http://localhost:3000

Stop Validating (Unstake)

# Deregister and begin the 2-epoch unbonding period
quanta-wallet unstake \
  --wallet /home/quanta/quanta_data/validator.qua \
  --fee 0.01 \
  --node http://localhost:3000

Delegate to a Validator (Non-validators)

Don't want to run a node? Delegate your QUA to an active validator and earn a share of rewards.

# Delegate QUA to an existing validator
quanta-wallet delegate \
  --wallet /home/quanta/quanta_data/my_wallet.qua \
  --validator 0x0217a3fcbadd38e31761f9f949954e9f2ac2503d \
  --amount 10000 \
  --fee 0.01 \
  --node http://localhost:3000

# Undelegate (locks for unbonding period before becoming spendable)
quanta-wallet undelegate \
  --wallet /home/quanta/quanta_data/my_wallet.qua \
  --validator 0x0217a3fcbadd38e31761f9f949954e9f2ac2503d \
  --fee 0.01 \
  --node http://localhost:3000

License

QUANTACHAIN operates under an Open-Core Dual License model:

For commercial licensing: contact@quantachain.org

Assets 2
Loading