Jeff Matthews
@jeff-matthews.bsky.social
Reposted by Jeff Matthews
RT /StLouisBlues: Demidov / Deniedov same thing
December 8, 2025 at 1:41 AM
RT /StLouisBlues: Demidov / Deniedov same thing
Reposted by Jeff Matthews
Never been more excited to sign an NDA before 🔥🔥🔥
November 13, 2025 at 7:13 PM
Never been more excited to sign an NDA before 🔥🔥🔥
Reposted by Jeff Matthews
I am very intrigued
I forget which one of you maniacs inceptioned me into this, but we're trying the pop tart peanut butter sandwich
November 11, 2025 at 6:44 PM
I am very intrigued
Reposted by Jeff Matthews
Reposted by Jeff Matthews
THE BLUES SCORE LATE TO WIN IT‼️
November 4, 2025 at 4:18 AM
THE BLUES SCORE LATE TO WIN IT‼️
Reposted by Jeff Matthews
THE BLUES TAKE THE LEAD WITH 1:23 TO GO IN THE THIRD! 😳
November 4, 2025 at 4:17 AM
THE BLUES TAKE THE LEAD WITH 1:23 TO GO IN THE THIRD! 😳
I took action with People Not Politicians - Missouri. Will you join me? Use this link to sign up: www.mobilize.us/pnpmo/event/...
Pledge To Collect Signatures to Protect Missouri's Congressional Maps · People Not Politicians - Missouri
Sign up to receive more information about upcoming events to collect signatures with the People Not Politicians campaign.
www.mobilize.us
September 16, 2025 at 1:19 AM
I took action with People Not Politicians - Missouri. Will you join me? Use this link to sign up: www.mobilize.us/pnpmo/event/...
Reposted by Jeff Matthews
As v3 continues to take shape, there are more updates on the way!
Including updates regarding a return to Twitter and expansion of social media to other platforms.
Stay tuned
Including updates regarding a return to Twitter and expansion of social media to other platforms.
Stay tuned
August 27, 2025 at 5:44 PM
As v3 continues to take shape, there are more updates on the way!
Including updates regarding a return to Twitter and expansion of social media to other platforms.
Stay tuned
Including updates regarding a return to Twitter and expansion of social media to other platforms.
Stay tuned
Reposted by Jeff Matthews
BREAKING: Trump just missed Gavin Newsom’s ultimatum. California will officially draw new gerrymandered maps in favor of democrats.
August 13, 2025 at 12:02 AM
BREAKING: Trump just missed Gavin Newsom’s ultimatum. California will officially draw new gerrymandered maps in favor of democrats.
Reposted by Jeff Matthews
Not a bad sized commit lol
August 3, 2025 at 4:55 AM
Not a bad sized commit lol
Reposted by Jeff Matthews
Weeee modules #2-4 finished and running properly!
July 15, 2025 at 3:13 AM
Weeee modules #2-4 finished and running properly!
Reposted by Jeff Matthews
Thus far, the iOS app works flawlessly and all of the entry points needed to turn on the network work perfectly in tests.
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.
June 24, 2025 at 6:53 PM
Thus far, the iOS app works flawlessly and all of the entry points needed to turn on the network work perfectly in tests.
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.
Reposted by Jeff Matthews
5. Consensus Must Be Mobile-First and Bandwidth-Respectful
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.
June 24, 2025 at 6:53 PM
5. Consensus Must Be Mobile-First and Bandwidth-Respectful
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.
Reposted by Jeff Matthews
4. Every Node Is Equal — Until Trust Expires
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.
June 24, 2025 at 6:53 PM
4. Every Node Is Equal — Until Trust Expires
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.
Reposted by Jeff Matthews
3. Finality Should Be Emergent, Not Imposed
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.
June 24, 2025 at 6:53 PM
3. Finality Should Be Emergent, Not Imposed
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.
Reposted by Jeff Matthews
2. Consensus Should Be Asynchronous and Leaderless
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.
June 24, 2025 at 6:53 PM
2. Consensus Should Be Asynchronous and Leaderless
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.
Reposted by Jeff Matthews
1. Trust Comes from Hardware, Not Humans
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.
June 24, 2025 at 6:53 PM
1. Trust Comes from Hardware, Not Humans
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.
Reposted by Jeff Matthews
shdwDrive v3’s consensus engine returns to the first principles that I had been championing to our former team for almost two years…
June 24, 2025 at 6:53 PM
shdwDrive v3’s consensus engine returns to the first principles that I had been championing to our former team for almost two years…
Reposted by Jeff Matthews
Somewhere along the line they strayed tremendously from first principles.
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.
June 24, 2025 at 6:53 PM
Somewhere along the line they strayed tremendously from first principles.
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.
Reposted by Jeff Matthews
The existing consensus engine for shdwDrive v2 is garbage (and basically non-existent).
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.
June 24, 2025 at 6:53 PM
The existing consensus engine for shdwDrive v2 is garbage (and basically non-existent).
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.
Reposted by Jeff Matthews
The last of the architectural design modules for shdwDrive v3’s newly designed consensus engine are finally finished.
Now to get to building them.
At some point, I’ll compile all 15 module documents and publish them.
Now to get to building them.
At some point, I’ll compile all 15 module documents and publish them.
June 24, 2025 at 6:53 PM
The last of the architectural design modules for shdwDrive v3’s newly designed consensus engine are finally finished.
Now to get to building them.
At some point, I’ll compile all 15 module documents and publish them.
Now to get to building them.
At some point, I’ll compile all 15 module documents and publish them.
Reposted by Jeff Matthews
And this is why I left crypto.
Sure, I’m still building decentralized technology but I won’t actively be a part of participating in a community that is so completely misaligned with my morals and ethics.
Sure, I’m still building decentralized technology but I won’t actively be a part of participating in a community that is so completely misaligned with my morals and ethics.
June 8, 2025 at 2:03 PM
And this is why I left crypto.
Sure, I’m still building decentralized technology but I won’t actively be a part of participating in a community that is so completely misaligned with my morals and ethics.
Sure, I’m still building decentralized technology but I won’t actively be a part of participating in a community that is so completely misaligned with my morals and ethics.
Reposted by Jeff Matthews
A shdwDrive Thread:
So, it’s completely accurate to say that the deployment of shdwDrive v2 was an utter mess.
Many parts of shdwDrive v2’s architecture made absolutely zero sense.
However, one of the things that is the most game changing about AI is that nobody can hide bad code anymore.
So, it’s completely accurate to say that the deployment of shdwDrive v2 was an utter mess.
Many parts of shdwDrive v2’s architecture made absolutely zero sense.
However, one of the things that is the most game changing about AI is that nobody can hide bad code anymore.
May 31, 2025 at 5:25 PM
A shdwDrive Thread:
So, it’s completely accurate to say that the deployment of shdwDrive v2 was an utter mess.
Many parts of shdwDrive v2’s architecture made absolutely zero sense.
However, one of the things that is the most game changing about AI is that nobody can hide bad code anymore.
So, it’s completely accurate to say that the deployment of shdwDrive v2 was an utter mess.
Many parts of shdwDrive v2’s architecture made absolutely zero sense.
However, one of the things that is the most game changing about AI is that nobody can hide bad code anymore.