# ETH Bridge ?

<figure><img src="https://1452464627-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F22e9Obw9OsMd9SEGHYF2%2Fuploads%2F0n985XS0a5AkV8X1FjUE%2F111111.jfif?alt=media&#x26;token=c9ad49f0-898b-4a48-b064-b5fbfd3b1426" alt=""><figcaption></figcaption></figure>

Web site <https://eth.metaversefacemaker.com/&#x20>;

TOKENS <https://etherscan.io/token/0x5d95901D045926EC7Ae7D4a64487D7A69c5b6D8F> <https://bscscan.com/token/0x6Ad0F087501Eee603AeDa0407c52864bc7f83322&#x20>;

Bridge <https://etherscan.io/address/0xcc856b6d725a58b43ab27890fc9685f2247cc1f0#code> <https://bscscan.com/address/0xCC856b6d725A58b43Ab27890fc9685f2247Cc1f0#code&#x20>;

Bot @mefa\_bridge\_bot

On February 25, 2022, the ETH bridge was established and mefa eth was built.

There done a fork on the ETH network. We had 2 solutions for this.

1. Single server ( implies 1 validator and 1 relayer both placed on 1 server)
2. Multisig Bridge ( 3 validators and 2 relayers, each placed on separated servers - total 6 servers) Amazon AWS servers will be used as servers.

We used the second solution. But, as can be seen on the network, it was almost never in demand. That's why the servers that charge every month have been silenced. Three weeks after the announcement of the ETH bridge, it was commissioned at record speed.

We have researched the causes and consequences of this quite a bit. We could have had a supply problem when a token was created on the ETH side. The supply could have doubled. The supply problem had to be solved. A liquidity pool had to be created on the side of the ETH bridge. So on a DEX like uniswap a liquidity pool was required.

We understood more clearly how this problem can be overcome. For this, we thought of something like this. Creating a mefa contract in the ETH network and starting a new pre-sale after the audit. The pre-sale will be held in eth parity on the eth network. The pinksale platform can be used for this. So what to do next? Once a secure and locked-in liquidity token is created on the ETH side, the supply will be burned continuously according to a plan. The burn will correspond to 95 percent. A very small supply of 5 percent will be left on the eth side. And in order not to cause a supply problem in this 5 percent part, this much part will be burned by BSC. Thus, there will be no supply problem. When the price of the two pools is balanced, the bridge will be activated so that the mefa will live on both the eth and the bsc network. Because building the bridge first did not help anyone. The best way is to create a liquidity pool on both sides and connect these two lines with a bridge. However, this is currently considered purely draft and we can implement it after discussion and discussion with the community. We are also sure that a mefa token liquidity in uniswap will definitely reflect positively on mefa.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://whitepaper.metaversefacemaker.com/eth-bridge.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.