[ANN] CypherMint — Python SHA-256D UTXO Chain | ASERT | 21M Cap | No Premine |

[CYpherMInt]

CypherMint Mainnet V3 is scheduled for public launch on August 5, 2026 at 12:00 EDT / 16:00 UTC.

CypherMint is a new open-source proof-of-work blockchain written entirely in Python. It uses a SHA-256D UTXO model, a ten-minute block target and integer-only ASERT difficulty adjustment.

A major focus during development has been basic network reliability. CypherMint nodes support automatic bootstrap-peer discovery, synchronization from genesis, chainwork verification and failover between reachable peers. These behaviors have been tested across Windows, Debian Linux and three independent public nodes.

Mainnet V3 features:

• SHA-256D proof of work
• UTXO transaction model
• ASERT difficulty adjustment
• 21 million mineable coin limit
• No premine or private launch mining
• Automatic peer discovery
• New-node block synchronization
• Public block, transaction and address explorer
• Python CPU miner included
• One public cyphermint.py entry point

Each mined block distributes 97% to the miner, 1% to the pool operator and 2% to the permanent development address.

The public nodes are currently held at the official genesis block. The source code (GITHUB), release archive and mining instructions will be published simultaneously at launch so everyone begins with the same public software.

Explorer, countdown and whitepaper:
https://cyphermint.org

Whitepaper:
https://cyphermint.org/whitepaper

Official Instagram:
https://www.instagram.com/satoshicypher/

Official Reddit:
https://www.reddit.com/user/curioscrypto/

CypherMint is experimental open-source software. Participation is at the user’s own risk, and no value, profitability, security or continued development is guaranteed.

[CYpherMInt]

Wallet ownership and automatic mining rewards tested


CypherMint mining rewards are distributed automatically at the protocol level when a valid block is accepted. The miner does not need to log into an account, request a withdrawal or manually claim the reward. Part of what I saw when I started this was some new coins would require the release of the reward to the miner, no automation. but what happens if the person who decides when to release them, just doesn't? Lost work ...?

The resulting UTXOs belong to the addresses specified by the miner. Spending authority remains exclusively with the holder of the corresponding private key. Public balance/address lookup does not provide spending authority.

Coinbase maturity is enforced before newly mined rewards become spendable.

This has been tested alongside:

mining and reward creation
wallet signing and spending
coinbase maturity enforcement
public address balance lookup
transaction propagation and mining
peer discovery and synchronization
node failover
multi-node chain agreement

The public Mainnet V3 chain remains at genesis until the August 5 launch.

Explorer and whitepaper: https://cyphermint.org

[CYpherMInt]

Consensus testing update — competing blocks and chain selection

Another part of CypherMint Mainnet V3 consensus testing has focused on how nodes resolve competing valid branches.

If two miners produce valid blocks at approximately the same height, nodes can temporarily see different chain tips.

CypherMint does not rely on a bootstrap server, explorer or administrator to resolve this. Each node independently validates the competing branches and follows the valid chain with the greatest accumulated proof of work.

Once one branch gains additional chainwork, nodes converge onto that chain and the competing block becomes stale.

This is important because the same consensus logic applies regardless of which peer originally supplied a block.

It has been tested alongside peer synchronization, chainwork verification, peer failover and multi-node agreement.

Mainnet V3 remains at genesis until the public launch on August 5, 2026.

Explorer and whitepaper:
https://cyphermint.orgFresh-node synchronization tested

Another CypherMint Mainnet V3 networking test has focused on joining the network from a clean node.

A new node begins from the known genesis block, discovers reachable bootstrap peers and requests the blocks required to reach the current chain tip.

Those blocks are not blindly trusted. The receiving node independently validates the chain, including proof of work, transaction rules, difficulty and accumulated chainwork.

We have tested nodes joining from genesis, synchronizing to the existing tip and continuing through an alternate peer when another peer becomes unavailable.

The bootstrap infrastructure therefore provides an initial path into the network rather than consensus authority.

Mainnet V3 remains at genesis until the public launch on August 5, 2026. Less than 1 week!!

Explorer and whitepaper:
https://cyphermint.org

[CYpherMInt]

Peer-failure and bootstrap failover tested

CypherMint Mainnet V3 does not rely on a single bootstrap node.

A new node has multiple public entry points. If one bootstrap node is unavailable, it can attempt to connect through another. Nodes already participating in the network can continue communicating and synchronizing through their remaining reachable peers.

Bootstrap nodes provide initial peer discovery only. They do not determine consensus, approve blocks or select the valid chain. Each node continues to validate proof of work, transactions, difficulty and accumulated chainwork independently.

This behaviour has been tested by taking a node offline and confirming that other nodes continued operating and synchronizing through alternate peers.

Mainnet V3 remains at genesis until the public launch on August 5, 2026.

Explorer and whitepaper:
https://cyphermint.org

[CYpherMInt]

Updated - all testing completed

Live on August 5, 2026 at noon EST/16:00UTC!!

[CYpherMInt]

All links - tested

github for the download

https://github.com/BXBOOT/Cyphermint-V3

Explorer

cyphermint.org

[chn520]

reject too high

[CYpherMInt]

Stop and restart your miner.
Interesting that this happened, but everyday is a learning day.
I will look into it more.

[CYpherMInt]

reject too high

Looks like all the responses are working as they should. the notify to miners is sent as soon as a block is mined
and at that time blocks were fast and furious, perhaps what we could call a hash storm.
Without any changes, when the hash storm died down, the number of rejected shares fell.
While the system builds difficulty there may be bumps that rejections increase if large hash rates join the mining.
As the blocks move closer tot he 10minute target difficulty, the reject should get lower.
From launch, the difficulty is almost 300 times more difficult so eventually it will catch up.

[CYpherMInt]

The Chain has passed a real world milestone.
Live for just over a week. The network has had a large uptick in difficulty due to a bit of
a hash storm near the beginning. ASERT worked as it should to adjust the difficulty up, and as the has power directed at the network slowed,
ASERT once again corrected toward the goal of the 10 minute mark. There were no crashes during this time.

[saamxx]

Looks like explorer has stopped working.
Or maybe there's a fork?

[CYpherMInt]

The explorer is currently online. There was a brief moment where I restarted it
after I changed the banner to reflect the time it has been live versus the run up to launch.
Due to the hash storm near the start, the difficulty level shot up very quickly but has
returned to a more manageable level. ASERT does not do a dramatic changes up or down but rather a gradual
up and down change to get closer to the 10 minute target. I have aimed 1 slower miner at the chain
to keep an eye on the difficulty adjustments and to ensure the explorer is reporting correctly also.