<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Buffer-Account on wid@internet:~$ </title>
    <link>https://widnyana.web.id/en/tags/buffer-account/</link>
    <description>Recent content in Buffer-Account on wid@internet:~$ </description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 05 May 2026 15:07:35 +0700</lastBuildDate>
    <atom:link href="https://widnyana.web.id/en/tags/buffer-account/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Deploy, Upgrade, and the Buffer Account Pattern</title>
      <link>https://widnyana.web.id/en/posts/solana/solana-program-deploy-upgrade-buffer/</link>
      <pubDate>Sat, 02 May 2026 10:00:00 +0700</pubDate>
      <guid>https://widnyana.web.id/en/posts/solana/solana-program-deploy-upgrade-buffer/</guid>
      <description>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.</description>
    </item>
  </channel>
</rss>
