Architecture-first engineering for AI & Web3. From inception to production: AI apps, smart contracts, audits, fractional CTO. Senior team with real ownership.
Argentina
Joined March 2022
- Tweets1.9K
- Following50
- Followers1.4K
- Likes696
Pinned Tweet
Now more than ever, the Web3 world demands education and thoughtful leadership as we drive its evolution. Our blog and innovation newsletter break down the latest in blockchain, AI, and everything in between—insights, trends, and deep dives, straight to you.
Join us: ratherlabs.com/blog
Rather Labs retweeted
Cloudflare has open-sourced Cloudflare OS, solving the problem that kills most enterprise AI projects: how to give agents access to internal systems without losing control over your data.
In this post, we break down the full architecture:
- Cloudflare OS as the permissions boundary
- Castform for proprietary specialized models
- Neon for the retrieval layer
Link: ratherlabs.com/blog/enterpri…
Rather Labs retweeted
Why do AI systems sometimes state something false with total confidence?
Often it is not the model, it is the data layer.
For an AI to look things up, the usual setup keeps your data in one place and your search engine in another, syncing all the time. When they drift apart, the AI does not warn you: it answers with stale data, and it does so with total confidence.
Neon just moved search inside the same database where the data already lives. One place, one query, nothing to sync. And since the index no longer lives in memory, the database shuts itself down when nobody is using it and stops costing money.
In the link I explain why we chose this at @rather_labs and how we are applying it across the products we build.
ratherlabs.com/blog/database…
Vibe-coded MVPs don't break randomly. They degrade on a predictable schedule.
Here's what happens to a codebase over 1,000 prompts with Cursor, Lovable, or Bolt. 🧵
Prompts 700–1,000: the things you can't see.
Security gaps at the seams. Business logic scattered across the database, the API, and React components. A schema that made sense at prompt 10 and creates friction at prompt 1,000.
A scan of 1,600+ Lovable apps found 170+ leaking user data: not edge cases, just standard output.
None of this means vibe coding was a mistake.
You validated an idea fast, that's the point. But what you built is a concept, not a production foundation yet.
The real next step is understanding what you actually have.
Full breakdown ratherlabs.com/blog/what-hap…
We’ve been building Launkr.io, a token launcher for @Stacks
Alongside our human-led marketing efforts, we’ve also registered our AI agent, Solemn Owl, on @aibtcdev (Claim code: 3K23AF).
He’ll be running our agent-to-agent marketing campaigns across the #AIBTC ecosystem 🚀
Welcome to the team, Solemn Owl!
For a decade, "build or buy?" had one answer: buy.
AI-assisted engineering just changed the math: it cut the cost of a custom build by ~90% and the timeline by ~80%.
Which is exactly why a lot of teams are about to make an expensive mistake. 🧵
That last part — owning it — is where most teams get burned.
The build was never the hard part. Keeping a system running, secure, and compliant costs several times what it took to build. Cheap to build + nobody to maintain isn't a saving. It's a liability with a delayed invoice.
So build. But build responsibly, with a team that owns what comes after launch.
Full framework → ratherlabs.com/blog/build-vs…
Weighing a specific process? → ratherlabs.com/custom-softwa…
Live from the @StacksEndowment account!
Our very own @sebastrosen will be presenting Launkr.io, our ongoing project built on @Stacks
Tune in, and feel free to reach out if you have any questions about the platform!
xitter.cf/i/spaces/1XxyggpvqPZGM…
AI agents are launching their own tokens.
On Ethereum, @bankrbot and @clanker_world already showed how big this can get.
@Stacks deserved its own version, one that actually fits the Bitcoin economy.
That's launkr.io/ our latest product for Stacks!
🧵👇
Rather Labs retweeted
Checking the public Stacks grants tracker offers a clear view of how early-stage funding is being executed on the network.
Unlike many grant programmes that announce capital and then go quiet
The @Stacks Getting Started Grant shows teams progressing through structured milestones in a fully transparent public tracker.
The below teams have been actively working through defined deliverables.
Here is a summary of what these teams are currently building and the status of their milestones:
───────────────────
➥ @rather_labs | LAUNCH - STX (Stacks Strategy Protocol)
Category: DeFi
Description:
Stacks Strategy Protocol is building programmable token and liquidity primitives on Stacks, including restricted SIP-010 token logic and treasury-driven liquidity pool infrastructure.
The goal is to deploy these primitives to mainnet and make them usable by external builders and DAOs to bootstrap structural token and liquidity strategies.
───────────────────
➥ @FlashStackBTC | FlashStack
Category: DeFi
Description:
FlashStack is building flash loan infrastructure on Stacks to support advanced DeFi use cases such as arbitrage and capital-efficient transaction execution.
The project aims to deploy production-ready flash loan primitives to mainnet so external developers and users can execute live flash loan strategies on Stacks.
───────────────────
➥ @flowvault | FlowVault
Category: DeFi
Description:
FlowVault is building programmable contract infrastructure on Stacks that allows builders to create advanced, non-custodial asset routing flows, such as time-locked splits and multi-signature payouts.
The purpose is to provide reusable on-chain primitives that external developers can integrate into wallets, dApps, and protocol workflows.
───────────────────
➥ @SSEProtocol | Stacks Stablecoin Engine
Category: DeFi
Description:
Stacks Stablecoin Engine is building a collateralised debt position (CDP) and stablecoin infrastructure layer on Stacks.
This includes vaults, liquidation logic, and stability mechanisms backed by assets like stSTX.
The goal is to deploy this core stablecoin engine to mainnet and make it usable by external builders, integrators, and early participants.
───────────────────
➥ @VelumXProtocol | VelumX
Category: Payments
Description:
VelumX is building gasless transaction infrastructure on Stacks, enabling users to pay fees in SIP-010 tokens rather than STX.
This is achieved through a paymaster contract, relayer service, SDK, and developer tooling to deploy this infrastructure to mainnet and support real sponsored transaction usage by live applications.
───────────────────
➥ @VoltFiLabs | VoltFi
Category: DeFi
Description:
VoltFi is building a yield vault on Stacks that allows users to deposit USDC, receive a vault receipt token, and participate in a yield-generating strategy with transparent accounting and on-chain distribution.
The goal is to launch the vault on mainnet, activate the yield engine and TVL, and complete an initial distribution cycle.
───────────────────
➥ @x402stacks | x402 Stacks
Category: AI
Description:
x402 Stacks is building payment and monetisation infrastructure on Stacks for APIs and services, including facilitation, analytics, and subscription tooling.
The purpose is to expand the product into a broader commercial infrastructure layer, support outside deployments, and increase paid usage and transaction volume on mainnet.
───────────────────
The Stacks ecosystem is supporting early-stage builders through a milestone-driven and publicly visible process.
This approach provides clear visibility into execution and helps new teams move from concept to deployment with structured accountability.
AI agents are launching their own tokens.
On Ethereum, @bankrbot and @clanker_world already showed how big this can get.
@Stacks deserved its own version, one that actually fits the Bitcoin economy.
That's launkr.io/ our latest product for Stacks!
🧵👇
This is possible because of Clarity. Unlike EVM, Clarity lets you enforce conditions at transfer time, including whether the counterparty is an approved pool.
No forks. No workarounds. Fee capture isn't a suggestion. It's in the token itself.
This is already live on Stacks!
In this article, you'll find transaction links, implementation details, and an end-to-end demo by @sebastrosen.
Check it out and let us know what you think. We'd love to hear your feedback!
ratherlabs.com/blog/protecte…
⚠️ Someone registered ratherlabs.co, cloned our website, and posted fake job listings across multiple platforms.
That wasn't us. We've already taken action.
How to identify real Rather Labs communications:
✅ Domain: always ratherlabs.com
✅ Open roles: ratherlabs.com or our official LinkedIn ✅ No coding challenges or take-home assignments
✅ Emails: always @ratherlabs.com
Questions? → [email protected]
#Scam #RatherLabs #CyberSecurity
