$KNX Building the Offline Settlement Stack
~Dev Update
We are building KnoxNet as an offline-first value transfer network, not another smart contract chain or wallet layer. The stack includes the KnoxNet node, KnoxNet CLI, and KnoxNet explorer. The node handles note validation, settlement records, peer communication, and reconciliation logic. The CLI gives users a direct way to create wallets, receive test notes, send and accept offline note bundles, submit them for reconciliation, and check settlement status. The explorer will make the network visible through note activity, settlement history, account states, and live network stats.
At the center of KnoxNet is the Note primitive. A note is a signed value object that can move between users without internet at the moment of transfer. Alice can send a note to Bob offline, Bob can send it to Charlie offline, and the full ownership path can later be submitted to the network for reconciliation. Once submitted, the network verifies ownership, signatures, note history, and double-spend conflicts before accepting the latest valid state.
This build is focused on proving the KnoxNet flow end-to-end. Users should be able to run nodes, create wallets, receive testnet notes, transfer them offline, pass them across multiple hops, submit them back to the network, and view the complete note lifecycle inside the explorer. This is the foundation for KnoxNet as an offline-first value transfer network where execution can happen locally first, and global settlement happens later.