Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(e2s): add RoleTester service account key for mainnet part 1 #2352

Closed
wants to merge 1 commit into from

Conversation

kc1116
Copy link
Contributor

@kc1116 kc1116 commented Nov 1, 2024

This PR adds a RoleTester key for mainnet so that we can submit xmsgs to mainnet via a script.

issue: #2275

- Add new key type for "service" keys or keys not used for anything protocol or stack related

- map RoleTester to mainnet service key to be used for test mainnet app
@kc1116
Copy link
Contributor Author

kc1116 commented Nov 1, 2024

Currently the key generation tool assumes that all keys being created for a application service. This PR adds the Service key type so that we can generate keys for utility purposes.

 go run e2e/main.go key-create -f e2e/manifests/mainnet.toml --name=tester --type=service

We generated a new service key for mainnet and mapped it to the RoleTester. Now we can access this key in the e2e app the same way we access RoleTester for other networks.

Copy link
Contributor

@chmllr chmllr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code LGTM, can't validate the logic yet.

@@ -46,5 +46,6 @@ var statics = map[netconf.ID][]Account{
remote("0x9496Bf1Bd2Fa5BCba72062cC781cC97eA6930A13", RoleDeployer),
secret("0xfD62020Cee216Dc543E29752058Ee9f60f7D9Ff9", RoleMonitor),
secret("0x6191442101086253A636aecBCC870e4778490AaB", RoleRelayer),
secret("0x84aC7eeC1e035Fa13a7DEBD5f6da69B82CBDC5B5", RoleTester),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wouldn't it be better for this account to be remote type, managed by Fireblocks?

@@ -22,14 +22,15 @@ const (
P2PConsensus Type = "p2p_consensus"
P2PExecution Type = "p2p_execution"
EOA Type = "eoa"
Service Type = "service"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no need for a new type, this is an eoa

@@ -4,6 +4,9 @@ public_chains = ["ethereum","arbitrum_one","base","optimism"]
multi_omni_evms = true
prometheus = true

[keys.tester]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

don't think this is the way to go, it deplicates whatever is in the eoa package. Follow the same patterns as relayer and monitor keys.

Copy link
Collaborator

@corverroos corverroos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Blocking review since christiaan aproved and this is not the 100% correct way to go

@kc1116
Copy link
Contributor Author

kc1116 commented Nov 4, 2024

Did not have to do.

@kc1116 kc1116 closed this Nov 4, 2024
@corverroos corverroos deleted the khalil/mainnet-tester-account branch November 22, 2024 15:44
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.

4 participants