-
Notifications
You must be signed in to change notification settings - Fork 31
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
Bech32 Prefix Mismatch During DRS-4 Upgrade #434
Comments
hi @eaddaa, thank you for that.
@artemijspavlovs will look into this. re
when you rebuilt the binary manually as instructed, did you happen to export |
hi @omritoptix Yes, I mistakenly used KITTY instead of kitty while exporting the prefix during the manual binary rebuild as instructed. I now understand this caused the mismatch and has likely affected the Rollapp's functionality. Currently, the Rollapp is not working, and I'm encountering the following issue: Before the upgrade, the RollApp worked for a while, but now it has stopped and is unreachable. Dec 27 06:38:35 vmi2293635.contaboserver.net roller[1435651]: time="Dec 27 06:38:35.495" level=info msg="Using pending block.[height 1517]" module=block_manager |
hey @eaddaa , re:
have you tried running |
hi @artemijspavlovs INFO starting migration process from a656462 to 7a981ca ❗ The Rollapp sequencer is in unhealthy state. Please check the logs for more information. 💈 RollApp ID: kittyverse_448466-1 💈 Filesystem Paths: Rollapp root dir: /root/.roller/rollapp 💈 Process Info: OS: linux |
Bech32 Prefix Mismatch During DRS-4 Upgrade
I encountered an issue during the DRS-4 upgrade process on the Rollapp platform. The error message indicates a Bech32 prefix mismatch:
Expected prefix: kitty
Received prefix: KITTY
This issue appears when querying an address or restarting services after the upgrade.
Additionally, when attempting to restart services, I received the following error:
Current balance: 67 DYM (67008604481108790246adym)
Necessary balance: 6 DYM (5010000000000000000adym)
Error: failed to restart systemd services: a migration from a65646 to 7a981c is required
Steps to reproduce:
Perform the DRS-4 upgrade.
Attempt to query an address or restart services with a prefix mismatch.
Encounter the error rollapp bech32 prefix does not match.
Attempt to restart services and receive the migration error.
Expected behavior:
The Bech32 prefix should match the expected value (kitty), and the services should restart without errors.
The system should not require migration from a65646 to 7a981c for the upgrade process.
Actual behavior:
The Bech32 prefix does not match, causing errors during address queries and service restarts.
A migration from a65646 to 7a981c is required, preventing services from restarting.
This issue seems directly related to the DRS-4 upgrade process. Can you please investigate and provide a fix for this?
The text was updated successfully, but these errors were encountered: