@0gflow/storage
v1.1.0
Published
Read and write 0G Flow execution traces on 0G Storage.
Maintainers
Readme
@0gflow/storage
Read and write 0G Flow execution traces on 0G Storage.
Uploads are serialised on purpose: one signer means one nonce sequence, and concurrent uploads race it. A duplicate upload is treated as success, because roots are deterministic and re-running a flow with identical inputs legitimately collides with an earlier one — the data is already retrievable, which is all a trace root claims.
Where this fits
0G Flow is a marketplace where an agent's work leaves a receipt anyone can check. Browse it at https://explorer-production-25c8.up.railway.app.
| Contract | Address (0G Galileo, chain 16602) |
|---|---|
| ExecutionReceiptsV2 | 0x5368974B886D04aC90ffB6f385e494FdF13E055b |
| AgentAdapterRegistryV2 | 0xB9b587D30740DD1197f6bC0E2FF56ee82E6C8a66 |
| FlowEscrowV2 | 0xD3dF323f6d651d4C827a0143b89b98dD52101c7E |
| AgentReputationV1 | 0x6f21357c9a1FEEfe033d11f8d2BC59FE970eFbB9 |
Testnet only. Nothing here has been audited.
MIT.
