Versions Compared

Old Version 2

changes.mady.by.user Silas Davis

Saved on

compared with

New Version Current

changes.mady.by.user Angelo De Caro

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

- v0.31.0 - Much goodliness - WASM and complete eWASM improvements galoresupport, Vent support for mainline Ethereum, Web3 fixes, cross-smart-contract-engine calling

...

After a fallow period in Q4 2020 Burrow has seen the best quarter of activity I can remember. We have made significant strides in supporting WASM and draft eWASM standards completed the draft ewasm standard supported by Sean Young's work on (https://github.com/hyperledger-labs/solang) with Burrow as a supported ledger. This means that Burrow combined with Solang offers a complete stack for compiling and running Solidity ewasm contracts. Since Fabric, Sawtooth, and Iroha already consume the Burrow EVM implementation, these could easily be extended to also include the ewasm implementation. This would make it possible to use Solang and other ewasm tooling with those ledgers.

Vent - our Ethereum-to-SQL mapping layer now supports listening to web3 JSON-RPC chains (all mainline Ethereum clients) to build tables. This opens up interesting possibilities for contract oracles, state channels, and layer-2 scaling. We have continued to keep up-to-date with the latest Tendermint.

We now also support calling between our three smart contract engines - EVM, WASMewasm, and Go 'natives'. Our calling and state conventions are all Ethereum, but provide a lot of flexibility compared to mainline Ethereum clients.

...

Burrow is preparing itself to support connection to multiple other chains by supporting reading from Ethereum with Vent and we soon hope to support Cosmos via the IBC protocol which we are poised to adopt based on our use of Tendermint consensus.

I want to provide support for AssemblyScript (a subset of Typescript) contracts via eWASM ewasm that can call, and be called from Solidity.

...

...

One of the most battle-tested and potentially widely applicable parts of burrow is Vent - our SQL mapping layer. To my knowledge nothing else quite like it exists serving the Solidity/Ethereum community. With our recent addition of Ethereum support I believe this component of Burrow might be of significant value even to those not using Burrow today. It would be useful to have an opportunity to describe briefly how this component works, what one can do with it, and to solicit opinions on how to attract collaborators.

I think the recent developments with Vent and our ewasm abilities could position Burrow as a pragmatic state channel/oracle solution for public blockchain.

Reviewed By