CryptEX v0.6.3

CryptEX v0.6.3 Release Notes

Public contact: [email protected]

These notes describe the CryptEX v0.6.3 maintenance release as of April 2026. This release focuses on unifying the GUI and CLI mining paths so they operate on one backend chain state, while carrying forward the recent chain-repair, activation, and external-worker hardening work.

Highlights

• Unified the GUI miner and CLI miner around the live backend RPC session instead of maintaining a separate gui-miner blockchain state
• Added RPC-backed mining to cryptexd mine, using getblocktemplate plus submitblock as the single mining control path
• Removed the GUI mined-block replay glue that existed only because of the old split datadir model
• Kept the external SHA3-512 PoW worker architecture intact, including the dedicated ARM64 and x86_64 handwritten assembly workers
• Carried forward the recent fixes for chain repair, activation-path integrity, stale-template rejection diagnostics, and bundled daemon/worker sync

Unified Mining

• cryptexd mine now supports:
  • --rpc-url
  • --rpcuser
  • --rpcpassword
  • --rpcallowselfsigned
  • --rpccacert
• In RPC-backed mining mode, the miner no longer opens its own Blockchain instance
• The miner now fetches candidate blocks from the running backend with getblocktemplate
• Found blocks are submitted back through submitblock on the same backend that the GUI wallet and dashboard are already using
• The GUI mining page now launches this RPC-backed path by default, using the active backend RPC settings from the desktop client

Desktop Behavior Changes

• The GUI miner no longer defaults to a dedicated gui-miner subdirectory for blockchain state
• The GUI no longer parses MinedBlockHex from miner stdout and resubmits it itself
• The old pending mined-block reconciliation flow was removed from the GUI refresh cycle
• Mining status text and hints in the GUI were updated to reflect the new single-backend model

Chain Integrity and Acceptance

• Preserved the recent active-chain repair behavior for stale and broken local tails
• Preserved the safer activation-path handling so valid candidates are resolved before live active state is mutated
• Preserved the hardened tip-candidate diagnostics used when a PoW worker result is rejected after validation
• Preserved the macOS bundle refresh behavior so the Qt app launches the same daemon and worker binaries that were just rebuilt

PoW Worker Notes

• ARM64 macOS and Linux builds continue to use dedicated handwritten assembly workers
• Linux x86_64 and Windows x86_64 continue to ship dedicated handwritten assembly workers with AVX2-focused nonce search
• Consensus still remains entirely in the daemon; workers only search nonce ranges and return candidate results

Packaging and Release Infrastructure

• Updated release metadata to v0.6.3 across the desktop app, docs, and packaging helpers
• Rebuilt the release assets from the current source tree before tagging
• Regenerated staged release artifacts and SHA-256 checksums for the GitHub release payload

Upgrade Guidance

• Replace older app bundles with the v0.6.3 binaries before starting the GUI miner
• Existing legacy gui-miner folders from older runs are not auto-deleted, but new GUI mining sessions no longer rely on them
• If you previously depended on standalone local-chain mining behavior, switch to backend-RPC mining so wallet, dashboard, node state, and mining all stay aligned

CryptEX v0.6.2

CryptEX v0.6.2 Release Notes

Public contact: [email protected]

These notes describe the CryptEX v0.6.2 maintenance release as of April 2026. This release focuses on consensus hardening, miner/backend correctness, chain repair, and desktop startup stability after the broader v0.6.0 feature wave.

Highlights

• Hardened compact-target handling with canonical bits validation, overflow/sign-bit checks, and documented SHA3-512 target rules
• Reduced difficulty oscillation by preventing emergency min-difficulty rescue blocks from poisoning later LWMA/EMA retarget history
• Repaired invalid active-chain tails automatically on startup for both bits and missing-block failures
• Tightened mining acceptance so PoW success is separated cleanly from consensus acceptance and stale replay blocks do not loop forever in the GUI
• Added dedicated handwritten x86_64 external assembly PoW workers for Linux and Windows with AVX2-focused four-lane nonce search
• Improved desktop/backend startup behavior when ports are busy, checkpoints are stale, or RPC comes up before peer approval does

