-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Gate: Disable bpf loader management instructions #34424
Comments
SIMD link does not link to a SIMD |
Linked. |
Please update the fields in the PR description before closing this, for historical tracking purposes. |
feature has been activated on mainnet. |
Hi @HaoranYi, I was trying to deploy a solana program and accidentally used solana cli 1.14.29 with "solana deploy" instead of "solana program deploy". The deployment txs failed with the following errors:
It created an account that belongs to BPFLoader2 and took about 3 SOL. As a result, I can't close it. How can I get my SOL back? Is there any instruction that allows me to recover my funds? |
Sorry to hear about this. I am not aware of any instructions to withdraw these funds. |
If you created the account with BPFLoader2 as owner (instead of gifting the account during program initialization), then it is finalized and thus the funds are burnt unfortunately. We should deactivate the CLI of the older loaders to prevent others from stepping in the same issue. |
@Lichtso Thanks for your response! Is there any chance of adding a 'rescue' instruction to BPFLoader2? I have the account keypair, and I think I should be eligible to recover my funds. The issue seems to have happened because the CLI wasn't deactivated earlier. Another possibility could be to return the funds through a bug bounty—I'm happy to work something out if this can help improve the system and prevent others from facing the same problem. Let me know if this could be an option! |
SIMD
Disable bpf loader V1 program deployment
Description
bpf loader still reads and writes account
executable
meta to check and set whether an account is executable. Therefore, it is a blocker to deprecateexecutable
meta on the accounts.This feature, when activated, will make sure that there will no more bpf loader program deployment on chain. Then, we can safely deprecate account
executable
meta.Feature ID
7WeS1vfPRgeeoXArLh7879YcB9mgE9ktjPDtajXeWfXn
Activation Method
Single Core Contributor
Deployment Considerations
NA
Minimum Beta Version
v1.17.20
Minimum Stable Version
v1.17.20
Testnet Activation Epoch
608
Devnet Activation Epoch
659
Mainnet-Beta Activation Epoch
601
The text was updated successfully, but these errors were encountered: