-
Notifications
You must be signed in to change notification settings - Fork 955
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
CI for the eth-bridge-integration
branch
#394
Conversation
eth-bridge-integration
brancheth-bridge-integration
branch
eth-bridge-integration
brancheth-bridge-integration
branch
pls update wasm |
2 similar comments
pls update wasm |
pls update wasm |
8d7b66f
to
c285b74
Compare
pls update wasm |
7 similar comments
pls update wasm |
pls update wasm |
pls update wasm |
pls update wasm |
pls update wasm |
pls update wasm |
pls update wasm |
Create an Ethereum bridge sub-crate
…llocator Plug `BlockSpaceAllocator` logic into `ProcessProposal`
Malformed transactions can cause the node to panic because this function unwraps values. Return the proper error, or a failure if asked to verify a transaction with no shielded part.
* ray/vp-verify-masp-failure: changelog: add #942 vp_verify_masp: avoid panicking unwrap()s
Merge v0.12.1
Fix Tendermint release in CI
pls update wasm |
…tor-specs Write specs for the `BlockSpaceAllocator`
…posal Optimize block proposal
…al-alloc Fix allocator logic in `ProcessProposal`
@james-chf Is this PR still relevant? |
This PR is only open to run CI against |
* Add scripts to start proxy, update Cosmos env for consistency * Add proxy env to extension, update README.md * SDK & Query must also use proxy if specified
This PR is for running CI on every merge to the
eth-bridge-integration
branch. It shouldn't be merged so should stay as a draft PR. This PR should ideally always be building green.