Consensus and Difficulty

• Added compact-target round-trip validation (bits -> target -> bits) and canonical encoding enforcement at consensus boundaries
• Rejected malformed compact targets with sign-bit misuse, zero targets, or 512-bit overflow conditions
• Documented proof-of-work header serialization, target expansion, and comparison rules in docs/pow.md
• Adjusted the hybrid difficulty controller so emergency low-difficulty rescue blocks do not destabilize follow-on retargets
• Restored post-recovery difficulty from the last stable non-emergency target rather than letting rescue blocks drag the network back toward pow_limit

Chain Repair and Datadir Recovery

• Added automatic repair for stale checkpoints that pinned chains beyond the real valid tip
• Broadened startup repair so invalid active tails caused by missing canonical blocks are truncated back to the last valid prefix
• Pruned stale canonical height files after repair so broken tails do not silently reappear
• Cleaned up rejected contextual candidates from hash-addressed storage instead of leaving them behind in by-hash caches

Mining and Backend

• Confirmed the ARM64 assembly PoW worker against the C++ reference path and fixed the only mismatch found: bounded no-hit iteration accounting
• Added self-contained dedicated x86_64 .S worker sources for Linux and Windows instead of the earlier mixed include/C++ fallback path
• Validated the Linux x86_64 worker against SHA3-512 reference jobs across randomized worker-protocol cases
• Ensured the GUI bundle is refreshed with the current daemon and PoW worker during release builds so the app does not launch stale binaries
• Prevented replayed stale mined blocks from being retried indefinitely after the backend rejects them
• Exempted localhost RPC traffic from generic rate limiting so local mined-block reconciliation does not self-throttle
• Completed the external PoW worker protocol on non-ARM platforms so Linux x86_64 and Windows x86_64 builds ship dedicated worker binaries that the daemon can launch directly

Desktop and Wallet Behavior

• Reworked startup bootstrap handling so backend launch failures surface as failures instead of endless “starting” loops
• Improved bind-conflict handling so the GUI stops retrying aggressively when another process already owns the RPC or P2P port
• Preserved the distinction between “locally caught up” and approval-gated wallet state more consistently during recovery scenarios
• Improved mining and backend log clarity around rejected candidates and repair reasons

Packaging and Release Infrastructure

• Updated release metadata to v0.6.2 across the desktop app, docs, and packaging helpers
• Refreshed macOS ARM64 release assets from the current source tree
• Added Linux x86_64, Linux ARM64, and Windows x86_64 release artifacts to the build matrix
• Added a reproducible Windows x86_64 dependency bootstrap path for the MinGW OpenSSL and Opus prefixes used by the release build

Known Notes

• Public IP autodetect may still emit warning noise on networks where the HTTPS lookup endpoints are blocked or truncated
• Wallet balances remain approval-gated when the node has not established enough confidence in chain state; this release improves recovery behavior but does not remove the approval model

Upgrade Guidance

• Replace older app bundles with the v0.6.2 binaries before starting the GUI miner
• If you previously mined on a stale or partially corrupted local chain, allow the backend to complete its startup repair once before judging final chain height
• If a very old mined-block backlog exists, v0.6.2 will reconcile and discard stale rejected entries instead of replaying them forever

CryptEX v0.6.1

CryptEX v0.6.1 Release Notes

Public contact: [email protected]

These notes describe the CryptEX v0.6.1 maintenance release as of April 2026. This release focuses on consensus hardening, miner/backend correctness, chain repair, and desktop startup stability after the broader v0.6.0 feature wave.

Highlights

• Hardened compact-target handling with canonical bits validation, overflow/sign-bit checks, and documented SHA3-512 target rules
• Reduced difficulty oscillation by preventing emergency min-difficulty rescue blocks from poisoning later LWMA/EMA retarget history
• Repaired invalid active-chain tails automatically on startup for both bits and missing-block failures
• Tightened mining acceptance so PoW success is separated cleanly from consensus acceptance and stale replay blocks do not loop forever in the GUI
• Improved desktop/backend startup behavior when ports are busy, checkpoints are stale, or RPC comes up before peer approval does

