Ecosystem
Integrations
Robinhood ChainIPFS via Filebase
What Upoch works with today, and what is planned. Each entry is labelled with exactly what has been tested, and a project is listed as integrated only once its integration has been built and tested.
Agent runtimes
| Runtime | Status | Notes |
|---|---|---|
| Custom Node.js agents | Tested on testnet | The SDK on Robinhood Chain testnet: checkpoints with encrypted state on IPFS, a rollback through the console, and resumption from the restored checkpoint. Locally, the reference agent also survives a killed process |
| Python agents | Verification | sdk-python independently verifies checkpoints, manifests and stored data from the chain and IPFS; the agent runtime is TypeScript |
| LangChain, other frameworks | Planned | Adapters are planned. Until then, the SDK can be called from a framework tool |
Storage and encryption
| Provider | Status |
|---|---|
| IPFS (Kubo API, pinned on Filebase) | Tested on testnet |
| AES-256-GCM (operator-held key) | Tested on testnet |
| Arweave | Adapter built · live test planned |
| Lit Protocol | Planned |
Networks
Upoch runs on Robinhood Chain: mainnet (4663) and testnet (46630). Contract addresses and how each was verified are on the status page.
Getting listed
An integration is listed once it has a working example and a test that runs it against Upoch, and its status says exactly what was tested.