Another milestone completed for Chipcoin's Post-Quantum integration.

Today we verified that the consensus activation gate for CHCQ (Post-Quantum) addresses behaves exactly as intended.

To test it, we used a funded legacy wallet and attempted to send coins to a CHCQ address before the scheduled activation height.

The node correctly rejected the transaction with:

>

This confirms that:

• Legacy wallets continue to operate normally.
• The network already recognizes CHCQ addresses.
• Consensus prevents the creation of Post-Quantum outputs until activation at testnet height 30000.

This is an important distinction: the feature is already implemented in the protocol, but it cannot be used prematurely because activation is enforced by consensus rules rather than by wallet software.

The next milestone will be reaching height 30000, creating the first on-chain CHCQ outputs, and then verifying transactions from a Post-Quantum wallet back to legacy addresses.

We're taking a conservative approach: implement, test thoroughly, activate only when the network is ready.

Feedback and technical questions are always welcome.

Another milestone completed for Chipcoin's Post-Quantum integration.

Today we verified that the consensus activation gate for CHCQ (Post-Quantum) addresses behaves exactly as intended.

To test it, we used a funded legacy wallet and attempted to send coins to a CHCQ address before the scheduled activation height.

The node correctly rejected the transaction with:

>

This confirms that:

• Legacy wallets continue to operate normally.
• The network already recognizes CHCQ addresses.
• Consensus prevents the creation of Post-Quantum outputs until activation at testnet height 30000.

This is an important distinction: the feature is already implemented in the protocol, but it cannot be used prematurely because activation is enforced by consensus rules rather than by wallet software.

The next milestone will be reaching height 30000, creating the first on-chain CHCQ outputs, and then verifying transactions from a Post-Quantum wallet back to legacy addresses.

We're taking a conservative approach: implement, test thoroughly, activate only when the network is ready.

Feedback and technical questions are always welcome.

Another milestone completed for Chipcoin's Post-Quantum integration.

Today we verified that the consensus activation gate for CHCQ (Post-Quantum) addresses behaves exactly as intended.

To test it, we used a funded legacy wallet and attempted to send coins to a CHCQ address before the scheduled activation height.

The node correctly rejected the transaction with:

>

This confirms that:

• Legacy wallets continue to operate normally.
• The network already recognizes CHCQ addresses.
• Consensus prevents the creation of Post-Quantum outputs until activation at testnet height 30000.

This is an important distinction: the feature is already implemented in the protocol, but it cannot be used prematurely because activation is enforced by consensus rules rather than by wallet software.

The next milestone will be reaching height 30000, creating the first on-chain CHCQ outputs, and then verifying transactions from a Post-Quantum wallet back to legacy addresses.

We're taking a conservative approach: implement, test thoroughly, activate only when the network is ready.

Feedback and technical questions are always welcome.

Most Proof-of-Work networks reward only one thing: whoever finds the next block.

But the network depends on much more than miners.

It needs:

• reliable full nodes
• publicly reachable peers
• network propagation
• validation
• long-term operators willing to stay online

Chipcoin is experimenting with a different approach.

Alongside traditional PoW mining, the protocol introduces reward nodes: independently operated full nodes that contribute to the health and resilience of the network and receive protocol-level rewards for doing so.

This isn't delegated staking.
It isn't masternodes.
It isn't Proof-of-Stake.

Mining still secures the blockchain.

The goal is simply to recognize that infrastructure has value too.

Current testnet snapshot:

• 37 unique miners in the last 100 blocks
• Largest miner: 6%
• 19 operational peers
• 54 registered reward nodes
• Ongoing public testnet with continuous consensus and networking improvements

We're still testing, breaking things, fixing them and collecting feedback before mainnet.

The question we're trying to answer is simple:

Can a PoW blockchain sustainably incentivize both security and infrastructure without sacrificing decentralization?

I'd be interested to hear what Bitcoin and PoW developers think about this design. Constructive criticism is welcome.

Over the last days we've completed a significant round of security and operational hardening across the Chipcoin testnet.

The goal is not only functionality, but also resilience against abuse and better observability.

Completed improvements

P2P

• Oversized frame protection
• Early payload rejection
• 8 MB frame cap to mitigate memory DoS vectors

Wallet

• Private keys are no longer printed unnecessarily
• More restrictive wallet file permissions

Special transactions

• Domain separation by network
• Protection against cross-network replay
• Safer node registration and reward-node operations

Snapshot bootstrap

• Local bootstrap locks
• Retry backoff
• Duplicate snapshot avoidance
• More conservative trust defaults

Reward epoch seed

• Multi-block seed generation
• Reduced influence from a single epoch-closing miner

Reward attestations

• Better aggregation
• Additional diagnostics
• Reduced mempool pressure

Mempool

• Early rejection of clearly non-standard transactions
• Lower validation cost under spam conditions

Peer behavior

• Better penalties for repeated protocol violations
• Richer logs with more operational context

HTTP API

• Body size limits
• Raw payload caps
• Pagination for diagnostic endpoints

Current status

Most issues identified during the initial security review are now fixed or significantly hardened on the current testnet code path.

Still planned before mainnet

• Snapshot trust enforcement with pinned signer keys.
• Mandatory special transaction v2 from genesis.
• Evaluation of commit-reveal for epoch randomness.
• Deeper runtime, sync and mempool audits under hostile conditions.

The philosophy is simple:

Build. Test. Harden.

The objective is to anticipate spam, DoS, replay attacks, retry loops and operational mistakes before mainnet rather than after.

Over the past weeks we've completed several important security and infrastructure improvements on the Chipcoin testnet.

Recent work includes:

• Special node transaction signature v2 with network domain separation
• Snapshot trust hardening
• P2P frame size limits
• Wallet private key permission improvements
• Snapshot bootstrap recovery protections
• Reward attestation aggregation and diagnostics improvements

The network has also become significantly more stable during testing. We are consistently observing dozens of active nodes, reward node participation remains healthy, and the network has been operating without the persistent fork issues often seen in early-stage experimental networks.

Chipcoin remains an open-source Bitcoin-inspired proof-of-work project currently focused on testing, validation, network incentives, and node reward mechanisms.

If you're already running a node, consider updating to the latest version:

git pull

Feedback, testing, bug reports, and independent node operators are always welcome.

Current height: 8983

Over the last 24 hours the network observed 76 active nodes, with 516 unique active nodes seen during the last 7 days.

The reward node system currently shows:

• 50 registered reward nodes
• 41 successfully attested and passed
• 13 public peers online at the time of the report
• 18 active peer sessions

Mining also remains broadly distributed. Looking at the most recent 100-block window, the largest miner accounted for only 9% of blocks, with many other miners contributing smaller shares.

The goal of this testnet remains the same: evaluate whether protocol-level incentives can increase participation in public full-node infrastructure while preserving decentralization and avoiding excessive concentration.

Feedback and criticism remain welcome. The entire purpose of the testnet is to learn what works and what doesn't.

• 34 operational peers
• 24 public nodes
• 0 banned peers
• network fully synced

One statistic stands out: in the last 100 blocks, the largest miner accounted for only 4% of block production.

For a small proof-of-work testnet, this is exactly what we want to see: broad participation, no dominant miner, and a healthy distribution of activity across the network.

A few weeks ago we were focused on synchronization, snapshot bootstrapping and network stability. Today the network is running steadily above 30 peers with no visible forks or major operational issues.

Still early, but the trend is encouraging.

What is the strongest argument against incentivizing public full nodes?

Not miners.

Not Lightning routing.

Specifically public nodes that provide network connectivity to other participants.

I'm interested in the trade-offs, not slogans.

What stands out isn't who won.

It's the distribution.

Instead of rewards concentrating around a single operator, the latest epoch produced 15 different winners, all with confirmed payouts and nearly identical rewards.

For a project exploring protocol-level incentives for public nodes, this is an encouraging result. The objective is not to create a few large operators, but to encourage broad participation across the network.

Thank you to everyone running nodes, testing the software, reporting issues, and helping strengthen the testnet.

The network continues to operate with more than 30 active peers and no major synchronization issues.

On to the next epoch.

A short update on the Chipcoin public testnet.

Over the last few weeks we've received a lot of useful criticism regarding node incentives, Sybil resistance and network design.

At the same time we've been working through several real-world operational issues discovered by external testers.

Most recently, a community member identified a bug that could cause miners to construct blocks that would later be rejected by validation under specific mempool conditions. The issue was analyzed, patched and deployed.

Current status:

• 20+ nodes online
• Stable block production
• Public explorer operational
• Browser wallet operational
• Multiple independent hosts participating
• Recent CPU and efficiency optimizations merged
• No persistent fork events observed

What I'm finding interesting is that many of the hardest problems are no longer protocol ideas on paper.

They're operational problems that only appear once real nodes, real users and real traffic start interacting with the network.

For those who have worked on distributed systems, what surprised you most once your software left the lab and started operating in the wild?

A few weeks ago I posted about an experiment exploring incentives for independent node operators in a Bitcoin-inspired PoW blockchain.

Quick update from the public testnet:

• 22 nodes currently online
• Public explorer operational
• Browser wallet live
• External testers running nodes
• First external bug reports submitted through GitHub
• Multiple protocol discussions around incentives, Sybil resistance and verification

One of the most valuable outcomes so far hasn't been adoption.

It's criticism.

A community member recently identified a bug that could cause miners to build blocks that their own validators would reject under certain mempool conditions. The issue was analyzed, patched and deployed.

The experience reinforced something I've learned repeatedly over the last few weeks:

Building software is one challenge.

Building systems that behave correctly under adversarial incentives is another.

Many of the discussions here have gradually shifted my thinking away from "How do we reward nodes?" toward broader questions about verification, public goods, Sybil resistance and measurable contribution.

For those working on protocol design, what has been the most surprising lesson you've learned once real users started interacting with your system?

After a few weeks discussing node incentives with developers and protocol researchers, I'm starting to think the problem may be deeper than incentives themselves.

Independent verification benefits the network as a whole.

Everyone benefits from having participants who independently verify the rules, validate the state, and reject invalid behavior.

But the value created by that verification is diffuse.

The verifier bears the cost.
The network receives the benefit.

That sounds a lot like a public good problem.

Some people argue Bitcoin already solved this through self-interest:

If you care about verifying your own transactions, that's enough incentive to run a node.

Others argue that if independent verification is truly important, relying entirely on altruism and sovereignty seems fragile.

The difficulty is that attempts to introduce rewards appear to create new problems:

• Sybil attacks
• Incentive gaming
• Oracle dependencies
• Centralization pressures

So I'm curious how people think about this.

Is independent verification fundamentally a public good?

Or is the self-sovereignty incentive already sufficient?

Over the last week I've been discussing node incentives with developers, protocol researchers and infrastructure operators.

A pattern has started to emerge.

Almost nobody seems convinced that rewarding nodes directly is a good idea.

The usual objections are familiar:

• Sybil attacks
• Incentive gaming
• Identity vs decentralization tradeoffs
• Difficulty of measuring meaningful contribution

What's interesting is that many successful examples of blockchain incentives appear to reward services rather than nodes:

• Filecoin rewards storage
• Lightning routing earns fees for routing
• Infrastructure providers monetize APIs, liquidity or bandwidth
• Application networks reward service consumption

That has me wondering whether the question itself is wrong.

Maybe the goal shouldn't be:

"How do we reward full nodes?"

Maybe the better question is:

"How do we reward useful infrastructure?"

Curious whether people think these are fundamentally different problems, or simply different ways of describing the same thing.

I've been building a small Bitcoin-inspired PoW blockchain called Chipcoin, and the main thing I'm trying to understand isn't mining—it's node incentives.

Bitcoin has a clear mechanism for rewarding miners. Full nodes, meanwhile, are generally operated because their owners value independent verification.

The challenge is obvious:

If you try to reward node operators directly, how do you prevent someone from spinning up hundreds of VPS instances and collecting rewards without providing meaningful value to the network?

Some of the questions I'm currently wrestling with:

• What contribution from a full node can actually be verified by the protocol?
• Is uptime enough? (Probably not.)
• Can useful network services be measured in a decentralized way?
• How do you avoid turning node rewards into a Sybil farm?
• How do you prevent reputation systems from becoming centralized?

I'm genuinely interested in existing research, papers, projects, or failed experiments that have attempted to solve this problem.

Has anyone seen a design that gets close?