Lee Duong

[Lee Duong @Leduongthi]

@CNPYNetwork A block doesn't just finalize what was included. It also changes the conditions under which the next transactions will be evaluated.

[Lee Duong @Leduongthi]

A block can change the fate of transactions that weren't even included in it.

After a block is committed, @CNPYNetwork removes the transactions included in that block from the mempool.

But it doesn't simply leave everything else untouched.

[Lee Duong @Leduongthi]

@CNPYNetwork What I find interesting is that the mempool isn't just a waiting room. It has to keep adapting as the blockchain state moves forward.

[Lee Duong @Leduongthi]

@BeldexCoin Ring signatures solve one specific part of transaction privacy: hiding which participant is the actual signer.

Not the receiver, not the transaction amount, and not the network metadata. Those are different privacy problems that require different mechanisms.

[Lee Duong @Leduongthi]

What if a transaction could prove that someone in a group signed it without revealing who?

That's the basic idea behind a ring signature.

Instead of attaching the signature to one identifiable public key, the real signer is placed in a group with other public keys. @BeldexCoin

[Lee Duong @Leduongthi]

@BeldexCoin The important part is that the transaction can still be verified. Privacy here doesn't mean giving up verification. It changes what the transaction reveals about the person who authorized it.

[Lee Duong @Leduongthi]

@BeldexCoin Ring signatures solve one specific part of transaction privacy: hiding which participant is the actual signer.

Not the receiver, not the transaction amount, and not the network metadata. Those are different privacy problems that require different mechanisms.

[Lee Duong @Leduongthi]

What if a transaction could prove that someone in a group signed it without revealing who?

That's the basic idea behind a ring signature.

Instead of attaching the signature to one identifiable public key, the real signer is placed in a group with other public keys. @BeldexCoin

[Lee Duong @Leduongthi]

@BeldexCoin That's what creates signer ambiguity.

The important part is that the transaction can still be verified. Privacy here doesn't mean giving up verification. It changes what the transaction reveals about the person who authorized it.

[Lee Duong @Leduongthi]

@CNPYNetwork What I find interesting is this simple idea: moving to a new round doesn't mean starting over. The strongest evidence from earlier rounds can still shape what happens next.

[Lee Duong @Leduongthi]

@CNPYNetwork 's consensus doesn't simply forget what happened when a new round begins.

HighQC is the highest PRECOMMIT quorum certificate a node knows for the current height.

[Lee Duong @Leduongthi]

@CNPYNetwork That matters because a round change shouldn't erase the safety state established by previous rounds.

HighQC isn't finality, and it isn't the mechanism that chooses the leader. It is evidence that helps the next proposal respect what consensus has already established

[Lee Duong @Leduongthi]

@CNPYNetwork What I find interesting is that Canopy isn't replacing stake with computation. It uses computation to add something stake alone doesn't provide: a verifiable signal of elapsed time.

[Lee Duong @Leduongthi]

How can a blockchain prove that time actually passed?

Proof of Stake can give the network economic weight through validator stake, but in @CNPYNetwork 's design, stake alone does not provide a cryptographic signal of elapsed time.

This is where VDFs come into NestBFT.

[Lee Duong @Leduongthi]

@CNPYNetwork That's the idea behind Canopy's Proof of Age: adding a verifiable time dimension to Proof of Stake.