Merged
Conversation
andreabadesso
moved this from In Progress (WIP)
to In Progress (Done)
in Hathor Network
r4mmer
previously approved these changes
Apr 16, 2025
luislhl
reviewed
Apr 16, 2025
| To run the seed and add the HTR token again, use the following command: | ||
|
|
||
| ``` | ||
| yarn dlx sequelize-cli db:seed:all |
Collaborator
There was a problem hiding this comment.
For this to work, I think there should exist a .env file with the right variables, is that correct?
Maybe we should state this in the guide.
Also, I believe NODE_ENV=production should be present among the variables, otherwise it will always try to connect to a database in localhost instead.
Collaborator
Author
There was a problem hiding this comment.
I updated the readme with the minimal env variables required to run the seeder
r4mmer
approved these changes
Apr 24, 2025
luislhl
approved these changes
Apr 24, 2025
github-project-automation
Bot
moved this from In Review (WIP)
to Waiting to be deployed
in Hathor Network
r4mmer
added a commit
that referenced
this pull request
Jul 3, 2025
…-lib-v2.1.1 * origin/master: chore: bumped to v1.9.0 (#259) chore: nano-testnet-hackaton (#243) fix: address invalid parameter (#235) chore: added htr token seed (#256) fix: invalid assert in release tx proposal utxos (#251) fix: we should await mark utxos with proposal id to prevent a race condition (#250) Merge pull request #248 from HathorNetwork/feat/version-camel-case fix: v1.8.2-rc.3 qa issues (#246) fix: firebase env variables should be optional (#245) chore: remove error handler middleware from authorization lambda (#242) feat: version data validation (#241) fix: Mainnet release script (#203)
This was referenced Nov 17, 2025
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
Previously, the HTR token was inserted via a migration, which could lead to issues if the database was reset or cleaned, as the migration would not re-insert the token. Additionally, there was no clear, documented process for cleaning up the database and reseeding essential data.
This PR introduces a proper seed script for the HTR token that dynamically calculates its transaction count, and updates the documentation to provide clear instructions for database cleanup and reseeding.
Acceptance Criteria
Checklist
master, confirm this code is production-ready and can be included in future releases as soon as it gets merged