<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[CryptoEarnLab Notes]]></title><description><![CDATA[CryptoEarnLab Notes]]></description><link>https://cryptoearnlab.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Fri, 20 Nov 2026 15:29:06 GMT</lastBuildDate><atom:link href="https://cryptoearnlab.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Airdrops Are State Machines: A Developer's Model for Tracking Claim Status]]></title><description><![CDATA[Most airdrop mistakes are stale-state bugs. Model each campaign with explicit states, a source of truth, and UTC deadlines, and the bugs mostly go away.]]></description><link>https://cryptoearnlab.hashnode.dev/airdrops-are-state-machines-tracking-claim-status</link><guid isPermaLink="true">https://cryptoearnlab.hashnode.dev/airdrops-are-state-machines-tracking-claim-status</guid><category><![CDATA[Web3]]></category><category><![CDATA[Blockchain]]></category><category><![CDATA[Cryptocurrency]]></category><category><![CDATA[Security]]></category><category><![CDATA[Productivity]]></category><dc:creator><![CDATA[CryptoEarnLab]]></dc:creator><pubDate>Fri, 20 Nov 2026 03:39:02 GMT</pubDate><content:encoded><![CDATA[<p>If you follow more than a handful of airdrop campaigns, you will eventually act on stale data. A guide from last spring says "farm the testnet," a thread says "claim is live," and a bookmarked portal still loads. None of those tell you what the campaign's state is <em>today</em>.</p>
<p>Developers already have a tool for this problem: the state machine. A campaign is not a vague "opportunity." It is an object that moves through a small set of states, and each move is triggered by an event you can point to on an official page. Model it that way and most airdrop mistakes become ordinary stale-state bugs, which you know how to prevent.</p>
<p>This article is not about spotting fake claim sites or decoding signatures. It is about the bookkeeping layer underneath: knowing which state a campaign is in, where that state comes from, and when you need to check it again.</p>
<h2>The states</h2>
<p>Here is a minimal set that covers almost every campaign we track:</p>
<ul>
<li><code>UNANNOUNCED</code>: people speculate about a token, but the project has not announced a token, airdrop, snapshot, or claim page.</li>
<li><code>RESTRICTED</code>: participation exists, but it is gated (invite-only, staking requirement, application).</li>
<li><code>QUALIFYING</code>: a published eligibility period is running.</li>
<li><code>CLAIM_OPEN</code>: an official claim page is live, with a deadline.</li>
<li><code>ENDED</code>: the claim window has closed. Unclaimed tokens may be forfeited.</li>
<li><code>SUNSET</code>: the product or chain itself has been shut down or retired.</li>
</ul>
<p>The transitions are the interesting part. <code>UNANNOUNCED â†’ QUALIFYING</code> only happens when the project publishes rules. <code>CLAIM_OPEN â†’ ENDED</code> happens at a timestamp, whether or not anyone updates the guides. And <code>ENDED</code> is terminal for that round: a new season is a <em>new</em> object, not a reopened one.</p>
<h2>Real examples of each state</h2>
<p>These are taken from CryptoEarnLab's <a href="https://cryptoearnlab.com/airdrops/">airdrop index</a>, where each page carries a "last verified" date and links to the official source.</p>
<p><strong>UNANNOUNCED: Base.</strong> As of 16 November 2026, Base and Coinbase had not announced a Base token, airdrop, snapshot, or claim page. The only first-party signal is a September 2025 note that a network token was being explored, with no date, name, or eligibility. In this state, any "Base airdrop claim" page is, by definition, not official.</p>
<p><strong>RESTRICTED: Pipe Network.</strong> Official Pipe docs (updated 27 September 2026) describe invite-only mainnet Firestarter nodes rather than a public extension-farming phase. Running one requires 10,000 PIPE staked, and the docs say individual nodes receive no rewards or payouts. Treating this as an open airdrop is a state error.</p>
<p><strong>CLAIM_OPEN: Jupiter ASR.</strong> Jupiter's current Active Staking Rewards round covers July to September 2026. When CryptoEarnLab last checked the official rewards page on 16 November 2026, claims had been open since 12 October, eligibility was an average of 50 JUP or more staked during the quarter, and voting was not required. That last point matters: older guides say you must vote, which was a rule for earlier rounds, not this one.</p>
<p><strong>ENDED: Falcon Finance, Monad, Magic Newton, Kite, PAWS.</strong> Falcon Finance's FF claim closed at 12:00 UTC on 28 December 2025, and unclaimed FF from that window was forfeited. Monad's claim portal closed on 3 November 2025. Magic Newton, Kite and PAWS claims are also over. Tutorials for all of these still circulate.</p>
<p><strong>SUNSET: Lisk.</strong> The <a href="https://cryptoearnlab.com/airdrops/lisk-airdrop/">Lisk page</a> is a good example of why <code>SUNSET</code> deserves its own state. The Lisk Chain shut down on 2 November 2026, along with the user-facing Portal and Bridge. Legacy Lisk L1 claims closed on 21 May 2026. Lisk has said a manual claims process for assets left on the chain is planned for January 2027, with details to come from Lisk. "Season 2" is not a live campaign, and there is no portal to stake in.</p>
<h2>A record schema</h2>
<p>Write the state down. A small JSON record per campaign is enough:</p>
<pre><code class="language-json">{
  "id": "jupiter-asr-2026-q3",
  "state": "CLAIM_OPEN",
  "source_of_truth": "https://jup.ag/rewards/asr-2026-q3",
  "checked_at_utc": "2026-11-16T00:00:00Z",
  "claim_opens_utc": "2026-10-12",
  "claim_closes_utc": null,
  "requirements": ["avg &gt;= 50 JUP staked during Jul-Sep 2026"],
  "not_required": ["voting"],
  "wallets": ["staking-wallet"],
  "approvals_to_revoke": []
}
</code></pre>
<p>A few design choices are deliberate:</p>
<ul>
<li><code>source_of_truth</code> <strong>is a single official URL.</strong> Not a guide, not a thread. If you cannot fill this field, the state is <code>UNANNOUNCED</code> at best.</li>
<li><code>claim_closes_utc</code> <strong>can be</strong> <code>null</code><strong>.</strong> If the official page shows a relative countdown rather than a date, record <code>null</code> and re-check often. Never invent a closing date.</li>
<li><code>not_required</code> <strong>is a field.</strong> Rules change between rounds. Writing down what is <em>no longer</em> needed stops you from doing unnecessary on-chain actions based on old instructions.</li>
<li><code>checked_at_utc</code> <strong>drives your re-check schedule.</strong> Stale records are the root cause of most mistakes.</li>
</ul>
<h2>Always store time in UTC</h2>
<p>Many projects publish deadlines in UTC (Falcon Finance and Gnosis Pay both did), but your calendar and your phone render them in local time. If you are in UTC+8, a 12:00 UTC deadline is 20:00 the same day. A 23:59 UTC deadline is 07:59 the <em>next</em> day for you, but 18:59 the same day in New York (UTC-5). Off-by-one-day errors are common, and they are fatal for claim windows.</p>
<p>Store the raw UTC value. Convert only at display time. Set your reminder well before the deadline, not at it.</p>
<h2>A re-check policy</h2>
<p>How often you look should depend on the state:</p>
<table>
<thead>
<tr>
<th>State</th>
<th>Re-check</th>
<th>Why</th>
</tr>
</thead>
<tbody><tr>
<td><code>CLAIM_OPEN</code></td>
<td>Every few days, daily near the end</td>
<td>Deadlines are hard and often relative</td>
</tr>
<tr>
<td><code>QUALIFYING</code></td>
<td>Weekly</td>
<td>Rules can change mid-period</td>
</tr>
<tr>
<td><code>RESTRICTED</code></td>
<td>Monthly</td>
<td>Gates rarely open quickly</td>
</tr>
<tr>
<td><code>UNANNOUNCED</code></td>
<td>Monthly, or when the project announces</td>
<td>Nothing to act on yet</td>
</tr>
<tr>
<td><code>ENDED</code> / <code>SUNSET</code></td>
<td>Once, then archive</td>
<td>Only to catch follow-up processes (like Lisk's planned manual claims)</td>
</tr>
</tbody></table>
<p>A simple script can do the dull part: fetch each <code>source_of_truth</code>, hash the visible text, and flag records whose hash changed since <code>checked_at_utc</code>. A human still reads the page and decides the transition. The script only tells you where to look.</p>
<h2>The <code>ENDED</code> checklist: clean up after yourself</h2>
<p>Ending a campaign in your tracker should trigger a cleanup step, because the risks outlive the rewards:</p>
<ol>
<li><strong>Archive the bookmark.</strong> An old claim URL is a phishing target. If the domain later lapses or gets copied, the bookmark becomes a liability.</li>
<li><strong>Review token approvals.</strong> Under the ERC-20 standard (<a href="https://eips.ethereum.org/EIPS/eip-20">EIP-20</a>), an <code>approve(spender, amount)</code> stays in force until you change it. Any allowance you granted to a staking, bridge or claim contract for that campaign can be reset with <code>approve(spender, 0)</code>, usually through your chain explorer's approval tool or your wallet's permission settings.</li>
<li><strong>Treat "Season 2 claim" messages with suspicion.</strong> Unless the record's <code>source_of_truth</code> page announces a new round, the state is still <code>ENDED</code>. Any message that says otherwise points somewhere you have not verified.</li>
<li><strong>Note follow-up processes.</strong> For <code>SUNSET</code> campaigns, write down any planned process and its official channel, then re-check at the stated time, not before.</li>
</ol>
<h2>Why this beats a bookmark folder</h2>
<p>A bookmark folder stores <em>where</em> things were. A state record stores <em>what is true now, according to whom, and as of when</em>. That is the difference between "I think the Jupiter claim needs a vote" and "the official page checked on 16 November 2026 says voting is not required."</p>
<p>If you are new to the topic, CryptoEarnLab's explainer on <a href="https://cryptoearnlab.com/guides/what-is-an-airdrop-crypto/">what a crypto airdrop is</a> covers snapshots, eligibility, and claims before you start modelling them. Then build your own tracker, keep it in UTC, and let an official page, not a screenshot, be the only thing that moves a campaign to a new state.</p>
<hr />
<p><em>Disclosure: this article was written with AI assistance for CryptoEarnLab (</em><a href="http://cryptoearnlab.com"><em>cryptoearnlab.com</em></a><em>) and links to our site. Campaign facts were checked against our live pages and official sources in November 2026. Nothing here is financial advice.</em></p>
]]></content:encoded></item></channel></rss>