Skip to content

Update validator-info.md for BlockSync - #161

Open
0xblocksync wants to merge 1 commit into
atomone-hub:mainfrom
0xblocksync:main
Open

Update validator-info.md for BlockSync#161
0xblocksync wants to merge 1 commit into
atomone-hub:mainfrom
0xblocksync:main

Conversation

@0xblocksync

Copy link
Copy Markdown

Update validator-info.md for BlockSync

Update validator-info.md for BlockSync

@tbruyelle tbruyelle left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants