Some tools that can be useful when working with Ocean Protocol.


Barge is a shell script allowing you to run an Ocean network by orchestrating all core components locally with Docker and Docker Compose. Extensively used by Ocean developers to develop and test Ocean core components locally, and the quickest way to get a full Ocean network up and running.


Tuna is a showcase and provides cross environment examples & tests for the Squid client libraries.


🐟 Tuna eat squid, so does this. Example showcase for squid


Plecos is a Python tool to check metadata (a JSON file) to see if it conforms to the OEP-8 schema. It wraps the jsonschema validator. Aquarius uses Plecos for checking metadata and other Ocean Protocol software will probably use it in the future.

Faucet Server

The Ocean Protocol Faucet Server is a microservice that allows users to request Ether for a particular Ethereum network (e.g. the Nile Testnet). It is deployed in multiple networks, and started by default when using Barge.

Submarine Blockchain Explorer

Submarine is based on BlockScout (by POA), an open source blockchain explorer for EVM-based blockchain networks. We use our own fork of BlockScout.

Instances are deployed for:

Ocean Network Status

The Ocean status page checks all Ocean network connections from your browser.


🐚 Overview and status checks of all Ocean Protocol RPC network connections.

Command-Line Interfaces

There are a few Ocean Protocol command-line interfaces (CLIs). All of them were under development at the time of writing, so you may have issues with using them.


The IPFS protocol is integrated into the Ocean Protocol stack in various places. For this, we run and maintain our own IPFS node and gateway with a custom frontpage for simple adding of files to that IPFS node.


👩🏽‍🚀 Ocean Protocol's public IPFS node & gateway.

To learn more about how IPFS is used, have a look at OEP-15 and the respective blog post: