Search Results

0x12 in hex is 18 in decimal. So I think the error you're seeing is: /// Mint decimals mismatch between the client and mint #[error("The provided decimals value different from the Mint decimals")] Min …

You can create the token account first, which you can do in JS like this: const toTokenAccount = await getOrCreateAssociatedTokenAccount( connection, payer, // this is the funder (a signer) mint …

You can represent 18 decimal places in a 64-bit integer. If you put 2^64 into wolfram alpha then you'll get its scientific notation: 1.8446744073709551616 × 10^19. The 19 tells you that it can represe …

I'm not certain, but I think you'll find that once initialised the mint address can't be used to pay fees because it's not owned by the system program (it'll be owned by the token program). That'd mak …

If you followed that guide then at some point you'll have done spl-token mint <mint address> 100. Just do that again with any amount to mint more to yourself. Every token has a mint authority, which i …

You can use SystemProgram.assign to make the first account owned by a program. I'm not sure if it'll let you assign to an account that is not a program (eg it could check the owner is executable). It' …

First of all, msol and jitosol are both owned by the standard token program, so they don't use a custom program. You can see this by calling getProgramAccount, eg: curl https://api.mainnet-beta.solana …

You can use connection.getParsedAccountInfo(mint), which will give you the JSON of the mint account. Stackblitz example: https://stackblitz.com/edit/node-6hvxsq?file=index.mjs const mint = await conne …

getAssociatedTokenAddress takes as input, in order, the mint and then the owner to get the token account for. The token program and associated token program IDs are not required if you're using the de …

You can fetch multiple accounts together, using the getMultipleAccounts RPC call. That's also available in web3.js as connection.getMultipleAccountsInfo and connection.getMultipleParsedAccounts. In an …

The information about isSigner and isWritable comes from the header field of the transaction. It contains this data: numReadonlyUnsignedAccounts: number; numReadonlySignedAccounts: number; numRequired …

This isn't something apps are able to configure, and wallets are free to display whatever they like. This is a security feature for users. Usually the estimated changes are based on transaction simula …

I looked into this a bit myself a while ago, definitely not an expert but this is what I figured out: I think it's basically that the _checked variant requires you to pass the mint account and the num …

The Connection object doesn't have a publicKey field, which is why you're getting an undefined address. You can see all its fields/methods here: https://solana-labs.github.io/solana-web3.js/classes/Co …