Closed MaksymZavershynskyi closed 4 years ago
@nearmax @k06a for Eth Bridge events needs, given we don't have events - what kind of support is actually needed? Why not store whatever value is needed in specified by contract key?
@nearmax @k06a for Eth Bridge events needs, given we don't have events - what kind of support is actually needed? Why not store whatever value is needed in specified by contract key?
@ilblackdragon There is a terminology collision. Let's call this "changes": https://github.com/nearprotocol/nearcore/pull/1910 , because they are not verifiable (we cannot construct individual proofs to them). And let's call whatever corresponds to Ethereum events "events". "Events" have proofs and can be emulated either by:
Is https://github.com/nearprotocol/nearcore/pull/2045 done? @k06a
Is #2045 done? @k06a
Yep, we need this PR to get merged before merging depending PRs in other repos.
Closing, as Denver is long in the past.
@kcole16 is going to be presenting on February 13. So the deadline is February 12.
We will be using testnet for the EthDenver, because all our online documentation is pointing to the testnet and was not updated to support stagingnet.
Here is the list of items that we want to have for the EthDenver:
env::collections::*