blockscout VS realtime

BlockScout

Blockscout is a great project! https://github.com/blockscout/blockscout

If decentralized means, "run their own blockchain explorer on a PC and always have secure access to their explorer without being tracked", then that includes iquidus explorer, and blockscout, and those were just quickly found with google. Both of those projects have working code and support multiple altcoins (not affiliated). "First" is a wildly incorrect claim.

We are developing a custom version of the BlockScout block explorer which will serve as the Emerald block explorer. It will launch by the end of December.

Any reason why we don't use https://github.com/blockscout/blockscout for the explorer instead of building our own? To me it looks like blockscout already has lots of feature that are missing in the current explorer.

BlockScout

Blockscout is the right solution. However, there is a bug and an open issue: https://github.com/blockscout/blockscout/issues/4203

blockscout team suggests the polygon upgrade to pull/3715 and that might solve the issue. I've added to my open ticket with matic support. I can also see an open ticket surround code verification for Aave linked to the same update in blockscout's github: https://github.com/blockscout/blockscout/issues/3752

You can LISTEN/NOTIFY. Or you can use logical replication and a custom subscriber.[1] Supabase uses the latter.[2]

[1]: https://www.postgresql.org/docs/current/logical-replication....

[2]: https://github.com/supabase/realtime

Supabase Realtime is great for building collaborative applications. You can receive database changes over websockets, store and synchronize data about user presence, and broadcast any data to clients via "channels".

We use :telemetry to collect usage data per tenant for Supabase Realtime.

We do this for rate limiting but it also makes it very easy for us to attach a listener (https://github.com/supabase/realtime/blob/main/lib/realtime/...) which ships these (per second) aggregates to BigQuery (via Logflare), which then the billing team can aggregate further to display and actually bill people with.

Yo :D This is what Supabase Realtime does!

https://github.com/supabase/realtime

Spin up a Supabase database and then subscribe to changes with WebSockets.

You can play with it here once you have a db: https://realtime.supabase.com/inspector/new

Every project is a Postgres database, wrapped in a suite of tools like Auth, Storage, Edge Functions, Realtime and Vectors, and encompassed by API middleware and logs.

Where can I learn more about this? I've been thinking of trying to integrate Supabase Realtime (https://github.com/supabase/realtime) into my Django app (without the rest of Supabase), but I'd also like to keep things even simpler if possible.

Also, what was the reason not to go with Gevent?

I believe #2 was the main driver for the supabase team to build their real-time component: https://github.com/supabase/realtime

Background/announcement: https://supabase.com/blog/supabase-realtime-multiplayer-gene...

As a minor note, one of the linked articles talks about having used RethinkDB for its changefeeds and I made a mental note a bit back that if I ever want that supabase's realtime ( https://github.com/supabase/realtime ) provides something rather like that atop Postgres and I should try that before doing anything clever.