<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Developers Forum for XinFin XDC Network: Eugene Guerra</title>
    <description>The latest articles on Developers Forum for XinFin XDC Network by Eugene Guerra (@happynick).</description>
    <link>https://www.xdc.dev/happynick</link>
    <image>
      <url>https://www.xdc.dev/images/xmRhJmwBu-UB6qHq48GLmBoS7iTiB8YbhSBOY2n9PWE/rs:fill:90:90/mb:500000/ar:1/aHR0cHM6Ly93d3cu/eGRjLmRldi91cGxv/YWRzL3VzZXIvcHJv/ZmlsZV9pbWFnZS84/MTMzLzYyNzRjMGI5/LTNmMjUtNDQxMi1h/M2JlLTliYjg4N2Uw/MTM0ZS5wbmc</url>
      <title>Developers Forum for XinFin XDC Network: Eugene Guerra</title>
      <link>https://www.xdc.dev/happynick</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://www.xdc.dev/feed/happynick"/>
    <language>en</language>
    <item>
      <title>From Apothem to Mainnet: A Release Checklist for XDC Apps</title>
      <dc:creator>Eugene Guerra</dc:creator>
      <pubDate>Wed, 18 Nov 2026 10:22:09 +0000</pubDate>
      <link>https://www.xdc.dev/happynick/from-apothem-to-mainnet-a-release-checklist-for-xdc-apps-89a</link>
      <guid>https://www.xdc.dev/happynick/from-apothem-to-mainnet-a-release-checklist-for-xdc-apps-89a</guid>
      <description>&lt;p&gt;A successful deployment on Apothem is an important milestone, but it is only one part of releasing an XDC application. Before inviting real users, I would check the network configuration, contract behavior and the steps a new user must take to complete a transaction.&lt;br&gt;
&lt;strong&gt;Make the network explicit&lt;/strong&gt;&lt;br&gt;
XDC Mainnet uses chain ID 50; Apothem Testnet uses 51. Keep their RPC settings, contract addresses and environment variables separate. At startup, the app should check the wallet’s chain ID and show a clear message when the user is connected to the wrong network.&lt;br&gt;
A contract address copied from a testnet deployment should never silently appear in a mainnet build. Record the deployed address and version for each environment so the team can identify exactly which contract the interface is calling.&lt;br&gt;
&lt;strong&gt;Verify what the interface displays&lt;/strong&gt;&lt;br&gt;
After mainnet deployment, verify the contract source and test its read and write functions with small, controlled transactions. Check the transaction result in a block explorer as well as in the app.&lt;br&gt;
If the application handles tokens, confirm the contract address and decimals used by the interface. A familiar token name is not enough to identify an asset. The amount shown to users must match the amount the contract processes.&lt;br&gt;
&lt;strong&gt;Test the first-user journey&lt;/strong&gt;&lt;br&gt;
A developer with a configured wallet can miss steps that are unclear to a new user. Try the application with a fresh wallet and no saved settings. Can the user identify the right network? Do they understand why a transaction needs native XDC for gas? Does an error message explain what to do next?&lt;br&gt;
Users may obtain XDC through an exchange such as &lt;a href="https://www.bydfi.com/"&gt;BYDFi&lt;/a&gt;. If your onboarding instructions mention an exchange, tell users to confirm its current withdrawal options and the destination network before sending funds. Testnet tokens cannot fund a mainnet transaction.&lt;br&gt;
&lt;strong&gt;Plan for transactions that do not go as expected&lt;/strong&gt;&lt;br&gt;
The interface should display a transaction hash once a transaction is submitted and distinguish pending, confirmed and failed states. Avoid treating a submitted transaction as a completed action. If users retry after an unclear result, the application should help them check the first transaction before they submit another.&lt;br&gt;
A useful final test is simple: give someone unfamiliar with the project a fresh wallet and ask them to complete one task without guidance. Every point where they hesitate is a chance to improve the release.&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
