Skip to content

Chainweb Revolution - #49

Open
edmundnoble wants to merge 467 commits into
masterfrom
evm/main
Open

edmundnoble wants to merge 467 commits into
masterfrom
evm/main

Conversation

@edmundnoble

Copy link
Copy Markdown

This PR includes:

  • PayloadProvider, a new protocol that decouples the block execution and payload storage layer from the consensus layer thereby bringing us closer to a multi-process, clustered future for massively parallel nodes.
  • The Pact payload provider based on the existing PactService, with automatic migration from the previous version. This comes with a drastic simplification of the data flow between consensus and Pact, which should make future Pact development easier.
  • An "EVM" payload provider which uses an Ethereum node (specifically kadena-reth) as an execution engine, appearing to developers to be an ordinary Ethereum node with added cross-chain capabilities.
  • A minimal payload provider that only produces cross-chain proofs of miner rewards to be used on other chains. This is necessary not only for testing but also because chainweb requires the use of expander chain graphs which may be larger than the desired chain count at a given time. For example, the next largest chain graph has 38 chains, and if we only wanted to add e.g. 5 EVM chains to mainnet, we could keep 20 Pact chains, 5 EVM chains, and 13 minimal chains.
  • Incremental block header and payload pruning and a standalone tool for executing this pruning on demand.
  • Improved fork resolution, meaning less scenarios where due to corruption an operator must manually rewind the node.
  • Optimizations and additional benchmark coverage for the catchup process.

There's much more to say about the EVM payload provider, but it will require more testing and updating to bring to mainnet, not to mention operational challenges that come with multi-process coordination and changes to the build.

edmundnoble and others added 30 commits May 30, 2025 14:12
Change-Id: Id000000003df0e6228643907b06fda6e13d2dea2
Change-Id: Id00000001b24cc3d269cffcf1b3a67d230747c18
Change-Id: Id000000056296ea25046e7a8b9b001e84c259047
Change-Id: Id0000000ed99ccb169d20e1c82392d7caeaebc07
Change-Id: Id00000004fff1e1eabf1711fa760fc3322b5c6d2
Change-Id: Id0000000d4951d048a44b5125ed5989baa634712
Change-Id: Id00000004bbbaefabb706f8ce15ce299b916598c
Change-Id: Id0000000b7c10bea6c1dd66d95c2bcba718a2e52
Change-Id: Id0000000cdc2ae11e7d1dd855f4a9d31f7a8262d
Change-Id: Id0000000faf6a22224ec34917461fad9062c07bd
The old code was not safe; the thread could be lost and not stopped in
theory, if PactService was interrupted.
Change-Id: Id00000001a7bf815abbbedd23159bd9c11a2bd00
Comment thread .github/workflows/macos.yaml Fixed
edmundnoble and others added 6 commits October 19, 2026 19:58
…ntain permissions'

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
The cabal-cache sync step fails intermittently (e.g. S3 access issues),
aborting otherwise healthy builds. Mark it continue-on-error so builds
proceed from source when the remote cache is unavailable.
The macos-latest runners fail to link with:
  ld: tapi error: malformed file ... MacOSX27.0.sdk ...
  unknown architecture arm64e.x1-macos
because clang and ld are picked from mismatched toolchains. Probe both
xcode-select locations and keep the one that can actually link.
The macOS workflow still pointed at the upstream kadena-cabal-cache bucket
with the upstream secret names, so the cache sync failed with exit code 1
on this fork. Point it at community-kda-cabal-cache with the
kda_community_* secrets, matching applications.yml.
@CryptoPascal31 CryptoPascal31 changed the title PayloadProvider + EVM Chainweb Revolution Oct 21, 2026
@CryptoPascal31
CryptoPascal31 added this pull request to stack #51 October 23, 2026 09:03
CryptoPascal31 and others added 14 commits October 30, 2026 21:43
Make the SPV proof fork error message version-aware via chainweb231Pact, matching master's forkedError. Since the SPV proof expiration window was introduced at the Chainweb231Pact fork, the message now reads 'target header is not in the chain or is out of bounds' for post-231 blocks instead of just 'target header is not in the chain'.

This threads the current block height and a HasVersion constraint into checkProofAndExtractOutput and its callers in both the Pact 4 and Pact 5 SPV support, since this branch's HeaderOracle only carries the chain id.
---------

Co-authored-by: KadenaFriend <241389759+kdafriend@users.noreply.github.com>
Updated permissions to allow write access to contents and added a step to generate and commit a freeze file if it doesn't exist. Adjusted conditions for various jobs to always run.
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

Successfully merging this pull request may close these issues.

6 participants