Index Supply pfp

Index Supply

@indexsupply

1 Following
223 Followers


Index Supply pfp
Index Supply
@indexsupply
Here is a power user's tip for querying the logs table directly. Keep in mind: you'll want to add a `block_num` predicate since we don't have an index on tx_hash. This is useful if you want all logs for a specific tx. https://www.indexsupply.net/query?query=select+topics%2C+data+%0Afrom+logs+%0Awhere+tx_hash+%3D+0x856230d65058272c1c53722e758c737f190722523f745b2e62dddcf33ee31179%0Aand+block_num+%3D+26774642&event_signatures=&chain=8453
1 reply
1 recast
7 reactions

Ryan pfp
Ryan
@ryansmith
Very excited to start deploying enterprise SSDs for @indexsupply This one here is 7TB pcie4 kioxia cd6 going into the backup server. Planning to deploy even more powerful pcie5 cm7s to production soon.
1 reply
3 recasts
19 reactions

Index Supply pfp
Index Supply
@indexsupply
Thank you! Appreciate working with you too!
0 reply
0 recast
1 reaction

Index Supply pfp
Index Supply
@indexsupply
indeed! https://tinyurl.com/zora-query
1 reply
1 recast
4 reactions

Index Supply pfp
Index Supply
@indexsupply
Fascinating example of how to query events with nested tuples!
2 replies
1 recast
16 reactions

Index Supply pfp
Index Supply
@indexsupply
If you have a Pro plan we can setup direct chat support. Otherwise email: [email protected] -- or just mention on FC ;) Yes! Sounds like you found the PG JSON arrow operator.
0 reply
0 recast
1 reaction

Index Supply pfp
Index Supply
@indexsupply
The list of chains grow like the grass of spring
0 reply
1 recast
14 reactions

Index Supply pfp
Index Supply
@indexsupply
We don't index tx input data. Maybe we should.
1 reply
0 recast
2 reactions

Index Supply pfp
Index Supply
@indexsupply
SSE is ideal for one way communication whereas WS is good for two way. In the case of delivering data from a server to a client as quickly as possible SSE is the simplest and fastest way to do that.
0 reply
0 recast
2 reactions

✳️ dcposch on daimo pfp
✳️ dcposch on daimo
@dcposch.eth
Index Supply is a real feat of engineering. Radically simplify your eth apps. Skip RPCs, indexing, "subgraphs" and just query the chain directly. Now with any-chain payments. Follow @ryansmith for more!
0 reply
11 recasts
30 reactions

Index Supply pfp
Index Supply
@indexsupply
See first hand how easy and fast it is to query data using Index Supply. Total amount for a specific address: https://tinyurl.com/bdzfxdmm Status of a specific payment: https://tinyurl.com/kmmerca2
1 reply
0 recast
3 reactions

Index Supply pfp
Index Supply
@indexsupply
With Index Supply's API, you can open a Live SQL Query to be notified the instant your user completes a payment. Index Supply uses Postgres extensions, HTTP SSE, and a TypeScript SDK to make this simple and easy! Read all the details here: https://github.com/indexsupply/indexsupply.js/pull/6
1 reply
0 recast
6 reactions

Index Supply pfp
Index Supply
@indexsupply
How Index Supply collects payments with Daimo Pay + Index Supply @daimo is the simplest service for accepting any coin, on any chain, from any wallet. Index Supply is the simplest API for instant access to Ethereum. But can they blend?
2 replies
7 recasts
33 reactions

Index Supply pfp
Index Supply
@indexsupply
Daimo's webhooks are a good option for knowing when a payment is complete, but there are scenarios where running a server for webhooks is not ideal. One of the cool things about Ethereum is that we don't need privileged access to extend Daimo Pay's functionality – we can go straight to the chain!
1 reply
0 recast
5 reactions

Index Supply pfp
Index Supply
@indexsupply
Thanks for the ping! For anyone coming across this cast, see the following tweet: https://x.com/indexsupply/status/1888677935537951183
0 reply
0 recast
1 reaction

Nick T pfp
Nick T
@nt
chat we have realtime trades 🔥🔥🔥 data from @indexsupply
0 reply
1 recast
11 reactions

Index Supply pfp
Index Supply
@indexsupply
We've got plenty of indexes around these parts ;)
1 reply
0 recast
1 reaction

Index Supply pfp
Index Supply
@indexsupply
It's the same query without the address. If the underlying data is cached (in pg's shared buffers or the OS's page cache) (it is as of this cast) then there will be no difference. This particular query is on the slower side simply because of how many rows are being returned. I'm not saying that queries without addresses will always have a penalty, but in this particular case, adding the address predicate will increase cache hit rate because fewer file system pages are needed. And when it's not cached it will be quicker for the same reason.
1 reply
1 recast
3 reactions

Index Supply pfp
Index Supply
@indexsupply
If you are querying WowTokenCreated on the Index Supply free plan, please reach out to me as I have a query suggestion for you. It will bring your cold query latency from a couple of seconds down to ~150ms. here is the faster query: https://tinyurl.com/wowtoken-with-addr
2 replies
3 recasts
15 reactions

Index Supply pfp
Index Supply
@indexsupply
Fun Query for this Friday: Token Balances for a Wallet https://tinyurl.com/token-balance
1 reply
5 recasts
53 reactions