Pinned
Introducing Marble.
Marble is a platform for offchain software, built by the team behind Ponder.
We're making it radically easier to build fast & reliable backend systems for crypto apps.
28
47
306
Created a new Ponder chat including full history from the old one - come say hi!
7
9
55
Anyone have experience getting a (legitimate) Telegram group unbanned?
The Ponder chat (support, feature requests, etc for an open-source tool) got banned last night. No idea why. We have 600+ members, it's a key support tool for us - appreciate any leads immensely.
5
15
33
Ponder 0.10
This release speeds up large factories and contract reads, adds a new `event.id` property, and fixes several reliability issues →
1
2
12
I find the Prometheus data model intuitive (counter gauge histogram + labels), but the PromQL side of things (instant vs range vectors, series, etc) has never clicked.
Even on this cheat sheet, the return type / shape of each statement is not obvious to me. Feels strictly worse than SQL - what am I missing? Skill issue?
1
17
Is anyone using Tailwind v4.0 ? Required browser versions seem rather recent.
tailwindcss.com/docs/compati...
4
2
26
The TypeScript team is rewriting the compiler in Go. Incredible news.
5
4
27
If you choose a chain ID greater than Number.MAX_SAFE_INTEGER for your chain, call me. There's something I'd like to say. Best not in writing
4
8
39
2
11
Use this one WEIRD trick to differentiate ANY shadcn/ui slop website
Designers hate it!
3
3
29
Going all-in on Postgres was the single best decision we made in 2024.
Much simpler, with no regression to the quickstart / local dev experience (thanks to PGlite). Obvious in retrospect.
6
1
45
Goal: By the end of 2025, even the largest Ponder app backfills will be fast enough to run in CI. Seconds or minutes, not hours or days.
It should feel like a build or reload, not a "backfill".
4
2
33
Ponder 0.9.3 adds a new event ordering strategy designed for low-latency apps that index 10+ chains.
The current ordering strategy is “omnichain” - events across all chains share a single queue, with blocks ordered by (block timestamp, chain ID, block number).
2
2
28