Claim your SHERPA tokens
Your SHERPA allocation is released and claimable now.
@blaze.apps · @xyjmc · @happycapital · @futurem · @sherpa.promote · @swfg · @abrar65 ·
@tabula.rasa · @steem-space · @mostafezur001 · @steem-agora.evm · @xpilar · @xpilar.witness ·
@luxalok · @upex · @cur8 · @blazed007 · @yasu · @dhaka.witness · @justyy · @ahp93
124,930,791 SHERPA is held in a contract on the Steem Virtual Machine, waiting for you. There is
no deadline — your allocation cannot expire and nobody can take it. Claim whenever you like.
Claiming takes three steps:
- Link your Steem username to an EVM address (one time, ~5 minutes)
- Confirm the link in the SVM app
- Claim on the explorer
What you need first
- Your Steem account, with at least 1 STEEM to send
- MetaMask (or any EVM wallet) installed
Add the Steem VM network to MetaMask
| Network name | Steem VM |
| RPC URL | https://evm.steemvmscan.com |
| Chain ID | 81630 |
| Currency symbol | STEEM |
| Block explorer | https://evmscan.steemvmscan.com |
Step 1 — Link your Steem name to your wallet
Send 1 STEEM from your Steem account to svm.bank, and put your MetaMask address in the
memo.
To: svm.bank
Amount: 1.000 STEEM
Memo: svm-register 0xYourMetaMaskAddressHere
Send STEEM, not SBD. Both work for the bridge, but transaction fees on the Steem VM are paid in
STEEM — so if you bridge only SBD, you will arrive with no way to pay for the claim. The 1 STEEM
you send becomes 1 STEEM on your EVM address, which is far more than the few fractions of a cent a
claim costs.
Check the memo twice before sending. The memo is what decides which wallet your name links to,
and your name can only be linked once. Paste the address — do not retype it.
Step 2 — Confirm the link
Go to https://www.svmapp.com/wallet and connect the same MetaMask address you put in the memo.
You will see a pending incoming name registration request. Check that the Steem username shown
is yours, then confirm it.
Your Steem username and your EVM address are now linked.
Only you can do this. The confirmation has to come from your own wallet, which is why nobody —
not the Sherpa team, not anyone else — can link your account for you or claim on your behalf.
Step 3 — Claim your SHERPA
Open the contract's write page:
- Click Connect wallet and connect the address you just linked
- Find
claimin the Write section - Type your Steem username in the box
- Click Write and confirm in MetaMask
Your SHERPA arrives in the same transaction.
Type your username exactly like this
This is the one thing that goes wrong, so it is worth being careful about:
- no
@— typexpilar, not@xpilar - all lowercase —
blaze.apps, notBlaze.Apps - keep the dots and dashes —
tabula.rasa,steem-space
The contract matches your name character for character. A capital letter or a stray @ reads as a
different name, and you will get no allocation even though your allocation is sitting right
there. Nothing is lost — just fix the spelling and try again.
Check before you claim (optional, free)
On the same page, open the Read tab and find claimStatus. Type your username and it tells
you three things without costing anything:
amount— your allocationalreadyClaimed— whether it has been takenlinked— the address your name is linked to, or all zeros if Step 2 is not done yet
The amount is shown in the token's smallest unit, so 415,000 SHERPA appears as
415000000000000000000000. That is normal — there are 18 zeros' worth of decimals.
See your SHERPA in MetaMask
After claiming, add the token so your wallet displays it:
Token address: 0x6103286f7e807a9E582EDB35c503D0ee7851DE58 — symbol SHERPA, 18 decimals.
Your tokens are yours from the moment the claim confirms, whether or not your wallet is showing
them.
If you hold more than one account
Use claimMany instead of claim and pass your usernames as a list:
["myaccount","my.witness"]
Every name in the list must be linked to the wallet you are claiming from. If one of them is not,
the whole call is refused and nothing is claimed — so claim them one at a time with claim if you
are unsure.
@xpilar, please note: your two allocations have been combined into xpilar.witness at
915,000 SHERPA (500,000 + 415,000). Claim with xpilar.witness. Claiming with xpilar will say
no allocation, because that row no longer exists.
If something goes wrong
| Message | What it means | What to do |
|---|---|---|
no allocation | The name you typed is not in the table | Check for a leading @, a capital letter, or a missing dot |
name not linked | Steps 1–2 are not finished | Complete the link at svmapp.com/wallet |
not the linked address | You are claiming from a different wallet | Switch MetaMask to the address you linked |
already claimed | This allocation has been claimed | Check the receiving wallet — it is a one-time claim |
| Transaction fails on gas | No STEEM on your EVM address | Bridge a little STEEM (Step 1) |
Still stuck? Post in the Sherpa channel with your Steem username and the error message. You
never need to share a private key, a seed phrase or an active key to claim — anyone who asks for
one is trying to rob you.
Allocations
| Account | SHERPA |
|---|---|
| @blaze.apps | 50,415,000 |
| @xyjmc | 25,700,000 |
| @happycapital | 15,415,000 |
| @futurem | 15,000,000 |
| @sherpa.promote | 5,000,000 |
| @swfg | 2,700,000 |
| @abrar65 | 2,000,000 |
| @tabula.rasa | 1,500,000 |
| @steem-space | 1,415,000 |
| @mostafezur001 | 949,000 |
| @steem-agora.evm | 915,000 |
| @xpilar.witness | 915,000 |
| @luxalok | 416,791 |
| @upex | 415,000 |
| @cur8 | 415,000 |
| @blazed007 | 415,000 |
| @yasu | 415,000 |
| @dhaka.witness | 415,000 |
| @justyy | 415,000 |
| @ahp93 | 100,000 |
| Total | 124,930,791 |
Why it works this way
Your allocation was promised to a Steem account name, but SHERPA is a token on an EVM chain,
which only understands addresses. Those are two different kinds of thing, and only you can connect
them — the bridge requires the confirmation to come from your own wallet.
So the tokens were not sent out to addresses. Sending them would have meant guessing an address for
every account that had not linked yet, and an unlinked name resolves to nothing — the
transaction would have succeeded while burning the tokens. Instead the allocation table was written
into the contract once, and each person claims for themselves.
That contract has no owner, no admin and no recovery function. Nobody can change your
allocation, redirect it, pause your claim or take it back — including the people who deployed it.
The only thing it can do is pay a claimant. You can read the code yourself:
verified source.
The flip side is that it is permanent. SHERPA for a name nobody ever links stays in that contract
forever, and not even a governance vote can retrieve it. There is no rush — but there is also no
backup plan.
Contract: 0x377c9F86bE6492C73609EBd44411a8Ab7f674699
SHERPA token: 0x6103286f7e807a9E582EDB35c503D0ee7851DE58
Chain: Steem VM, 81630