Consensus and Difficulty

• Added compact-target round-trip validation (bits -> target -> bits) and canonical encoding enforcement at consensus boundaries
• Rejected malformed compact targets with sign-bit misuse, zero targets, or 512-bit overflow conditions
• Documented proof-of-work header serialization, target expansion, and comparison rules in docs/pow.md
• Adjusted the hybrid difficulty controller so emergency low-difficulty rescue blocks do not destabilize follow-on retargets
• Restored post-recovery difficulty from the last stable non-emergency target rather than letting rescue blocks drag the network back toward pow_limit

Chain Repair and Datadir Recovery

• Added automatic repair for stale checkpoints that pinned chains beyond the real valid tip
• Broadened startup repair so invalid active tails caused by missing canonical blocks are truncated back to the last valid prefix
• Pruned stale canonical height files after repair so broken tails do not silently reappear
• Cleaned up rejected contextual candidates from hash-addressed storage instead of leaving them behind in by-hash caches

Mining and Backend

• Confirmed the ARM64 assembly PoW worker against the C++ reference path and fixed the only mismatch found: bounded no-hit iteration accounting
• Ensured the GUI bundle is refreshed with the current daemon and assembly worker during release builds so the app does not launch stale binaries
• Prevented replayed stale mined blocks from being retried indefinitely after the backend rejects them
• Exempted localhost RPC traffic from generic rate limiting so local mined-block reconciliation does not self-throttle

Desktop and Wallet Behavior

• Reworked startup bootstrap handling so backend launch failures surface as failures instead of endless “starting” loops
• Improved bind-conflict handling so the GUI stops retrying aggressively when another process already owns the RPC or P2P port
• Preserved the distinction between “locally caught up” and approval-gated wallet state more consistently during recovery scenarios
• Improved mining and backend log clarity around rejected candidates and repair reasons

Packaging and Release Infrastructure

• Updated release metadata to v0.6.1 across the desktop app, docs, and packaging helpers
• Refreshed macOS ARM64 release assets from the current source tree
• Kept the release packaging scripts aligned with the dedicated assembly PoW worker binaries

Known Notes

• Public IP autodetect may still emit warning noise on networks where the HTTPS lookup endpoints are blocked or truncated
• Wallet balances remain approval-gated when the node has not established enough confidence in chain state; this release improves recovery behavior but does not remove the approval model

Upgrade Guidance

• Replace older app bundles with the v0.6.1 binaries before starting the GUI miner
• If you previously mined on a stale or partially corrupted local chain, allow the backend to complete its startup repair once before judging final chain height
• If a very old mined-block backlog exists, v0.6.1 will reconcile and discard stale rejected entries instead of replaying them forever

Attached assets in this publish:

• macOS ARM64 app bundle zip
• macOS ARM64 daemon
• macOS ARM64 assembly PoW worker
• macOS ARM64 test binary
• SHA-256 checksums

CryptEX v0.6.0

CryptEX v0.6.0 Release Notes

Public contact: [email protected]

These notes describe the CryptEX v0.6.0 release as of April 2026. The project now spans the native chain, desktop GUI, wallet and RPC stack, networking and sync infrastructure, website, and the wrapped-asset EVM workspace.

Featured Changes

• Full SHA3-512 proof of work with 512-bit target math and cumulative-work chain selection
• Separate Qt GUI and backend daemon with a wallet-first desktop flow and a dedicated node window
• New Advanced Mode toggle that keeps the default desktop flow simpler while unlocking the Node Window and P2P Messenger for power users
• Major P2P Messenger overhaul with address-first recipient resolution, separate public/private/forum/voice sections, and responsive layouts
• New secure voice relay path using chat signaling, capability exchange, ECDH-derived session keys, AES-GCM frame encryption, Opus audio, and optional voice cloaking
• Public blockchain address directory actions for Message, Call, and Save Contact
• New forum-style public feed, separate private history, and improved media workflows with dedicated composer windows
• Hybrid adaptive difficulty controller combining LWMA, EMA, real-time overdue easing, and emergency minimum-difficulty recovery
• Expanded wallet system with encrypted storage, HD support, recovery tooling, multiple address encodings, and wallet management RPCs
• Stronger network stack with peer persistence, bans, DNS bootstrap, LAN/WLAN auto-discovery, peer activity controls, and sync-aware mining
• FastAPI-based website with live downloads, reserve-status surfacing, and deployment configs
• EVM workspace for Wrapped CryptEX (wCRX) plus bridge automation and reserve reporting tooling

