kmd-fl on dev-metrics
Fix formatting (compare)
kmd-fl on dev-metrics
Add service metrics Improve service metrics (compare)
kmd-fl on dev-metrics
Add service metrics (compare)
folex on v1.9.11
boneyard93501 on send_status_refactor
trigger build (compare)
github-actions[bot] on gh-pages
deploy: 56a4243525d6c5fdf8d4a10… (compare)
boneyard93501 on send_status_refactor
trigger build (compare)
folex on send_status_refactor
trigger build (compare)
folex on send_status_refactor
folex on send_status
folex on master
Report reason if particle sendi… (compare)
Hey @osarrouy
So, for Pando Protocol case.
The main idea that Fluence is going to update index from Ethereum (not only, but it's an important feature we're working on), and then you can implement logic to organize your data with any Webassembly-supported language. Then do whatever you want with it :)
The workflow with Fluence might be the following:
ipld
ipld
data. But you may implement some service that, for example, launches a periodical query to Fluence and updates ipld
accordingly. Or you may query Fluence directly from client's browserSo there's no special constrainst on ipld
structure :)