Labrys

Onchain & AI Product Studio | Est. 2017

[Labrys @Labrys_io]

We just launched the new Labrys site.

After 8 years building blockchain, AI and serious software, it finally reflects who we actually are.

🛠️ Deeply technical
📦 Delivery-focused
🧠 Pragmatic about cutting-edge tech
☀️ Brisbane-based

Built for companies that need real capability, not just prototypes.

https://t.co/lIIR3YlgHr

[Gal Shir @galshirart]

Logo design for @Labrys_io ✨

[Labrys @Labrys_io]

@fede_intern respect Fede 👊

[Labrys @Labrys_io]

@SuperteamAU @toriwest__ @Glasgow_2026 Congrats Tori!

[Labrys @Labrys_io]

@hexens congrats team, very much needed!

[Labrys @Labrys_io]

@PredictEX @base congrats team!

[PredictEX @PredictEX]

Public Mainnet is now live!

PredictEX is a sports prediction market built on @base.

You can trade live World Cup markets and more onchain, climb the leaderboard, and back your takes.

Available to non-US, verified users only.

[Labrys @Labrys_io]

@Jerry94_HC spot on 👊

[Labrys @Labrys_io]

One of our Senior Engineers just admitted that AI killed the job he had in January.

He's not worried about it, and he thinks you shouldn't be either.

https://t.co/DwDSJB7x5O

[Labrys @Labrys_io]

@darrenrogan Mondays are good to re-start the counting 😙

[Farside @farsideapp]

Farside's Public Release is now LIVE!
After a successful beta, we're shipping the full platform:

• Trade on autopilot on both @HyperliquidX and @dYdX
• Email + Telegram notifications for performance updates and alerts
• A simplified grid bot experience with asset-specific leverage controls
• The Farside Points System: earn 1 point for every $100 in trading volume

[ATB | ALL THINGS BLOCKCHAIN @allthingsblock]

We’re excited to welcome @Labrys_io back as a Platinum Sponsor of All Things Blockchain for 2026! 🎉

Since 2017, Labrys has been building innovative blockchain and AI products, helping projects across Web3, fintech, and emerging technologies bring ambitious ideas to life.

[Labrys @Labrys_io]

We're not paid to play in the noise anymore. We're paid to remove it.

Our new brand reflects that: quieter, sharper, more restrained.

https://t.co/EEACDGSYiW

[Independent Reserve @indepreserve]

Are chats with your AI agent private? Can you trust your chatbot not to share your data with others?

#AI #Copilot #privacy
@Labrys_io

[Independent Reserve @indepreserve]

The latest existential threat is that AI is coming for our jobs. But what if it just intercepts the distracting #noise between you and upper management?

#lockin #podcast
@Labrys_io

[Labrys @Labrys_io]

@binji_x rather interested here

[Labrys @Labrys_io]

8/8 If you're standing up indexed infra on a new EVM chain and want a team that's done it before — DMs open.

Full write-up by our Engineer @mjkid0 in the Labrys Blog👇

https://t.co/PMm9iOy4St

[Labrys @Labrys_io]

7/8 The real shift isn't the framework. It's the workflow.

When your indexer runs with the same ergonomics as the rest of your TypeScript stack, you stop dreading it and start iterating on it.

That's the difference between an indexer that works and one that keeps up.

[Labrys @Labrys_io]

6/8 Ponder isn't a universal replacement though.

@graphprotocol still wins when:

→ You need decentralised, censorship-resistant data infra
→ You're forking an existing subgraph from a major protocol
→ Ecosystem maturity matters more than DX

Right tool, right context.

[Labrys @Labrys_io]

4/8 Enter @ponder_sh

Open-source @typescript framework. No YAML. No @AssemblyScript. No manual schemas.

Configuration in one TS file. ABI imported as a constant. Every event name, arg type, function signature is type-inferred end to end.

@DrizzleORM-style schemas.

One source of truth.

[Labrys @Labrys_io]

5/8 What this looks like in practice:

→ Engineers go from zero to deployed indexer in under a day
→ Hot reload drops the feedback loop to seconds → Writes directly to Postgres (join onchain with offchain data, no extra infra)
→ 10-15x faster indexing than Graph Node on some contracts

[Labrys @Labrys_io]

3/8 But the subgraph workflow has friction that compounds under pressure:

→ YAML manifests that duplicate your handlers
→ AssemblyScript (looks like TS, isn't TS)
→ Manual GraphQL schemas drifting out of sync
→ Docker + Graph Node + IPFS + Postgres locally, no hot reload

On a 2-week sprint, this kills velocity.

[Labrys @Labrys_io]

2/8 Every EVM app needs indexed data. You deploy the contracts, then realise the frontend can't read any of it efficiently. So you build an indexer.

For years, that meant The Graph. Battle-tested. Trusted by @Uniswap, @aave, every major DeFi protocol.

It earned its position.