Hacking Gravity 1625
Moon
Joined December 2024
- Tweets1.4K
- Following245
- Followers2.5K
- Likes2.9K
It's finally here! Agents' loving it.
We are open-sourcing blcli: an Agentic Infra Stack, battle-tested at 30M+ user scale.
It allows coding agents like Codex or Claude Code to help manage your whole cloud infrastructure through code, PRs, dry-runs, and deterministic apply workflows. A solid & serious infra that can support to millions of users.
This is a collaboration across multiple teams, the same stack that powers @AlvaApp, @Galxe, @GravityChain, and @ReahPlatform.
Check it out here:
Docs: blbl.gitbook.io/blcli-docs/
blcli: github.com/ggsrc/blcli
Production stack template: github.com/ggsrc/bl-template
Personal account starter: github.com/ggsrc/bl-template…
A common take today is:
AI agents are useful for toy apps and prototypes, but not for serious infrastructure.
The conclusion is wrong, because the issue is not that agents cannot work on real systems.
The issue is that real infrastructure requires a large amount of expert context to get it correct in the first place, and even more context to guide agents through the next 18 months of iteration.
Production infrastructure is not just a few Terraform files or Kubernetes YAMLs.
It includes:
cloud projects
IAM boundaries
networking
VPC / subnet / firewall design
Terraform state and backend management
Kubernetes clusters
cluster add-ons
secrets management
Git-based deployment workflows
observability and telemetry (logs, metrics, traces. All integrated together and ready for your Agents to debug live on your prod env)
databases, often self-hosted for cost efficiency and control
environment separation: stg / beta / prd
operational runbooks
rollback paths
production failure patterns
Most of this knowledge usually lives in senior engineers’ heads, internal docs, shell scripts, Slack threads, old runbooks, and lessons learned from real incidents.
If an agent does not have that context, of course it will build toy infrastructure.
So the real question is:
How do we package production infrastructure expertise into a form that AI agents can read, reason about, modify, and operate safely?
That is what blcli does. At its core, blcli is a CLI tool plus a whole package of best practices of Infrastructure as Code. The key design principle is simple: Agents are already very good at reading and modifying code. So we make infrastructure code-first. The generated repo is intentionally self-explanatory. An agent can open the repo and understand what happened, and what's next.
Who blcli is for?
We built blcli for two types of users.
1. Product teams that need to scale beyond prototypes
The first group is teams building real products that need infrastructure capable of growing beyond the prototype stage. These teams want the speed of AI-assisted development, but they cannot afford toy infrastructure.
2. Frontier labs and agent teams building self-improving systems
The second group is frontier labs, data companies, and agent teams that need infrastructure not just to run applications, but to train, evaluate, and improve agents.
If you are building coding agents, infra agents, or long-horizon autonomous systems, blcli stack is a good agent harness/env.
Authors:
@SiriJhui @p0pUBhv35I8308 @alvinFu1 @ryan4yin @algoxstonk
Almost two summers ago, we started building in public. On our github github.com/Galxe/gravity-sdk , you can trace the commit history all the way back — the design, the experiments, the walls we ran into (many of them), the rebuilds, and the iterations that followed.
Funny thing is, this period also happened to overlap with the moment when coding agents began to reshape software engineering. You can see that shift: how AI-assisted coding becoming part of how software is built. But even as AI coding agents have become incredibly powerful, building a production-grade blockchain is still not something that can be easily handed off to an “agent.” When it comes to security, stability, and engineering quality, there is almost no room for sloppiness. It remains a precise, serious, and long-term engineering effort.
Gravity stands on the foundation of many great open-source projects. We built on Reth, and we are probably one of the external teams that contributed to its performance optimization. Thank you to the @paradigm @ithacaxyz @gakonst team for their help and recognition. We are also grateful to @Aptos — its elegant design and high-quality code are an important reason Gravity is able to achieve high performance at the consensus layer. @AptosLabs @AveryChing
Today feels like the end of a prologue, and the beginning of the next chapter.
No matter how the market changes, we continue to believe that blockchain itself will be an essential part of the future world. Maybe today most of the attention is on AI, but when agents truly enter every part of life and business, blockchain may become one of the fundamental tools they cannot operate without.
Gravity L1 is live, marking the next chapter in a journey the Galxe team started with Alpha Mainnet.
Learn about @GravityChain's technical innovations, what's live and what's coming next.
good move, it should, and Gravity does it too
HIP-4 update. This one is big.
Hyperliquid just removed the need for external oracles on prediction markets. The validator set itself is now the oracle.
The same 24 validators that sign blocks every 70ms, secure $3B+ in deposits, and vote bridge withdrawals now deploy and settle prediction markets natively. Automated newsfeed software running as part of regular chain operations. Deployment and resolution through onchain validator vote.
No Chainlink. No Pyth. No UMA. No third party. Closed circuit.
Polymarket uses UMA. Kalshi is centralized. Hyperliquid just made real-world event resolution a native chain function.
Hyperliquid.
1
4
206
Congrats on Reth 2.0! Gravity is also powered by Reth, and we’re excited to keep growing with the ecosystem.
No matter the market, we’re still building — and years from now, people may look back and realize the infrastructure was already ready for what comes next.
Gravity Intern retweeted
We ran end-to-end rigorous stress tests on Gravity Reth and the results were mindblowing.
Gravity Reth delivered substantially higher sustained throughput than we expected from our initial Reth/Geth baselines, even when fully accounting for persistence and network I/O.
Gravity Intern retweeted
🔼 Top 3 On-Chain Revenue Gainers
No speculation. Just chains converting activity into revenue at scale
1️⃣ @GravityChain +245%
2️⃣ @avax +95%
3️⃣ @0xPolygon +87%
See who’s climbing → chainspect.app/dashboard/fin…
Stay Fugly!
THE TIME IS NOW 💋
The official mint page is LIVE.
🔗 fuglys.art/
The gates of chaos are officially open.
ENTER THE FUGLY-VERSE!
Gravity Intern retweeted
Execution clients haven’t been pushed to their limits until now.
Earlier this year, we introduced Gravity Reth, our performance-focused fork that reached 1.5–1.9 gigagas/s and revealed where execution bottlenecks truly live.
Read more about our contributions to Reth below.
Gravity Intern retweeted
Hellooo hoomans 🌀
It’s time to explain why we chose @GravityChain for our experiments
It’s
- fast
- parallel
- a lot of test subjects
and we see uuuuuuu
gremilio are everywhere
gremilio
date saved. how fugly will this get?
Fuglys Mint Price Details are here!
We’ve seen the questions about a free mint — and we get it.
Fuglys is a project built by the community, for the community, not by VCs or hidden backers.
The mint price is what allows Fuglys to exist.
It funds the treasury, supports development, covers on-chain costs, art, infra, and everything needed to turn chaos into something real.
Without it, Fuglys would’ve never been born — and with it, we unlock what comes next.
This isn’t an ordinary mint.
It’s your entry point into the Fugly-Verse.
No second chances.
Once it starts, there’s no rewind 💋