Core Protocol and Consensus

• Native mainnet, testnet, and regtest profiles
• Full-width SHA3-512 proof-of-work validation
• 512-bit target expansion and chainwork accounting
• Genesis baked into network parameters for deterministic startup
• Cumulative-work chain selection rather than height-only chain choice
• Conservative fork handling with local path reconstruction and revalidation before activation
• Local approval and reorg-safety logic for stronger full-node behavior during sync and competing-chain observations

Difficulty and Liveness

• Adaptive retargeting now uses a hybrid controller instead of a slow legacy-only retarget model
• Current controller components:
  • damped LWMA-style estimator
  • EMA smoothing term
  • real-time overdue easing
  • emergency minimum-difficulty fallback after clear stall conditions
• Timestamp sanity checks and bounded solve-time behavior help reduce timestamp-based retarget abuse
• The chain is explicitly tuned to recover when a strong miner leaves and only low hash-rate miners remain

Wallets and Addresses

• Encrypted Wallet.dat storage
• BIP32 HD derivation
• BIP39 mnemonic generation and restore
• Safer wallet persistence through temp-file write and backup rotation
• Recovery path from backup copies via wallet recovery tooling
• Wallet manager support in the GUI
• Wallet session handling decoupled from node-startup settings
• Legacy root Wallet.dat discovery now works alongside managed wallet paths

Supported address encodings now include:

• Base64
• Base58
• 0x + hex
• Bech32

The current implementation treats these as multiple encodings over the same underlying address payload while preserving native Base64 compatibility for existing CryptEX wallets.

Wallet RPC and Maintenance

Current wallet-facing RPC coverage includes:

• getnewaddress
• getunusedaddress
• listwallets
• createwallet
• openwallet
• closewallet
• deletewallet
• setwalletformat
• dumpmnemonic
• dumpprivkey
• importprivkey
• importmnemonic
• backupwallet
• recoverwallet
• walletpassphrasechange
• rescanwallet

Additional wallet behavior updates:

• better immature / spendable / locked / total balance reporting
• corrected coinbase maturity boundary handling
• improved GUI balance and wallet-state refresh behavior
• better wallet-password prompting and restart handling in the desktop client

GUI and Desktop Client

The Qt client is now a serious desktop surface rather than a thin wrapper over CLI functionality.

Main user tabs:

• Overview
• Send
• Receive
• Transactions

Advanced functionality is moved into a separate Node Window, including:

• information
• wallet manager
• wallet tools
• console
• system log
• terminal
• miner output
• network tools
• chat
• settings

Desktop improvements include:

• wallet-first layout inspired by Bitcoin Core structure
• Advanced Mode toggle for expert tooling instead of exposing every operator surface by default
• startup splash and sync-details behavior
• bottom sync / peer / network activity indicators
• explicit node controls separated from ordinary wallet use
• address-format chooser dialogs
• improved wallet table stability and reduced refresh churn
• refresh-on-open behavior instead of heavy background refresh loops
• more resilient RPC-startup handling so backend wiring states do not show up as false messenger/call errors
• resizable messenger layouts with scroll-wrapped tabs, wrapped forms, and sane splitter defaults

Networking and Synchronization

• Boost.Asio-based TCP peer-to-peer transport
• Peer persistence through peers.dat
• Peer reputation and ban persistence through peer_state.dat
• Headers-first synchronization with bounded parallel block downloads
• DNS bootstrap support
• Peer exchange through protocol messages
• Direct peer connection support
• LAN/WLAN auto-discovery for same-network nodes
• Optional SOCKS5/Tor outbound proxy support
• Optional external IP discovery and self-advertisement

Additional sync/network changes:

