Night Ash
Events in Xai infrastructure and its ecosystem, organized by what changed.
The month's clearest structural change was the key denomination reset: holdings and capacity were rescaled while the stated reward relationship was preserved. Lower nominal entry prices broadened the proposed distribution channel, but they did not mechanically increase a holder's economic share. This year-end assessment draws on the month's announcements rather than claiming a new launch on the closing day.
Read report
Xai announced completion of the Vanguard: Genesis phase 2 NFT distribution on Xai Mainnet. Its published tiers were Vanguard for the top 5%, Legendary for the top 15%, Epic for the top 30%, Rare for the top 50%, and Common below that threshold. These cumulative cutoffs describe the ranking bands, not percentages to add together as separate allocations.
Read reportThe Sentry Key Ambassador Raid announcement named 20 randomly selected winners and required a support ticket to claim by January 13, 2025. That deadline made the claim process a distinct campaign step. The notice did not give a prize amount or confirm transfers, so a winner count alone cannot be converted into a distributed incentive budget.
Read reportXai's year-end message reported more than 1 billion transactions and over 14 million connected gamers, alongside a catalog of more than 12 games. It also claimed a leading network-activity rank. These were project-reported scale measures: the message did not provide the comparison universe or a method for distinguishing individuals, repeat accounts and retained economic users. The activity claim cannot by itself establish customer revenue.
Read reportA Xai administrator identified blocks 287861622 and 287863741 as scheduled token mints under the emissions plan. The notice mixed forward-looking wording with a statement that minting had occurred, and supplied no quantity. It provides a specific reconciliation starting point, not enough information to calculate new circulating supply, dollar selling pressure or tokens deposited at exchanges.
Read reportA quarter-point cut accompanied a higher projected rate path.
Read reportSoby reported the X account back online at 02:51 UTC. Later, at 23:41 UTC, Xai's administrator announced renewed Crossmint crypto minting and changes to referral-code handling: clearer self-referral errors and the ability to remove a code supplied through a promotional URL. Recovery restored a communication route; checkout changes addressed specific purchase failures rather than proving that every payment path was fault-free.
Read reportXai announced 5 randomly selected winners of its CoinMarketCap engagement contest. The selection method makes this a promotion result rather than a ranking of investment skill or contribution to protocol performance. The notice identified winners but did not state a transferred prize amount; selection and payment should remain separate stages of the campaign record.
Read reportXai reopened Discord and Telegram after the sale-period restrictions and said outstanding support tickets were being handled. Later, Soby and an administrator separately reported that the official X account was suspended. The record concerns access to communication channels; it does not establish an interruption of blockchain settlement. Soby disputed the suspension, but the notices did not establish the platform's reason for it.
Read reportXai reported nearly 60,000 mints in 24 hours. The count measured keys, not unique buyers. An edited administrator update identified self-referral codes as a cause of failed purchase transactions and said Crossmint card payments were working again. Conversion friction therefore remained visible alongside the headline mint total, rather than disappearing from the record because demand was strong.
Read reportAfter a 100-for-1 key split, Xai opened sales at a much lower unit price and supported ETH, XAI, esXAI and card payments.
Read reportThe sale-open notice arrived at 02:00 UTC. Xai's accompanying post described the keys as wallet-bound, with no secondary market. The economic distinction is fundamental: an ascending primary-sale tier is not an executable resale price for an existing holder. Access to future ecosystem distributions was the proposition being promoted, not unrestricted transferability.
Read reportAt 00:02 UTC, Xai reported completion of the additional-key distribution but kept minting, staking and unstaking disabled during automatic pool allocation. The restoration notice followed at 03:35 UTC: pool staking was complete, staking controls reopened and challenges resumed. Reading these as separate milestones avoids mistaking the arrival of keys in a wallet for the return of the full operating service.
Read reportXai added an Indonesian-language community channel with ambassador oversight and language-role access. Separately, its official account announced Planet-X's participation in the airdrop season without specifying an allocation amount. These developments addressed different distribution constraints: local support for participation, and another project's commitment to reach key holders. Neither announcement supplied retention or conversion figures.
Read reportThe key airdrop was taking longer than expected, according to Xai's administrator, who attributed the delay to increased network activity. The notice said time-based challenge rewards would make the first challenge after downtime larger to compensate for the pause. That described the intended accounting mechanism; the message did not show a completed compensation payment.
Read reportThe deployment notice separated the contract migration from the later sale. During the first phase, staking controls would close while additional keys were distributed and challenges continued. The second phase would pause challenges and restore the original pool allocations. Pool key capacity would increase by 100 while esXAI staking capacity per key would be divided by 100, preserving the denomination adjustment on both sides.
Read reportAhead of the sale, Xai announced a $10,000 contest prize pool and participation points for Xai Vanguard: Genesis. The campaign rewarded promotion and creative activity. Its stated budget described an acquisition expense, not game revenue or the amount already paid to individual winners.
Read reportResponding to a community question, Xai administrator Diablo said the key price had prevented some games from reaching their intended audience through airdrops. The proposed reduction, he said, helped secure commitments from more than 12 projects. That explanation connects key pricing to distribution reach. It does not measure how many new participants would remain active after incentives ended.
Read reportThe sale timetable fixed December 13 at 18:00 PST, equivalent to December 14 at 02:00 UTC. The announcement listed Arbitrum payments in ETH, XAI, esXAI and USDC; Ethereum payments in ETH and USDC; Solana payments in SOL and USDC; Polygon payments in SUPER; and cards. Multiple funding routes did not mean the keys were issued independently on every payment network.
Read reportThe upgrade requirement in Xai's December 3 announcement deserves separate attention ahead of the planned migration. Operators were instructed to install version 1.2.0 because older versions would become incompatible with the coming contracts. This was an operational dependency, not an optional interface refresh: assessing key economics also required checking whether the software could continue participating after the contract change.
Read reportXai scheduled a phased release beginning December 10: disable minting, distribute the additional keys, restake them in the original pools and update the staking application and contracts. Stake and unstake actions would be unavailable during the migration. The edited notice estimated 3 hours without challenges; that was a planning assumption, not a measured outage duration.
Read reportThe Xai Foundation adopted the community's Tiny Keys proposal. Each existing key would receive 99 additional keys, producing a 100-fold count; pool-held additions would be staked in the original pool in the same proportions. The announcement described unchanged rewards. A larger number of units alone therefore did not imply a larger ownership share or a corresponding gain in wealth.
Read reportXai followed its smaller-key teaser with a post pointing to the following day. This established an announcement window, not the sale price, allocation formula or reward terms. The distinction matters at this stage: a campaign signal can focus attention before holders have enough information to assess the economic change.
Read reportXai highlighted a $2.5 million play-to-airdrop promotion at Valeria. The amount was the campaign figure in the promotional message, rather than a report of money already received by participants. Assessment of the incentive would require the award asset, valuation basis, eligibility and delivery conditions. Its scale can be recorded as advertised without treating it as revenue, an investment return or a completed distribution.
Read reportXai continued its small-key teasers after a November 28 post had contrasted a key with a smaller one. The November 29 messages repeated the visual motif and suggested that something small was coming, without stating a product name, price, conversion ratio or entitlement. For node-economics research, those missing specifications determine whether a change affects capital requirements, reward allocation or simply presentation. The posts belong in the communications chronology; assigning them a new instrument or revised ownership rights would outrun their content.
Read reportThe official account contrasted keys with smaller keys.
Read reportXai announced that it was joining NodeFi Network State as a founding member alongside MetaStreet, Aethir and Impossible Finance. The subsequently edited community notice described tokenising node yields, borrowing against a node and earning additional rewards through trading or liquidity provision, while directing readers to a waitlist. Those proposed tools would introduce financing and market risks alongside node operation. Evaluating them would require the collateral terms, control of yield rights, liquidation rules and available trading depth; waitlist access is a development stage rather than a record of executed lending.
Read reportXai introduced an airdrop season for games and projects serving its community, naming Valeria as the first participant. The post scheduled Land Before the War for the coming Friday and pointed to December 3, 2024 for information on participation. This set a sequence of product promotion followed by campaign instructions. Eligibility, allocation and delivery therefore remained separate milestones: being in the community was not, by itself, a stated entitlement to a particular amount. Research on the programme should track its actual participation terms and distribution records rather than treating the launch calendar as a transferable claim.
Read reportA participant asked about placing keys and esXAI in different pools.
Read reportThe day brought a proposal-status question and practical staking support.
Read reportA community member asked whether the foundation had staked any assets and whether the resulting rewards would be distributed. The administrator replied that there was no update yet. The exchange leaves the allocation and distribution questions open; silence about an update cannot establish either an investment or its absence. A useful treasury account would distinguish assets committed, rewards accrued and transfers actually made, together with the relevant dates. The question concerned those disclosures, rather than announcing a new staking mandate or an approved distribution.
Read reportThe official account posted an unfinished word as a teaser.
Read reportXai continued its playful social-media voice with a password post.
Read reportThe official account invited interested people to message soby0x.
Read reportThe Trench-a-palooza notice advertised $5,000 in crypto prizes and daily content challenges over 5 days. Submissions and coordinated promotional participation were also to earn Vanguard: Genesis leaderboard points, with entry governed by contest rules and channel access. The subsequently edited announcement describes a marketing incentive programme, not a financing round. Its useful performance test would compare the cost and reach of rewarded contributions with participation after the contest. Prize delivery and lasting acquisition would need their own records; the advertised budget measures neither outcome.
Read reportAn administrator directed a participant to a proposal about Foundation staking.
Read reportXai promoted a The Lost Glitches update under which keeping the game client open would accumulate Memory Fragments. That incentive changes how activity figures should be interpreted: time with software running can increase without a matching increase in active play. For an economic assessment, the relevant questions are the cost of supplying rewards, their usable rights and whether participants return once accrual stops. Xai's message gave no issuance rate or redemption terms, so a cash value cannot be assigned to the fragments from this announcement.
Read reportXai announced two forthcoming Tollan titles, with a subsequently edited community notice naming Tollan Worlds and Tollan Survivors. The stated direction connected action-adventure products through shared intellectual property and gave users a prospective role in creating content. This expanded the announced development pipeline, rather than documenting two completed migrations. A shared creative setting can support reuse across products, but its commercial value depends on delivery, creator rights and how the resulting content is maintained. Those operating terms remained outside the announcement.
Read reportXai advertised a Trench Talk session with Planet-X's ghost_ppx covering optimisation, open beta and gameplay strategy. The notice offered listeners a chance to win two X-Pods. For product research, the useful next evidence would be the actual technical discussion and subsequent release behaviour, rather than the promotion's reach. The programme listing did not establish that an open beta had already passed testing or that the giveaway had been distributed.
Read reportXai renewed its invitation to DevCon events, presenting them as opportunities to meet its team, builders and creators. An earlier notice had advertised a Bangkok gathering on November 13 and offered entry to selected commenters. This was an outreach programme with a stated date and audience. Participation, subsequent development work and commercial agreements would be separate outcomes; an invitation alone does not establish attendance or investment commitments.
Read reportThe Phase 3 launch notice appeared on X late on November 10 UTC, followed by the community announcement just after midnight on November 11 UTC. Both described quests as available to new and returning participants. The earlier programme schedule ran to January 2, 2025. These messages establish a launch announcement, not the value of future awards or a causal explanation for a token-price move.
Read reportA community reply placed phase three immediately after the end of phase two.
Read reportParticipants reported verification failures and delayed leaderboard points.
Read reportSoby floated a hypothetical combination of airdrops to node holders and XAI stakers, plus Xai Foundation buybacks funded from game revenue shares. His post asked the community for a response. It was a value-distribution idea, not an adopted treasury policy or a record of purchases. Evaluating such a mechanism would require revenue actually received, the authority to allocate it and the execution terms of any buyback.
Read reportXai reported more than 110,000 hours played and more than 110,000 downloads for Riftstorm's first playtest. Hours and downloads measure different aspects of a trial and cannot be treated as a count of retained customers. Comparing them with a later cohort, acquisition spending and revenue would help assess whether trial reach translated into sustained demand. The announcement itself did not provide those commercial measures.
Read reportThe campaign announcement scheduled Vanguard: Genesis Phase 3 from November 11, 2024 to January 2, 2025. It emphasized achievements inside upcoming games and added a developer quest track using ecosystem tools. The change moved the programme toward product participation rather than social engagement alone. The announcement described the planned activity; the commercial question was whether participants would continue using the products after incentives ended.
Read reportA staking participant asked how to get pool operators to restart.
Read reportXai reported that Riftstorm's playtest had trended first among free games on Steam. The announcement highlighted time spent playing and community participation, but supplied neither the chart's measurement window nor a retention cohort. Its significance was early product discovery: a temporary free-test ranking could help a developer reach an audience, while repeat use and commercial conversion would determine whether that attention supported a durable business.
Read reportA developer update relayed by Diablo attributed failed reward claims to a subgraph bug introduced alongside the Referee upgrade for time-based rewards. Operators could not obtain the available claims from challenges, even though they continued submitting assertions. The team said network support had continued and rewards were not lost; after the subgraph fix, restarting an operator would trigger retrieval and claiming of outstanding rewards. This is the team's incident explanation and recovery instruction, not an independently reconciled payout ledger.
Read reportA holder reported reduced esXAI receipts as a separate node-sale offer was announced.
Read reportXai announced the release of contract upgrades for time-based challenge rewards. Rewards would depend on elapsed time since the previous challenge, with the stated aim of better compensating keys after a disruption. The same notice announced staking-interface fixes for redemptions failing to load and duplicate pool listings. These were distinct changes: an allocation rule and corrections to its user interface. The release notice explains the intended mechanism but supplies neither a measured post-upgrade distribution nor proof that every holder had already received the expected amount.
Read reportChristian reported 79% support among 109 votes and said he would coordinate next steps with the Xai Foundation. He also said opportunities such as liquid-staking tokens would be evaluated after the staking vault had been live for one quarter. That review point was conditional on operations beginning, not a fixed calendar launch date. The announcement advanced the proposal from consultation toward implementation planning; actual deployment, allocation sizes and subsequent earnings would require their own records.
Read reportThe Foundation-staking poll closed with the support option shown as the winning answer at 79%. This was a dated community preference signal, not an on-chain execution record or a binding allocation decision. The closure notice did not provide a complete voter breakdown or implementation schedule. Its immediate significance was to give the proposal process a recorded result; confirmation of the next operational step remained a separate matter.
Read reportThe three-day poll offered support, abstention and opposition.
Read reportA participant reported inconsistent values; support described a display issue.
Read reportThe new language channel introduced zzaby as its ambassador.
Read reportThe reminder set October 31 as the leaderboard deadline.
Read reportThe NodeFi discussion moved from product structure to the source of liquidity. David C said stXAI could be used in a liquidity pair, while the follow-up explained that someone would have to supply it as lending capital. The discussion set an end-of-October launch target and contemplated a separate grant request to seed a borrowing pool. A target and a prospective funding request are not proof of launch or committed capital; the relevant dependency was who would supply the assets and on what terms.
Read reportThree-player teams could compete for ten advertised $300 prizes.
Read reportMetaStreet's proposal introduced a Yield Pass, an ERC20 representing node income, and a Discount Pass, an ERC721 associated with the underlying Sentry Key. The intended structure combined yield trading with fixed-rate, fixed-duration borrowing against an illiquid principal asset. Borrowing was optional rather than a prerequisite for every yield position. The proposal therefore addressed both the pricing of future emissions and access to temporary liquidity, two different sources of financial exposure.
Read reportA weekly recap cited one billion transactions and three million connected wallets.
Read reportAn airdrop announcement prompted a separate warning about wallet connections.
Read reportThe follow-up question concerned a possible migration, not a confirmed move.
Read reportXai's brief public post paired the two projects without implementation details.
Read reportXai released operator version 1.2.0 for desktop and CLI and labelled the update mandatory. The notice warned that incompatible operators would stop receiving rewards. It included a fix for the MacOS client being blocked or flagged and prepared operators for future contract changes intended to enable Sentry Key airdrops. Those contract changes had no announced release date; the team said it would provide at least 7 days notice when a date was set. Software readiness and delivery of an airdrop were therefore separate milestones.
Read reportSoby described the proposed Foundation allocation as vested reserve tokens, estimating around 8 million XAI from a conversation with the Foundation. He argued for staking rather than selling and said its earnings would support ecosystem growth. The number was an attributed estimate, not a published balance reconciliation. Existing token supply and reward dilution are different questions: moving vested tokens into staking need not mint new tokens, but can still change the distribution among participants.
Read reportChristian, introducing himself as being from Gauntlet, proposed deploying idle XAI Foundation tokens across community staking pools through an Aera strategy. The stated design would return 100% of earned rewards to community uses, including liquidity, incentives or growth funding. It also aimed to distribute stake without overcrowding individual pools and said the Foundation would retain control of its funds. These were the proposed operating terms, not a report that the vault had already deployed or distributed earnings.
Read reportXai announced a collaboration between Novadash and Spiral_DAO around Liquid Locker, describing it as a way to stake XAI while maintaining liquidity. The announcement established public support for a community-built mechanism. Its investment relevance lies in separating the yield-bearing position from the means of exiting it: receipt liquidity, redemption conditions and the underlying staking exposure require distinct analysis. The notice supplied neither a measured exit time nor market-depth data. The mechanism's liquidity proposition therefore remains separate from the depth available at a particular trade size and the conditions for redemption.
Read reportThe October 4 release reported 254,000 additional nonfarm jobs.
Read reportA response to the key-split proposal separated a smaller purchase denomination from return on the capital committed. The participant argued that splitting keys would leave the economics relative to holding ETH or XAI largely unchanged, and offered an approximate 7 years payback estimate including future halvings, with other conditions held constant. That was a participant's conditional estimate, not an independently reproduced valuation. The investment question was whether a lower entry ticket could overcome the same reward-to-cost ratio; evaluating it requires explicit token-price, emission and operating-cost assumptions, not the key count alone.
Read reportA community proposal by ccc put Sentry Key denomination under review. The author reported 35,178 keys minted against a 50,000 cap, more than 6,400 holders and a current entry price of approximately 1.43 ETH. The proposed 1:100 split would raise the cap to 5,000,000, multiply each sale tier's inventory by 100 and divide its unit price by 100. Existing holders would receive 99 additional keys per key, preserving their proportional ownership at the change rather than creating a new economic windfall.
Read reportIran's October 1 missile attack forms the dated external context.
Read reportXai opened Meme Week with an advertised $5,000 crypto prize pool and Genesis points for contest participation and promotional activity. A later notice that day started the first creation contest around Web3 versus Web2 games. This is a defined acquisition campaign with two incentive types: competitive prizes and programme points. Assessing its value requires separating submissions and promotional reach from continued participation after the campaign; the prize announcement itself is neither a payout record nor token-price performance.
Read reportThe Phase 2 leaderboard notice said rewards from Phase 1 and Phase 2 would stack, while describing a fresh start for the new phase's rankings. It also announced 150 points for the daily Vanguard mint starting on day 30. Stacked rewards and a reset ranking are different rules: the notice does not say that all points from both phases are simply added into one unchanged table. For participation analysis, the mint-point change is an incentive adjustment, not evidence that the underlying network's organic demand increased.
Read reportDermes asked Xai to examine another project's approach to transferable node keys.
Read reportXai previewed a $10 million ecosystem grant programme with Aethir for AI-powered games and studios. Applications were not yet detailed in the announcement; the post said those instructions would follow shortly. For a capital-allocation timeline, this is a programme-level announcement before a published application process, named recipients or confirmed disbursements. The announced envelope is not evidence that any particular studio had received funding, and it is not capital belonging to Night Ash.
Read reportThe explanation distinguished tradable receipts from non-transferable esXAI.
Read reportKey holders questioned reward gaps; support had no new airdrop information.
Read reportXai's incident account attributed the challenge disruption to a validator being unavailable for approximately 4 hours. It distinguished nodeCreated, when a rollup is created, from nodeConfirmed, when the parent chain Arbitrum accepts it. Because confirmations trigger challenges, the team described an immediate challenge gap and expected another roughly 4-hour gap about 5 days later from the delayed creation stage. It said transaction processing on Xai continued without issue. The retained account mixes relative day labels, so those mechanisms and estimates are more reliable than assigning an exact future outage date from its wording.
Read reportA validator outage interrupted challenge creation for roughly four hours while the chain continued processing transactions.
Read reportXai announced Riftstorm as an upcoming exclusive flagship title, describing it as the network's first roguelite shooter and stating that it had support from Xai Foundation. The post placed a playtest announcement in the future. That gives the pipeline a named genre and project to follow, but the word support alone does not specify financing terms or an amount invested. The next delivery milestone was the promised playtest information, not a completed commercial launch.
Read reportAn Xai administrator reported a disruption in challenges and said the team believed the issue was resolved, with new challenges appearing at roughly hourly intervals again. A detailed post-mortem was promised separately. This entry captures the initial recovery assessment at the time it was communicated, not the later root-cause findings. For operators, a return of challenge creation is the first observable milestone; the number of missed opportunities and any delayed consequences require the subsequent incident account.
Read reportXai claimed 12 consecutive weeks as the leading blockchain for activity, alongside rising DappRadar positions and Steam listings. These are different measures, not one combined adoption statistic. A network activity ranking requires a defined activity measure, comparison set and observation window; storefront presence records distribution access. Keeping those categories separate makes it possible to test whether sustained network use accompanies a broader product pipeline, instead of using a promotional ranking as a substitute for that analysis.
Read reportThe week's scheduled policy meeting was September 17–18.
Read reportA participant compared a previous 155% rate with a new 127% reading.
Read reportXai promoted Builder support for Unity, UE5 and mobile development, and said builders could earn Genesis points for the success of their projects. The programme was therefore addressing the supply side of the ecosystem as well as individual quest participation. For research, the distinction is between tooling that helps a team deploy and incentives that encourage it to ship and attract use. The announcement did not quantify the success criteria or establish how many community projects had reached production.
Read reportThe Lost Glitches announced its presence on Steam and asked readers to add the game to their wishlist. That is a specific distribution milestone: an ecosystem title was directing prospective users into a mainstream storefront's pre-purchase funnel. A wishlist invitation does not establish that a paid release was available, that Steam supported on-chain transactions, or that the listing had converted into sales. The useful next comparison is between expressed interest and the title's subsequent release and retention evidence.
Read reportABC hosted the September 10 debate.
Read reportXai promoted new quests alongside The Lost Glitches reward upgrade and directed readers to the game's explanation. The observable development is cross-promotion between the network's participation programme and an ecosystem title. The post supplies no reward schedule or before-and-after retention figures, so it supports tracking an acquisition initiative rather than assigning it a measured commercial outcome. Reward design, campaign cost and activity after the quest window closes are the next inputs needed to assess that initiative.
Read reportBuild 0.9.4.4 addressed a login issue affecting new users.
Read reportXai circulated a recap of its August town hall and announced the imminent start of Trench Talk with James, founder of Planet X. The discussion agenda focused on reaching conventional gamers and the X-Armoury. The two formats serve different purposes: a recap gives existing participants a route back to earlier discussion, while a founder interview connects acquisition strategy with product design. The agenda identifies those subjects for examination without supplying the interview's eventual conclusions.
Read reportRyan's reply clarified his reading of the reward proposal: elapsed time runs from the previous challenge, not from the previous challenge an individual node joined. That matches the formula in the original proposal. It answers the clock-reference question but does not resolve the earlier objection about a node returning from an offline period just in time. For reward modelling, network-wide elapsed time and a node's eligible participation remain different inputs; treating them as interchangeable would overstate what the proposal specifies.
Read reportThe proposal requested resources valued at $1 million, not a cash payment.
Read reportXai proposed replacing a fixed per-challenge esXAI allocation with an allocation based on seconds since the previous challenge. The stated problem was variable rollup timing: an hourly reward assumption could miss its intended distribution when challenges did not arrive hourly. The proposal's illustrative rate of 1 esXAI per second produces 3,600 esXAI after 3,600 seconds and 7,200 after 7,200 seconds. Those figures explain the formula; they are not the actual emission schedule.
Read reportAn esXAI staker reported an annualized rate of 140.8% calculated from 100 hours of rewards, while explicitly saying they did not own Sentry Keys and asking others for per-key returns. The report therefore concerns token staking, not a key-holder return. Its short measurement window and self-reported calculation matter: annualizing that interval does not establish a realized annual return, and it cannot be used to price a key without the separate key-reward data.
Read reportThe Xai Vanguard: Genesis announcement stated that Phase 1 had concluded and its final snapshot had been taken. Phase 2 was to begin immediately afterward, with the leaderboard resetting to 0. A commemorative NFT airdrop remained forthcoming. The reset changes how rankings can be compared: a new score cannot be read as a continuation of the preceding phase's total. Evaluating sustained participation would require linking cohorts across the reset and separating completed activity from rewards that had only been announced.
Read reportOn August 30, 2024, Jswagy reminded participants to claim all points before the snapshot.
Read reportXai issued an episode-two reminder while a community member described an XAI-based staking project.
Read reportThe guidelines called for supported proposals and excluded price and market discussion.
Read reportSoby warned that another community's Discord had been compromised and advised members not to click anything until its representative confirmed recovery. A later message from the same author was brief and ambiguous, rather than a technical incident report. The sequence documents a warning and a follow-up, but not the attack method, affected accounts or restoration checks. For operational risk research, a trusted announcement channel and a verified recovery procedure are separate controls; a reassuring message should not be substituted for the latter.
Read reportXai's administrator said the team was waiting for Galxe to investigate a verification problem.
Read reportOn August 25, 2024, Quang Anh reported that a wallet used with Xai had been hacked and asked for advice.
Read reportOn August 24, 2024, Votex.eth expanded a cross-game asset proposal with swap and staking ideas, using transferable weapons and vehicles between supporting games as examples.
Read reportAn administrator posted that the roadmap town hall with Soby and John Shipman was starting. Later that day, community discussions made the practical consequences of asset restrictions more explicit. Dermes described losing wallet access and watching rewards remain accessible to an attacker. That account was the author's stated motivation for a recovery proposal, not a verified incident report or a Night Ash experience.
Read reportReal-time audio and video were the planned integration focus.
Read reportThe developer scheduled the core land game's shutdown for August 30.
Read reportThe announcement covers governance design and treasury strategy.
Read reportThe community invitation named Soby, described as a core contributor, and John Shipman, described as the Xai Foundation's CEO in transition, as speakers for an August 23 roadmap town hall. It invited questions through a form and warned that the live session might not cover them all; a later recap was intended to address some remaining questions. This created a public route for scrutiny of the revised roadmap. Whether specific concerns received answers must be assessed from the subsequent responses, rather than inferred from the invitation or speaker titles.
Read reportThe new weekly conversation series was announced with Luca Netz as a guest.
Read reportAn Xai administrator notified the community that Sentry Node upgrades and maintenance were expected to cause a short-lived assertion delay, after which the frequency should return to normal. This is a maintenance expectation, not a measured outage duration or a subsequent recovery report. For node-return analysis, assertion timing and credited rewards need to be compared over the same window before a delay is classified as a permanent earnings loss. The notice itself did not supply pool-level reward records.
Read reportThe beta became available through the Epic Games Store.
Read reportOn August 13, 2024, Mustard reported that Alpha 10 had attracted more than 11 million esXAI during its first 44 hours as a Diamond-tier pool, quoting a 179% annualized rate for that initial period.
Read reportThe obstacle-course racer launched with free training play and loaned Try-Out Unicorns.
Read reportA user reported an unstaking error; a separate message promoted an 80% reward share for esXAI stakers.
Read reportThe poll's closing notice showed 47% for the lockup-and-penalties option.
Read reportXai's roadmap update identified additional uses for XAI and esXAI, on-chain governance and a liquid staking token. The accompanying posts said community feedback had informed the revision. These subjects change the research agenda: token utility concerns what holders can do, governance concerns how decisions are made, and staking liquidity concerns how a locked position might become transferable. The posts set directions without providing implementation dates or deployed contracts for those additions.
Read reportThe foundation published an updated roadmap proposing new XAI and esXAI utility, on-chain governance and a liquid staking token.
Read reportThe report covered esXAI claims, key staking and MetaMask connections.
Read reportA user reported a failed staking transaction and later said a retry worked.
Read reportXai announced that The Lost Glitches open beta would begin on August 15. The post paired that planned product milestone with a credits giveaway and social participation conditions: following the project, reposting the announcement and tagging friends. For ecosystem research, the useful distinction is between a scheduled test and the campaign intended to attract participants. The announcement establishes the intended opening date; participation, retention and conversion require observations after the beta actually opens.
Read reportThe Xai staking application update added sorting by esXAI reward rate, key reward rate and other columns, alongside a filter for the amount of esXAI staked in each pool. The accompanying administrator notice explained why a bronze pool could display an unusually high estimated rate: its esXAI reward allocation might be divided across a very small stake. Adding a substantial position changes that denominator, so the displayed estimate is not necessarily the rate available after entry.
Read reportThe community timing poll closed with Saturday at 15:00 UTC displayed as the winning answer, at 26%. The closing notice supplied neither a vote count nor a breakdown of the other options. That result identifies the displayed leading choice, not a majority preference or a statistically representative schedule for the wider community.
Read reportXai congratulated EUFT on its Coinstore listing and described the fantasy football project as a use case for $XAI. Its message anticipated further growth with Season 2 in August. This was a distribution announcement and a forward expectation: the post did not supply trading volumes, market depth or measured player retention with which to assess the commercial impact.
Read reportXai announced that Planet X was coming to its network and directed readers to the game's account for the first upcoming hunt. The post expressed the team's belief that the game could attract mainstream players at scale. It was an ecosystem announcement and an adoption expectation, not a report of measured user growth, a completed launch or independently reviewed commercial terms.
Read reportXai promoted staking with a post referring to estimated reward rates and remaining capacity for the top 3 pools. The accessible caption does not provide the pool names, numerical rates or capacity amounts. It establishes what the project was advertising, but is insufficient to reconstruct a ranked yield table or to present the estimates as realized returns.
Read reportXai highlighted Tarochi's new season and MAYG's planned token airdrop to players.
Read reportA Xai community administrator announced a Crypto Unicorns game night covering growth strategies and a question-and-answer session. The message said Crypto Unicorns would give away 1000 XAI during the stream and mentioned an additional privilege for Sentry Key Holders. This records an event invitation and the organizer's announced reward pool, not a completed distribution.
Read reportOn July 19, 2024, leigh6185 reported in Discord that the leaderboard showed neither points nor a placement.
Read reportValeria Games announced that it would move to Xai, citing faster transactions and smoother blockchain integration as the intended benefits. Its post thanked the Xai team and specifically Soby. The future-tense announcement is evidence of a planned move, not confirmation that migration had finished, and its acknowledgement does not name Night Ash.
Read reportFinal Form introduced the House of Celestials in a teaser following earlier references to Beasts and Mortals. The caption described immortal gods with their own story to tell. A Xai administrator shared the same post and invited the community to await further information. These are linked promotional statements, not separate confirmations of a product milestone.
Read reportParticipants debated how to assemble a diamond-tier pool and distribute its rewards. One proposed a 1:8000 key-to-token ratio and an allocation written as 0:95:5; another said the arrangement could be attempted if 1000 keys were assembled. A follow-up proposed 1000 keys against 8 million tokens. These were community proposals, not a published configuration change or a verified pool launch. The abbreviated allocation did not consistently label each recipient category.
Read reportXai's account announced sponsorship of a $50,000 tournament associated with YakuCorp and said it was starting that day. Its qualification notice set the cutoff at July 21, 18:00 UTC. YakuCorp's own kickoff post described a $50,000 prize pool and said the 10 players with the most kills would qualify for the finals. These are the organizers' published competition terms, not verified prize disbursements or final results.
Read reportA planned node upgrade slowed assertion publication without halting the chain, reducing challenge frequency and near-term Sentry rewards.
Read reportAn administrator's explanation said Offchain Labs had performed a scheduled node upgrade on July 3. According to that account, Xai remained operational during the upgrade, while assertions arrived later than their typical hourly cadence. The distinction matters: the statement describes delayed scheduling within an operating chain, not a declared chain shutdown. The broad performance and security assessment remains the team's report, not an independent audit.
Read reportA follow-up maintenance announcement said challenge frequency was still variable. The team expected the issue to resolve approximately 14 hours after its notice, followed by a more regular challenge cadence. The estimated interval is preserved as an expectation, not a recovery timestamp or proof that every affected operator had returned to normal.
Read reportAn administrator said a scheduled node upgrade during the previous week had increased variation in assertion-posting timing. The announcement reported at least 12 assertions delayed from their expected time and said they were being confirmed. This is the team's status report at publication, not a completed confirmation count independently reconstructed from chain records.
Read reportFinal Form asked which character groups mortals should be strong or weak against, offering gods, beasts and machines as the choices in its post. A Xai administrator shared the same teaser and invited comments. The exchange records a design-feedback request promoted to the community, not a binding governance vote or an implemented balance change.
Read reportXai disclosed roughly 107.9 million tokens scheduled to unlock and said contributors had voluntarily deferred most of their July allocation.
Read reportXai announced that contributors had agreed to relock their July allocation over 6 months, reducing the team's announced July unlock from approximately 85 million to 17.7 million tokens. The statement appeared on the project's account and in an administrator's announcement. It reports an agreement and revised release schedule, not an independently inspected contract transaction or a verified legal obligation.
Read reportA member reported that a node had stopped and asked how to update and restart it, later specifying that it ran on a VPS. An ambassador first pointed to the restart procedure. When the member said the Linux client appeared to ask for staking rather than an update, the ambassador clarified that restarting and upgrading used different instructions. The conversation documents a support distinction, not a confirmed automatic-update or wallet-login defect.
Read reportFinal Form published a production thread introducing a House of Mortals preview and describing the game as nearing completion while acknowledging remaining difficulties. The team listed work across game design, UX, UI, 3D, lighting and VFX, narrative, Unity development, sound and blockchain development. This was the project's account of its workstreams, not an independently verified staffing inventory or a confirmed release date.
Read reportAn administrator announced version 1.1.14 as optional for both desktop and CLI users. The specific change was updated Xai branding in the desktop UI. The announcement explicitly described the CLI release as a version-number bump with no other associated changes. This was a presentation update, not an announced change to staking eligibility, reward economics or protocol security.
Read reportXai's account announced that Crypto Unicorns players could also score in Season 2 and said batches of in-game quests would arrive every week during the month, starting that Wednesday. The post connected the game's recent launch on Xai with a planned participation campaign. The weekly cadence was a forward schedule for that month, not evidence that every batch had already been delivered.
Read reportA member said a key and esXAI had been staked in a pool and asked whether a personal node also needed to run on a VPS. The exchange contains a reply saying it was not necessary; the questioner's later thanks explicitly quotes that answer. This records a community response about the need for an additional node after joining a pool, rather than a verified change to the member's infrastructure.
Read reportA key holder reported that a monitoring bot had detected pools submitting reward claims without receiving rewards, and asked whether the resulting gas consumption was normal. Another participant suggested that a pool owner might have automated claims. The original questioner then described the empty claims as frequent and the automation as incorrectly configured. These are a user report and a proposed explanation, not a confirmed diagnosis from the operator.
Read reportAn announcements-channel update said 100% of the first-come-first-served bundles had been claimed, while reserved claims remained open for another 6 days. It again assigned distribution decisions to Crypto Unicorns. This is an attributed status update for one allocation category, not proof that every reserved bundle was claimed or that every key holder received an asset. No recipient-level transaction reconciliation accompanies the message.
Read reportA Xai administrator reminded key holders of a Crypto Unicorns claim scheduled for June 28 and directed them to check eligibility for reserved or first-come-first-served allocations. The reminder assigned the arrangement, execution and distribution decisions to Crypto Unicorns. It was preparation for a claim, not confirmation that every holder qualified or that assets had already been delivered.
Read reportXai announced that Crypto Unicorns was live on its network. A separate Chapter 9 post described an ongoing Camelot campaign for providing liquidity to the XAI-wETH pair and receiving points weekly. It said Chapter 10 would arrive on Monday. The launch is an attributed project announcement; the later chapter remained a plan, and the post does not define how individual weekly points were calculated.
Read reportAn administrator added a per-esXAI estimate explainer and a worked-example input set: 482,160 esXAI in total rewards over 7 days, 1000 staked keys, 11,000,000 staked esXAI, a 60% token-staker share and a 40% key-holder share. The example is explicitly illustrative, not a verified pool payment. The messages were authored on June 25 UTC and displayed locally on June 26; the formula-heading message also carries an edit marker.
Read reportA Xai administrator posted an estimated key-rate formula heading, explicitly identifying the unit as 1 staked key, with an image attachment. The message was authored on June 24 UTC, displayed locally on June 25 and marked as edited on June 26. Those dates distinguish the original post from the retained edited presentation; they do not establish the exact equation available at every earlier moment.
Read reportA Xai administrator shared a Crypto Unicorns announcement about a benefit for Sentry Key holders and directed members to the project's own channels for details. The notice explicitly placed the arrangement, execution and distribution methods at the discretion of Crypto Unicorns, describing the team's role as sharing the news. It was authored on June 23 UTC and displayed locally on June 24. The distinction concerns responsibility for the proposed distribution, not a completed payout.
Read reportResponding to a participant who alleged interference with redemptions after a wallet compromise, a Xai administrator said the team had no access to the wallet and would never request wallet access or a private key. The participant asked about adding two-factor authentication. The administrator acknowledged the feedback but said no solution for a compromised wallet was available at that moment. The participant then requested a private ticket review of a proposed solution; the proposal itself is not disclosed in this exchange.
Read reportXai said that the launch of Season 2 had seen it scale to the largest EVM chain by TPS, presenting this as progress toward consumer-gaming capacity. An administrator repeated the claim in the announcements channel and linked the same post. Both messages were authored on June 21 UTC but displayed on June 22 locally. They are two publications of the team's position, not two independent confirmations of the ranking.
Read reportA member asked how to monitor a particular pool when no delegated address was shown. In a directly attached, edited reply, a Xai ambassador pointed to the pool's contract address and said its owner was not using a delegated address to run the node. This documents an address-discovery response. It is not a reproduced inspection of the contract or proof of the operator's identity.
Read reportA member asked whether esXAI submitted for redemption into XAI could still be staked and earn rewards during the lockup. A directly attached participant reply said the tokens could not be staked, followed by a brief message specifying the start of the redemption process. The exchange records community guidance about eligibility. It does not establish that the questioner submitted a redemption or received a payment.
Read reportXai stated that the Ethereum ecosystem had reached a weekend record of 246 transactions per second, with over 40% taking place on its network, 1 week into Season 2. This is an attributed ecosystem-level claim. It does not mean that the entire quoted transaction rate occurred on one chain, and it does not supply the measurement interval or raw transaction data needed to reproduce the comparison.
Read reportA key holder reported that their pool had moved from Platinum to Silver and said they could not find spare key capacity in a higher-tier pool. Another participant replied directly with a pointer to the announcements channel. The original report carries an edit marker. This records a member's observed allocation constraint and a referral, not a verified inventory of every pool or confirmation of the cause of the tier change.
Read reportA key holder reported receiving no rewards since the pool rollout and asked whether a low challenge-winning probability explained the experience. In a directly linked response to the participant's documentation question, a Xai administrator described a default probability of 1%, increased by staking esXAI to reach a higher tier. The participant then asked for documentation to emphasize probability rather than an expectation of rewards every few days or 7 days. The exchange was authored on June 16 UTC, although its local display shows June 17.
Read reportXai reported that Crypto Unicorns had almost completed its migration and would arrive on the network soon. The wording marks a late-stage transition, not a completed production launch. The post also described the game as ranked 1 in the play-to-earn category by dAppRadar and pointed to a leaderboard promotion. That ranking remains an attributed statement in the announcement, not a separately verified ranking snapshot or evidence of reward payments.
Read reportParticipants questioned how Galxe associated staking eligibility with a primary wallet. One key holder described keeping keys and staked esXAI in a separate wallet, adding it as secondary to an existing profile, and still failing to complete the Chapter 4 staking-pool quest. Another participant reported the same difficulty and suggested using Discord roles. These are specific user reports, not a verified conclusion that every key holder was excluded or that a replacement eligibility mechanism had been adopted.
Read reportA Xai administrator reported just over 2 million daily mainnet transactions. This is the team's stated activity figure, not an independently reproduced count with a specified block range. Transaction totals are also different from unique users, paying customers and token-holder revenue. Without those separate measures, the announcement cannot establish the economic quality or durability of the activity.
Read reportXai promoted its protocol-enshrined gas subsidy and invited users to mint NFTs daily. The same post said Chapter 3 would arrive in 24 hours, rather than identifying the current promotion as an already-open third chapter. Its claim about superior user experience is promotional positioning, not a comparative benchmark. A subsidy can lower the user's direct transaction charge without eliminating network costs or proving sustainable demand.
Read reportXai announced that Chapter 1 of Vanguard Genesis was live. The accompanying community announcement identified the onboarding quests on Galxe and said Chapter 2 would become available within the next 24 hours. The official post described a month focused on ecosystem partners. It did not promise a permanent chapter release every 24 hours or establish that the next chapter had already opened.
Read reportA member asked whether a community vote had been held on changing staking-pool tiers and what future changes were planned. A Xai ambassador responded in the negative and said feedback was being actively collected. The response is explicitly attached to the question. The earlier description of an unanswered question was therefore inaccurate; acknowledgment and feedback collection are documented, even though no future timetable was supplied.
Read reportA participant reported a compromised wallet in two community channels and asked for help stopping withdrawal and redemption requests allegedly initiated by an attacker. A Xai ambassador replied directly to the report and said a response had been provided in the participant's ticket. These messages were authored on June 9 UTC, although the displayed local date was June 10. The repeated reports concern the same participant, not independent evidence of multiple incidents.
Read reportA Xai ambassador corrected a member's claim that unstaking a genesis key required 6 months. The response specified two months, described as 60 days, for the genesis key and 7 days for other keys. This is the actual support clarification, not an approval of the member's proposed shorter lock. The distinction changes the withdrawal horizon described in the earlier account; it does not establish that any particular withdrawal transaction completed.
Read reportA Xai administrator published new pool thresholds. The retained notice lists Bronze at a 0 threshold with 1% probability; Silver at 30,000 esXAI with 1.5x; Gold at 2,000,000 esXAI with 2x; Platinum at 4,000,000 esXAI with 3x; and Diamond at 8,000,000 esXAI with 7x. It gives a maximum of 1000 keys, capacity of 20,000 esXAI per key and a pool limit of 20,000,000 esXAI. These are announced parameters, not annual yields or proof of realized payouts.
Read reportXai announced Season 2 and the Genesis of the Vanguard, describing a programme for engaged players. The planned activities included playing games, using applications and earning rewards such as in-game assets. An administrator relayed the same announcement shortly afterward. Both messages were authored on June 6 UTC, although the displayed local dates fall on June 7. The repost confirms distribution of the announcement, not independent evidence of adoption or reward delivery.
Read reportA Xai administrator announced the Bithumb listing and linked an exchange notice describing a KRW market addition. The announcement establishes the team's statement about a new trading venue. It does not measure order-book depth, trading volume or buying pressure. The administrator's celebratory comment was the administrator's own, not a statement made by Night Ash at the time.
Read reportA participant asked when staking tiers would be adjusted after halving. A Xai ambassador initially replied that the tiers would remain the same and that changes were not expected. The participant then pointed to the earlier halving announcement, which said a formula-based adjustment would follow and that details would be shared. The ambassador acknowledged the point and said an update would be shared. This sequence records a request for clarification, not a completed change to staking parameters.
Read reportA pool participant said that rewards appeared to have fallen by more than 70%, despite observing roughly one challenge each hour. In response, a Xai administrator described the post-halving amount as approximately 32 esXAI per challenge. The participant's percentage and the administrator's per-challenge figure refer to different measurements; neither message supplies the complete transaction series needed to reconcile them. The retained reply does not validate the percentage, identify a loss mechanism or establish a guaranteed payout. The price rally previously attached to the discussion is not supported by these records.
Read reportA message advised participants who believed their pool had been compromised to consider withdrawing and moving elsewhere. It distinguished assets held in contracts from the risk that the operator would stop running the pool. The displayed extract does not identify its author, and its conditional wording does not confirm a new wallet theft on this date. Its assurance about funds is not a substitute for checking contract and wallet exposure. A separate participant reported less frequent rewards after the staking change; that report is not a network-wide frequency measurement.
Read reportAfter users reported trouble opening the staking site, a Xai administrator acknowledged that the team was working on it at 00:07 UTC. Another administrator reported a fix at 00:49 UTC and asked the affected user to refresh the page. These messages establish a reported access problem and the team's recovery statement. They do not measure the complete outage duration, its technical cause or the experience of every user.
Read reportXai announced a partnership with SuperWalk, describing the application as based in Korea and Japan and reporting more than 25000 NFT holders. The post presented the collaboration as a link between East Asia and the Xai and Arbitrum ecosystems, with further details to follow. The holder count is an attributed promotional figure, not a measurement of paying users, current activity or revenue. Claims about market leadership and product-market fit need separate evidence; the announcement does not establish them or a month-end token return.
Read reportThe software channel marked version 1.1.13 as optional for desktop and CLI operators. Its patch note described a fix for KYC submission hanging in the desktop operator client. A client-submission fix is distinct from approval of a KYC application or recovery of previously accrued rewards. The retained notice was edited after posting and is not an independently reproduced test result. It supplies no evidence for the market-flow narrative previously attached to this date.
Read reportXai announced Xai Builder with Horizon and Sequence, describing it as an all-in-one Layer 3 developer console for AAA game development. The community notice repeated the launch announcement and linked the project post. This establishes the announced tool and relationship, not an independent hands-on assessment, production workload count or demonstrated development-cost saving. It is an external ecosystem tool covered by Night Ash, not a Night Ash game or deployed internal platform.
Read reportXai said the Gaming Catalyst proposal was open for voting in the Arbitrum DAO and described its value as 269 million USD. The project presented the initiative as potential support for Xai and other parts of the gaming ecosystem. That amount described the proposal as a whole, not an allocation already paid to Xai or Night Ash. A campaign post about an active vote does not establish passage, disbursement, investment ownership or the amount any individual recipient would receive.
Read reportA participant illustrated a reported daily decline with 200 before halving, an expected 100 afterwards and receipts nearer 60. A Xai ambassador initially discussed amounts per challenge, then gave a separate example of 70 esXAI before halving and 34.5 esXAI afterwards, while pointing to winning keys and pool uptime. These are statements made in a support exchange, not reconciled account totals or a common measurement series. The daily example and the per-challenge example must not be treated as directly comparable observations.
Read reportA participant said that increasing a stake from 1000 to 4000 esXAI had not produced an observable reward difference and asked how pool weight and tiers interacted. Messages in the discussion described separate allocations for the owner, key holders and esXAI stakers, alongside pool size and tier. Their displayed author identity is incomplete, so they are not attributed to an administrator. Without matched observation periods and transaction records, the participant's comparison cannot establish either proportional returns or a broken reward calculation.
Read reportCommunity questions about the next halving challenged a projection based on reward emissions alone, asking how other token creation should enter the calculation. A Xai ambassador clarified that the relevant measure was the combined supply of XAI and esXAI, including the effect of burning, rather than accumulated rewards alone. The exchange does not establish a fixed calendar date for the next threshold. The useful analytical distinction is between an emission-rate assumption and the full supply changes required to forecast a supply-triggered event.
Read reportThe community announcement said Blockpass, working with the Xai Foundation, had introduced an appeal route for some applicants previously rejected during KYC. Eligibility was conditional rather than automatic. It also announced an extension of the KYC completion window from 180 to 270 days, intended to reduce loss of accrued esXAI while appeals were completed. The notice does not establish that every rejected applicant could appeal, that an appeal would succeed or that all accumulated rewards were recovered.
Read reportXai's project account announced QuickNode support for developers on the network. The post records an infrastructure-support announcement, not measured uptime, endpoint performance or customer adoption. For research purposes, availability of a service and evidence that developers use it productively are separate questions. The announcement does not establish a post-halving price reaction or a Night Ash deployment using that service.
Read reportThe protocol crossed its first supply threshold and automatically reduced daily Sentry emissions from about 1.71 million to 856,164 esXAI.
Read reportXai announced that its first halving had completed. Its explanatory notice described a maximum combined supply of 2.5 billion XAI and esXAI and an emission schedule tied to combined-supply thresholds. The initial threshold was 1.25 billion; the first two daily schedule bands were approximately 1712329 and 856164 esXAI. These are rounded figures from the published schedule, not an independently reconstructed record of the triggering block or actual daily issuance.
Read reportA participant challenged the wording of the genesis-key withdrawal notice, asking whether the key could be staked elsewhere after 60 days. Later in the discussion, a Xai ambassador distinguished the key used to create a pool from ordinary keys and described a 7-day withdrawal period for ordinary keys. These messages document a usability question and a role distinction. They do not prove that the interface wording was changed or that a withdrawal completed, and they provide no basis for the earlier token-price and market-causation narrative.
Read reportA community member asked whether diamond pools were a fixed group that could eventually fill up. Another participant, identified as a Sentry Key Holder, answered that a pool could reach diamond when it had 5.5 million esXAI staked. The exchange concerns the reported qualification threshold, not a verified inventory of open capacity or an administrative guarantee that deposits would be accepted. It does not establish the live supply countdown previously described for this date.
Read reportA participant reported receiving less esXAI after moving keys and tokens into the same platinum pool. A Xai ambassador declined to recommend a particular pool and explained that the tier multiplier was only part of the calculation: the allocation to key stakers, the allocation to esXAI stakers and the number of keys also mattered. The participant's comparison was a self-report, not a controlled performance test. The exchange identifies allocation terms that must be compared before treating a higher pool tier as a higher personal return.
Read reportAn operator who had created a pool with a single key asked whether its withdrawal could be accelerated. A Xai administrator explained that the pool-creation key becomes the genesis key: its withdrawal wait was 60 days, compared with 7 days for ordinary staked keys. Adding another key would not shorten that genesis-key period. The administrator also said rewards remained possible during withdrawal while the node was running. That was an explanation of the historical operating rules, not a fixed payment schedule or a verified return for the operator.
Read reportThe software notice for version 1.1.10 marked the release as required for desktop and CLI operators. Its patch notes described support for pool-contract addresses in the operator whitelist, startup and past-challenge synchronization improvements, a fix for duplicate desktop operator instances, and loading owner wallets and newly minted keys without restarting. These are the publisher's release-note claims, not independently benchmarked performance or a deployment record for Night Ash.
Read reportXai's project account and community announcement introduced new branding and a refreshed website. Both also teased an unnamed development that the team said it had been preparing for some time. The published milestone was the branding and website announcement; the teaser did not identify a delivered feature. Neither post provided a price observation, a token-supply reconciliation or evidence that market participants reacted in a particular way.
Read reportA community security discussion focused on whether a pool operator had used the key-holding wallet directly on a server instead of a delegated Sentry wallet. An administrator said the owner had placed the key wallet's private key on a VPS. A participant separately suggested that a server compromise was the likely cause of exposure. The administrator's statement about key handling and the participant's intrusion hypothesis are different claims; the discussion does not supply a complete incident investigation.
Read reportXai announced an AMA featuring Binance and Soby, identified as a core contributor, scheduled for May 14 at 05:00 UTC. Its community announcement repeated the invitation and linked the project post. These were advance notices, not a session transcript or attendance record. They do not place a Night Ash author on the broadcast, establish a financing relationship or measure trading activity ahead of a halving.
Read reportAfter users questioned a genesis-key unstaking countdown, an administrator first said the developers would investigate a suspected interface issue. A later reply said the display problem occurred when requests to unstake all keys were followed by requests to unstake esXAI, while the actual genesis-key waiting period remained 60 days. The administrator said a web-app update could address it. These messages record the team's diagnosis and proposed remedy, not independent contract execution tests or confirmation that the fix had shipped.
Read reportA participant preparing to close a pool asked what would happen to its remaining esXAI balance after the genesis key was withdrawn. The participant said other keys and token stakes had already been removed and described a plan to join a larger pool. This was a question about residual balances and closure mechanics, not proof that the closure completed or that moving produced a better return. A displayed pool balance and an individual's withdrawable entitlement should not be treated as interchangeable.
Read reportXai issued a notice for node users whose KYC approval had just completed in the desktop client. It instructed them to restart the node and claim accrued esXAI before staking their keys with a pool. The order matters in the notice: claiming comes before pool entry, not after it.
Read reportThe Final Form project account introduced George Varodi and described his work helping define the game's visual style during more than 2 years at Ex Populus. The post also discussed earlier creative collaborations and said the game was expected later that year. The profile documents the project's presentation of its creative work and release target; it does not establish a playable launch, sustained weekly delivery or an independently verified employment history.
Read reportXai announced that it was working with Binance Pay to enable $XAI payments and said the token could be used at thousands of participating merchants worldwide. The same announcement promoted a giveaway of up to 2999 $XAI for first-time send users. The amount was a promotional ceiling, not an entitlement for every user. This is a record of the historical announcement, not a current offer or evidence of Night Ash participation; actual eligibility and availability depend on the applicable service and campaign terms.
Read reportXai promoted Final Form as an upcoming fully on-chain game and stated an intended 100% community token allocation. That was a description of the project's proposed design, not evidence of a completed token distribution or an independent assessment of the game's quality. Night Ash does not treat the announcement as its own product launch.
Read reportAsked what was coming in the following weeks and months, a community administrator said Final Form updates would arrive soon and pointed to the roadmap for other developments. The reply gives neither a release date nor a completed launch. Its role in the chronology is an expression of near-term communication plans, not evidence of game delivery or a new Night Ash product.
Read reportA different participant compared rewards over 14 days before a staking change with 16 days afterward while using 3 keys. A reply asked whether the pool owner's node was continuously operational. That question identified a possible factor to investigate, not evidence of downtime. Unequal periods and self-reported amounts do not isolate the effect of pooling; a valid comparison would also need reward-allocation terms and operational records for the same windows.
Read reportA participant reported receiving 17 esXAI during 2 days in a Platinum pool, compared with 361 from a week of running independently. Another participant replied that the pool's split and number of staked keys mattered. The amounts were self-reported and the observation windows differed; a monthly projection from that short sample is not a realized monthly return. The exchange documents a comparison problem, not audited performance or an operator's uptime record.
Read reportAn ambassador's reply connected pool tiers with key multipliers and challenge participation, while emphasizing that the reward split also mattered for esXAI stakers. A separate administrator message said additional keys increased a pool's esXAI staking capacity and that its multiplier applied to all keys in that pool. Capacity, probability and allocation describe different parts of the mechanism; these explanations do not establish a fixed payout per key or a measured return advantage.
Read reportA community administrator said pool owners did not set the unstaking period: the stated defaults were 60 days for a genesis key and 7 days for ordinary keys. In a separate explanation, an ambassador described the genesis key as the first key used by an owner to create a pool. These historical replies distinguish the pool-creation role from ordinary participation. They do not constitute a current contract audit, nor do they verify a halving countdown or a market response to monetary policy.
Read reportIn response to a roadmap question, a community ambassador described Tarochi as live and listed Final Form, LAMO Verse, Crypto Unicorns, Battle Plan and Hall of Goats as upcoming. This dated distinction separates an announced pipeline from a delivered product list. It is not an exhaustive audit of network applications, a launch date for each title or evidence that these are Night Ash products.
Read reportCommunity participants raised separate questions about what happens after an unstaking waiting period and about allocating keys and esXAI to different pools. One asked whether an unclaimed position could keep earning; another compared a pool's key-holder share with its token-staker share. The questions show which mechanics still needed clarification, but they are not answers about continuing reward eligibility. They also do not establish a monthly closing price, a staking-total change or why the market moved.
Read reportXai announced another regional chat room and instructed members to select the Indian role through the community's language-selection controls. It also invited flag reactions to suggest future regional rooms. The announcement identifies a regional access role, not a specific spoken language, so it does not establish that the room was exclusively Hindi-speaking. It provides no membership-growth or node-uptime measurement.
Read reportAsked whether staking esXAI in a pool was preferable, a community administrator listed several variables: the number of keys, the owner's reward share, the shares assigned to key and esXAI stakers, and the pool's tier. The answer also distinguished contributing tokens from contributing a Sentry key. The useful research point is that a tier label alone does not describe a participant's allocation; the message neither ranks pools nor reports a price low or rebound.
Read reportA participant asked whether placing esXAI in a Diamond pool and a key in a separate Platinum pool would affect the key multiplier, or whether using the same pool added a further multiplier. The ambassador's reply said keys would still receive their multipliers when the two contributions were placed in different pools. The clarification concerned eligibility for a key multiplier, not equality of payouts across pools or a promise of an additional return.
Read reportA community ambassador explained that pooled staking was intended to help participants with fewer keys reduce long gaps between rewards. The reply contrasted this design with individual staking, where a multiplier did not remove the possibility of a prolonged wait. This was an explanation of the intended mechanism, not a measured reduction in variance. Assessing that effect would require comparable reward histories; the exchange supplies no order-book depth or execution-cost measurement.
Read reportXai posted a live-session reminder for the discussion with the Ex Populus CEO and The Lost Glitches team. Its official account also shared the listening link. The notice records that the session was being advertised as live; it is not a transcript, a verified attendance total or proof that a particular product commitment was delivered during the conversation.
Read reportXai announced that the card game The Lost Glitches was coming to its network. Its official post promised further information within 48 hours. The wording describes an announced destination and a communication plan, rather than a completed migration or a live player population.
Read reportXai announced that Camelot was live on Xai Mainnet. The community notice identified the decentralized exchange explicitly and linked the accompanying official post. This establishes the project's launch announcement, without assigning exchange volume, trading depth or a market-share ranking to the deployment.
Read reportA community participant compared hypothetical Diamond-tier pools with different reward-allocation splits, using an assumed key and esXAI contribution. The post explicitly described its monthly results as estimates. It is useful as a record of which allocation questions participants were examining, but the example is not an account statement or a measured performance comparison. Its assumptions and projected amounts cannot establish what a real participant earned.
Read reportCommunity questions concerned whether staking a key alone qualified for rewards, how esXAI staking differed, and how long a participant might wait for a reward. Separately, a community administrator described pools as a way for esXAI holders and key holders to combine holdings and increase reward probabilities. The discussion records interest in participation mechanics; it does not establish an individual payment schedule, a market rebound or the proportion of airdrop recipients who had sold their tokens.
Read reportA community administrator answered a question about keeping a personal node running after joining a pool. The reply said the pool creator was expected to operate the delegated key, while the holder could also run that key alongside as a fallback. It distinguished operating one's own key from operating every key in the pool, and said eligible rewards would still enter the pool's distribution. This was historical community guidance, not evidence of a tested failover or guaranteed pool availability.
Read reportXai shared an interview featuring Soby, whom its account identified as a core contributor. The announcement promoted the interview; it did not make Night Ash its author or participant. No interview transcript or market-volume series accompanies the announcement, so the record does not infer what was said in the recording or how traders responded.
Read reportCommunity questions focused on how pool rewards were divided between key holders and esXAI stakers. One discussion distinguished the amount awarded per assertion from the probability of participating in an assertion; those are different inputs to an expected-reward calculation. In a separate reply, a community administrator described conversion from XAI to esXAI as immediate at 1:1 and said pools used the escrowed token. These exchanges document questions and explanations at the time, not measured pool returns or a network-uptime series.
Read reportXai's official account highlighted community coordination around staking pools and named Xaibhais, GCRClassic and Vanpoxai as the leading 3 pools at that point. The post used an absorption metaphor for staking demand but supplied neither the ranking method nor a balance for each pool. Its message concerned the emerging pool structure, not measured returns for individual key holders.
Read reportXai announced that staking pools were live, linking to pool creation and staking interfaces. The notice said XAI holders could convert the asset to esXAI and stake in a pool. This marked a change from the earlier release plans to an availability announcement; participation levels and realized returns require separate observations.
Read reportThe pool system opened staking participation to XAI and esXAI holders without requiring every participant to own and run a Sentry Key.
Read reportXai announced compulsory Operator version 1.1.7 for desktop and CLI. The release notes describe an assertion-submission issue in which the same key appeared twice, leading to an erroneous second claim transaction with no associated reward. The stated fix concerns duplicate submission and claiming, not an increase in the reward allocation.
Read reportXai shared an explanatory article ahead of staking V2, saying it addressed community questions. The announcement highlighted Sentry Key Owners, Pool Owners and esXAI Owners as distinct participants in the planned system. This guidance was part of launch preparation; it did not itself announce live pools.
Read reportXai published required Operator version 1.1.5 for desktop and CLI, preparing compatibility with the forthcoming staking release. Its notes listed bulk assertion, bulk claiming and removal of the previous add-stake function, while retaining unstaking. The release notice concerned Operator readiness; staking pools remained a separate rollout.
Read reportXai scheduled Operator version 1.1.5 for April 11 at approximately 13:00 Pacific Time, with staking V2 targeted about a week later. The announcement warned that version 1.1.4 and older would not support keys participating in the new pools. This was a preparation schedule, not an announcement that pools were already available.
Read reportXai's official account stated that deploying a Smart Account on Xai Mainnet cost 0.000049 USD. The figure refers to account deployment, rather than every transaction or the full cost of operating an application. The short post did not provide a transaction sample, fee assumptions or an observation series, so the amount is retained as the project's reported example rather than a general fee guarantee.
Read reportXai announced an imminent live conversation about Pixel Vault's migration to its network. Community reminders described a Xai and Reboot session, followed by a replacement listening link. These notices establish the discussion topic and the access update; they do not establish completed migration, an audience count or changes to individual staking income.
Read reportA Xai community announcement highlighted an airdrop announced by Crypto Unicorns for the community. It positioned an external project's campaign as a new ecosystem development. The message did not specify the campaign's value, a claim date or a complete eligibility policy.
Read reportXai asked community members to review its staking-pool explainer and submit questions and feedback through a form. The announcement continued to describe the pools as forthcoming. It presented consultation on the product and its communication, not a newly released set of staking terms.
Read reportXai explained the design of its forthcoming staking pools. Sentry Key holders would be able to create pools, each key would carry a limited esXAI staking capacity, and combining keys would increase that capacity. The stated aim was to let smaller participants coordinate toward higher reward thresholds, with rewards distributed among pool members.
Read reportA community announcement shared a replay of the recent exchange-hosted Xai Q&A. Its accompanying description identified the project's direction, upcoming games and staking as discussion topics. Sharing the replay made the earlier conversation available for follow-up; it was not a separate game launch or staking release.
Read reportThe Xai team announced that staking V2 would be released in April, explaining that the additional time was intended to improve product quality. It also asked Sentry Node Operators to watch for a preparatory software update the following week. The message did not specify an exact release day or software version.
Read reportXai invited the community to a live question-and-answer session hosted by an exchange. The announced agenda centred on the MIX partnership and the possibility of bringing 100 games into Web3. The invitation described a discussion of the pipeline, not a new batch of completed integrations.
Read reportXai and Media Indie Exchange announced a plan to bring more than 100 independent games into the ecosystem over the following year.
Read reportXai announced a strategic partnership with the Media Indie Exchange, known as MIX. The announcement set a goal of bringing more than 100 games from the partner's independent-game network to Xai within the following year. That figure described a planned integration pipeline, not games already running on the network.
Read reportXai announced that Dora was live on its mainnet and provided a link to the block explorer. This was an infrastructure announcement about access to network information, separate from token-market performance or staking incentives.
Read reportXai previewed a forthcoming partnership announcement associated with GDC and linked to a spring game showcase. The brief message signalled an upcoming business-development update, but did not set out the partner's obligations, financial terms or a game-release timetable.
Read reportA Xai community announcement reported completion of the Dencun upgrade and said claim transactions should cost 3 US cents or less. The statement attached the expected cost to claims, not to every transaction type on the network.
Read reportXai highlighted an Arbitrum DAO gaming proposal described as a $400 million initiative. Its message explicitly made support conditional on the proposal passing. A later version on the same day clarified that the proposed support covered the Xai ecosystem and others, not Xai alone.
Read reportXai previewed staking V2 with three planned features: staking pools, lower transaction costs and support for third-party rewards. The announcement described the version as forthcoming. It did not specify a launch date, reward rate or compensation programme for earlier participants.
Read reportXai shared a contributor update featuring the Ex Populus chief executive, identified as TobyOneK. The announcement described an in-person planning meeting held the previous month and framed 2024 as an important year for the team. It offered a statement of direction, rather than a delivery schedule or a measure of network adoption.
Read reportOn March 10, 2024, a Xai support reply explained that permitting a wallet to use a Sentry operator entails responsibility for gas associated with assertions and reward claims. The reply recommended restricting operation to the relevant key-holding wallet and pointed readers to troubleshooting guidance.
Read reportOn March 8, 2024, Soby announced a partnership with Hall of Goats, naming Matt Leinart, Brian Graham and Greig Carlson as its leaders.
Read reportOn March 7, 2024, a Xai support response described esXAI emissions as split between 85% for Sentry nodes and 15% for a gas-subsidy node. The response linked this arrangement to reducing transaction friction for players. These percentages describe the allocation presented in that response, not a return rate or a measurement of subsidy spending.
Read reportOn March 6, 2024, XAI_GAMES reported 4,651,587 transactions, 574,079 active wallets and a peak of 364,176 daily transactions.
Read reportOn March 5, 2024, XAI_GAMES said community feedback had shaped the revised V1 staking tiers.
Read reportA troubleshooting post dated March 4, 2024 reproduced a command-line operator log from March 3. The log showed successful health checks followed by an EAI_AGAIN name-resolution error while processing a challenge. The publication date of the support record and the timestamp of the logged failure are different and should not be merged.
Read reportOn March 2, 2024, Xai pointed readers to a staking guide and separately described roughly 50% of total token supply as allocated to nodes. That allocation statement concerns token distribution, not an annual yield or a claim that the full allocation had already been paid out. The guide announcement alone does not establish its detailed terms.
Read reportOn March 1, 2024, the Sentry release notice made version 1.1.4 mandatory for desktop and command-line operators. The stated reason was compatibility with updated staking tiers; the notice warned that operators without the required version would no longer participate in challenges. This was a compatibility requirement, not an optional interface refresh.
Read reportOn February 29 UTC, a Discord post from the account displayed as XP Team described Staking Version 1 challenge-probability multiplier tiers: 1x with no esXAI staked, 2x at 1,000 esXAI, 4x at 10,000, 8x at 100,000, and 16x at 1,000,000 esXAI. It attributed higher gas fees at higher tiers to more frequent wins and claims, and described network rewards as shared among challenge winners.
Read reportOn February 28, 2024, Xai reported that more than $30 million in XAI had been staked. The same statement described v1 as an initial phase and pointed ahead to v2 community pools. It did not announce that those pools were already available.
Read reportOn February 27, 2024, Xai warned operators that a mandatory upgrade was needed for the staking launch. The 1.1.2 release notice described a breaking contract change and said older operators would stop participating in challenges. The optional 1.1.3 notice later that day added persistent logging that the preceding release had missed.
Read reportStaking and redemption went live after a mandatory Sentry node client update prepared operators for the contract change.
Read reportOn February 26, 2024, Xai reported 14,000 unique users and 2 million transactions for Tarochi. These are the project's published figures. The post did not specify the counting window, the method for identifying a unique user or the proportion of transactions supported by subsidies.
Read reportOn February 24, 2024, Xai announced that its Chinese New Year airdrop had been completed and asked Sentry node holders to check their wallets. This is an issuer completion statement; the post does not provide a wallet-by-wallet reconciliation or establish that Night Ash received any distribution.
Read reportOn February 23, 2024, Xai scheduled staking v1 for the following week and v2 for March. A follow-up statement clarified that esXAI-to-XAI redemptions were also planned to open with v1. These were forward schedules on the announcement date, not evidence that either release was already available.
Read reportOn February 22, 2024, Xai published a short statement announcing a partnership with Validao. The text named the partner but supplied no contract value, investment amount, implementation milestone or service-level commitment.
Read reportOn February 21, 2024, hmalviya9 published a node-reward explainer using reported averages of 25 challenges and 7,000 assertions per day.
Read reportOn February 20, 2024, Xai announced a partnership with LayerZero. Its statement said LayerZero supported Xai and joined the Data Availability Committee. The announcement also referred to further work that had not yet been disclosed; it did not describe that work as delivered.
Read reportOn February 17, 2024 in UTC, Xai's announcement channel warned about phishing aimed at its community through unsolicited messages, tokens and NFTs directing recipients to airdrop-claim sites. The notice identified xai.games as the official website and warned of wallet-drain risk. It did not quantify affected wallets or confirmed losses.
Read reportAn XAI_GAMES post dated February 16, 2024 reported more than 360000 daily transactions and more than 438000 wallets on Xai mainnet. It described the network as being roughly a month into mainnet operation. These are the project account's reported figures; the post does not specify the observation window, wallet-count method or transaction classification.
Read reportOn February 13, 2024, the account @andyyy said it had recorded an interview with @sobylife about Xai, describing the project as an L3 application chain built on Arbitrum Orbit. The post identified on-chain gaming and Arbitrum's role for developers as discussion topics, and said the interview was forthcoming.
Read reportThe February 12, 2024 Sentry notice identified version 1.0.86 as optional for desktop and CLI users. Its patch notes announced a Chinese New Year airdrop claim page and a correction to the KYC status shown there. The instructions distinguished automatic Windows updates from downloads for other supported clients and said existing keys did not need reassignment.
Read reportXai's February 10, 2024 announcement proposed a Lunar New Year distribution for eligible Sentry Node Key holders. It specified 88 XAI for the first key and 8 XAI for each additional key. Eligibility required completed KYC and a post about XAI. These were announced conditions, not evidence that any particular holder had received tokens.
Read reportA Tarochi post dated February 9, 2024 in UTC announced that its public mint was live, thanked more than 500 participants and named February 15 as its mainnet launch target on Xai. The participation figure was reported by the project, not independently counted here. The launch date was still a forward-looking announcement.
Read reportOn February 8, 2024 in UTC, XAI_GAMES said rollup-service providers were asking for Sentry node software. It also said work was underway on a solution intended to align the community's interests with software licensors. The post expressed commercial interest and a design objective; it did not name counterparties or disclose signed agreements.
Read reportXai published two Sentry update notices on February 6, 2024 in UTC. Version 1.0.82 was marked required for desktop and CLI users; its notes described a public node, a key-monitoring dashboard, last-challenge timing and display corrections. The later 1.0.83 notice was marked required for desktop and described minor interface fixes.
Read reportOn February 5, 2024, Tarochi's account said it was deploying to Xai mainnet and watching Xai stakers, inviting them to follow its token economics. The post described Tarochi as the first game deploying there. That priority claim remains the project's statement, not an independently established comparison of all deployments.
Read reportOn February 4, 2024, Mad_wongR summarized proposed esXAI-to-XAI redemption terms: 25% after 15 days, 62.5% after 90 days and 100% after 180 days.
Read reportAn XAI_GAMES post dated February 3, 2024 in UTC stated that XAI staking drew heavily on TIA staking. The post repeated the comparison in English and Chinese. It did not provide a launch date, an audited implementation or evidence of a partnership between the projects.
Read reportOn February 2, 2024, Xai's announcement channel described Final Form as a game planned for the network later that year, with all game logic on-chain. It linked an XAI_GAMES post timestamped February 1 in UTC. The records document an announcement of intended architecture and timing, not a completed launch.
Read reportIn Xai's community discussion on February 1, 2024, staking was described as drawing inspiration from Celestia. Another message that day used the name TIA for the same comparison. These statements concern design influences; they do not announce an operating staking service or document rewards paid to participants.
Read reportOn January 31, 2024, a Xai staking update said implementation of staking and redemptions was nearly finished. It also said several more weeks were needed for stress testing and a code audit. This was a development-status statement with remaining work, not an announcement that users could already stake or redeem through the planned system.
Read reportOn January 30, 2024, Xai announced Sentry software version 1.0.80 as a recommended update for desktop and CLI users. Its patch notes described infrastructure hardening intended to improve challenger stability. The notice set out different update steps for Windows, Mac and Linux; it did not report a measured reduction in failures.
Read reportOn January 26, 2024, Xai's announcement channel reported that a major global exchange had integrated XAI mainnet. The message linked an exchange announcement titled around completion of the integration and the opening of deposits. The retained record establishes when Xai communicated that development, rather than the time of the first successful customer transfer.
Read reportOn January 25, 2024, ethan_hunt answered a game-launch question by linking Xai's January-March roadmap.
Read reportOn January 18, 2024, XAI_GAMES welcomed Crypto Unicorns in a post that placed the announcement within Arbitrum's gaming ecosystem. Its wording presented the project as coming to Xai. This records an announced direction, not a completed migration or a measured increase in network usage.
Read reportOn January 16, 2024, XAI_GAMES published a short statement favoring decisions optimized for its community rather than venture investors. The post expressed a priority; it did not announce new token allocations, changes to vesting or a binding governance decision.
Read reportThe January 15, 2024 Sentry update notice recommended version 1.0.77 for desktop and CLI users. Its listed changes included displaying the CLI version during startup and health checks, making the KYC URL available through the kyc command, wallet-allowlist guidance and fixes, and improved internal alerts for the challenger.
Read reportA January 13, 2024 administrator notice described reports of people offering help in public channels before asking users to move into direct messages. It asked members who observed that behavior to alert administrators or moderators. The warning concerns the handover from visible support to a private conversation, where an apparent helper may be impersonating someone trusted.
Read reportOn January 11, Tarochi Game reported that its onchain RPG testnet had passed 4,500 unique users and was still receiving 50-100 daily active users nearly 2 months after deployment. It described a Xai mainnet release as close, with features and incentives still planned.
Read reportXai announced that its mainnet was live and published a bridge route from Arbitrum, followed by a Thirdweb integration notice.
Read reportXai's January 10, 2024 announcement stated that mainnet was live and directed readers to connection documentation and the Arbitrum bridge. This records the project's launch communication. It does not independently establish transaction throughput, uninterrupted availability or the scale of subsequent adoption.
Read reportThe Xai token-claim notice scheduled opening for 09:30 UTC on January 9, 2024. It identified a claim contract, a token contract and a claim page, and warned participants about impersonators and unsolicited messages.
Read reportThe token claim opened before Binance began trading XAI in six spot pairs on January 9, completing the distribution step announced six days earlier.
Read reportAn announcement on January 8, 2024 put the XAI airdrop claim roughly fifteen hours away and said official communications would follow across the project's channels. It urged readers not to open links shared elsewhere. The timing was an estimate in the announcement, not a record of completed claims.
Read reportIn an updated post dated January 4, XAI_GAMES called the following week's airdrop Season 1 and said Season 2 was coming soon. It gave no Season 2 eligibility, allocation, schedule, or distribution terms.
Read reportBinance announced a four-day XAI farming program, a 75 million XAI reward pool and a January 9 listing schedule.
Read reportOn January 3, a major global exchange announced an XAI farming programme that accepted BNB, FDUSD, and TUSD for staking. Later, XAI_GAMES said direct support would follow the programme. The announcements set the staking assets and stated subsequent support, without individual allocation or trading terms.
Read reportOn January 2, 2024, Final Form previewed Scourge, describing it as a rare ability that damages all adversaries at once.
Read reportOn January 1, 2024, KILICASLAN reported that eight days after starting a node and applying for KYC, verification was still pending and the displayed reward balance remained zero.
Read reportNo matching reports.