gRialo friends, in the usual blockchain model, security comes from validators redoing the same computation across the network. A transaction comes in, a result is produced, and then the network checks that result by running the same computation again. That model is strong, but it is also expensive. And once the computation gets heavy or the inputs involve private data, it starts to feel pretty inefficient.
The model @RialoHQ is pushing looks at the problem differently.
Here, the computation is not repeated by everyone. It happens once, a cryptographic proof is generated to show it was done correctly, and the chain verifies that proof instead of rerunning the whole thing. If the proof is valid, the application can use that verified result and settle the state update onchain.
So the difference is basically this:
In the classic model, the network keeps repeating the same work. In this model, the computation happens once, and correctness is checked through a proof. That matters because some things are just not a good fit for repeated onchain execution. The computation might be too heavy, the data might be too large, or the inputs might be private.
Think about something like calculating an index price. The raw data could be huge or proprietary. Instead of having everyone onchain recalculate it over and over, you can compute it offchain and bring the result onchain with a proof.
The same applies to eligibility checks. Maybe you want to verify whether a user qualifies for a reward, a loan, or some rule-based access. With the right proof system, you can prove that the condition was satisfied without exposing all of the user’s private data.
That is also how Rialo is positioning itself here. Not as the place where everything has to execute onchain, but more like the layer that verifies proofs of offchain computation and lets applications settle those verified results onchain.
One of the most important distinctions in the article is this:
A proof can show:
“Given these inputs, this computation was executed correctly.”
But it does not automatically show: “These inputs were true in the real world.”
So a proof can prove the computation was done correctly, but input validity is still something the application has to handle carefully. That is honestly one of the most useful parts of the article, because it makes the limits clear instead of pretending proof solves everything.
I also put together a simple visual below comparing the classic model with the approach Rialo is describing. It makes the difference easier to see at a glance. At the end of the day, the classic blockchain model says, “everyone should recompute.” The model Rialo is describing says, “compute once, verify the proof onchain, and let the application settle the verified result.”
If heavier computation, privacy, and more complex financial apps are going to live onchain, it is not hard to see why this approach is getting attention.
Note: This is not a paid partnership or an ad. I only enabled the label because I tagged @RialoHQ@RialoTR
gRialo fam, the numbers @RialoHQ shared are genuinely impressive.
Builder’s Hub started with 120 attendees in January and has now grown to 475. Shark Tank reaching 685 attendees is no small thing either. Looking at it from a community participation angle makes it even more meaningful.
Because this is not just about bigger numbers. It also shows that the community is consistently paying attention to these spaces. Seeing participation keep climbing in builder focused events month after month is a strong signal.
For anyone who is not familiar with Builder’s Hub and Shark Tank, here is the simple version.
Builder’s Hub feels like the place where builders in the community show what they are working on, get feedback, and become more visible.
Shark Tank feels like the more intense version of that. Builders get up, pitch their project, answer questions, and show what they have actually built.
That is why these should not be read as just regular community meetups. One makes the building process more visible, and the other puts that work more directly in the spotlight.
That is the most valuable part of Rialo’s tweet to me. Not just that they are running events, but that the community is showing up to them more and more over time.
Note: This is not a paid partnership or an ad. I only enabled the label because I tagged @RialoHQ@RialoTR
When we launched Builder's Hub in mid-January, 120 people showed up. No incentives. No giveaways. Just builders from the community.
We thought that was a great start. Then it kept going.
Jan → 120 | Feb → 250 | Mar → 300 | Apr → 360 | Today → 475 🔥
Every single month the community has broken the record.
We also launched Shark Tank, a bimonthly event where community builders pitch, answer tough questions, and prove they belong. Started at 250 attendees. All-time high: 685.
All organic. All community-driven.
Get Real. Get Rialo.
gRialo friends, If you want to build a strong onchain finance product, the data layer has to be strong too.
Because if the data you use for pricing, valuation, and risk calculations is weak, the product built on top of it will hit a ceiling sooner or later. In financial apps especially, data quality directly shapes product quality.
That is exactly what @RialoHQ's latest post is pointing to. Alongside Subzero Labs being featured in @CBOE’s Innovation Spotlight, the bigger story is that Cboe’s EDGX market data is being integrated into the Rialo ecosystem.
What makes that important is that Cboe is not some random data source. It is a major exchange network that institutions already rely on. So the message here is pretty clear: Rialo wants institutional grade market data to feel like a built in part of the infrastructure.
And that matters.
Because the goal is not to make developers build data pipelines from scratch every time. The idea is that high quality market data should already be there, so teams can spend less time cleaning and stitching data together, and more time actually building products.
That is especially important for trading, fintech, and more serious financial applications. Because this is not just about putting a price on a screen. Pricing engines, valuation models, and decision systems all need reliable data underneath them.
Another interesting part is how they are framing the EDGX feed. Not as some outside add-on you plug in later, but as a native layer inside the network that developers can access while building.
So this is not just a “new partner” announcement.
The bigger point is that Rialo wants to make real world market data more accessible for onchain applications at the infrastructure level.
And if stronger financial apps are actually going to be built onchain, this is one of the layers that really matters.
Note: This is not a paid partnership or an ad. I only enabled the label because I tagged @RialoHQ@RialoTR
We are proud to share that Subzero Labs (Rialo) has been featured in the @CBOE Innovation Spotlight.
CBOE (Chicago Board Options Exchange) is one of the world's largest derivatives and securities exchanges, handling 3.8 billion options contracts a year and powering $45B+ in daily FX volume. We are integrating CBOE's high-fidelity market data directly into Rialo, giving developers building on Rialo access to institutional-grade financial data as a native part of their onchain applications.
This is what it means to build neofinance infrastructure seriously: the data that institutional markets run on, available to developers building financial applications onchain. With market data from the likes of @CBOE provided natively, developers on Rialo can build sophisticated, data-rich applications without relying on third-party infrastructure or building custom data pipelines.
Rialo takes care of the data so developers can focus on building world-class apps.
Read the full spotlight: https://t.co/QuDtYgNbsT
gLiquid friends, big update from @liquidtrading. The team just announced a new $18M raise, which brings total funding to over $25M.
But the real thing that stands out here isn’t just the amount. It’s the vision behind it.
Liquid isn’t trying to be just another crypto trading app. The goal is to build a mobile first trading experience that gives people access to equities, preIPO exposure, prediction markets, commodities, FX, and crypto in a more unified way. So this is bigger than just “come trade something.” The bigger play is bringing different markets into one product experience.
Based on the numbers they shared, Liquid reached 40k traders, 120+ countries, and $3B+ in volume in just 7 months after launch. That shows it’s not just an idea on paper anymore. People are actually using it.
On the investor side, Neo and Left Lane Capital stand out in this round. And seeing names like Paradigm and General Catalyst still in the picture also says a lot about the confidence behind the project.
That’s the part that matters most here. Liquid isn’t trying to stay stuck in one lane. It’s trying to bring together the different markets traders already move through during the day. Instead of crypto in one place, prediction markets somewhere else, commodities somewhere else, and stocks in another app, the goal is to make that experience feel more connected.
Note: this is not a paid partnership or an ad. I only turned on the paid partnership label because I tagged
@liquidtradingfor the event.
Today, we're announcing an $18 million Series Seed, led by @neo and @leftlanecap, with continued support from Paradigm, General Catalyst, and other top VC firms — bringing our total raised to over $25 million.
gRialo friends, with AI agents, the issue is not just intelligence anymore. Trust matters just as much.
Because you can already give an agent a task.
You can make it pay for things.
You can make it pull data.
You can even let it use other tools.
But the real question is this: What exactly is this agent allowed to do, and what is off limits?
Think of a simple example.
A sales agent can pull lead data for you.
Cool.
But can that same agent also spend money from your wallet?
Can it cancel a subscription?
Can it send a payment to someone?
And if it can, does it hit a limit?
That is where the real issue starts.
That is also what the a16z piece is getting at. What the agent economy is missing is not just better models. Identity, permissions, payments, verification, and trust infrastructure matter just as much.
For an agent, things like this need to be clear:
- who it represents
- what boundaries it operates within
- how much it is allowed to spend
- where responsibility sits if it makes a mistake
- why another system should trust it in the first place
And this is exactly where @RialoHQ is putting the spotlight, especially on permissions and guardrails.
The simplest way to read their point is this:
You cannot just hand an agent the keys and hope for the best. You also need to code the limits around what it can do.
So an agent might:
- use only certain tools
- never spend more than $100
- ask for extra approval on sensitive actions
- interact only with specific addresses
That is basically where their idea of programmable authority is going.
So the question is not just “does the agent work?”
The real question is: how controlled is the agent while it works?
That is why the conversation is slowly moving away from model quality alone and toward infrastructure.
A smarter agent can be useful.
But an agent with no clear limits is risky.
So the bigger takeaway is this:
The AI agent era probably will not be unlocked by intelligence alone.
The real shift will come from infrastructure that makes identity, permissions, and trust much more solid.