Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bringing main to dev #7

Merged
merged 37 commits into from
Jul 13, 2022
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
37 commits
Select commit Hold shift + click to select a range
628f619
Merge pull request #2 from gnosischain/dev
giacomolicari Jun 13, 2022
02a3652
initial configuration
alebanzas Jun 14, 2022
de67419
Remove CACHE rules on Staging deployments
giacomolicari Jun 16, 2022
fcad35c
add ignore
alebanzas Jun 17, 2022
2934bb5
adding gnosis beacon chain documentation
alebanzas Jun 17, 2022
852f3a8
removing unused files
alebanzas Jun 17, 2022
29946b2
starting quick start and home pages
alebanzas Jun 17, 2022
326cd72
Merge branch 'main' of https://github.com/gnosischain/developers-portal
alebanzas Jun 17, 2022
c98fba8
upgrading dependencies + removing package lock
alebanzas Jun 17, 2022
e82e5ca
upgrading node version
alebanzas Jun 17, 2022
afdc3d5
docusaurus version
alebanzas Jun 17, 2022
a6571a1
fix broken link
alebanzas Jun 17, 2022
f8d04ac
staging url
alebanzas Jun 17, 2022
b2e3568
updating docusaurus to last version
alebanzas Jun 18, 2022
a002d9c
node version 16.14.2
alebanzas Jun 18, 2022
6fe10db
fixing deploy
alebanzas Jun 18, 2022
8802dea
re-arrange info section
alebanzas Jun 20, 2022
1759b70
fixing internal links
alebanzas Jun 20, 2022
a874723
gnosis logo + colors
alebanzas Jun 20, 2022
411c149
governance, hard forks, consensus, specs
alebanzas Jun 26, 2022
55c0152
bridge specs + fixes
alebanzas Jun 27, 2022
95af898
image links
alebanzas Jun 27, 2022
1718713
renaming
alebanzas Jun 27, 2022
030bea2
bridges initial commit
alebanzas Jun 28, 2022
e8c47ed
highlights
alebanzas Jun 28, 2022
7b45be7
bridge docs reorg + link fixing
alebanzas Jun 29, 2022
a3c4e23
network naming
alebanzas Jun 29, 2022
acd9172
fixing links
alebanzas Jun 29, 2022
44b3b91
link fixing
alebanzas Jun 30, 2022
00c45af
images in lowercase
alebanzas Jun 30, 2022
6afd4e3
images in lowercase
alebanzas Jun 30, 2022
793ccf9
images in lowercase
alebanzas Jun 30, 2022
decfe1f
reorg links
alebanzas Jul 1, 2022
4e2f0df
tabs functionality
alebanzas Jul 11, 2022
58d425b
youtube link
alebanzas Jul 11, 2022
ad4fa02
url changes + youtube embeded
alebanzas Jul 11, 2022
0fde95a
xdai bridge
alebanzas Jul 13, 2022
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
link fixing
  • Loading branch information
alebanzas committed Jun 30, 2022
commit 44b3b9115e5cb0e72484986970cb008cf74cca47
2 changes: 1 addition & 1 deletion docs/specs/bridges/bsc-gc/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,4 +23,4 @@ The mediator contracts rely on the following information about the BSC-GC Arbitr

