oceanprotocol/docs
1
0
Fork 0
mirror of https://github.com/oceanprotocol/docs.git synced 2024-11-26 19:49:26 +01:00
Code Releases Activity

GITBOOK-45: change request with no subject merged in GitBook

Browse Source
This commit is contained in:
Veronica Manuel 2023-05-10 19:28:06 +00:00 committed by gitbook-bot
parent 56703f8d4f
commit 1654f408f4
No known key found for this signature in database
GPG Key ID: 07D2180C7B12D0FF
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
SUMMARY.md
View File

@ -13,7 +13,7 @@
* [Using Ocean Market](how-tos/using-ocean-market/README.md)
* [Publish an NFT](how-tos/using-ocean-market/marketplace-publish-data-asset.md)
* [Download NFT Assets](how-tos/using-ocean-market/marketplace-download-data-asset.md)
* [Asset Hosting Options](how-tos/using-ocean-market/asset-hosting.md)
* [Hosting Your Assets](how-tos/using-ocean-market/asset-hosting.md)
* [Liquidity Pools \[deprecated\]](how-tos/using-ocean-market/remove-liquidity-using-etherscan.md)
* [📚 Tutorials](tutorials/README.md)
* [Build a Marketplace](tutorials/build-a-marketplace/README.md)

4
how-tos/using-ocean-market/asset-hosting.md
View File

@ -5,11 +5,11 @@ description: >-
Arweave, AWS, and Azure.
---
# Asset Hosting Options
# Hosting Your Assets
### Overview
To publish on the Ocean Marketplace, publishers must first host their assets. It is up to the asset publisher to decide where to host the asset. For example, a publisher can store the content on decentralized storage like Arweave or choose a centralized solution like their AWS server, private cloud server, or other third-party hosting services. Through publishing, the information required to access the asset is encrypted and stored as a part of DDO on the blockchain. Buyers don't have access directly to this information, but they interact with the [Provider](https://github.com/oceanprotocol/provider#provider), which decrypts it and acts as a proxy to serve the asset. The DDO only stores the location of the file, which is accessed on-demand by the Provider. Implementing a security policy that allows only the Provider to access the file and blocks requests from other unauthorized actors is recommended. One of the possible ways to achieve this is to allow only the Provider's IP address to access the data. But, not all hosting services provide this feature. So, the publishers must consider the security features while choosing a hosting service.
To publish on the Ocean Marketplace, publishers must first host their assets! It is up to the asset publisher to decide where to host the asset. For example, a publisher can store the content on decentralized storage like Arweave or choose a centralized solution like their AWS server, private cloud server, or other third-party hosting services. Through publishing, the information required to access the asset is encrypted and stored as a part of DDO on the blockchain. Buyers don't have access directly to this information, but they interact with the [Provider](https://github.com/oceanprotocol/provider#provider), which decrypts it and acts as a proxy to serve the asset. The DDO only stores the location of the file, which is accessed on-demand by the Provider. Implementing a security policy that allows only the Provider to access the file and blocks requests from other unauthorized actors is recommended. One of the possible ways to achieve this is to allow only the Provider's IP address to access the data. But, not all hosting services provide this feature. So, the publishers must consider the security features while choosing a hosting service.
On Ocean Marketplace, a publisher must provide the asset information during the publish step in the field shown in the below image. The information is a `link` for a classic URL, a `transaction ID` for a file stored on Arweave or a `CID` for an IPFS file.