Now I’m building out all of the Rust components that drive the actual shdwDrive v3 network itself.
Meaning, the consensus mechanism and the gossip network.
Now I’m building out all of the Rust components that drive the actual shdwDrive v3 network itself.
Meaning, the consensus mechanism and the gossip network.
DAGGER is built for phones. It assumes spotty connections, 5G or Wi-Fi, and limited resources — and still delivers fast, secure consensus.
DAGGER is built for phones. It assumes spotty connections, 5G or Wi-Fi, and limited resources — and still delivers fast, secure consensus.
Every device in the network is an equal participant, but only if it stays active and proves it’s secure via device-level attestation. If a device stops checking in or can’t prove it’s real, the network simply ignores it.
Every device in the network is an equal participant, but only if it stays active and proves it’s secure via device-level attestation. If a device stops checking in or can’t prove it’s real, the network simply ignores it.
Finality happens when enough of the network has observed an event — not because of a round number or election. It emerges from the DAG itself.
Finality happens when enough of the network has observed an event — not because of a round number or election. It emerges from the DAG itself.
DAGGER avoids leaders, rounds, or global sync. Events propagate freely through gossip, enabling continuous progress across disconnected, mobile nodes.
DAGGER avoids leaders, rounds, or global sync. Events propagate freely through gossip, enabling continuous progress across disconnected, mobile nodes.
Nodes prove they’re real and unmodified using hardware-backed attestation, not by holding tokens or credentials. Trust is earned at runtime, not assumed by default.
Nodes prove they’re real and unmodified using hardware-backed attestation, not by holding tokens or credentials. Trust is earned at runtime, not assumed by default.
By the time shdwDrive v2 launched, the consensus engine for v2 was this aberration that had somehow started using libraries that are widely known for being incompatible with mobile devices…
Again, my fault for trusting.
By the time shdwDrive v2 launched, the consensus engine for v2 was this aberration that had somehow started using libraries that are widely known for being incompatible with mobile devices…
Again, my fault for trusting.
Somehow, we went from a fully functioning consensus engine (remember Solana XRoads when we debuted the mobile testnet?) to a barely functional mess.
It’s my fault for giving people too much freedom and trust.
Somehow, we went from a fully functioning consensus engine (remember Solana XRoads when we debuted the mobile testnet?) to a barely functional mess.
It’s my fault for giving people too much freedom and trust.