Mainnet Activation Blog Post #639
Merged
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
danield9tqh
reviewed
Mar 7, 2024
| - [FIP-8](https://fips.ironfish.network/fips/fip-8-difficulty-adjustment) : Difficulty adjustment (to accommodate the algorithm change) | ||
| - [FIP-9](https://fips.ironfish.network/fips/fip-9-swap-randomness-and-graffiti) : Swap randomness and graffiti field positions in the Block Header | ||
|
|
||
| The most notable change is the hashing algorithm switch from blake3 to FishHash. To read more about FishHash, the motivation behind finding a new hashing algorithm for Iron Fish, as well as exploration of other algorithm choices, please see [FIP-3](https://fips.ironfish.network/fips/fip-3-memory-hard-mining-algorithm) (or community created video walkthroughs like this [one](https://youtu.be/1R7VffTzM9g?si=U0PhustQsp8TG9ak)). Please note that [FIP-9](https://fips.ironfish.network/fips/fip-9-swap-randomness-and-graffiti) that is included in this hardfork also changes the Block Header format for Iron Fish. |
There was a problem hiding this comment.
Don't think we need to call out FIP-9 again explicitly here as it only changes the block header when mining. Not changing the block header in other contexts like networking layer or block explorer
danield9tqh
reviewed
Mar 7, 2024
|
|
||
| If you’re using the Node App, please make sure to upgrade it as well to **[version 3.0](https://ironfish.network/use/node-app) (or greater if available).** | ||
|
|
||
| ### What you need to know if you’re a miner or a mining pool |
There was a problem hiding this comment.
I think we should have separate sections for miners and mining pools. Miners are a big cohort and mostly don't run a node whereas mining pools run a node. So very different instructions. For miners I like something like
### What you need to know if you’re a miner
At block 503,338 (~April 2nd) miners will need to manually switch their devices to start mining FishHash instead of blake3. Your mining pool should already be compatible with the change. All [major mining software](https://ironfish.network/use/get-started/mining#mining-software) developers are planning on releasing new versions that include a FishHash miner. Be on the lookout for a new release of your mining software that includes FishHash which should be available at least a week before the hardfork.
There was a problem hiding this comment.
For pools maybe something like
### What you need to know if you’re a mining pool
You need to **upgrade** your Iron Fish node **as soon as possible** to [version 2.0.0](https://github.com/iron-fish/ironfish/releases/tag/v2.0.0). Some notable changes for pools:
- [FIP-2](https://fips.ironfish.network/fips/fip-2-enforce-sequential-block-time) : If your pool creates blocks with negative timestamps those will no longer be valid after the hardfork
- [FIP-3](https://fips.ironfish.network/fips/fip-3-memory-hard-mining-algorithm) : The obvious switch of the mining algorithm from blake3 to FishHash
- [FIP-9](https://fips.ironfish.network/fips/fip-9-swap-randomness-and-graffiti) : randomness and graffiti field positions are switched in the Block Header
All these changes are included in the Node v2.0.0 release but if you have customized your node make sure that those changes are still compatible
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changed?
Mainnet Activation Blog Post