Kevin

@typedarray.eth

460 Following

185343 Followers

Kevin pfp

@typedarray.eth

We still don't really know - it got suddenly banned for violating Telegram's ToS citing "illegal goods". Never got through to a human being despite many attempts through their support and abuse channels. Also searched for alternatives that would deliver an on-par experience but came up short.

0 reply

0 recast

1 reaction

Kevin pfp

@typedarray.eth

It's a community chat for an open-source framework that I work on called Ponder (https://ponder.sh)

1 reply

0 recast

2 reactions

Kevin pfp

@typedarray.eth

Created a new Ponder chat including full history from the old one - come say hi! https://t.me/pondersh

8 replies

12 recasts

109 reactions

Kevin pfp

@typedarray.eth

0 reply

0 recast

2 reactions

Kevin pfp

@typedarray.eth

I'm a fan. Though I did just notice that they ripped off linear's landing page design. Can't really blame them, but funny to see.

1 reply

0 recast

1 reaction

Kevin pfp

@typedarray.eth

Love to see it!

0 reply

0 recast

1 reaction

Kevin pfp

@typedarray.eth

Telegram banned our group, still don't know why and haven't heard back from support. Working to get us back online. DM me here or on telegram with any questions / issues. Context: https://warpcast.com/typedarray.eth/0x1a5ba3d3

1 reply

0 recast

1 reaction

Kevin pfp

@typedarray.eth

0 reply

0 recast

0 reaction

Kevin pfp

@typedarray.eth

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 replies

12 recasts

42 reactions

Kevin pfp

@typedarray.eth

Honestly no! It's optimized for humans.

1 reply

0 recast

1 reaction

Kevin pfp

@typedarray.eth

Started with the most viewed page https://ponder.sh/docs/contracts-and-networks Have learned a lot about user expectations in the past ~6 months - can improve the way we present information accordingly.

0 reply

0 recast

0 reaction

Kevin pfp

@typedarray.eth

Yes, was not a fan the 4.0 release - direction and design feels off. You can probably guess which docs tool we're using this time ;) (though we're also improving the IA, rewriting, etc)

0 reply

0 recast

1 reaction

Kevin pfp

@typedarray.eth

Just finished the first page of Ponder's new docs website

7 replies

3 recasts

45 reactions

Kevin pfp

@typedarray.eth

Before you upgrade, *please* read the migration guide. This release includes a database migration to the `ponder_sync` schema that can lead to downtime. That's it - enjoy! Migration guide: https://ponder.sh/docs/migration-guide#010 GitHub: https://github.com/ponder-sh/ponder Chat: https://t.me/ponder_sh

0 reply

0 recast

0 reaction

Kevin pfp

@typedarray.eth

We also improved the behavior around a common RPC provider bug where eth_call requests incorrectly return `0x` near tip. While this is a "success" response, it's best to retry it a few times. The latest addition to a long list of RPC quirks we've found and handled.

1 reply

0 recast

0 reaction

Kevin pfp

@typedarray.eth

The new `event.id` property is a globally unique ID for a log, transaction, block, or trace that works across all chains. For tables that don't have a logical unique constraint, `event.id` is a good option for primary key values.

1 reply

0 recast

0 reaction

Kevin pfp

@typedarray.eth

In 0.10, filtering runs entirely in-memory, with the address list cached in the database to avoid refetching. Our Uniswap V3 factory benchmark got 3.6x faster with this release. Now, there's ~zero overhead to indexing huge factories - very happy with where we landed.

1 reply

0 recast

0 reaction

Kevin pfp

@typedarray.eth

Ponder's factory pattern collects a list of addresses from decoded event logs, then plugs that list anywhere in your config. Before this release, the address list was built on-the-fly and filtering ran in SQL. This didn't scale well.

1 reply

0 recast

0 reaction

Kevin pfp

@typedarray.eth

Ponder 0.10 This release speeds up large factories and contract reads, adds a new `event.id` property, and fixes several reliability issues →

1 reply

3 recasts

34 reactions

Kevin pfp

@typedarray.eth

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? https://promlabs.com/promql-cheat-sheet/

1 reply

1 recast

14 reactions