You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The trusted-sync binary is an extremely lightweight implementation of a consensus node that offloads payload validation to a "trusted" rpc. Effectively, it's used to verify that the derivation pipeline (in the kona-derive crate) is producing valid payload attributes over the abstracted RPC providers - L1 provider, beacon client, L2 provider (for validating payload attributes).
Description
The
trusted-sync
binary is an extremely lightweight implementation of a consensus node that offloads payload validation to a "trusted" rpc. Effectively, it's used to verify that the derivation pipeline (in thekona-derive
crate) is producing valid payload attributes over the abstracted RPC providers - L1 provider, beacon client, L2 provider (for validating payload attributes).An effort is in the works to create a fully-featured L2 consensus client in https://github.com/paradigmxyz/op-rs. This will also provide backwards-compatible support with
trusted-sync
to run in "trusted" validation mode.The output of this ticket is to remove the trusted sync example from kona, as well as any accompanying jobs, tests, or other references. Notably, the trusted sync docker image github action workflow will need to be sunset in favor of a docker image with https://github.com/paradigmxyz/op-rs. (Note here to @refcell - replace trusted-sync in kubernetes - maybe even remove and just run reth + hera + op-reth?).
The text was updated successfully, but these errors were encountered: