Update validator-info.md for BlockSync - #161
Conversation
Update validator-info.md for BlockSync
tbruyelle
left a comment
There was a problem hiding this comment.
Thanks for the submission — it can't be verified as it stands.
The transaction exists, but its memo is empty.
79A9B9DA7CC48C5ECC1B11BB9C7D257F6F9AF47B258EE9F891DD8167D9698F6C
The memo is the whole mechanism — it is what binds specific Discord accounts to your validator key. Your row lists blocksync, but nothing on chain records that.
To fix: send 0.01 ATONE from your validator's own account to any ATONE address with blocksync in the memo, then update the row with that hash.
atomoned tx bank send <your-validator-account> <any-atone-address> 10000uatone \
--note "<your discord handles>" --chain-id atomone-1
validator-info.md changed after you opened this: #170 added every verified entry, so this branch now conflicts with main. Update your branch and add your row at the end of the table.
The three checks every submission has to pass, and the full audit of all 128 submissions, are in #168.
Update validator-info.md for BlockSync