Getting Started

nautilus uses the ethers Signer. In v6, JsonRpcProvider is a top-level export; the providers namespace no longer exists.

import { JsonRpcProvider, Wallet } from 'ethers'
 
const provider = new JsonRpcProvider('https://rpc.dev.pontus-x.eu')
const signer = new Wallet('0x...', provider)

The chain is read from the signer's provider, so there is no chain argument. What nautilus does need is an ocean-node: one node now serves metadata, provider services and the indexer, replacing v1's separate Aquarius and Provider URLs.

import { JsonRpcProvider, Wallet } from 'ethers'
import { Nautilus } from '@deltadao/nautilus'
 
const provider = new JsonRpcProvider('https://rpc.dev.pontus-x.eu')
const signer = new Wallet('0x...', provider)
 
const nautilus = await Nautilus.create(signer, { 
  config: { oceanNodeUri: 'https://ocean-node.dev.pontus-x.eu' } 
}) 

ocean.js ships contract addresses for a set of chains, including Pontus-X devnet (32456) and OP Sepolia (11155420), so oceanNodeUri is usually all you pass. On a chain it does not know, pass the addresses in config too — see Custom Configuration.

nautilus works with OceanProtocolEnterprise ocean-node 4.2.x. For access to the deltaDAO test environment, or to have your own ocean-node run as a service, contact deltaDAO at delta-dao.com/contact or contact@delta-dao.com.

const { url } = await nautilus.access({ assetDid: 'did:ope:1234abcd...' }) 
 
const data = await fetch(url) 

nautilus orders the service if you do not already hold a valid order, and reuses your existing one if you do.