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

Rootstock checksum is not applied on the address page #2494

Open
vbaranov opened this issue Nov 1, 2024 · 0 comments · May be fixed by #2500
Open

Rootstock checksum is not applied on the address page #2494

vbaranov opened this issue Nov 1, 2024 · 0 comments · May be fixed by #2500
Assignees

Comments

@vbaranov
Copy link
Member

vbaranov commented Nov 1, 2024

If I am not mistaken, the hash displayed on the Address page is taken from the query string.

However, on Rootstock chains, the address checksum is different.

For instance if to open https://rootstock.blockscout.com/address/0x1723e4d5DAAc7D6761941237d9a70b200424AF41,
the page will display

Screenshot 2025-01-02 at 13 44 11

Which is Ethereum checksummed address.

At the same time correctly checksummed address hash can be taken from the API response:

curl -s https://rootstock.blockscout.com/api/v2/addresses/0x1723e4d5DAAc7D6761941237d9a70b200424AF41| jq ".hash"
"0x1723e4d5daAc7D6761941237d9a70b200424AF41"
@vbaranov vbaranov changed the title Rootstock checksum is not used on search results page Rootstock checksum is not applied on the search results page Nov 1, 2024
@vbaranov vbaranov changed the title Rootstock checksum is not applied on the search results page Rootstock checksum is not applied on the address page Jan 2, 2025
@vbaranov vbaranov transferred this issue from blockscout/blockscout Jan 2, 2025
@tom2drum tom2drum self-assigned this Jan 3, 2025
@tom2drum tom2drum linked a pull request Jan 3, 2025 that will close this issue
4 tasks
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 a pull request may close this issue.

2 participants