Adding Solana support

[johnpmitsch]

import { solanaWeb3, Solana } from "@quicknode/sdk";
const { Transaction, SystemProgram, Keypair, PublicKey } = solanaWeb3;

const mainSecretKey = Uint8Array.from([
//redacted
]);
const sender = Keypair.fromSecretKey(mainSecretKey);
const receiver = new PublicKey("redacted");
const senderPublicKey = sender.publicKey;

const endpoint = new Solana({
  endpointUrl:
    "https://some-cool-name.solana-mainnet.quiknode.pro/redacted",
});

const transaction = new Transaction();

// Add instructions for each receiver
transaction.add(
  SystemProgram.transfer({
    fromPubkey: senderPublicKey,
    toPubkey: receiver,
    lamports: 10,
  })
);

(async () => {
  // can use endpoint.connection, is @solana/web3js Connection
  // await endpoint.connection.sendTransaction(...)

  // Endpoint must added to Priority Fee API to do this
  const signature = await endpoint.sendSmartTransaction({
    transaction,
    keyPair: sender,
    feeLevel: "high"
  });
  console.log(signature);
})().catch(console.error);

If the user doesn't have the add-on installed:

[coveralls]

coverage: 95.714% (-3.0%) from 98.726%
when pulling 94ff395 on solana
into 7150e52 on main.

[amilz]

the issue is that your simulation did not include the priority fee instruction…so it’s returning too few compute units. If you fetch the priority fee before the simulation and pass it into your simulation transaction it works:

Suggested change

	async sendWithPriorityFees(
	transaction: Transaction,
	keyPair: Keypair,
	feeLevel: PriorityFeeLevels = 'medium'
	) {
	// eslint-disable-next-line prefer-const
	let [computeUnitPriceInstruction, units, recentBlockhash] =
	await Promise.all([
	this.createDynamicPriorityFeeInstruction(feeLevel),
	this.getSimulationUnits(
	this.connection,
	transaction.instructions,
	keyPair.publicKey
	),
	this.connection.getLatestBlockhash(),
	]);
	async sendWithPriorityFees(
	transaction: Transaction,
	keyPair: Keypair,
	feeLevel: PriorityFeeLevels = 'medium'
	) {
	const computeUnitPriceInstruction = await this.createDynamicPriorityFeeInstruction(feeLevel);
	const allInstructions = [...transaction.instructions, computeUnitPriceInstruction];
	// eslint-disable-next-line prefer-const
	let [units, recentBlockhash] =
	await Promise.all([
	this.getSimulationUnits(
	this.connection,
	allInstructions,
	keyPair.publicKey
	),
	this.connection.getLatestBlockhash(),
	]);

[amilz]

@johnpmitsch I'm wondering if insteading of (or maybe in addition) this being a sendSmartTransaction it's assembleSmartTransaction (or something like that), where we return the new Transaction object instead of sending it to the network.
the benefit here is that many circumstances, you're dealing w/ a wallet, not a keypair. In that case, I think it might be more useful to be able to pass in my instructions (or transaction) and return the smart transaction...then I can sign/send with my wallet adapter.
WDYT?

[amilz]

any reason this shouldn't be private?

[amilz]

I think you don't need this since you pass allInstructionsn

Suggested change

	const computeUnitPriceInstruction =
	await this.createDynamicPriorityFeeInstruction(feeLevel);
	const testInstructions = [...instructions, computeUnitPriceInstruction];
	const testInstructions = instructions, computeUnitPriceInstruction;

[amilz]

is there any risk that these values go stale while we process the rest of the function?