BLD Staker Airdrop Guide

[otoole-brendan]

So you want to airdrop to BLD stakers? (A guide by Agoric)

Reach out

The first thing you’ll want to do is reach out to the Agoric team (via Discord or Telegram) and let them know you’re planning on including BLD stakers in your airdrop.

Request a Snapshot

You’ll likely need a delegator snapshot that includes all BLD staker addresses and amount of BLD staked. Please request this from us via appropriate channels when required.

118 vs 564 Coin type addresses

If your airdrop supports both 118 and 564 coin-type addresses then you should be able to get what you need from querying the snapshot as is. However if your airdrop only supports 118 coin type addresses, there are additional steps that some BLD stakers and you need to take to ensure their inclusion in their airdrop.

The kind of coin-type address a BLD staker has depends on whether they are using a ledger device or not.
Ledger accounts are 118 coin-type addresses whereas non-ledger accounts are 564 coin-type addresses. Only the account owner might know if they have a 118 or 564 account - it’s possible they also don’t know.

Note to airdropper: If your airdrop only supports 118 coin-type addresses - BLD stakers will need to take the below steps in order to designate a 118 address from their existing delegate addresses (such as a 564 coin-type address) in order for the airdrop to reach them. As part of your airdrop announcement and communications - we advise you to direct the BLD staker community to this guide should they need to take some action in order to receive the airdrop (e.g. if they don't yet have an 118 coin type address per below). Agoric will similarly co-market and support as needed.

Obtaining a 118 coin-type address (if you’re a non-ledger BLD staker)

Follow below instructions to generate a 118 coin-type address

1. In Keplr, click Profile -> ‘Add Wallet’ -> ‘Import an Existing Wallet’
2. Enter your known seed phrase for your existing account
3. Click ‘Advanced’
4. Enter ‘118’ in the first field under HD Derivation Path (see screenshot below)

5. Hit ‘Import’
6. Name wallet i.e. ‘Coin-type 118’
7. Select chains (including ‘Agoric’)
8. Hit ‘Save’

As BLD Staker: Ensuring your new 118 address is queryable/findable in snapshot

Once you have your 118 coin-type address (copied from Keplr), you'll need to send 1/1000000 BLD (1ubld) from your 564 account to your new 118 address with the following text in txn memo field:

The sender designates the recipient as the Agoric address to use in the [insert airdropper name] airdrop

As Airdropper: Querying historical events for 564-derived 118 addresses in delegator snapshot

In order to query these newly derived 118 addresses in your airdrop, you’ll be able to search for them using events:

Here is an example of a query that could be made against an archival RPC node to check for transfers of 1ubld from a given staker address (such as a 564 address), with a matching memo (as above) to designate a replacement recipient (the 118 address above).

memo="The sender designates the recipient as the Agoric address to use in the [insert airdropper name] airdrop"
staker=agoric1...
agd query txs --node=<your archival RPC node> --limit=100 \
  --events="transfer.amount=1ubld&transfer.sender=$staker" -o json |
jq -r --arg staker "$staker" --arg memo "$memo" '.txs[]
 | select(.tx.body.memo == $memo)
 | [
 $staker, .timestamp,
 (.logs[].events[] | select(.type == "transfer") | .attributes[]
   | select((.key == "amount" and .value == "1ubld") or
     (.key == "sender" and .value == $staker) or
     (.key == "recipient"))
   | select(.key == "recipient")
   | .value)
 ]
 | @csv'

Support

If you’re still having issues - please reach out to us in our Support channel on Discord and we’ll be happy to assist

[michaelfig]

The agd query txs command fails with a base64 error, and will not work until agd upgrades to Cosmos SDK v0.47.