mirror of
https://github.com/oceanprotocol/docs.git
synced 2024-11-26 19:49:26 +01:00
GITBOOK-16: Center not image on binance
This commit is contained in:
Ana Loznianu
gitbook-bot
parent
514ba1a07c
commit
ad1aa35281
|
Before Width: | Height: | Size: 151 KiB After Width: | Height: | Size: 151 KiB |
|
Before Width: | Height: | Size: 288 KiB After Width: | Height: | Size: 288 KiB |
BIN
.gitbook/assets/polygon-login.png
Normal file
BIN
.gitbook/assets/polygon-login.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 253 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 170 KiB |
BIN
.gitbook/assets/wallet/transferring (1).png
Normal file
BIN
.gitbook/assets/wallet/transferring (1).png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 226 KiB |
@ -36,7 +36,7 @@
|
||||
* [Data Farming Background](rewards/df-background.md)
|
||||
* [Emissions & APYs](rewards/emissions-apys.md)
|
||||
* [Rewards Tutorial](rewards/veOcean-Data-Farming-Tutorial.md)
|
||||
* [👨💻 👨💻 Developers](developers/README.md)
|
||||
* [👨💻 👨💻 👨💻 Developers](developers/README.md)
|
||||
* [Core concepts](developers/core-concepts/README.md)
|
||||
* [Architecture Overview](developers/core-concepts/architecture.md)
|
||||
* [Data NFTs and Datatokens](developers/core-concepts/datanft-and-datatoken.md)
|
||||
|
||||
@ -62,7 +62,7 @@ Ocean provides convenient methods to list ERC20 datatokens for sale, with fixed-
|
||||
|
||||
### High-Level Behavior
|
||||
|
||||
|
||||
.png>)
|
||||
|
||||
Here's an example.
|
||||
|
||||
|
||||
@ -13,25 +13,21 @@ We suggest using the following solutions to transfer Ocean tokens between Ethere
|
||||
|
||||
To transfer Ocean tokens to and from the Binance Smart Chain, we recommend using the [Binance Bridge](https://www.bnbchain.org/en/bridge). BSC offers various options such as withdrawing crypto from [Binance](https://www.binance.com/en) and utilizing the [Binance Bridge](https://www.bnbchain.org/en/bridge). You can refer to the Binance Academy article "[How to Get Started with BSC](https://academy.binance.com/en/articles/how-to-get-started-with-binance-smart-chain-bsc)" for more information.
|
||||
|
||||
|
||||
|
||||
{% hint style="warning" %}
|
||||
In case you opt for an alternative bridge option and intend to transfer tokens to Binance, it is crucial to ensure that the contract address you are sending the tokens to is correct. 
|
||||
In case you opt for an alternative bridge option and intend to transfer tokens to Binance, it is crucial to ensure that the contract address you are sending the tokens to is correct.
|
||||
|
||||
##   <img src="../../.gitbook/assets/wallet/binance-receive.png" alt="" data-size="original">
|
||||
###   <img src="../../.gitbook/assets/binance-receive.png" alt="Binance deposit" data-size="original"> <a href="#binance-deposit" id="binance-deposit"></a>
|
||||
{% endhint %}
|
||||
|
||||
|
||||
|
||||
## Polygon (ex Matic) Bridge
|
||||
|
||||
The Polygon Network (previously known as Matic) offers a [bridge](https://wallet.polygon.technology/bridge/), which lets you easily transfer digital assets between Ethereum and Polygon blockchains and a dedicated [wallet](https://wallet.polygon.technology/) designed for this purpose, which can be linked to your account through Metamask or other compatible wallets. 
|
||||
The Polygon Network (previously known as Matic) offers a [bridge](https://wallet.polygon.technology/bridge/), which lets you easily transfer digital assets between Ethereum and Polygon blockchains and a dedicated [wallet](https://wallet.polygon.technology/) designed for this purpose, which can be linked to your account through Metamask or other compatible wallets.
|
||||
|
||||
All you need to do is click on the [wallet](https://wallet.polygon.technology/) link, select your preferred method of connection, and log in to get started. In this guide, we'll be using Metamask to connect the wallet.
|
||||
|
||||
|
||||
<figure><img src="../../.gitbook/assets/polygon-login.png" alt="Polygon login options"><figcaption><p>Login options</p></figcaption></figure>
|
||||
|
||||
You might come across the name "Matic" in some places instead of "Polygon" because the network is still using its old brand name in certain instances. Don't worry though, it's the same network whether you see Matic or Polygon. For the sake of this guide, we'll be using the name Matic in the following paragraphs because the interfaces we'll be using still use the old brand name. 
|
||||
You might come across the name "Matic" in some places instead of "Polygon" because the network is still using its old brand name in certain instances. Don't worry though, it's the same network whether you see Matic or Polygon. For the sake of this guide, we'll be using the name Matic in the following paragraphs because the interfaces we'll be using still use the old brand name.
|
||||
|
||||
Check out our [blog post](https://blog.oceanprotocol.com/ocean-on-polygon-network-8abad19cbf47) for more details.
|
||||
|
||||
@ -53,7 +49,7 @@ Select the amount of tokens you want to transfer and hit the "Transfer" button.
|
||||
|
||||
#### Withdraw Tokens
|
||||
|
||||
The process of withdrawing tokens also utilizes the bridge interface, but this time the withdrawal will happen from Matic to the Ethereum Mainnet. The bridge interface will guide you through all the necessary steps for this process as well. 
|
||||
The process of withdrawing tokens also utilizes the bridge interface, but this time the withdrawal will happen from Matic to the Ethereum Mainnet. The bridge interface will guide you through all the necessary steps for this process as well.
|
||||
|
||||
For more detailed information about depositing and withdrawing actions, you can refer to the official Polygon [documentation](https://wiki.polygon.technology/docs/develop/ethereum-polygon/plasma/eth/).
|
||||
|
||||
@ -63,7 +59,7 @@ Unlike the first two cases where transactions are signed on the Ethereum Mainnet
|
||||
|
||||
The easiest one is to go to the [polygon network explorer](https://polygonscan.com/) and tap on the "Add polygon network" button.
|
||||
|
||||
<figure><img src="../../.gitbook/assets/wallet/polygon-explorer.png" alt=""><figcaption></figcaption></figure>
|
||||
<figure><img src="../../.gitbook/assets/polygon-explorer.png" alt=""><figcaption></figcaption></figure>
|
||||
|
||||
Alternatively, you can manually configure the network on Metamask by using the following parameters. To learn how to set up a custom network in Metamask using these values, you can refer to our guide.
|
||||
|
||||
|
||||
@ -28,7 +28,7 @@ Select Ubuntu OS and choose a plan. The required CPU, Memory depends on the numb
|
||||
|
||||
Also, select the region where you want Aquarius to be hosted and a root password.
|
||||
|
||||
.png>)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -182,41 +182,41 @@ Create an account on [Azure](https://azure.microsoft.com/en-us/). Users might al
|
||||
|
||||
Go to the Azure portal: https://portal.azure.com/#home and select `Storage accounts` as shown below.
|
||||
|
||||
|
||||
.png>)
|
||||
|
||||
**Create a new storage account**
|
||||
|
||||
.png>)
|
||||
|
||||
|
||||
**Fill in the details**
|
||||
|
||||
|
||||
.png>)
|
||||
|
||||
**Storage account created**
|
||||
|
||||
.png>)
|
||||
|
||||
|
||||
**Step 2 - Create a blob container**
|
||||
|
||||
|
||||
.png>)
|
||||
|
||||
**Step 3 - Upload a file**
|
||||
|
||||
.png>)
|
||||
|
||||
|
||||
**Step 4 - Share the file**
|
||||
|
||||
**Select the file to be published and click Generate SAS**
|
||||
|
||||
|
||||
.png>)
|
||||
|
||||
**Configure the SAS details and click `Generate SAS token and URL`**
|
||||
|
||||
.png>)
|
||||
|
||||
|
||||
**Copy the generated link**
|
||||
|
||||
.png>)
|
||||
|
||||
|
||||
**Step 5 - Publish the asset using the generated link**
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user