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

[ FEATURE REQUEST ] - Add IBC capability to Azure Blockchain #252

Open
GoodFaithParadigm8 opened this issue Aug 24, 2021 · 2 comments
Open

Comments

@GoodFaithParadigm8
Copy link

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ x ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

N/A

Any log messages given by the failure

N/A

Expected/desired behavior

When I launch a blockchain on Azure, I want my blockchain to have interoperability with other chains that have IBC implemented.

OS and Version?

EVM

Versions

latest

Mention any other details that might be useful

EVM machines and other corporate enterprise chains that are a part of the Hyperledger community are already implementing IBC, the Inter Blockchain Communication protocol. The nearest protocol that could be most useful is here.

Thanks! We'll be in touch soon.

@GoodFaithParadigm8
Copy link
Author

Teku is the Eth2 client powered by ConsenSys, built by the team behind Hyperledger Besu,
the leading Ethereum client for enterprises. It is the only client built to meet institutional
needs and security requirements.

Saw the closed issue #247 that Microsoft blockchain was being retired, and reference to ConsenSys.

@GoodFaithParadigm8
Copy link
Author

I'll leave this open for now, I don't see where the blockchain workbench is being retired as it's still in public preview.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant