Closed Wollac closed 1 day ago
can i take on this issue ?
@mahmudsudo, sure! This is a good first issue
@Wollac, did you address this? I no longer see the deprecated call in the example (although the commit above it says "there are two options", and it's unclear what's that's referring to exactly) https://github.com/risc0/risc0-ethereum/blob/main/examples/erc20-counter/apps/src/bin/publisher.rs#L143-L146
If this is fixed, go ahead and close this issue
@nategraf good call, this was fixed as a byproduct in https://github.com/risc0/risc0-ethereum/pull/316
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: