Luxy

hadeh nggak ngapa-ngapain kena ghost ban

[Luxy @Kerasakit00]

One reason I'm interested in joining AGP is that it focuses on something AI agents will eventually face in the real world: operating within constraints.

In practice, agents won't have unlimited budgets or unlimited compute. They'll need to decide when to spend resources, when to wait, and how to achieve the best outcome with what's available.

That's what makes this challenge interesting to me.

Instead of rewarding brute force, AGP encourages participants to think about strategy, efficiency, and decision making. A well designed agent isn't just one that produces the right answer it also knows how to use its resources wisely.

I'm looking forward to experimenting with different prompting approaches, refining how an agent manages its budget through Latch, and learning from how other participants tackle the same challenges.

Curious to see which strategies perform best once the race begins. 🏁

[Subzero Labs @Subzero_Labs]

▀▄▀▄▀ Welcome to Agent Grand Prix (AGP) ▀▄▀▄▀

You don’t win a Formula 1 race by being the fastest car or buying up all the gas. Throwing every resource at your agent doesn’t work either. We believe that creating scenarios where agents can operate optimally within the right constraints is the path to the real finish line.

Agent Grand Prix puts Latch in action. Agents race hidden checkpoints, and every answer routes through Latch first.

Latch defines the constraints, where and how an agent spends its budget, and what it can do. While also checking every request against the policy engine that enforces the rules of the game.

Smart prompting, efficiency under a fixed cap, is what gets you to the FIN.

[Luxy @Kerasakit00]

What I like about AGP is that it doesn't reward the biggest budget.

It rewards how well an agent operates within constraints.

That's a much more interesting way to evaluate autonomous systems than simply throwing more resources at the problem.

Curious to see the different strategies builders come up with. 🏁

[Subzero Labs @Subzero_Labs]

▀▄▀▄▀ Welcome to Agent Grand Prix (AGP) ▀▄▀▄▀

You don’t win a Formula 1 race by being the fastest car or buying up all the gas. Throwing every resource at your agent doesn’t work either. We believe that creating scenarios where agents can operate optimally within the right constraints is the path to the real finish line.

Agent Grand Prix puts Latch in action. Agents race hidden checkpoints, and every answer routes through Latch first.

Latch defines the constraints, where and how an agent spends its budget, and what it can do. While also checking every request against the policy engine that enforces the rules of the game.

Smart prompting, efficiency under a fixed cap, is what gets you to the FIN.

[Luxy @Kerasakit00]

Real world assets are often described as one of blockchain's biggest opportunities.

But tokenizing an asset is only the first step.

Once an asset exists on chain, it still needs an environment where it can interact with other applications, respond to real-world events, and integrate into broader financial workflows.

Without that foundation, tokenization alone doesn't unlock its full potential.

That's one reason Rialo's approach stands out to me.

Rather than focusing only on asset issuance, the project explores infrastructure that brings together execution, automation, external connectivity, and privacy into a more unified environment.

For developers, that could mean spending less time assembling supporting infrastructure.

For institutions, it could provide a more practical foundation for applications that need security, compliance, and interoperability.

As interest in RWAs continues to grow, the conversation may gradually shift from "How do we tokenize assets?" to "How do we make those assets useful once they're on-chain?"

To me, that's where infrastructure becomes just as important as the assets themselves and it's an area where Rialo is exploring an interesting direction.

[ade | rialo.io @itachee_x]

The internet's access model was built for humans.
Passwords. Sessions. API keys. OAuth tokens. Wallet keys.
Different shapes, same assumption: if you hold the secret, you can act.
That assumption breaks when the actor is software.
Early access is open: 👉 https://t.co/BtYLOQoLvH

[Luxy @Kerasakit00]

The best technology often goes unnoticed.

Not because it lacks capability,

but because it removes unnecessary complexity from the experience.

In Web3, developers often spend as much time managing infrastructure as they do building applications.

External services.

Automation.

Data integrations.

Different components that all need to work together.

That's one aspect of @RialoHQ that I find interesting.

Rather than adding more layers around blockchain, Rialo explores ways to make core capabilities work together within the infrastructure itself.

The goal isn't to make blockchain more complicated.

It's to let developers spend more time building products and less time connecting the pieces behind them.

For users, the ideal outcome is simple.

Applications should feel responsive, reliable, and intuitive without needing to understand everything happening under the hood.

As blockchain infrastructure continues to evolve, the biggest improvements may not always come from adding new features.

Sometimes they come from reducing friction and making complex systems feel effortless.

That's a direction from Rialo that I think is worth following.

[Luxy @Kerasakit00]

A lot of blockchain interactions still follow a simple pattern:

Send a transaction → wait for everything to finish → continue.

That works for basic transfers.

But real-world applications often need something more flexible.

Think about applications interacting with:

• APIs
• AI services
• payment systems
• enterprise databases
• cross-chain messaging

These processes don't always return results instantly.
This is where asynchronous execution becomes interesting.

@RialoHQ treats async transactions as part of the architecture itself rather than something developers need to build around manually.

A contract can initiate a request, continue operating, and receive the result later through a callback once the task is completed.

The practical benefit is fairly straightforward:

less waiting,
more parallel workflows,
and applications that can respond to external systems without unnecessarily blocking execution.

This model seems particularly relevant for automation, AI agents, event-driven applications, and workflows that involve multiple steps across different environments.

As blockchain adoption moves beyond simple transfers, execution models may need to look more like modern distributed systems.

That's one of the ideas behind Rialo's async architecture that I find worth paying attention to.

[Luxy @Kerasakit00]

One challenge in public blockchains isn't always speed.

Sometimes it's what happens before a transaction is even confirmed.

Pending transactions are often visible before they're included in a block.

That visibility can create opportunities for bots or other participants to react before execution takes place.

It's one of the reasons topics like MEV and front-running continue to receive so much attention.

While exploring @RialoHQ , I found its approach to encrypted transaction handling particularly interesting.

By using technologies such as Distributed Key Generation (DKG), transaction details can remain encrypted while waiting to be processed.

This means validators can determine transaction order without immediately seeing the underlying contents.

Only after the order is finalized can the encrypted data be collectively decrypted for execution.

The broader idea isn't simply adding another security feature.

It's creating a fairer execution environment where transaction ordering is less influenced by visible information before confirmation.

As blockchain infrastructure evolves, protecting users may involve more than securing private keys.

It may also involve designing execution systems that reduce opportunities for unfair advantages before a transaction is even processed.

[ade | rialo.io @itachee_x]

Some alpha: SCALE (see @chunliweb3 demo) is being integrated into https://t.co/BtYLOQoLvH meaning multi-agent coordination as a first class primitive.

https://t.co/zcZLSQp0mx

[Luxy @Kerasakit00]

For a long time, Web3 has asked users to adapt to blockchain.

New wallets.
Extra steps.
Multiple services running behind the scenes.

Maybe the better question is:
How can blockchain adapt to the way people already use the internet?

That's partly why Rialo's direction is interesting to me.

The project explores infrastructure where real-world data, web interactions, automation, and execution can work together more natively.

The practical benefit is fairly simple:

less infrastructure to assemble,
fewer moving parts to coordinate,
and potentially less friction for developers.

Because complexity doesn't only affect builders.

Eventually, users feel it too.
Slow onboarding.
Disconnected experiences.
Applications that feel harder to use than they should be.

If blockchain infrastructure can become more integrated, applications may start feeling less like "crypto products" and more like regular internet services that happen to use decentralized systems underneath.

It's still early, and many ideas remain to be proven.

But reducing friction between real-world activity and on-chain execution feels like a direction worth paying attention to.

That's one aspect of Rialo that I find particularly interesting.

[Luxy @Kerasakit00]

Blockchain security requirements are starting to look very different from a few years ago.

Treasury management, AI automation, RWAs, and institutional applications often involve multiple participants making decisions together.

In these environments, security isn't only about protecting a wallet.

It's also about managing authorization and coordination.

This is one reason @RialoHQ 's native multisig approach is interesting.

Rather than relying on fragmented tooling around the chain, multisig can become part of the infrastructure itself.

Features such as:

• configurable approval rules
• role-based permissions
• asynchronous execution
• reactive transaction

allow organizations to design workflows that fit different operational needs.

The idea extends beyond treasury management.
Similar models could be useful for DAO governance, enterprise approvals, asset custody, and automated systems that require multiple layers of authorization.

As blockchain applications move into more complex environments, programmable collaboration may become just as important as transaction execution itself.

That's where Rialo's approach seems to be heading: exploring infrastructure where security, coordination, and governance work together more naturally.

[ade | rialo.io @itachee_x]

Turns out many of you were interested in why agents need new primitives in order to scale.

Thanks to our community for showing up today!

Huge shoutout to the builders who got their hands on Latch early and submitted bugs and feature requests!

https://t.co/BtYLOQoLvH is on 🔥

[Luxy @Kerasakit00]

As blockchain use cases move beyond DeFi, the infrastructure requirements start to look very different.

Real-world finance, AI systems, and enterprise applications need more than transaction execution alone.

They require access to external data, private computation, automation, and stronger security controls.

This is where @RialoHQ 's architecture becomes interesting.

Different components are being developed to support different needs:

• Web2 connectivity for interacting with external services and real-world data

• Confidential computation for processing sensitive information while preserving verifiability

