Content
@
https://warpcast.com/~/channel/m3ter-heads
0 reply
0 recast
0 reaction
I. Christwin〔▸‿◂〕💡
@ichristwin.eth
Look what @emmo00 has been cooking!! 😃 Above all odds, he has managed to index our activity on Arweave especially the smart meter data payload. Most other garphql indexes for Arweave won't index data payload, hence clients have to look that up on arweave.net That approach definitely ain't gonna work for us where each payload is a datapoint in a timeseries, hence we needed a subgraph to index our activity and lookup the payload as well. Great job @emmo00 👏
2 replies
2 recasts
6 reactions
ar://kemp
@kempsterrrr
Glad you solved the problem 🙌 Your original question re indexing data specific to M3tering should definitely be possible but I'm a little confused as the requirements explained above and solution you found :) Did you manage to do this by optimising/customising the gateways indexing or did you opt for a different solution entirely? And any more you can share about the indexing requirements re data types, super interested learning and feedback for us!
1 reply
0 recast
2 reactions
emmo00.base.eth
@emmo00
Yes, while the original question focused on indexing and storing data from a specific device or application, our solution goes a step further. Our solution: Running our own gateway that index and caches M3tering Protocol data (this is a vital piece as we cannot use the publicly available Arweave gateway because it is a public resource, and we'd benefit greatly from the speed of an extra level of indexing and caches). This is an ar-io, includes specific index filters (similar to the screenshot) to improve query efficiency and latency. With the need to return the transaction data and also the inputs for the warp contract in one step, we implemented an api gateway that sits in front of our Arweave gateway for this exact purpose. This layer is implemented as an Apollo GraphQL server.
1 reply
1 recast
3 reactions