It is possible to get the status of an AMB transaction using [the Live Monitoring app](https://docs.tokenbridge.net/about-tokenbridge/components/amb-live-monitoring-application): [https://alm-bsc-xdai.herokuapp.com/](https://alm-bsc-xdai.herokuapp.com). Transactions require a multi-sig (for bridge validators, not users) for a successful transfer. Current validators can be viewed with the live monitoring application.

For transactions from the Gnosis Chain [manual execution](submit-confirmations-manually.md) is required. This action delivers the validator confirmations gathered on the Gnosis Chain to the Binance Smart Chain and triggers the transferred message handling.
For transactions from the Gnosis Chain [manual execution](/specs/bridges/bsc-gc/submit-confirmations-manually) is required. This action delivers the validator confirmations gathered on the Gnosis Chain to the Binance Smart Chain and triggers the transferred message handling.
2 changes: 1 addition & 1 deletion docs/specs/bridges/bsc-gc/omnibridge-extension/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ The OmniBridge multi-token extension for the Arbitrary Message Bridge between th

:::info
* BSC-GC isaccessed through the [OmniBridge UI](https://omni.xdaichain.com/bridge). Select BSC-GC from the dropdown menu and set the MetaMask network to GC or BSC to proceed.
* OmniBridge does not require a UI for functionality, and[ tokens can be transferred manually](manual-tokens-transfer.md).
* OmniBridge does not require a UI for functionality, and [tokens can be transferred manually](/specs/bridges/bsc-gc/omnibridge-extension/manual-tokens-transfer).
* [Live Monitoring App](https://alm-bsc-xdai.herokuapp.com)
* Additional items may be referenced in the [ETH-GC Omnibridge Extension ](/specs/bridges/eth-gc/multi-token-extension/)section.
:::
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -14,5 +14,5 @@ The sUSD bridge extension of the ETH-GC Arbitrary Message Bridge is a pair of me
This extension was deployed to demonstrate a working model of the ETH-GC AMB. Anyone who owns sUSD tokens can use the bridge - sUSDs are locked in the bridge contract and the same amount of [sUSD bridgeable tokens](https://blockscout.com/xdai/mainnet/address/0x4c36d2919e407f0cc2ee3c993ccf8ac26d9ce64e) are minted on the Gnosis Chain. The reverse operation burns sUSD bridgeable tokens on the Gnosis Chain and unlock Synth sUSD tokens on the Ethereum Mainnet.

:::success
Follow the step-by-step instructions to [Transfer sUSD through the bridge extension.](transfer-susd-through-the-bridge-extension.md)
Follow the step-by-step instructions to [Transfer sUSD through the bridge extension.](/specs/bridges/eth-gc/susd-bridge-extension/transfer-susd-through-the-bridge-extension)
:::
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ description: >-
# Send sUSD between two wallets on GC

:::success
sUSD can be sent between any two GC enabled wallets. You will need some amount of sUSD on the Gnosis Chain, as well as some xDai for gas (less than $.01), to send from one wallet to another. To transfer sUSD from the Ethereum Mainnet to the Gnosis Chain, see the [transfer using the bridge extension](transfer-susd-through-the-bridge-extension.md) post.
sUSD can be sent between any two GC enabled wallets. You will need some amount of sUSD on the Gnosis Chain, as well as some xDai for gas (less than $.01), to send from one wallet to another. To transfer sUSD from the Ethereum Mainnet to the Gnosis Chain, see the [transfer using the bridge extension](/specs/bridges/eth-gc/susd-bridge-extension/transfer-susd-through-the-bridge-extension) post.
:::

In this example we use [**Alpha Wallet**](https://alphawallet.com), a mobile wallet with built-in xDai support, and [**Nifty wallet**](https://chrome.google.com/webstore/detail/nifty-wallet/jbdaocneiiinmjbjlgalhcelgbejmnid?hl=en), a web3 enabled wallet similar to MetaMask but better equipped to work with Gnosis Chain.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ description: How to develop a web-application to transfer tokens through AMB

# UI to transfer tokens through AMB

This manual describes how to rapidly develop a web-application to transfer tokens using the Arbitrary Message Bridge between the Ethereum Mainnet and the Gnosis Chain. It assumes that an `erc-to-erc` extension was deployed [using these steps](deploy-erc20-erc677-erc827-to-erc677-amb-bridge-extension.md).
This manual describes how to rapidly develop a web-application to transfer tokens using the Arbitrary Message Bridge between the Ethereum Mainnet and the Gnosis Chain. It assumes that an `erc-to-erc` extension was deployed [using these steps](/specs/bridges/eth-gc/deploy-erc20-erc677-erc827-to-erc677-amb-bridge-extension).

:::info
The application is based on [the Burner Wallet 2 interface](https://github.com/burner-wallet/burner-wallet-2). Quick launch of a new application is possible with [the TokenBridge plugin developed for the Arbitrary Message Bridge mediators](https://github.com/poanetwork/tokenbridge/tree/master/burner-wallet-plugin).
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ There is an [OMNIBRIDGE UI](https://omni.xdaichain.com) now available which call

## General Case: ERC20 Token Transfer

The general case describes a "pure" ERC20 token. For tokens compatible with ERC677 and ERC827 token standards the steps may be simplified - see [the separate section below](how-to-transfer-tokens.md#simplification-for-erc-677-erc827-tokens).
The general case describes a "pure" ERC20 token. For tokens compatible with ERC677 and ERC827 token standards the steps may be simplified - see [the separate section below](#simplification-for-erc-677-erc827-tokens).

### Ethereum -> Gnosis Chain

Expand Down Expand Up @@ -108,7 +108,7 @@ Also, the MetaMask/NiftyWallet must be unlocked and rights to access the account

:::warning
Make sure that the token contract is verified in BlockScout. Token contracts deployed as part of the multi-token mediator operations are not verified automatically, so if the token does not allow read and write in the block explorer, follow [the steps to verify the contract](/specs/bridges/eth-gc/multi-token-extension/new-token-contract-verification-in-blockscout) before starting.

:::

#### Step 1: transferAndCall method to transfer tokens

Expand Down Expand Up @@ -150,11 +150,11 @@ Click Write Contract and specify the multi-token mediator contract address on Et

:::danger
Do Not Use the `transfer` method to send tokens to the multi-token mediator on Ethereum. It will lead to loss of tokens.

:::

The token contact deployed on the Gnosis Chain is a customized version of ERC677 standard. It contains [the changes](https://github.com/poanetwork/tokenbridge-contracts/blob/e09bd71bb67cf2ebce3cd7a4ec7130beea733018/contracts/ERC677BridgeToken.sol#L58-L62) that allow calling the `transfer` method to withdraw tokens from the Gnosis Chain instead of `transferAndCall`. So, it is enough to specify the multi-token mediator contract address on the Gnosis Chain (`0xf6A78083ca3e2a662D6dd1703c939c8aCE2e268d`) as the recipient and amount of tokens to initiate request to transfer tokens back to Ethereum.

:::warning
:::caution
The method described above works only for tokens deployed by the multi-token mediator in the Gnosis Chain.

:::

Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ description: Tokens Bridged using the multi-token bridge extension
A dynamic list with additional information is now available at [https://blockscout.com/xdai/mainnet/bridged-tokens](https://blockscout.com/xdai/mainnet/bridged-tokens)
:::

The OmniBridge multi-token bridge extension is now being used to bridge many tokens from Ethereum to Gnosis Chain. When a token is bridged, the name is appended with _**on GC**_. On a token page, you can also find the link to the original token on Ethereum. For more, see the [corresponding token contract addresses page](correspondence-of-bridgeable-tokens.md).
The OmniBridge multi-token bridge extension is now being used to bridge many tokens from Ethereum to Gnosis Chain. When a token is bridged, the name is appended with _**on GC**_. On a token page, you can also find the link to the original token on Ethereum. For more, see the [corresponding token contract addresses page](/specs/bridges/eth-gc/multi-token-extension/correspondence-of-bridgeable-tokens).

## 🌱 The Bridged Token List is growing daily! 🌱

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -14,4 +14,4 @@ Tokens Bridged from Ethereum: [https://blockscout.com/xdai/mainnet/bridged-token
Tokens Bridged from Binance Smart Chain: [https://blockscout.com/xdai/mainnet/bridged-tokens/bsc](https://blockscout.com/xdai/mainnet/bridged-tokens/bsc)
:::

The OmniBridge multi-token bridge extension is now being used to bridge many tokens from Ethereum to Gnosis Chain. A second instance bridges tokens to and from the Binance Smart Chain. When a token is bridged, the name is appended with _**on GC**_. On a token page, you can also find the link to the original token on Ethereum. For more, see the [corresponding token contract addresses page](../correspondence-of-bridgeable-tokens.md).
The OmniBridge multi-token bridge extension is now being used to bridge many tokens from Ethereum to Gnosis Chain. A second instance bridges tokens to and from the Binance Smart Chain. When a token is bridged, the name is appended with _**on GC**_. On a token page, you can also find the link to the original token on Ethereum. For more, see the [corresponding token contract addresses page](/specs/bridges/eth-gc/multi-token-extension/correspondence-of-bridgeable-tokens).
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ The NFT Extension is in Beta and transfers are performed at your own risk. NFT t
:::

:::info
If you want to bridge an [ERC1155 NFT or NFT collection, instructions are here](eip1155-based-nft-transfer-example.md).
If you want to bridge an [ERC1155 NFT or NFT collection, instructions are here](/specs/bridges/eth-gc/nft-omnibridge-extension/eip1155-based-nft-transfer-example).
:::

## -> Gnosis Chain to Ethereum
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ description: >-
# Send sUSD between two wallets on Gnosis Chain

:::success
sUSD can be sent between any two Gnosis Chain enabled wallets. You will need some amount of sUSD on the Gnosis Chain, as well as some xDai for gas \(less than $.01\), to send from one wallet to another. To transfer sUSD from the Ethereum Mainnet to the Gnosis Chain, see the [transfer using the bridge extension](transfer-susd-through-the-bridge-extension.md) post.
sUSD can be sent between any two Gnosis Chain enabled wallets. You will need some amount of sUSD on the Gnosis Chain, as well as some xDai for gas \(less than $.01\), to send from one wallet to another. To transfer sUSD from the Ethereum Mainnet to the Gnosis Chain, see the [transfer using the bridge extension](/specs/bridges/eth-gc/susd-bridge-extension/transfer-susd-through-the-bridge-extension) post.
:::

In this example we use [**Alpha Wallet**](https://alphawallet.com/), a mobile wallet with built-in Gnosis Chain support, and ****[**Nifty wallet**](https://chrome.google.com/webstore/detail/nifty-wallet/jbdaocneiiinmjbjlgalhcelgbejmnid?hl=en), a web3 enabled wallet similar to MetaMask but better equipped to work with Gnosis Chain.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ description: How to develop a web-application to transfer tokens through AMB

# UI to transfer tokens through AMB

This manual describes how to rapidly develop a web-application to transfer tokens using the Arbitrary Message Bridge between the Ethereum Mainnet and the Gnosis Chain. It assumes that an `erc-to-erc` extension was deployed [using these steps](deploy-erc20-erc677-erc827-to-erc677-amb-bridge-extension.md).
This manual describes how to rapidly develop a web-application to transfer tokens using the Arbitrary Message Bridge between the Ethereum Mainnet and the Gnosis Chain. It assumes that an `erc-to-erc` extension was deployed [using these steps](/specs/bridges/eth-gc/deploy-erc20-erc677-erc827-to-erc677-amb-bridge-extension).

:::info
The application is based on [the Burner Wallet 2 interface](https://github.com/burner-wallet/burner-wallet-2). Quick launch of a new application is possible with [the TokenBridge plugin developed for the Arbitrary Message Bridge mediators](https://github.com/poanetwork/tokenbridge/tree/master/burner-wallet-plugin).
Expand Down
2 changes: 1 addition & 1 deletion docs/specs/consensus/aura.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ Gnosis Chain currently uses Parity's AuRa (Authority Round) proof-of-authority c

Gnosis Chain uses delegated Proof of Stake to provide sybil protection. Validators and delegators must add STAKE to the protocol. If the nodes participate as expected, they receive additional STAKE rewards. If they engage in malicious behavior (like not revealing random numbers) the validator is banned and their STAKE (and delegators STAKE) is frozen. These behavioral rewards act as incentives to promote an honest group of validators participating in consensus.

(TODO: LINK)Learn more in the Whitepaper](../posdao-whitepaper.md)
[Learn more in the Whitepaper](/specs/consensus/posdao#whitepaper)

View current Gnosis Chain validator pools in the [BlockScout Staking Application](https://blockscout.com/xdai/mainnet/validators).

Expand Down
2 changes: 1 addition & 1 deletion docs/specs/gbc/upgradeability.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ A multi-sig Gnosis Safe is used to expand admin responsibilities to a larger ent

A proposed upgrade is presented to this board and a minimum of 7 signatures are required to enact any proposal.

:judge:[Governance Board Members](https://developers.gnosischain.com/for-users/governance#current-governing-board)
[Governance Board Members](/governance)

### Contracts managed by the Governance Board

Expand Down