Skip to content

Support cb-signer#2267

Draft
yorickdowne wants to merge 1 commit into
ethstaker:mainfrom
yorickdowne:eth-gas
Draft

Support cb-signer#2267
yorickdowne wants to merge 1 commit into
ethstaker:mainfrom
yorickdowne:eth-gas

Conversation

@yorickdowne

@yorickdowne yorickdowne commented Aug 31, 2025

Copy link
Copy Markdown
Collaborator

What I did

Add support for cb-signer. For better UX, a Python init script does some sanity checking of the config and sets the variables correctly for different clients.

(not mandatory) A picture of a cute animal, if possible in relation to what you did

image

@yorickdowne yorickdowne marked this pull request as draft August 31, 2025 16:12
@yorickdowne yorickdowne force-pushed the eth-gas branch 3 times, most recently from 03f58d1 to 8eaf075 Compare September 1, 2025 09:29
@yorickdowne

Copy link
Copy Markdown
Collaborator Author

On hold for now. It isn't clear what part of the ecosystem would be enabled by using cb-signer, and cb-signer itself isn't baked yet.

@yorickdowne

yorickdowne commented Jul 5, 2026

Copy link
Copy Markdown
Collaborator Author

This would be for eth-gas. Have to confirm that eth-gas uses standard commit-boost signer now, and how to configure https://github.com/ethgas-developer/ethgas-preconf-commit-boost-module

They use a relay now. Rather than do this twice, look at this idea post-Glamsterdam

It might be best to require web3signer when using eth-gas, ignore cb-signer entirely. And then ethgas would need to have a way to work with web3signer

From the CB docs, the cb_signer doesn't run when using web3signer :
"Web3Signer implements the same API as Commit-Boost, so there's no need to set up a Signer module. The parameters needed for the remote signer are:

[signer.remote]
url = "https://remote.signer.url

"

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.

1 participant