For a long time, people have talked about doing AI training on many different computers run by different people, but the big problem was always TRUST.
How do you know the work they send back is real? How do you stop someone from cheating or cutting corners? Most solutions were either too slow or too complicated.
Imagine you ask two AI tools a basic question
โHow do I reset my Wi-Fi router?โ
They both give different steps. One sounds right, the other soundsโฆ maybe right
Judge comes into play here. It checks both answers like a fair referee and picks the one thatโs actually correct and anyone can replay that check and get the exact same result.
Iโm not saying everything is solved. There are still things to figure out, especially once this runs at a bigger scale.
But seeing this made me think that decentralized AI compute might actually become real in the near future, not just an idea people talk about.
Gswarm
A recent update was made to ๐๐๐ซ๐๐ few days ago, and itโs a pretty important one.
Before diving into the improvements, letโs quickly understand what Verde actually does, then walk through the updates and why they make the system much more efficient.
The biggest improvement, in my opinion, is how much faster and cheaper it is now to check if AI work was done correctly. Before this update, verification almost felt like marking a studentโs homework by re-doing the entire assignment from scratch. Slow, expensive, and honestly kind of pointless.
But now?
Verde basically works like this:
Imagine you give the same math problem to two students.
If both answers match โ great, you trust it.
If the answers donโt match โ instead of redoing the whole homework, you only check the exact step where they disagree.
Thatโs exactly what Verde does with AI tasks.
It doesnโt re-run everything, it finds the tiny operation where two compute providers differ, and only re-runs that one step. This alone is a game changer because AI jobs can be huge, hours or days of work.
The second improvement that stood out is something called ๐๐๐ฉ๐๐ฉ๐ฌ, and hereโs how I understood it:
Different computers (GPUs, CPUs, etc.) normally do math slightly differently.
Itโs like asking two people to multiply a bunch of decimals, they might round numbers differently even if theyโre both honest.
๐๐๐ฉ๐๐ฉ๐ฌ fixes this by making all machines do the math in the exact same order, so the final result is literally bit-for-bit identical.
Example:
If one GPU normally calculates a matrix from left-to-right and another from right-to-left, RepOps forces both to do it the same way.
This means if two workers give different results, you instantly know someone is lying or messing up, not that their hardware is just buggy.
Which then makes the whole process efficient and effective, looking forward to more updates :)
๐๐ฌ๐ฐ๐๐ซ๐ฆ
The Gensyn team will be at NeurIPS next week, cohosting a series of community events with @akashnet and @PluralisHQ. If youโre in town, join us for co-working, discussion, and connection.
Our research team will be on-site to share our latest thinking and progress in decentralized AI.
A recent update was made to ๐๐๐ซ๐๐ few days ago, and itโs a pretty important one.
Before diving into the improvements, letโs quickly understand what Verde actually does, then walk through the updates and why they make the system much more efficient.
The biggest improvement, in my opinion, is how much faster and cheaper it is now to check if AI work was done correctly. Before this update, verification almost felt like marking a studentโs homework by re-doing the entire assignment from scratch. Slow, expensive, and honestly kind of pointless.
But now?
Verde basically works like this:
Imagine you give the same math problem to two students.
If both answers match โ great, you trust it.
If the answers donโt match โ instead of redoing the whole homework, you only check the exact step where they disagree.
Thatโs exactly what Verde does with AI tasks.
It doesnโt re-run everything, it finds the tiny operation where two compute providers differ, and only re-runs that one step. This alone is a game changer because AI jobs can be huge, hours or days of work.
The second improvement that stood out is something called ๐๐๐ฉ๐๐ฉ๐ฌ, and hereโs how I understood it:
Different computers (GPUs, CPUs, etc.) normally do math slightly differently.
Itโs like asking two people to multiply a bunch of decimals, they might round numbers differently even if theyโre both honest.
๐๐๐ฉ๐๐ฉ๐ฌ fixes this by making all machines do the math in the exact same order, so the final result is literally bit-for-bit identical.
Example:
If one GPU normally calculates a matrix from left-to-right and another from right-to-left, RepOps forces both to do it the same way.
This means if two workers give different results, you instantly know someone is lying or messing up, not that their hardware is just buggy.
Which then makes the whole process efficient and effective, looking forward to more updates :)
๐๐ฌ๐ฐ๐๐ซ๐ฆ
๐๐ก๐ ๐๐ข๐๐๐๐ง ๐๐๐ง๐๐๐ข๐ญ๐ฌ ๐จ๐ ๐๐๐ง๐ฌ๐ฒ๐ง ๐๐จ๐ซ ๐๐๐ ๐ฎ๐ฅ๐๐ซ ๐๐๐จ๐ฉ๐ฅ๐
Honestly, the more I learn about Gensyn, the more I realize how quietly it could improve everyday life for regular people, not just tech folks.
Take something as basic as AI writing tools. Right now, a lot of them charge high monthly fees because training these models is insanely expensive. But imagine if training costs dropped because of networks like Gensyn. You could get the same tools for a fraction of the price.
For me personally, that would mean not thinking twice before using an AI tutor to learn a new language or an AI assistant to help me edit videos. It becomes something everyone can use, not just people willing to pay premium subscriptions.
Hereโs how I see it ๐ฝ
๐๐ก๐๐๐ฉ๐๐ซ ๐๐ = ๐๐๐ญ๐ญ๐๐ซ ๐ญ๐จ๐จ๐ฅ๐ฌ ๐๐จ๐ซ ๐๐ฏ๐๐ซ๐ฒ๐จ๐ง๐
If AI becomes cheaper to train, weโll all get access to better apps like smarter language tutors, easier content creation tools, and even more accurate health assistants. Imagine getting pro-level help without paying pro-level prices.
๐ ๐๐ฌ๐ญ๐๐ซ ๐ข๐ง๐ง๐จ๐ฏ๐๐ญ๐ข๐จ๐ง
When developers donโt have to worry about huge compute costs, they can build more creative stuff. Think faster updates to AI apps, better automation tools for small businesses, and more powerful features for students and creators.
๐๐จ๐ซ๐ ๐ฉ๐ซ๐ข๐ฏ๐๐๐ฒ
A decentralized system means some AI can train without sending your personal data to big companies. For everyday people, thatโs a win for safer data and more control.
๐๐ฑ๐ญ๐ซ๐ ๐ข๐ง๐๐จ๐ฆ๐ ๐๐จ๐ซ ๐ซ๐๐ ๐ฎ๐ฅ๐๐ซ ๐๐จ๐ฅ๐ค๐ฌ
Got a GPU sitting idle? You could earn money by letting it do useful AI work instead of collecting dust. Even gamers or small studios could benefit from this.
๐๐๐ญ๐ญ๐๐ซ ๐๐จ๐ซ ๐ญ๐ก๐ ๐ฉ๐ฅ๐๐ง๐๐ญ
Instead of building endless new data centers, Gensyn taps into hardware that already exists. Less waste, less energy, more efficiency.
I know it sounds like a niche tech thing, but honestly, the ripple effects could touch everyone, from students to small business owners to people just trying to save time or money.
๐๐ฌ๐ฐ๐๐ซ๐ฆ
Ever wondered how Gensyn pulls off trustless verification?
The first time I explored it, I thought
"How are random machines on the internet training a model and we somehow know they arenโt lying?"
Well here's the breakdown of how the process works
Model Submitter โ Solver
Someone sends in a model training task.
The Solver is the machine that does the work. Think of the Solver like a student doing homework.
Solver โ Verifiers
After the Solver finishes, other machines (Verifiers) check the work.
To me, this is the cool part:
We donโt trust the Solver.
We donโt trust the Verifiers either.
But we do trust that they will disagree if something looks wrong.
Verifiers โ Disagreement Trigger
If the Verifiers think the Solver is lying or made a mistake, this red box is activated.
It basically means:
โHey, something doesnโt add up.โ
Disagreement Trigger โ Judge
When things donโt line up, the Judge steps in.
This Judge checks the specific part where Solver and Verifiers disagree.
Itโs not redoing everything just the part that matters.
Judge โ Verde โ Efficient Referee
This is the deeper verification pipeline.
Verde and the Efficient Referee help the Judge confirm who is correct.
When I learned this part, I thought:
โWow, itโs like a mini court system for machine learning.โ
Efficient Referee โ Final Consensus
At the end, the system reaches consensus.
When everything is checked, the system decides on one final correct result, and everyone has to accept it the Solver, the Verifiers, and the Judge. There is no more arguing after that point.
Ever wondered how Gensyn pulls off trustless verification?
The first time I explored it, I thought
"How are random machines on the internet training a model and we somehow know they arenโt lying?"
Well here's the breakdown of how the process works
Model Submitter โ Solver
Someone sends in a model training task.
The Solver is the machine that does the work. Think of the Solver like a student doing homework.
Solver โ Verifiers
After the Solver finishes, other machines (Verifiers) check the work.
To me, this is the cool part:
We donโt trust the Solver.
We donโt trust the Verifiers either.
But we do trust that they will disagree if something looks wrong.
Verifiers โ Disagreement Trigger
If the Verifiers think the Solver is lying or made a mistake, this red box is activated.
It basically means:
โHey, something doesnโt add up.โ
Disagreement Trigger โ Judge
When things donโt line up, the Judge steps in.
This Judge checks the specific part where Solver and Verifiers disagree.
Itโs not redoing everything just the part that matters.
Judge โ Verde โ Efficient Referee
This is the deeper verification pipeline.
Verde and the Efficient Referee help the Judge confirm who is correct.
When I learned this part, I thought:
โWow, itโs like a mini court system for machine learning.โ
Efficient Referee โ Final Consensus
At the end, the system reaches consensus.
When everything is checked, the system decides on one final correct result, and everyone has to accept it the Solver, the Verifiers, and the Judge. There is no more arguing after that point.
When AI Codes as a Teamโฆ CODEZERO Happens
A few days ago, Gensyn rolled out a new feature called CodeZero, and honestly, it grabbed my attention more than a typical update. Instead of training one model in isolation, CodeZero sets up a kind of shared โcoding hiveโ where different AI agents work together and learn from each other.
There are three types of agents in this setup:
Proposers | Solvers | Evaluators
โถ๏ธ Proposers: They come up with new coding challenges and adjust how difficult those problems are.
โถ๏ธ Solvers: These are the ones actually trying to solve the problems, learning on the fly through reinforcement learning.
โถ๏ธ Evaluators: Their job is to judge the quality of the Solversโ code and interestingly, they donโt always need to run the code to do it.
All of this happens across a peer-to-peer network, so thereโs no single โmainโ model controlling everything. The agents basically learn by bouncing knowledge off one another.
Why I think this matters:
It feels a bit like watching a group of developers brainstorm ideas move faster, and solutions get sharper. It also adds an extra layer of safety since the evaluation doesnโt always rely on running unknown code. And the decentralized design means the system can grow as more people join in, potentially improving AI training far beyond just coding task.
gswarm
From a new product environment to major testnet growth and new research, this was one of the busiest weeks yet for the Gensyn community. Hereโs everything we shipped. ๐
When AI Codes as a Teamโฆ CODEZERO Happens
A few days ago, Gensyn rolled out a new feature called CodeZero, and honestly, it grabbed my attention more than a typical update. Instead of training one model in isolation, CodeZero sets up a kind of shared โcoding hiveโ where different AI agents work together and learn from each other.
There are three types of agents in this setup:
Proposers | Solvers | Evaluators
โถ๏ธ Proposers: They come up with new coding challenges and adjust how difficult those problems are.
โถ๏ธ Solvers: These are the ones actually trying to solve the problems, learning on the fly through reinforcement learning.
โถ๏ธ Evaluators: Their job is to judge the quality of the Solversโ code and interestingly, they donโt always need to run the code to do it.
All of this happens across a peer-to-peer network, so thereโs no single โmainโ model controlling everything. The agents basically learn by bouncing knowledge off one another.
Why I think this matters:
It feels a bit like watching a group of developers brainstorm ideas move faster, and solutions get sharper. It also adds an extra layer of safety since the evaluation doesnโt always rely on running unknown code. And the decentralized design means the system can grow as more people join in, potentially improving AI training far beyond just coding task.
gswarm
Everyone keeps saying they know about Gensynโs products and their whole mechanism, so how about we put that to test?
I made a quiz module highlighting all of them:
-Codeassist
-RL-swarm
-Judge
-Blockassist
try it out here: https://t.co/xHCx89Nsmj