• Efficient verification mechanisms for more complex workloads

• Agent management frameworks that allow automation to operate within predefined boundaries

• Additional security layers for treasury and multi party operations

Individually, these capabilities solve different challenges.

Together, they point toward infrastructure designed for applications that need privacy, coordination, and automation operating side by side.

As Web3 continues to mature, it seems increasingly likely that real world applications will require environments that bring these capabilities closer together rather than treating them as separate systems.

[ade | rialo.io @itachee_x]

Latch is coming.

Tomorrow at 16:30 UTC (12:30PM ET) I'll be on the Rialo Discord stage talking through why agents need new primitives

Latch gives agents real authority, with proper oversight, enforced in hardware, with deep audit trail

Bring questions
https://t.co/BtYLOQoLvH

[Luxy @Kerasakit00]

A lot of blockchain discussions focus on performance.

Faster transactions.
Lower fees.
Higher throughput.

But lately I've been wondering if execution speed is only part of the equation.
Most blockchains are designed to process instructions once certain conditions are met.

The network verifies the transaction.

Then execution happens.

What interests me about @RialoHQ is that it explores a broader execution environment.

One that combines:

• external data
• confidential computation
• automation
• cross-system coordination
• programmable verification

within the same infrastructure.

Because many real-world applications don't operate in isolation.
They depend on information, events, and conditions that exist beyond the blockchain itself.

As systems become more automated, the challenge may not simply be executing actions correctly.
It may be ensuring those actions are informed by the right context before they happen.

That's one reason Rialo's architecture stands out to me.

It's less about making existing blockchain workflows faster,

and more about expanding what blockchain execution can interact with in the first place.

[Action Model @ActionModelAI]

Action Model is built on a simple idea:

If AI is being built using human data...

Humans should own part of it.

Here's the ecosystem in 30 seconds:

• Install the browser extension
• Train a community-owned AI model through your online actions
• Earn points for contributing data and completing specific ActionFi tasks
• Invite others and help grow the network
• Unlock early access to AI products
• The model gets smarter as the community grows
• The people helping build it share in the value created

That's it.

Instead of training AI for Big Tech for free...

Help build a model owned by the people.

[Luxy @Kerasakit00]

1 idea from Rialo that caught my attention is that blockchain costs don't always come from the transaction itself.

A lot of the complexity happens around the transaction.

Oracles.
Automation.
External data.
Web integrations.

Each service helps, but every additional layer also adds more dependencies to manage.

@RialoHQ explores a different approach by bringing key infrastructure closer to the protocol layer.

Instead of stitching together multiple external services, developers can rely on a more integrated environment for execution, automation, and data access.

The interesting part isn't just reducing complexity.

It's making infrastructure work together more naturally.

As Web3 evolves, better coordination between core services may matter just as much as faster transactions.

[Action Model @ActionModelAI]

JD Vance just admitted the White House could take ownership of every major AI company in the US.

Why?

Because even governments are starting to realize the same thing:

AI will create trillions in value, and at this rate, only a few Big Tech companies will benefit.

Right now, billions of people are training AI every day through their data, actions, and online behavior.

Yet almost all of the value flows back to a few billionaires and shareholders.

That doesn't seem fair.

At Action Model, we're building a different future.

A people-owned AI model where those helping train it can share in the value they help create.

If AI is built by the people, it should benefit the people too.

Sign up to the Action Model movement and join the 500k+ users already contributing to a community-owned AI.

[Rialo @RialoHQ]

Dario Amodei: AI Policy
> AI is progressing extremely fast, much faster than the policy process was built to handle, and the gap between the two is becoming the central challenge of the technology.

This is why we built https://t.co/P12bb0WAq7

https://t.co/FI4muydS57

[Luxy @Kerasakit00]

One thing I've always found interesting about blockchain is how isolated it can be from the systems people use every day.

Most real world activity already happens through APIs, online services, databases, and digital platforms.

Yet many blockchain applications still struggle to interact with that information efficiently.

That's one reason Rialo caught my attention.

Rather than viewing on chain and off chain environments as separate worlds, Rialo explores ways to make them work together more naturally.

External data.

Web services.

Automated workflows.

Real world events.

All becoming part of a more connected execution environment.

This opens interesting possibilities for things like:

• financial workflows
• business operations
• RWAs
• automated settlements
• event driven applications

Because many useful applications don't only need blockchain data.
They also need the ability to react to what's happening outside the chain.

As Web3 continues to mature, I think the challenge isn't simply bringing more people on chain.

It's building infrastructure that can interact with the systems people already use every day.

That's one of the ideas behind Rialo that I find particularly interesting.
#Moots

[Luxy @Kerasakit00]

2 kartu merah

[Luxy @Kerasakit00]

Wahh Canada pesta goll