Forgotten Heroes,
As of last week we’ve entered into Phase 2, most notably with the liquidity pools being launched. Now comes the time to resume the protocol, with block production and claims. We will mainly cover necessary steps for validators who were previously participating in the protocol, however most of this will apply to new participants.
Validator ID’s: Parent/Child Relationship
First point worth mentioning, is that if you are a participating Validator and still have a V1 ID, you will need to migrate it to a V2 ID. This can be done at heroglyphs.com under <d> “Identities”. Be sure each ID is set to set to a Validator Index (as found on beaconcha.in). For those who are not currently Validating, there is no rush to migrate.
Some people are running multiple Validators on one machine, and using great tools like Dappnode to manage them. One of the biggest drawbacks was that validators were not able to have more than one graffiti set per machine. With each Validator now requiring its own ID to be attached to the Validator Index, a work around was created involving a Parent / Child relationship for the IDs. Essentially, when a Heroglyphs block is proposed, the protocol will look at the ID, and see if there is any Children attached to ID in the proposed graffiti. Provided that the Validator Index which proposed the block is associated with one of the Children under the Parent ID used in the graffiti, the protocol will recognize the Child ID, and send the applicable tokens to the corresponding wallet. In short, the protocol looks at the “Identity Router” and checks if Child ID is one of the Validator Index associated with the proposed block.
To set up Parent / Child IDs:
Click on Identities, or press <d> to open the Identity panel
Be sure you have migrated from V1 to V2
Click on “Your IDs”
Click on the ID you wish to make the Parent
Click on Add Child Identities
Select the IDs you wish to re-route
Note: IDs are non-transferable. Therefore, should you wish to hold your assets in a different wallet, you can change the Receiving Address, and this should be the address that contain any of your Genesis Keys.
Medals, $BADGES, and Redirecting
Heroglyphs will resume and be live for claiming as of May 29 at 00:00 UTC. Any Validators who proposed valid Heroglyphs blocks previous to, and during the pause will be recognized and eligible to receive tokens. If this applies to you, it is necessary that all of your ID Receiving Addresses, and Withdraw Credentials or Redirect parameters are set up accordingly to ensure you will receive your tokens when the protocol resumes.
Medals are an offchain indicator to track all Validators that attest blocks. Medals are sent to the Withdraw Credential or to the Redirect Address. All Medals got erased, and the system restarted at Epoch 285,400. Old Medals/$BADGES will therefore not be eligible for claiming tokens. Going forward, Medals will be awarded at a more fair and liberal supply rate.
Some people prefer to keep their Withdraw Credential Address clean, or prefer not to have it active, so you can set a redirect wallet for your Medals/$BADGES. To do so, perform the following:
Click on Claim or press <g>
Click on Redirect $BADGES rewards or press <w>
You now have the option to
Redirect as Withdraw Credential
or if the Withdraw Credential is on a different device or isolated, can utilize the following:
Generate Permit Signature (json)
Redirect with Permit
With any of the options above, you will need to provide the Address in which you plan to redirect the Medals/$BADGES to, and sign on the corresponding wallets to prove ownership.
If any of the following is not yet set, you have until May 29 00:00 UTC to update any parameters, to ensure all rewards are directed accordingly. If they are not set before then, they will not take effect until you do so, and any previous rewards may not be retrievable depending on your configuration.
The protocol will take ~30-40 hours to fully sync up to the current Epoch.
Attesting and Proposing Blocks
After approximately 15 days (3375 Epochs) of consistent, uninterrupted validating, you should have attested enough blocks to redeem 1 $BADGES from the Medals you have accrued. Please note this is an estimate, and may not be exact. The Medals will be tallied to the Withdraw Credential by default, unless you have set the Redirect Address.
$BADGES are Soul-Bound Tokens (SBT) and can not be transferred. Once you have accrued whole numbers of $BADGES, you can redeem each of them for Genesis Tokens. Please note, that you will need to have the Genesis Key NFT in the corresponding wallet (Withdraw Credential / Redirect Address) in order to claim the desired token. You can add the desired NFT prior to claiming.
If your Validator proposes a block which contains a valid graffiti, tokens listed in the graffiti will be sent to the wallet associated with the ID, as discussed above. When you propose a block the reward is set to a fixed amount per execution, plus a time-base bonus capped at 1 day (24hrs) if the token has not been called in a while.
If you were using custom tickers in your graffiti in the past that point to Genesis Tokens, those tickers will need to be recreated before the protocol goes live in order for the tickers to be considered valid. If they are not, they will be ignored from the graffiti. If you had a custom ticker and attempted to withdraw and migrate, and encountered an issue, please reach out in Discord about this. Ticker withdraws and migrations should all be fine going forward.
Hopefully this is enough information to get you Heroes back on track with the protocol, and provide you with much more flexibility for management of your assets and wallets.
Onward Heroes.
Website:
http://heroglyphs.com
X.com:
https://x.com/hero_glyphs
Discord:
https://discord.gg/heroglyphs
Telegram:
https://t.me/hero_glyphs
Warpcast/Farcaster:
https://warpcast.com/heroglyphs
Lens/Hey:
https://hey.xyz/u/heroglyphs
Github:
https://github.com/HeroglyphEVM
