@frank-thetrader.bsky.social
Amen.
Crypto bros are literally ALWAYS looking for someone else to blame when the reality is simply that they’re idiots who don’t understand what they’re doing.
The same thing happened yesterday in $SPX, spreads that are normally pennies wide increased to being dollars wide. It’s normal.
Nice progress on cleaning and refining aspects of the gossip network over the past few days!
11.10.2025 17:49 — 👍 13 🔁 4 💬 1 📌 0
Crypto kids broke hard for Trump in the election.
Great job dumbasses 🤣🤣🤣
No shit Sherlock
10.10.2025 22:34 — 👍 0 🔁 0 💬 0 📌 0Seriously… MAGA = dumbasses 🤦♂️
10.10.2025 18:01 — 👍 2 🔁 0 💬 0 📌 0Nothing says “America First” like letting another country put an Air Force base in Idaho
10.10.2025 14:57 — 👍 19161 🔁 7562 💬 3466 📌 1752
www.newsweek.com/trump-admin-...
Trump voters really are the dumbest mother fuckers on the planet… 🤦♂️ We tried to warn you… dumbasses…
In building v3’s codebase, I created a dedicated module whose sole purpose is to manage the FFI surfaces. This bridge is how the iOS app initializes the storage runtime on the mobile device.
Why this is important is bc when we port to Android, it means simply adding new surfaces to one just module
It won’t be.
The bulk of the work is on the Rust components of the storage runtime. That’s where the innovation and edge-tech live.
I just started with iOS because I have an iPhone 😅
They’ve never read this
05.10.2025 22:02 — 👍 3 🔁 0 💬 1 📌 0Keep peepin’ the commits. Scrubbing module by module
04.10.2025 21:01 — 👍 21 🔁 3 💬 1 📌 0Home stretch!
Everything runs, the iOS app builds and runs perfectly!
Now, it’s just a matter of going module by module to clean up any AI slop remaining and optimize the codebase… but, it all works!
Oh no… a threat from a random loser on the internet whatever will I do…
30.09.2025 15:58 — 👍 0 🔁 0 💬 0 📌 0🙏🙏🙏
26.09.2025 05:54 — 👍 2 🔁 0 💬 0 📌 0
Weeeeee!
26.09.2025 05:53 — 👍 26 🔁 2 💬 1 📌 0Literally could not care less what you think @dkdkdv.bsky.social
24.09.2025 23:29 — 👍 0 🔁 0 💬 1 📌 0More to come in the near future, but I am feeling more and more confident that the end of the 3 - 5 year time frame for the construction and deployment of a finished shdwDrive protocol I’d laid out back in 2022 is quickly approaching!
24.09.2025 19:04 — 👍 18 🔁 1 💬 2 📌 0Which means, people’s opinions of me and/or GenesysGo ultimately become irrelevant… because all that matters is the codebase itself.
The fact that every single node in the network acts as a gateway to the network, means that even the DNS layer is no longer something that GenesysGo has to maintain.
This approach makes success for holders far more likely as no one has to trust or even like me or GenesysGo.
Anyone can fork, audit, and run the shdwDrive v3 codebase completely independently… anyone can tie their network into other existing networks, completely independent of me and GenesysGo.
Meaning, existing holders of Solana-based $SHDW don’t need to root for the network or platform of one specific team.
Instead, $SHDW holders get to focus on (and benefit from) the success of the shdwDrive protocol as a whole, regardless of which chain that success might occur on.
…and then let’s say $XYZ just completely blows up because the Eth team does an amazing job of marketing their network/platform built using the shdwDrive v3 protocol…
…well, this ensures that existing holders of the Solana-based $SHDW token see the benefit of that success too.
This enables anyone on any other blockchain to also make use of the shdwDrive v3 protocol, while ensuring existing token holders are provided for.
What does this look like? Let’s say someone creates $XYZ token on Ethereum and wants to tie $XYZ to their deployment of shdwDrive 3…
3) Deploying a network using the shdwDrive v3 protocol that uses a blockchain/token other than Solana and the Solana-based $SHDW token must include a mechanism by which holders of the Solana based $SHDW token can exchange their tokens proportionally at a 1:1 ratio.
24.09.2025 19:04 — 👍 14 🔁 0 💬 1 📌 02) The aspects of the codebase requiring node operators to stake SHDW tokens in order for their node to be allowed to join the network MUST be fully preserved OR must meet the requirements set forth in Requirement #3.
24.09.2025 19:04 — 👍 13 🔁 0 💬 1 📌 0There will only three restrictions on the license for the shdwDrive v3 protocol:
1) Any networks running the shdwDrive v3 software must, to the extent they are legally able, ensure a minimum of 75% of platform fees generated are passed directly to the operators running nodes on the network.
One of the things I’m MOST excited about is being able to open source the shdwDrive v3 protocol.
The license will be completely permissive as far as allowing people to create their own shdwDrive networks whenever they want.
Meaning, NO ONE will HAVE to rely on GenesysGo if they do not want to.
I’m pretty excited to announce that the actual storage runtime for shdwDrive v3 is basically done!
Steven and I have some bug hunting to finish up, but I’ve moved onto polishing the iOS app.
In the coming weeks, I’ll be able to give a more definite time frame as far as an actual release date!
