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.

Sign up for GitHub

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

Jump to bottom

Map Beacon Chain explorer from Config Service #1974

Open
iamacook opened this issue Sep 30, 2024 · 0 comments · May be fixed by #1976
Open

Map Beacon Chain explorer from Config Service #1974

iamacook opened this issue Sep 30, 2024 · 0 comments · May be fixed by #1976
Assignees
@iamacook

Comments

@iamacook
Copy link
Member

Description

We intend to return a value for the Beacon Chain explorer on the Config Service so clients need not use a hardcoded value per chain. This then needs to be mapped to the Chain entity on all layers accordingly.

Requirements

  • Add the new property to the relevant datasource schema.
  • Map datasource property to domain.
  • Add/update tests accordingly.

Additional information

No response
@iamacook iamacook linked a pull request Sep 30, 2024 that will close this issue
Open
@iamacook iamacook self-assigned this Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@iamacook iamacook

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Map beaconChainExplorerUriTemplate property safe-global/safe-client-gateway
1 participant
@iamacook