Tools for running airdrop and token distribution campaigns on the Solana blockchain.

Fix options

context

If my understanding is correct, this options leaves flexibilities to add arguments like --fund-recipient and --allow-unfunded-recipient for spl-token command.

issue

Without this modification, the to_str() will fail because the self.options is always None It is not a critical bug, but maybe worth to fix it.

Fix csv header of unconfirmed log:

lu.write('recipient,amount,error') -> lu.write('recipient,amount,error\n')

Hi, it seems that I'm not able to perform the airdrop with flat-distributor, I've double checked everything and the env is correct, mint address, solana address etc.

The error I'm getting is:

Running the airdrop in non-interactive mode. The airdrop will run without additional confirmations.
--------------------------------------------------
Enter Y to proceed
> y
Log file handlers closed.
Cancelling the airdrop.

this happens instantly and quits. Nothing in the logs

Allow users to use --fund-recipient and --allow-unfunded-recipient flags in the transfer sub-command of distributor tools. Both flags behave in the same manner as they do in the spl-token transfer command.

• --fund-recipient - if an address doesn't own an associated token account, the sender will create one (and fund it, this costs a bit of SOL!)
• --allow-unfunded-recipient - complete the transaction, even if the recipient has 0 SOL on their balance.

check-before and check-after sub-commands have been adjusted to better account for this use-case.

FYI, all the fixes are the same as #1

Fix options

context

If my understanding is correct, this options leaves flexibilities to add arguments like --fund-recipient and --allow-unfunded-recipient for spl-token command.

issue

Without this modification, the to_str() will fail because the self.options is always None It is not a critical bug, but maybe worth to fix it.

Fix csv header of unconfirmed log:

lu.write('recipient,amount,error') -> lu.write('recipient,amount,error\n')

Duplication removal is now done immediately after fetching the raw address data.

This still only affects owner type addresses. A different solution is needed to better handle multiple token addresses that belong to the same account.

Resolves #5

Implement a --retry-on-429 option for distributors when using transfer sub-command.

This was previously the default behaviour, but we learned that if spl-token transfer returns a HTTP Too Many Requests error (429), this is not a guarantee of a failed transaction. This is a bug in how spl-token handles those errors and according to Solana developer support, a fix is on the way.

A transaction happening despite this error is rare, but it can happen. The safe way to treat this error is to consider the transaction as unconfirmed, until the error is fixed in spl-token. The --retry-on-429 option will use the old behaviour, where the tool retried the transaction if it encountered this error.

When a HTTP 429 error is received while transferring tokens, the distributor attempts to retry the transfer. In rare cases, the transaction is completed regardless of the error. A possible explanation is that the error happens while polling the transaction status, according to Solana developer support.

ATM there is no clear solution other than to handle a 429 error as an unconfirmed transaction, even though this happens very rarely.

Print the number of addresses that are being dropped to (flat-distributor and proportional-distributor) and print the estimated total tokens to be dropped (flat-distributor˙).

address-fetcher is supposed to sort the address - balance pairs by the current balance amount in the address-list-balance.txt file.

When using owner type addresses, the tool sums up the balances of all pairs that have the same owner address (this happens when an owner account owns multiple token accounts, likely because of trading on some dex). Those address - balance pairs are sometimes not sorted properly.

E.g. when fetching Samoyed owner addresses:

3o35HGWTqvkTUX77CZN4VrFg1xAzZrTqs2oEGxRSvjNm,6472.0
AVYXwvrJLCdqJ1dEKieTnpQHvndT2ef5wwhPTULqfFBd,10431.0
2bn5FRNy3SD2udDxkW6oQY1ghSY3buxForh6BKsagyis,6459.0

AVYX... account owns 2 SAMO token accounts.

A simple solution would be to sort the list again after summing up the duplicate balances, but this might impact performance.

When either distribution tool (proportional-distributor or flat-distributor) is started without any parameters and without a config file, it will still prompt for the RPC API URL, token address and token decimals before exiting.

./flat-distributor.py

Select an endpoint
1. https://api.mainnet-beta.solana.com
2. https://api.testnet.solana.com
3. https://api.devnet.solana.com
Select an option:
> 1

Enter the token mint address:
> aaaa

Enter the number of token decimals:
> 8
No mode selected, use -h

I use macOs 11.6 (Big Sur) When running the python script I got this error

% ./address-fetcher.py 
Traceback (most recent call last):
  File "./address-fetcher.py", line 4, in <module>
    import requests
ModuleNotFoundError: No module named 'requests'

Do I need to deploy some depencies to be able to run the script?