• better sync status reporting through RPC and GUI
• explicit network activity enable/disable control
• improved separation of backend-unreachable vs RPC-auth-failure states
• safer async outbound connect behavior to reduce startup stalls
• peer maintenance and reconnection logic hardened for long-running nodes

Mining

• Multi-threaded CPU mining
• Sync-before-mining behavior when peers are present
• Continuous or bounded nonce-cycle mining
• Chained multi-block mining via --block-cycles
• GETWORK support
• getblocktemplate support
• Dedicated miner-output tooling in the GUI node window

The current mining and retarget path is designed to preserve liveness under unstable network hash-rate rather than assuming a large, steady industrial mining base.

RPC and Operator Surface

• JSON-RPC for blockchain, wallet, networking, mempool, mining, and chat operations
• Strict JSON parsing and parameter type enforcement
• Allowlist support
• Request-size limits
• Per-IP RPC rate limiting
• setnetworkactive support for runtime network control
• Better peer, sync, and approval telemetry through RPC
• Structured logging and config-file support

Secure Chat

CryptEX includes a non-consensus authenticated messaging layer between nodes.

Current chat support includes:

• signed public chat
• encrypted private chat
• inbox/history retrieval
• peer-routed delivery
• address-first recipient resolution from private contacts and the public directory
• forum-style public feed with full-post drill-down and local deletion controls
• separate private history view
• public directory actions to message, call, or save known chain addresses
• responsive media flows for image, video, and audio attachments through dedicated composer windows

Private chat currently uses an ECDH-derived AES-256-GCM session flow bound to recipient key material.

Voice Relay

P2P Messenger now includes a dedicated voice-call page for live, address-to-address encrypted relay calls.

Current voice relay support includes:

• chat-based signaling for call setup
• capability exchange during negotiation
• ECDH-derived shared session keys
• AES-256-GCM encrypted audio frames
• Opus audio transport
• optional live voice cloaking before encryption
• anonymous avatar / waveform UI
• active-call-only state, with no call logs or recordings persisted

The current implementation is designed around secure decentralized relay behavior first. It is functional, but still improving in latency-sensitive and NAT-hostile environments.

Storage and Persistence

• Binary block storage by height
• Header and block-index persistence
• Chainstate snapshots
• Hash-addressed known-block persistence improvements for side-branch continuity
• Wallet backup rotation and recovery-aware save paths
• System datadir defaults on macOS, Linux, and Windows so chain and wallet state survive binary replacement or deletion

Website and Release Infrastructure

The repository now includes a real web stack rather than a placeholder landing page.

Current website features:

• FastAPI backend
• Jinja templates
• home / downloads / technology / network / explorer / reserve / security / roadmap pages
• deployment examples for Caddy, nginx, and systemd
• release-directory surfacing on the downloads page
• reserve-status JSON and public reserve page integration

Release engineering additions include:

• cross-platform build matrix helpers
• Linux AppImage packaging
• Windows runtime packaging
• whitepaper PDF generation tooling

EVM and Bridge Workspace

The repository now contains a dedicated evm/ workspace for Wrapped CryptEX.

Current EVM implementation includes:

• WrappedCryptEX.sol
• wCRX deployment script
• Foundry configuration and tests
• operator runbooks
• automated bridge daemon
• reserve snapshot tooling
• deployment helper scripts

Bridge-related operational assets include:

• reserve-status publication
• deposit ID helper tooling
• example macOS and Linux service definitions
• mainnet deployment checklist and bridge operator runbook

Platform Outputs

Current repository packaging targets include:

• macOS ...

CryptEX v0.5.3

CryptEX v0.5.3

Public contact: [email protected]

Artifact status for this GitHub release:

• macOS ARM64 artifacts refreshed for v0.5.3
• Windows x86_64 artifacts refreshed for v0.5.3
• Linux x86_64 artifacts refreshed for v0.5.3
• Linux ARM64 artifacts refreshed for v0.5.3

---

CryptEX v0.5.3 Release Notes

These notes describe the CryptEX v0.5.3 release as of April 2026. The project now spans the native chain, desktop GUI, wallet and RPC stack, networking and sync infrastructure, website, and the wrapped-asset EVM workspace.

