4.8 KiB
| description |
|---|
| Use these steps to reveal the information contained within an asset's DID and list the buyers of a datatoken |
List datatoken buyers
Step 1: Find the Network and Datatoken address
How to find the network and datatoken address from an Ocean Market link?
If you are given an Ocean Market link, then the network and datatoken address for the asset is visible on the Ocean Market webpage. For example, given this asset's Ocean Market link: https://odc.oceanprotocol.com/asset/did:op:1b26eda361c6b6d307c8a139c4aaf36aa74411215c31b751cad42e59881f92c1 the webpage shows that this asset is hosted on the Mumbai network, and one simply clicks the datatoken's hyperlink to reveal the datatoken's address as shown in the screenshot below:
See the Network and Datatoken Address for an Ocean Market asset by visiting the asset's Ocean Market page.
How to find the network and datatoken address from a DID?
If you know the DID:op but you don't know the source link, then you can use Ocean Aquarius to resolve the metadata for the DID:op to find the chainId+ datatoken address of the asset. Simply enter in your browser "https://v4.aquarius.oceanprotocol.com/api/aquarius/assets/ddo/<your did:op:XXX>" to fetch the metadata.
For example, for the following DID:op: "did:op:1b26eda361c6b6d307c8a139c4aaf36aa74411215c31b751cad42e59881f92c1" the Ocean Aquarius URL can be modified to add the DID:op and resolve its metadata. Simply add "https://v4.aquarius.oceanprotocol.com/api/aquarius/assets/ddo/" to the beginning of the DID:op and enter the link in your browser like this: https://v4.aquarius.oceanprotocol.com/api/aquarius/assets/ddo/did:op:1b26eda361c6b6d307c8a139c4aaf36aa74411215c31b751cad42e59881f92c1
The metadata printout for this DID:op with the network's Chain ID and datatoken address circled in red
Here are the networks and their corresponding chain IDs:
"mumbai: 80001"
"polygon: 137"
"bsc: 56"
"energyweb: 246"
"moonriver: 1285"
"mainnet: 1"
"goerli: 5"
"polygonedge: 81001"
"gaiaxtestnet: 2021000"
"alfajores: 44787"
"gen-x-testnet: 100"
"filecointestnet: 3141"
"oasis_saphire_testnet: 23295"
"development: 8996"
Step 2: Query the Subgraph to see all buyers of the datatoken
Select the corresponding subgraph URL for the asset's network. Below are some of the popular subgraph URLs, to show you the subgraph URL format.
https://v4.subgraph.mainnet.oceanprotocol.com/subgraphs/name/oceanprotocol/ocean-subgraph/graphql?
https://v4.subgraph.polygon.oceanprotocol.com/subgraphs/name/oceanprotocol/ocean-subgraph/graphql?
https://v4.subgraph.bsc.oceanprotocol.com/subgraphs/name/oceanprotocol/ocean-subgraph/graphql?
https://v4.subgraph.moonriver.oceanprotocol.com/subgraphs/name/oceanprotocol/ocean-subgraph/graphql?
https://v4.subgraph.energyweb.oceanprotocol.com/subgraphs/name/oceanprotocol/ocean-subgraph/graphql?
https://v4.subgraph.goerli.oceanprotocol.com/subgraphs/name/oceanprotocol/ocean-subgraph/graphql?
https://v4.subgraph.mumbai.oceanprotocol.com/subgraphs/name/oceanprotocol/ocean-subgraph/graphql?
You can then use the following example query to find what you're looking for (you can remove datatokens, or the lines with where: {datatoken/consumer} to tweak your filtering criteria. You can then explore the graphql editor via the links above to learn how to use it, and to add/remove information to the query.
Copy and paste the query below to fetch a list of data NFTs in the Ocean Subgraph GraphiQL interface. Note, that you must first fill in the missing fields for the datatoken address.
query GetFilteredOrders {
orders (
where: {
datatoken_in: ["0xc22bfd40f81c4a28c809f80d05070b95a11829d9", "0xdatatoken_address2"],
consumer_in: ["0xconsumer1"]
}
orderBy: createdTimestamp
orderDirection: desc
first: 1000
) {
datatoken{
id
name
symbol
nft {
id
}
}
consumer{
id
}
}
}