Search Results

So typically how an Anchor application works is that you have the smart contract, a frontend for the user to interact with, and in-between that are calls to the smart contract using the @project-serum …

You forgot to add a <'info> for your Initialize accounts struct. #[derive(Accounts)] pub struct Initialize <'info> { #[account(init, payer = signer, space = 8 + 8)] pub new_account: Account<'i …

What you have above is how the smart contract "itself" gets the current time. When you add anchor.web3.SYSVAR_CLOCK_PUBKEY to your accounts, you're not passing in time from the frontend. You're simply …

Your seeds for global_authority in the validator are [GLOBAL_AUTHORITY_SEED.as_ref()]. Your signer seeds are [GLOBAL_AUTHORITY_SEED.as_bytes()]. These don't match and that's why you're getting that er …

This is an issue with Anchor 0.26. It won't actually stop your project from being built so you should just ignore it.

Clockwork lets you do this. It's an automation engine that lets you schedule transactions. Check out this repo for an example of on-chain usage. Here a Pda is given delegation over a token account, ma …

You’ll have to make sure that both the sending and receiving account are marked as mut on the client side. If you’re using anchor, you can do this by annotating the account field with the #[account(mu …

Short answer: The answer is that there's no difference. In this case, #[account] has no effect in the generated code. The reason for this is that the parsing logic for the #[account] macro in this spe …

0x0 means that you're attempting to initialize an already initialized account. If tx initializes your vote account then tx1 fails because it tries to initialize it again.

Try this: impl<'info> BuyIn<'info> { pub fn transfer_to_vault(&self, amount: u64) -> Result<()> { let cpi_context = CpiContext::new( ctx.accounts.system_program.to_account_info …

'info is a lifetime, a rust concept. tldr is that a struct A that holds a reference to some type B must specify a lifetime. This lets the compiler enforce that A isn't "alive" after B has "died". …

A way to do it is to define the key as a const with type &str. To use it in your program as a Pubkey you'd only need to parse it into a Pubkey. For example: const MINT: &str = "2TPExuywxs4K7J2WAE8N8Fi …

You can only conveniently access code written in Anchor with the interface Anchor provides through its ts package. This is because the entrypoint to an Anchor program first attempts to strip any instr …

Simply deriving or hardcoding a public key on-chain is not enough to make it acceptable as an account. Any accounts you need must be passed in from the client-side. In this case the right move would i …

Quoting an answer to this exact issue as shown here, with minor changes: "0x0 means you're attempting to initialize an already initialized account. What's happening here is that because your vaultAcco …