Featured Changes

• Full SHA3-512 proof of work with 512-bit target math and cumulative-work chain selection
• Separate Qt GUI and backend daemon with a wallet-first desktop flow and a dedicated node window
• Hybrid adaptive difficulty controller combining LWMA, EMA, real-time overdue easing, and emergency minimum-difficulty recovery
• Expanded wallet system with encrypted storage, HD support, recovery tooling, multiple address encodings, and wallet management RPCs
• Stronger network stack with peer persistence, bans, DNS bootstrap, LAN/WLAN auto-discovery, peer activity controls, and sync-aware mining
• FastAPI-based website with live downloads, reserve-status surfacing, and deployment configs
• EVM workspace for Wrapped CryptEX (wCRX) plus bridge automation and reserve reporting tooling

Core Protocol and Consensus

• Native mainnet, testnet, and regtest profiles
• Full-width SHA3-512 proof-of-work validation
• 512-bit target expansion and chainwork accounting
• Genesis baked into network parameters for deterministic startup
• Cumulative-work chain selection rather than height-only chain choice
• Conservative fork handling with local path reconstruction and revalidation before activation
• Local approval and reorg-safety logic for stronger full-node behavior during sync and competing-chain observations

Difficulty and Liveness

• Adaptive retargeting now uses a hybrid controller instead of a slow legacy-only retarget model
• Current controller components:
  • damped LWMA-style estimator
  • EMA smoothing term
  • real-time overdue easing
  • emergency minimum-difficulty fallback after clear stall conditions
• Timestamp sanity checks and bounded solve-time behavior help reduce timestamp-based retarget abuse
• The chain is explicitly tuned to recover when a strong miner leaves and only low hash-rate miners remain

Wallets and Addresses

• Encrypted Wallet.dat storage
• BIP32 HD derivation
• BIP39 mnemonic generation and restore
• Safer wallet persistence through temp-file write and backup rotation
• Recovery path from backup copies via wallet recovery tooling
• Wallet manager support in the GUI
• Wallet session handling decoupled from node-startup settings
• Legacy root Wallet.dat discovery now works alongside managed wallet paths

Supported address encodings now include:

• Base64
• Base58
• 0x + hex
• Bech32

The current implementation treats these as multiple encodings over the same underlying address payload while preserving native Base64 compatibility for existing CryptEX wallets.

Wallet RPC and Maintenance

Current wallet-facing RPC coverage includes:

• getnewaddress
• getunusedaddress
• listwallets
• createwallet
• openwallet
• closewallet
• deletewallet
• setwalletformat
• dumpmnemonic
• dumpprivkey
• importprivkey
• importmnemonic
• backupwallet
• recoverwallet
• walletpassphrasechange
• rescanwallet

Additional wallet behavior updates:

• better immature / spendable / locked / total balance reporting
• corrected coinbase maturity boundary handling
• improved GUI balance and wallet-state refresh behavior
• better wallet-password prompting and restart handling in the desktop client

GUI and Desktop Client

The Qt client is now a serious desktop surface rather than a thin wrapper over CLI functionality.

Main user tabs:

• Overview
• Send
• Receive
• Transactions

Advanced functionality is moved into a separate Node Window, including:

• information
• wallet manager
• wallet tools
• console
• system log
• terminal
• miner output
• network tools
• chat
• settings

Desktop improvements include:

• wallet-first layout inspired by Bitcoin Core structure
• startup splash and sync-details behavior
• bottom sync / peer / network activity indicators
• explicit node controls separated from ordinary wallet use
• address-format chooser dialogs
• improved wallet table stability and reduced refresh churn
• refresh-on-open behavior instead of heavy background refresh loops

Networking and Synchronization

• Boost.Asio-based TCP peer-to-peer transport
• Peer persistence through peers.dat
• Peer reputation and ban persistence through peer_state.dat
• Headers-first synchronization with bounded parallel block downloads
• DNS bootstrap support
• Peer exchange through protocol messages
• Direct peer connection support
• LAN/WLAN auto-discovery for same-network nodes
• Optional SOCKS5/Tor outbound proxy support
• Optional external IP discovery and self-advertisement

