Search Results

No. There's no way to force the normal arithmetic operations into their checked equivalents. The checked equivalents require extra handling of their result and this can't be magically generated to do …

No. It is impossible to do IO tasks like network requests deterministically. There are many ways that the behavior of the request could change from one validator to another

No. This cannot be done. The address of all accounts a transaction intends to interact with must be declared up front, otherwise the runtime can't resolve write conflicts during scheduling. On deman …

Try building from a release tag rather than whatever commit you are here.

You can't. The highest resolution on-chain wall timestamp available today is one second and available in the unix_timestamp field of the Clock sysvar. Sampling theory states, via Nyquist, that there …

The docs and code are a little confusing around this point. It's 10kB per account, per top-level instruction.

realloc() is implemented on AccountInfo. So per-account

Using a Ledger pubkey to reserve a program address (program id), while possible, doesn't particularly make sense. This keypair is only used once, during the initial deployment, then never needs to si …

This is conflating an account's address with the use of a PDA, which is not a strict requirement. Any ed25519 keypair can also be used to claim an address at the public key's value. That is, while al …

Little known fact: The 'A' in PDA stands for "address", not "account" (and even this is a misnomer). A PDA doesn't have to have an account allocated behind it at all to invoke_signed as a signer. Ren …

An alternative to "subscribing" is to poll using the getBlocksWithLimit and getBlock JSONRPC methods (or your favorite SDK's wrappers). getBlocksWithLimit is a light-weight call, that takes a start_sl …

Yes, it's safe to perform multiple reallocs. The per-tranasction limit is to rate-limit cluster-wide storage growth do a reasonable rate

While @vicyyn is correct in that using SystemInstruction::Transfer requires that the source account be owned by the System Program (generally, only the program which owns an account may debit its lamp …

What you saw on twitter is not quite correct. The maximum CU/tx is 1.4M, but only if you request more than the default. Without requesting, the max CU/tx is calculated as max(200k * instruction_count …

I don't know much about anchor, but you appear to be passing a PublicKey where a Keypair is needed. Public keys cannot produce signatures, the corresponding private key is needed for that