airdrop | Laravel package to speed up deployment by skipping asset | Cryptocurrency library

In order to execute instructions on a program, the program data account has to be marked executable.

Make sure you deploy your program with solana program deploy in the CLI and that the deployment is successful.

You can check what is deployed at the publicKey and if it is marked as executable with getAccountInfo

Gatsby must be using an algorithm or key size which is no longer allowed by default with OpenSSL 3.0.

UPDATE ⚠️

This is most likely a webpack issue - https://github.com/webpack/webpack/issues/14532

They have since released a fix in version 5.61.0 - https://github.com/webpack/webpack/releases/tag/v5.61.0 - so upgrading webpack should address the issue as well

A member of the webpack team has stated they do not plan to backport the fix to webpack 4, so if you are on webpack 4 you may need to look to upgrading to webpack 5 first.

From Node.js 17's announcement post:

If you hit an ERR_OSSL_EVP_UNSUPPORTED error in your application with Node.js 17, it’s likely that your application or a module you’re using is attempting to use an algorithm or key size which is no longer allowed by default with OpenSSL 3.0. A new command-line option, --openssl-legacy-provider, has been added to revert to the legacy provider as a temporary workaround for these tightened restrictions.

Running this on the terminal might look like:

solana-keygen recover 'prompt:?key=0/0' -o phantom_wallet.json

The system transfer requires that, at a minimum, the from account is a System Owned account. Not a PDA and not a Program Owned account.

If the PDA is owned by your program then your program can transfer from it to ANY account without invoking the system transfer.

See the cookbook: https://solanacookbook.com/references/programs.html#transferring-lamports

As far I studied, there is no way how to trigger it programmatically.

Also, what more I was interested in. Sharing dialog cannot be customised in a way where you would show only one item/service in the sharing dialog. For example, if you would like to offer sharing to WhatsApp only, it's not possible. But there is work around for doing with AirDrop only, as stated here: https://stackoverflow.com/a/36573915/13406256

No matter what, in order to airdrop tokens, you'll need to pay for the rent-exempt reserve for the recipient's token account, which is 0.00203928 SOL for each person.

After that, you'll need to pay for the transactions to mint to all of these recipients. If your payer key is the same as the minting authority, that comes out to 0.000005 SOL per transaction, and you should be able to fit quite a few mintings in one transaction.

Take a look at https://github.com/solana-labs/solana/tree/master/tokens#distribute-spl-tokens for an easy tool to distribute tokens.

This is a shot in the dark, but it looks like you're trying to use the keypair for the address DEVw4sdjjwo3he1JgJbycZuWmZuC28YFMEY9uYpnP7cP to do the deployment on devnet, but that account has no funds on devnet: https://explorer.solana.com/address/DEVw4sdjjwo3he1JgJbycZuWmZuC28YFMEY9uYpnP7cP?cluster=devnet

I'm not sure exactly how the script works, but to be safe, you can airdrop into both your default account and that account:

Program deploys are done through the TPU (transaction processing unit) of the validator, which listens to a different port, 8003. If that port isn't accessible, then sending the program deploy transactions will fail.

You can start by adding port 8003 in your startup, and if it's still failing, open up every port listed in the Dockerfile: https://github.com/solana-labs/solana/blob/005592998dd107b3d54d9203babe24da681834f5/sdk/docker-solana/Dockerfile#L3

You need to first calculate the contract address in the target chain and then tip it up to 1 EVER for deployment to succeed.

The amount of gas needed depends on the code of the contract, but cannot exceed 1 EVER.