Additional sync/network changes:

• better sync status reporting through RPC and GUI
• explicit network activity enable/disable control
• improved separation of backend-unreachable vs RPC-auth-failure states
• safer async outbound connect behavior to reduce startup stalls
• peer maintenance and reconnection logic hardened for long-running nodes

Mining

• Multi-threaded CPU mining
• Sync-before-mining behavior when peers are present
• Continuous or bounded nonce-cycle mining
• Chained multi-block mining via --block-cycles
• GETWORK support
• getblocktemplate support
• Dedicated miner-output tooling in the GUI node window

The current mining and retarget path is designed to preserve liveness under unstable network hash-rate rather than assuming a large, steady industrial mining base.

RPC and Operator Surface

• JSON-RPC for blockchain, wallet, networking, mempool, mining, and chat operations
• Strict JSON parsing and parameter type enforcement
• Allowlist support
• Request-size limits
• Per-IP RPC rate limiting
• setnetworkactive support for runtime network control
• Better peer, sync, and approval telemetry through RPC
• Structured logging and config-file support

Secure Chat

CryptEX includes a non-consensus authenticated messaging layer between nodes.

Current chat support includes:

• signed public chat
• encrypted private chat
• inbox/history retrieval
• peer-routed delivery

Private chat currently uses an ECDH-derived AES-256-GCM session flow bound to recipient key material.

Storage and Persistence

• Binary block storage by height
• Header and block-index persistence
• Chainstate snapshots
• Hash-addressed known-block persistence improvements for side-branch continuity
• Wallet backup rotation and recovery-aware save paths
• System datadir defaults on macOS, Linux, and Windows so chain and wallet state survive binary replacement or deletion

Website and Release Infrastructure

The repository now includes a real web stack rather than a placeholder landing page.

Current website features:

• FastAPI backend
• Jinja templates
• home / downloads / technology / network / explorer / reserve / security / roadmap pages
• deployment examples for Caddy, nginx, and systemd
• release-directory surfacing on the downloads page
• reserve-status JSON and public reserve page integration

Release engineering additions include:

• cross-platform build matrix helpers
• Linux AppImage packaging
• Windows runtime packaging
• whitepaper PDF generation tooling

EVM and Bridge Workspace

The repository now contains a dedicated evm/ workspace for Wrapped CryptEX.

Current EVM implementation includes:

• WrappedCryptEX.sol
• wCRX deployment script
• Foundry configuration and tests
• operator runbooks
• automated bridge daemon
• reserve snapshot tooling
• deployment helper scripts

Bridge-related operational assets include:

• reserve-status publication
• deposit ID helper tooling
• example macOS and Linux service definitions
• mainnet deployment checklist and bridge operator runbook

Platform Outputs

Current repository packaging targets include:

• macOS ARM64
• Linux x86_64
• Linux ARM64
• Windows x86_64

Release artifacts in this flow include:

• backend daemon binaries
• GUI applications
• test binaries
• Linux AppImages
• Windows runtime bundle
• whitepaper PDF

Documentation

Current top-level documentation surfaces:

• Whitepaper PDF: WHITEPAPER.pdf
• Whitepaper source: archives/CryptEX_Whitepaper_Source_April_2026.md
• Release notes: RELEASE_NOTES.md

Known Boundaries and Active Work

The current implementation is substantial, but a few areas are still improving:

• side-branch persistence and archival completeness are improving relative to long-lived production networks
• some wallet cryptography code paths still emit OpenSSL deprecation warnings on newer toolchains
• RPC transport is authenticated HTTP, not TLS-secured remote transport
• the EVM bridge stack is present and documented, but operational rollout still depends on reserve management and deployment policy
• the project has broad regression coverage, but continued hardening and cleanup remain active engineering work

Suggested GitHub Release Title

CryptEX Current Release

Suggested Short GitHub Release Summary

Current CryptEX release with 512-bit SHA3 proof of work, hybrid adaptive difficulty control, separate GUI and daemon, expanded wallet and RPC tooling, LAN-aware networking, website and release infrastructure, and a full Wrapped CryptEX EVM workspace.