as Deepit we are building a certificate application on Ethereum and are evaluating POA as a side chain.
Quickly our use case: a user requests to notarize a document, the system take in charge this request and issues a ERC-721 token. The tokens are issued on POA for scalability, performance and cost reasons.
But if the user want he can transfer one or more token on the Ethereum network were we deploy a twin ERC-721 contract. The POA ERC-721 token will be burned and the same token will be minted on the Ethereum side by the twin ERC-721 contract. We need a bridge!
We studied the POA Token Bridge smart contracts and the issue 46 proposing support for ERC-721 tokens. Igor Barinov in a call with us proposed the use of the Arbitrary Message Bridge that is on the PR 77. We also found the Oracle extension that support AMB (https://github.com/poanetwork/token-bridge/tree/arbitrary-message-bridging).
We found AMB contracts and mechanism very exciting! We think that AMB contracts are in a good shape and they fit well with our use case. A ERC-721 bridge is also a good fit but AMB enable many possibilities and can address well generic future needs, so we are going to use AMB.
We have some questions:
- are the AMB smart contracts ready to deploy? if not we can contribute
- the AMB enabled Oracle on the branch is complete and working?
- it seems to us that the smart-contracts of AMB are so generic that it is enough to have only one instance (in each chain) for all users, in the production environment. But there are two working mode (SUBSIDIZED e DEFRAYAL) that suggest two different deploy. So we are asking what is your plan. Or do we need to do our deploy?
- again, the oracle is so generic that we think that are sufficient N instances (one for each validator) for all users; it is correct?
We have other questions about the implementation of our token but we leave them to a future post.
Thanks in advance