Got 9 simulated iOS devices successfully gossiping and performing storage operations between one another!
The network’s properly erasure coding files and distributing the shards amongst the simulated operators.
Nodes are even verifying one another using App Attest Certs.
So close!
11.08.2025 04:38 — 👍 44 🔁 10 💬 5 📌 0
lfg
04.08.2025 20:33 — 👍 27 🔁 4 💬 1 📌 0
Not a bad sized commit lol
03.08.2025 04:55 — 👍 30 🔁 5 💬 6 📌 0
Weeee modules #2-4 finished and running properly!
15.07.2025 03:13 — 👍 63 🔁 11 💬 7 📌 0
Module #1 is fully operational! Here’s what it is solely responsible for:
- Maintains the DAG of gossip events
- Validates node operator signatures/attestations
- Tracks seen relationships
- Assigns levels/checkpoints as the DAG grows
- Manages local storage of the DAG history and its metadata
27.06.2025 17:09 — 👍 32 🔁 7 💬 4 📌 0
One module down, 14 more to go. To be clear, unit tests don’t mean everything will automatically work perfectly fyi.
Unit tests verifies that the code is valid and buildable, it does not confirm that the application will “work” when ran.
However, the integration tests are also now passing 😈
26.06.2025 19:29 — 👍 31 🔁 3 💬 3 📌 0
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.
24.06.2025 18:53 — 👍 43 🔁 12 💬 9 📌 0
Tell me why “shdwdrive.com” was being hosted using WebFlow for hundreds per month when we literally have nearly unlimited compute and storage resources available… 🙄
This is what happens when I give people too much freedom.
The real issue is WebFlow’s vendor-locks…
18.06.2025 21:01 — 👍 26 🔁 2 💬 3 📌 0
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.
31.05.2025 17:25 — 👍 42 🔁 9 💬 16 📌 0
Getting closer!
28.05.2025 22:46 — 👍 53 🔁 12 💬 15 📌 0
IYKYK
21.05.2025 00:55 — 👍 40 🔁 8 💬 12 📌 0
For the first time in a long time, building decentralized tech is fun again.
Still building, still have max conviction.
22.04.2025 20:36 — 👍 62 🔁 10 💬 20 📌 0
Issue resolved, gossip is gossiping again and links are properly resolving once more.
08.04.2025 22:33 — 👍 29 🔁 4 💬 17 📌 0
Error identified with gossip message routing, working on resolution. No ETA at this time but stored data is unaffected.
08.04.2025 20:39 — 👍 17 🔁 4 💬 2 📌 1
Some users are reporting an issue with v1.5. Investigating. Will update when resolved.
08.04.2025 19:59 — 👍 19 🔁 2 💬 4 📌 0
GenesysGo will always be committed to upholding the highest standards of regulatory compliance in all our operations and activities.
We appreciate the continued support of the community as we return 100% of our focus to the tech where it belongs!
25.03.2025 18:05 — 👍 36 🔁 2 💬 3 📌 0
We’re grateful and relieved to finally put this matter behind us and eagerly look forward to once again fully focusing our attention on building and advancing exciting cutting-edge technology and sharing it with the world.
25.03.2025 18:05 — 👍 28 🔁 2 💬 2 📌 0
It simply means that, after thorough examination of the provided documentation, the SEC has concluded their investigation into potential violations of securities law and decided that enforcement action against GenesysGo and its members was not warranted.
25.03.2025 18:05 — 👍 17 🔁 0 💬 1 📌 0
Again, this outcome does not in any way imply validation, certification, or approval of our project, token, or services by the SEC.
25.03.2025 18:05 — 👍 16 🔁 0 💬 1 📌 0
To that end, we are extremely pleased to announce that the SEC has completed its investigation and that they do not intend to recommend any enforcement action against GenesysGo or its founders!
25.03.2025 18:05 — 👍 17 🔁 0 💬 1 📌 0
Although responding to the subpoena was a labor-intensive and time-consuming undertaking, we were encouraged by the accommodating, inquisitive, and professional manner of the SEC staff throughout this process 9 month process.
25.03.2025 18:05 — 👍 15 🔁 0 💬 1 📌 0
We were informed that the SEC was opening a non-public, fact-finding inquiry into GenesysGo, its founders, its operations, the Shadowy Super Coder NFT, and the SHDW token to determine if any violations of Federal Securities Law had occurred.
25.03.2025 18:05 — 👍 19 🔁 0 💬 1 📌 0
GenesysGo Announces Conclusion of SEC Investigation! - A thread:
In July 2024, GenesysGo received a letter from the Securities & Exchange Commission.
PLEASE NOTE:
This positive outcome does not in any way imply validation, certification, or approval of our project, token, or services by the SEC.
25.03.2025 18:05 — 👍 59 🔁 13 💬 12 📌 0
170!
Spread the word to everyone who’s not over here yet!
23.03.2025 15:11 — 👍 25 🔁 5 💬 6 📌 0
164 followers! We’ll be back up to 60k+ before you know it!
23.03.2025 05:43 — 👍 24 🔁 4 💬 2 📌 1
Incredible news!
Will know soon the degree to which we can share.
21.03.2025 16:53 — 👍 35 🔁 11 💬 13 📌 0
Rumors of our demise have been severely over exaggerated.
While we’re sure that will come as a disappointment to those spreading FUD, nothing’s changed for us.
Ignore the noise, these people spread FUD like it’s their job.
Bumps in the road don’t change the goal.
21.03.2025 13:07 — 👍 41 🔁 8 💬 15 📌 0
Have spent the past few weeks reviewing the state of the code base. It misses the mark and needs to be overhauled.
The first rework is for node operator staking.
Will be rebuilding and redeploying the smart contract to solve the issues with rewards claiming and withdrawals.
Stay tuned
20.03.2025 06:35 — 👍 38 🔁 7 💬 8 📌 2
Excited to post updates in the coming days!
18.03.2025 06:18 — 👍 34 🔁 5 💬 8 📌 1
Temporarily delaying the release of shdwDrive v1.0.12 to ensure that the staking bug is resolved in this release along with the additional improvements originally planned.
Please stay tuned and we appreciate the patience!
05.03.2025 03:06 — 👍 20 🔁 3 💬 4 📌 0
