3 years ago, we shipped a leaderboard you had to mint.
Mad Wars for Zeta (now @Bulletxyz) ran as an xNFT inside Backpack: a mad board for the top teams, team rankings, and a global board ranking traders by volume and ROI.
3 months from start to live.
@0xeddiekim@0xeddiekim they don't carry over. the schedule on our bonding curve ends at migration. on the new meteora damm v2 pool, a separate scheduler starts at 50% and decays to about 1.99%, then stays there.
https://t.co/j9sovi6qps was an 18-month build for us.
Every compound gets its own token, and trading it funds lab work: worms, then flies, then mice.
We built the contract with dynamic fees against bots, and liquidity moves to Meteora by itself at set milestones.
Solana teams: if your dApp works on devnet but mainnet is where it falls over (dropped txs, RPC limits, wallet edge cases), that's the work we like.
We've shipped on Solana since 2022: an on-chain royalty program, a Grizzlython-winning xNFT, an open-source dApp scaffold, and many client projects.
Reply what you're building.
Your coding agent starts a dev server, the session ends, the server keeps running.
DevPorts is a Mac menu bar app that shows every dev server and leftover watcher with its project, port, uptime and memory, and stops the one you pick without touching the rest.
$9 once.
Event access should fail at the door, not at the lunch queue.
Three patterns:
1. Check the badge when guests enter the venue.
2. Show what the badge covers before the event.
3. Give staff a manual override for lost or incorrect badges.
Automate the common case. Keep a human fallback for every denial.
Two bots can run the same strategy and trade completely different markets
> one waits for JSON-RPC
> one streams processed state through Yellowstone
> one reconstructs transactions from shreds before normal execution metadata exists
By the time the first bot detects the opportunity, the third may already be pricing its exit.
This is why latency is not merely an execution problem on @solana.
It changes:
โข what your strategy can see
โข when it can decide
โข whether the opportunity still exists
The data path is part of the alpha
We opened @rpcedge for more traders and bot builders!
Start for free, scale up as you need.
Serious builders can apply for a 3-day Desk trial to compare setups and optimize edge.
Start today:
One bot. One prompt. It hired its own team.
I created a single Grok Bot - Atlas, chief of staff - and pasted one prompt. It interviewed me, wrote its own operating manual, specced four teammates, and launched them. Watch the sidebar: Kit, Studio, Ship, Peak come online one by one.
Each of them gets its own computer in the cloud. Six routines scheduled. The team runs while my laptop is closed.
And nothing sends, posts, or ships without my yes. That rule is in the prompt.
Full setup prompt in the first reply. Steal it.
I have open-sourced a lot of my work.
That does not mean I think everything should be free.
Open-source and paid products have different roles.
I open-source infrastructure that builders can inspect, extend, and run themselves.
Mission Control makes agent work visible.
Agent Security puts explicit boundaries around agent execution.
Council of High Intelligence turns difficult decisions into a multi-model process instead of trusting one answer.
Each project started with a problem I encountered while building.
Publishing the code lets other builders test the assumptions, expose missing cases, and decide whether the work is useful without asking for permission.
That feedback is more valuable than building privately for months and announcing something nobody needs.
But open source alone is not a business model.
People still pay for outcomes that remove work or risk:
โข Reliability they do not have to operate themselves
โข Workflows they can use immediately
โข Knowledge packaged around a specific problem
โข Support when something breaks
โข Infrastructure with clear operational responsibility
That is where the products come in.
@rpcedge is a bet that teams building onchain applications and agents will pay for a more dependable data path.
My digital products package repeatable knowledge and workflows so someone can get the result without hiring me for a custom project.
@builderzdotdev helps founders when the problem cannot be solved by a template or self-serve tool and still requires hands-on product work.
These layers feed each other.
Services expose painful edge cases.
Open source makes the solutions inspectable.
Content distributes the lessons.
Products turn repeatable solutions into something sustainable.
I am not trying to monetize every repository.
I am building a system where the free work proves what I can build, and the paid work solves problems people do not want to operate alone.
Open source creates trust.
Customers test whether that trust can become a business.
I've been using Grok Build as the daily driver lately.
I love it.
The TUI is what did it. Plan mode, the diffs, previews, being able to use the mouse.
Other agent CLIs I open get the job done, and I want out.
This one I could watch the goal and loop spinners forever.
What's your favorite?
I open-sourced a way to stop asking one AI to be right.
Council of High Intelligence turns hard decisions into an adversarial process:
โ 18 distinct reasoning lenses
โ independent first positions
โ forced cross-examination
โ FACT / INFERENCE / ASSUMPTION / UNKNOWN labels
โ weighted final stances
โ dissent stays visible
โ kill criteria + one concrete next action
And it runs across Claude Code, Codex, Gemini CLI & OpenCode, Grok, Hermes and more.
The important part isn't adding more agents.
It's making them disagree before they converge.
Because 10 agents repeating the same reasoning path is still one opinion with 10 token bills.
For your next expensive or irreversible decision, don't ask:
"What's the answer?"
Ask:
"What would have to be true for this answer to be wrong?"
That's what the council is built to surface.