[Cryptography] DSM: deterministic edge state machine (post-quantum, no public ledger/consensus)

[Viktor S. Kristensen]

Hi Brandon,

Thanks for putting DSM in front of the metzdowd list — strong primer. Skimmed the repo and read the README + onboarding walkthrough. The structure of the bilateral chain, the Lean4 work (DSMOfflineFinality.lean, DSM_dBTC_Conservation.lean in particular), and the BLE Coordinator on Android together look like a serious shot at offline-capable settlement done properly.

A bit about us: we run Quillon Graph (Q-NarwhalKnight), a live mainnet quantum-enhanced DAG-BFT chain with sub-3-second finality, Dilithium5 + Kyber1024 PQ stack, and ~$2B market cap on the QUG token. The repo is at code.quillon.xyz (self-hosted, not GitHub). We have the global-ledger anchor side of the equation that your design needs for dispute resolution of last resort.

We see a real fit for DSM's primitive — specifically, a Bluetooth-offline QUG transfer path between two wallets out of range of internet. Festivals, transit, remote areas, anywhere connectivity is unreliable. Our planned adaptation:

Lift the bilateral hash-chain transaction manager and the BLE Android stack

Swap dBTC primitives for QUG balances

Anchor disputes to a Quillon Graph smart contract (collateral + dispute window) rather than Bitcoin Signet

Adapt the Lean4 proofs to our anchor model

We're targeting two-phase rollout: Web Bluetooth API in the desktop wallet first, then a port to our Expo / React Native mobile app for iOS + Android.

We're not picking this up immediately — but it's queued as a real follow-on initiative.

A few questions when you have a moment:

Is the bilateral_transaction_manager.rs design abstracted over the anchor chain, or is there Bitcoin-specific coupling I'd need to refactor?

Are the Lean4 theorems stated in terms generic to the anchor (i.e., could DSMOfflineFinality.lean re-state cleanly with QUG replacing dBTC), or are they coupled to Bitcoin script primitives?

Are you open to a collaboration where we contribute back: an alternate-anchor adapter, an iOS BLE counterpart to your Android Coordinator, and (potentially) co-authored proof extensions?

Happy to email more concretely once we've completed our spike. If you'd prefer, I can also open a discussion thread on the GitHub repo.

Keep building. Critical-feedback-encouraged is the right disposition.

Best,
Viktor 


Really important if something matters

Afsendt med Proton Mail sikker e-mail.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: publickey - overdrevetfedmetodologi at pm.me - 0x5F4716BA.asc
Type: application/pgp-keys
Size: 1722 bytes
Desc: not available
URL: <https://www.metzdowd.com/pipermail/cryptography/attachments/20260515/3cfa99ec/attachment.key>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 603 bytes
Desc: OpenPGP digital signature
URL: <https://www.metzdowd.com/pipermail/cryptography/attachments/20260515/3cfa99ec/attachment.sig>