1
0
mirror of https://github.com/oceanprotocol/docs.git synced 2024-11-02 08:20:22 +01:00
docs/content/concepts/tools.md

77 lines
3.4 KiB
Markdown
Raw Normal View History

2018-11-16 13:37:06 +01:00
---
title: Tools
description: Some tools that can be useful when working with Ocean Protocol.
2018-11-16 13:37:06 +01:00
---
2019-07-30 12:43:04 +02:00
## Barge
2019-07-30 13:06:09 +02:00
Barge is a shell script allowing you to run an Ocean network by orchestrating all [core components](/components) locally with Docker and Docker Compose. Extensively used by Ocean developers to develop and test Ocean core components locally, and the [quickest way](/setup/quickstart/) to get a full Ocean network up and running.
2019-07-30 12:43:04 +02:00
<repo name="barge"></repo>
2019-07-09 21:56:59 +02:00
## Tuna
Tuna is a showcase and provides cross environment examples & tests for the Squid client libraries.
<repo name="tuna"></repo>
## Plecos
2019-02-20 16:56:38 +01:00
2019-06-06 14:06:51 +02:00
Plecos is a Python tool to check metadata (a JSON file) to see if it conforms to the [OEP-8 schema](https://github.com/oceanprotocol/OEPs/tree/master/8). It wraps the [jsonschema](https://github.com/Julian/jsonschema) validator. Aquarius uses Plecos for checking metadata and other Ocean Protocol software will probably use it in the future.
2019-02-20 16:59:15 +01:00
2019-06-06 14:06:51 +02:00
<repo name="plecos"></repo>
2019-03-01 13:30:51 +01:00
## Faucet Server
2018-11-16 13:37:06 +01:00
2019-07-30 12:54:55 +02:00
The [Ocean Protocol Faucet Server](https://github.com/oceanprotocol/faucet) 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](/tutorials/get-ether-and-ocean-tokens/#get-ether), and started by default when using [Barge](#barge).
2018-11-16 13:37:06 +01:00
2019-04-04 13:30:57 +02:00
<repo name="faucet"></repo>
2019-05-23 11:32:22 +02:00
## Submarine Blockchain Explorer
2018-11-16 13:37:06 +01:00
2019-07-30 13:12:41 +02:00
Submarine is based on [BlockScout](https://github.com/poanetwork/blockscout) (by [POA](https://poa.network/)), an open source blockchain explorer for EVM-based blockchain networks. We use our own [fork of BlockScout](https://github.com/oceanprotocol/blockscout).
Instances are deployed for:
- **Pacific Network: [submarine.oceanprotocol.com](https://submarine.oceanprotocol.com/)**
- **Nile Testnet: [submarine.dev-ocean.com](https://submarine.dev-ocean.com/)**
2019-06-06 14:06:51 +02:00
<repo name="blockscout"></repo>
2019-07-09 21:56:59 +02:00
## Ocean Token Bridge
2019-06-06 14:06:51 +02:00
2019-07-09 21:56:59 +02:00
The Ocean Token Bridge between the Ethereum Mainnet and the Pacific Network allows anyone with Ocean Tokens to move them from the Ethereum Mainnet to the Pacific Network.
2019-06-06 14:06:51 +02:00
2019-07-09 21:56:59 +02:00
- [**Ocean Token Bridge**](https://bridge.oceanprotocol.com)
- [Tutorial: Transfer Ocean Tokens between Networks](/tutorials/token-bridge/)
2019-07-08 17:29:12 +02:00
2019-07-09 21:56:59 +02:00
<repo name="token-bridge-ui"></repo>
2019-09-18 10:55:50 +02:00
## Ocean Network Status
The Ocean status page checks all Ocean network connections from your browser.
- [**Ocean Network Status**](https://status.oceanprotocol.com)
<repo name="status"></repo>
2019-07-09 21:56:59 +02:00
## 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.
2019-07-08 17:29:12 +02:00
2019-06-06 14:06:51 +02:00
- [ocean-cli](https://github.com/bigchaindb-gmbh/ocean-cli) was built using squid-java
- [ocean-cli-py](https://github.com/bigchaindb-gmbh/ocean-cli-py) was built using squid-py
2019-12-16 13:36:52 +01:00
## IPFS
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 💖 IPFS**](https://ipfs.oceanprotocol.com)
<repo name="ipfs"></repo>
To learn more about how IPFS is used, have a look at OEP-15 and the respective blog post:
- [OEP-15: Distributed Asset File Storage with IPFS](https://github.com/oceanprotocol/OEPs/tree/master/15)
- [Ocean Protocol and IPFS, Sitting In The Merkle Tree](https://blog.oceanprotocol.com/ocean-ipfs-integration-store-asset-files-43c623c356d7)