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 erc20-counter example currently dynamically creates either a block or a beacon commitment depending on its command line arguments. This uses the deprecated into_beacon_input:
// Finally, construct the input from the environment.
let evm_input = if let Some(beacon_api_url) = args.beacon_api_url {
#[allow(deprecated)]
env.into_beacon_input(beacon_api_url).await?
} else {
env.into_input().await?
};
Instead, the intended behaviour in steel v1.1 is to use builder.beacon_api(url). However, as we are using a typed builder pattern, the following will not work as the type of the builder changes:
The erc20-counter example currently dynamically creates either a block or a beacon commitment depending on its command line arguments. This uses the deprecated into_beacon_input:
Instead, the intended behaviour in steel v1.1 is to use
builder.beacon_api(url)
. However, as we are using a typed builder pattern, the following will not work as the type of the builder changes:The text was updated successfully, but these errors were encountered: