Search Results

You could use the logsSubscribe websocket endpoint for all transactions involving the token program, TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA, ie: { "jsonrpc": "2.0", "id": 1, "method": "logsSubscribe … mint by searching for Instruction: InitializeMint https://github.com/solana-labs/solana-program-library/blob/ca091b1711667bbb456c52f06e809d16b9255af3/token/program/src/processor.rs#L856 or the creation …

To add metadata to a token mint, you must sign with the token's mint authority. … Unfortunately, this mint has no mint authority: $ spl-token display 9bnKvEK2ymzbrtKGeCSbDtn7Dr1afCQoTTH1y4fL5seK SPL Token Mint Address: 9bnKvEK2ymzbrtKGeCSbDtn7Dr1afCQoTTH1y4fL5seK Program: TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA …

The concept is similar to wrapped ETH on Ethereum, which turns ETH from a native token to an ERC-20. Essentially, SOL is the native token on Solana, so it's ingrained into the base protocol. … SPL-Token provides a way to send SOL into an account and pretend like the SOL is a normal SPL-Token, and this process is called "wrapping". …

You can view the token on Solscan by clicking in the top right corner when viewing the token in Phantom. From there, you can see how people are interacting with it. … Or you can do more research on the token from the Solscan page. …

You can create a token with the "transfer fee" extension, and set the fee withdraw authority to the PDA for some simple program which allows anyone to withdraw and burn the fees on any account. …

There are two ways to make this much safer: Wallets warn whenever a wallet signature is made available to an opaque (non-system, non-token) instruction. … Users should be educated to treat the request for a signature on such an instruction as highly suspect The token program prohibits CPI calls with the user authority, forcing opaque programs to directly …

If new tokens are minted from a Mint Account that has this extension enabled, would the UI calculation for accrued interest be based on the entire life of the mint account (instead of accruing starti …

Another option is to use the token metadata extension that's available directly inside of the token-2022 mint. … spl-token initialize-metadata <MINT_ADDRESS> <NAME> <SYMBOL> <URI> And from there, you can update your metadata: $ spl-token update-metadata <MINT_ADDRESS> <KEY> <VALUE> …

/program/src/processor.rs#L790 This means that the mint hasn't been initialized yet, or at the very least, that it isn't assigned to the token program. … Be sure to create and initialize the mint before creating the associated token account. …

For example, a transfer hook might want to deduct a fee in USDC for a royalty payment, which requires token accounts, program, and a separate signer. …

Frozen token accounts are completely unusable by the owner. More info at https://spl.solana.com/token#freezing-accounts …

getTokenLargestAccounts requires an index on part of the token program, which is TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA. … To fix this, you'll need to use another node or configure your existing node to also index token accounts by passing --account-index spl-token-mint. …

If you want to find out the amount of burned tokens, you'll need to crawl through all transactions involving the mint address and look for burn instructions in the top-level or inner instructions.

The best option is to default to associated token accounts in your tooling and clients, but support any token account if it's provided to the program, similar to how the spl-token command-line utility … There, you can do: spl-token transfer <MINT_ADDRESS> <AMOUNT> <RECIPIENT_WALLET_ADDRESS>, which defaults to associated token accounts everywhere. …

its resolution: https://github.com/solana-labs/solana-program-library/issues/3684 In the meantime, to get around this, you can avoid using the --owner flag and instead specify the owner's associated-token-account … address, ie: spl-token mint <TOKEN_MINT> 1 <ASSOCIATED_TOKEN_ACCOUNT_FOR_B_PUBKEY> --mint-authority <A_KEYPAIR_PATH> …