https://widnyana.web.id/en/tags/bpf-loader/ Recent content in Bpf-Loader on wid@internet:~$ Hugo en-us Tue, 05 May 2026 15:07:35 +0700 https://widnyana.web.id/en/posts/solana/solana-upgrade-authority-keypair-to-immutable/ Tue, 05 May 2026 10:00:00 +0700 https://widnyana.web.id/en/posts/solana/solana-upgrade-authority-keypair-to-immutable/ Every upgradeable Solana program has one field that controls who can replace its bytecode: the upgrade_authority_address in the ProgramData account. This post traces the full lifecycle of that field, from a single keypair through Squads multisig and SPL Governance, to the irreversible --final flag that freezes a program forever. https://widnyana.web.id/en/posts/solana/solana-program-deploy-upgrade-buffer/ Sat, 02 May 2026 10:00:00 +0700 https://widnyana.web.id/en/posts/solana/solana-program-deploy-upgrade-buffer/ Solana program deploys are not atomic. They are a multi-step dance involving a temporary Buffer account, chunked bytecode writes, and a final activation step that creates or replaces the program. This post walks through the full deploy and upgrade flows, explains why Buffer accounts exist, and shows how to recover SOL when a deploy fails midway. https://widnyana.web.id/en/posts/solana/solana-program-lifecycle-two-account-model/ Sat, 25 Apr 2026 10:00:00 +0700 https://widnyana.web.id/en/posts/solana/solana-program-lifecycle-two-account-model/ Solana programs aren't stored in a single account. They're split across two linked accounts managed by the BPF Loader: a tiny Program Account that acts as the identity, and a larger ProgramData Account that holds the bytecode. This post breaks down the two-account model, explains why program IDs never change across upgrades, and shows how this architecture makes hot-swappable code possible.