Night Ash
Dated project history and imagined scenes in one creative chronicle.
A creative chronicle combining project history with imagined scenes. Story events are not verification of network activity.
At year-end, the community looked back on both construction and waiting. BTC closed the year at USD 42,000. The year's work explained why people were waiting, but it did not complete the last step for holders.
Read report
The community was still waiting for the claim entry point over the weekend, but annual retrospectives had taken over the discussion channels. The posts kept returning to the same observation: on this day a year earlier, the chain had been only a sentence in a document. That account could show newcomers that the project had a history, while reminding longtime members that elapsed time was no substitute for an actual claim.
Read reportEligibility rules and snapshots had been explained, but claiming had not opened. BTC held near USD 42,000 as the wider market awaited January's ETF decision. The discussion shifted from who qualified to how people could claim safely.
Read reportXai set claim eligibility for high-tier Odyssey badge holders and Sentry key owners, with different identity-verification requirements.
Read reportAfter the postponement, the community was waiting for more than a new date: it needed to know how eligibility would work. The official rules first corrected the term: this was not a traditional automatic airdrop but a claim that users had to initiate. The node snapshot that had still been pending the previous day was complete, and the eligibility boundaries were clearer.
Read reportThe scheduled distribution day arrived, but the airdrop had been postponed until the following week because of a team member's health problem. Two views coexisted in the chat. What had been a day for celebration became a test of trust.
Read reportOn the first day after the holiday, the community was expecting the first season of the airdrop on December 27. A short official notice postponed the $XAI airdrop until the following week, with the exact date still being confirmed, and repeated that the node snapshot had not yet been taken. The once firm date had become an unconfirmed day the following week, and key holders still could not treat their eligibility as settled.
Read reportOn Christmas Day, the community was still waiting for the airdrop, while the Night Watchman tended his node as usual. BTC was around USD 43,000, and his node passed 100 consecutive days online. The 100 days gave his persistence a measure and also made the limits of one person's energy visible.
Read reportDiscord still had people on duty on Christmas Eve. Half watched on-chain monitoring, while the others answered airdrop questions. Discord stayed open, but being on duty no longer had to mean that everyone watched every message.
Read reportAfter the first season was announced, the weekend conversation shifted from asking for a date to checking eligibility. Some had both types of qualification and began estimating their possible share. The same announcement became a ledger of hope and disappointment in the chat.
Read reportWith the first season of the airdrop approaching, Odyssey participants and Sentry Key holders were waiting to learn who qualified. The founder first posted guidance for people harmed by the “wrong contract” scam. The community finally had a date, but the two groups could not be treated as one finalized list.
Read reportThe previous day's game teaser was still circulating in the group, and Sentry key sales had not stopped. The inscription surge pushed fees higher, giving layer-two and layer-three narratives a favorable moment, while key sales continued. External fees made the project's technical argument easier to hear, but they did not solve new holders' practical problems.
Read reportXai was building a chain for games, and the internal test schedule for the first partner games was nearing completion. The announcement channel carried only one English sentence, “Final form's ready. are you?”, and a link. Previously, people had been guessing at progress from old images; this time the team itself sounded close to completion.
Read reportWith the Xai mainnet in place to support games, A-Zhen, a chain-side engineer, was turning her attention to game integration. Word came from the mainnet side that the internal test schedule for the first partner games was being finalized. The work had moved from talking broadly about games to arranging their internal tests, but a nearly finished schedule did not mean players could enter yet.
Read reportKey sales and the discussion after Odyssey's close still shared the announcement channel. BTC pulled back to USD 40,700, but few in the group paid it much attention. The short post drew attention back to the project without answering questions about timing or specific plans.
Read reportKey sales continued as the node software went through several rounds of patches. On Sunday, community members began assembling a long “Getting Started for Key Holders” post, walking through purchase, installation, and node operation. Scattered experience was becoming a guide newcomers could read in sequence, saving the Night Watchman from starting every explanation from scratch.
Read reportXai Odyssey had run for more than three months, including over 50 days of daily tasks. Odyssey ended today, and people still checked in on its last day. The rhythm of daily check-ins stopped, and the community's question shifted from what to do today to what its past participation meant.
Read reportAfter Sentry key sales began, losses caused by fake links remained unresolved. No plan had been announced. The questions had received a reply, but victims still did not know who would qualify or when they would hear more.
Read reportAfter buying a key, anyone seeking network rewards still had to complete identity verification. Officials coordinated document submissions one person at a time. The discussion moved from the speed of buying to eligibility and privacy after purchase.
Read reportAfter the key sale, the community chat still revolved around changing price tiers. The FOMC took a more dovish tone, its dot plot suggested possible rate cuts next year, and BTC stood at USD 43,000. The market mood made the discussion feel more urgent, but it did not answer how buyers would run nodes or cover their costs.
Read reportXai Odyssey's daily tasks had continued for more than three months. Officials reminded the community that Odyssey would end in four days. The reminder brought attention back to the long stretch of participation and gave the final checks a deadline.
Read reportThe node software was still being patched. Patches arrived one after another. The exchange helped newcomers stop treating every notice as a failure.
Read reportThe sale had reached its fourth day. The founder posted a message that read less like a routine announcement than an admission: “To be honest and transparent,” sales had far exceeded expectations. The narrator remembered the warning four days earlier: no purchase link had yet been published, supposed official links sent by private message were scams, and the team would not cover losses from them.
Read reportThe Sentry Key sale continued through the weekend. Official staff were overwhelmed with questions but answered them one by one. Manual replies showed that the team was present, but they also exposed a gap between support capacity and the pace of sales.
Read reportOn the second day of the Sentry Key sale, the Night Watchman was still helping late arrivals in the community chat check purchase information. BTC reached USD 44,000, a high for the year; Sentry Key prices also climbed through several tiers as sales continued. The conversation shifted from whether people could buy a key to whether they could keep a node running.
Read reportThe Sentry key sale began with web, desktop, and command-line purchase paths, followed by publication of the contract address amid phishing attempts.
Read reportAt 4 a.m. Three purchase routes opened at once: the website, desktop software and command line. The narrator wrote that the chain's first citizens had paid their own way in.
Read reportBy Coordinated Universal Time, Sentry node key sales would begin early the next day; for community members in some regions, this was the eve of the sale. The Foundation set out the rules together: a fair sale, with no private sale, allowlist or special treatment. The narrator read the two announcements side by side.
Read reportThe final round of questions before the sale had begun. Officials said not to put more than 70 keys in a single transaction, which could run into the parent chain's gas limit; for caution, they advised staying within 50. The answer gave people considering multiple keys a basis for splitting transactions, while showing how easily a rule could be distorted in retelling.
Read reportThe countdown to the node sale had begun, and the community was watching both the market and the sale rules. BTC broke above USD 40,000. The mood had changed: conversation shifted from whether the sale would arrive to whether one should rush to be early.
Read reportAs the Sentry node sale drew closer, community members in different time zones could easily record the same opening under different dates. The official global time-zone table gave the same opening moment as 8 p.m. on December 6 in San Francisco, 11 p.m. on December 6 in New York, and noon on December 7 in Hong Kong. The table turned 'next week's sale' into a time people could plan around.
Read reportWeekend conversation still revolved around the Sentry node sale. Community members brought back last month's announcement confirming that Turkey, China and Hong Kong could participate and read it line by line. Members in those three places could shift their attention from whether they were included to how to prepare.
Read reportDecember began with Sentry node keys due to go on sale the following week. BTC climbed to USD 38,500, and the announcement channel sounded more urgent as the sale approached. The higher price made waiting harder, but it did not answer how to buy a key or when a node could run.
Read reportBackground: November ended with BTC closing at USD 37,700. Today: The official account confirmed that the sale was still set for December 6. Impact and next steps: The date was clear, and so was one reason for caution before buying: claims that node software was already available needed to be checked against an official release.
Read reportBackground: BTC stood at USD 37,800, another step closer to its high for the year, but the community was more focused on the coming fair sale. Today: People in the group asked how the sale would stop bots from buying up keys. Impact and next steps: The previous day's answer settled who could participate; today's questions concerned competition once everyone could enter.
Read reportBackground: The day before, the narrator had only been able to tell the Turkish community that eligibility was being checked with legal counsel. Today: A day later, the narrator published the answer in all caps: Turkey, China and Hong Kong would all be allowed to take part in the Sentry node sale beginning December 6. Impact and next steps: People who had been left asking about eligibility could prepare on the basis of the published decision.
Read reportBackground: The Sentry node sale was near, but the Turkish community still did not know whether it could participate. Today: In the afternoon, the narrator first told the Turkish community that its concerns had been heard and that the team was checking with legal counsel whether Turkey could be included. Impact and next steps: To the narrator, rejecting a private sale meant passing up readily available money and giving people willing to buy publicly, and perhaps run nodes later, the opportunity to obtain keys.
Read reportBackground: With the sale approaching, tiered pricing made timing matter. Today: The same question circulated all day: would the first tier—3,000 keys at USD 300 each—be bought up almost instantly on sale day? Impact and next steps: The rules were fixed; buyers' behavior was not.
Read reportBackground: It was the weekend, with roughly ten days left before the Sentry key sale. Today: Someone checked their own machine against the documentation, item by item, and began treating buying a key and running it over time as separate decisions. Impact and next steps: The conversation before the sale became more concrete: obtaining a key would still leave the work of running it.
Read reportBackground: On Black Friday, Odyssey tasks were still under way and the Sentry key sale was drawing closer. Today: The official account promoted Tarochi again and confirmed that its achievements still counted toward Odyssey points. Impact and next steps: Preparing for the sale now meant more than watching the price.
Read reportThanksgiving arrived soon after Tarochi went live on the testnet. One player complained that Tarochi lagged badly and said it needed serious work; most others were exchanging holiday greetings. The cause of the lag did not become clear that day, but a passing complaint had a chance to become useful feedback.
Read reportTarochi had just reached the testnet, and players were starting to ask whether they could complete its tasks smoothly. Officials reported more than 60 million cumulative testnet transactions, averaging over 3 million per day, roughly three times Ethereum's daily transaction volume over the same period. The figures made the scale of the test phase visible, but every transaction counted had occurred on the testnet; they could not establish the experience of full operation.
Read reportTasks and the leaderboard were drawing players through the Odyssey's second phase, while the testnet needed things they could actually play. CZ pleaded guilty and stepped down as Binance CEO, and Binance settled with the United States for USD 4.3 billion. For participants pursuing second-phase points, Tarochi connected playing a game to their choice of tasks.
Read reportThe 1,375-point cutoff announced the day before gave Odyssey participants a reference, but they still wanted to see their places on the ranking. BTC reached USD 37,000, and funding conditions looked looser than before. The public board turned an abstract cutoff into positions people could inspect, while leaving a long wait between official checks.
Read reportUntil now, Pioneer status had been described only as a place in the top 15%, leaving Odyssey participants unsure whether their scores were enough. Officials clarified that, in that snapshot, a score of at least 1,375 was needed to enter the top 15% and qualify as a Pioneer. The 1,375-point mark replaced speculation with a visible line and gave those below it a concrete target.
Read reportOdyssey tasks were still underway, but submissions had formed a review queue. One participant found that a submission had sat for three days without an update, prompting people in the chat to ask whether they should submit again. Manual checks gave the problem a way forward, but review speed still depended on limited staff time.
Read reportLess than a month remained in the Odyssey's second phase. People asked about the cutoff in the chat every day, yet the only answer available was a rank, not a score. The discussion shifted from whether to participate to how to spend time while the cutoff was unknown.
Read reportFor a blockchain game trying to welcome new players, having to prepare a main wallet before starting remained a hurdle. The partner shared a plan: in the future, players could start with a temporary wallet and later connect their progress to a main wallet. The plan offered a concrete way to ease entry: let people enter the game first and handle the lasting wallet connection later.
Read reportThe Odyssey snapshot had just passed, and players were waiting for clearer eligibility information. The card battler released another skill preview, the only new item in the announcement channel that week. The preview gave players another detail to discuss, but it did not settle when the game would be available or how its full gameplay would work.
Read reportParticipants in the Odyssey's second phase were still completing tasks and watching for Pioneer eligibility, without knowing how their scores compared with others. CPI fell sharply, BTC stood above USD 36,000, and expectations of interest rate cuts rose. The snapshot gave that day's participation a fixed reference and focused worries about missing points that had previously been scattered.
Read reportMonday brought no new announcement, but the Sentry key sale was drawing closer. One member took the group's size as proof that the sale would draw attention; another worried that questions would disappear in the chat. The community no longer doubted that the sale would attract interest.
Read reportThe Odyssey's second phase was still underway, but its task platform worked inconsistently. After skipping the claim step for two nights, one player checked again and found that the points had appeared automatically. The automatic credit gave waiting players a useful example and eased the urge to repeat an action immediately, but it did not show that everyone's tasks had been settled.
Read reportOver the weekend, sale preparations and questions about the token crowded the community chat. People repeatedly asked how tokens would be allocated and whether there would be an airdrop, but the official account gave no answer. Members could at least check their eligibility and operating preparations, but the rules told them nothing about an airdrop or their share of tokens.
Read reportWith the sale date and total supply of Sentry license keys announced, the community's question shifted from whether people could buy one to which price tier they might reach. Someone broke down the curve: 50,000 keys were divided among 40 tiers of unequal size. The discussion moved from whether a key could be secured on sale day to what price each person was willing to bear.
Read reportWith the Sentry key sale terms published, the Chinese language community began turning announcement language into practical choices people could discuss. Community members translated and circulated the sale points one by one. The translation gave scattered purchase discussions a common basis, and the multiple key rule changed how people estimated node setups.
Read reportXai disclosed a permanent 50,000-key cap, a tiered sale starting near $300 in ETH, and XAI rewards for licensed Sentry operators.
Read reportThe Sentry node sale was approaching. The announcement set the sale for December 6: there would be 50,000 license keys in total, with that supply capped. Until then, joining the node effort had largely been a discussion of rules and equipment.
Read reportFinal Form had often been mentioned as a game connected to Xai, but players still did not know how it would reach the chain from where it was. An operator said Final Form would bridge from Solana when mainnet launched. Players previously knew only that the game and the chain were meant to meet.
Read reportThe community was waiting for the next steps on mainnet and the game while digesting the published token model. The card battle game released its first skill preview, prompting players to discuss how the skill might work in a match. The preview made the game more concrete than a name alone, though it was too little to judge the full experience.
Read reportBadge minting had just recovered, but another platform fault held up Odyssey tasks. The task platform remained stuck for another day, leaving points unclaimable. Points remained out of reach, and repeated attempts could not repair the platform.
Read reportWeekend discussion still revolved around the Pioneer badge minting fault. An operator explained that once released, anyone would be able to download and run the software, but submitting attestations and receiving network rewards required buying a Sentry license key first. With minting repaired, the conversation could move from errors back to eligibility and cost.
Read reportOdyssey participants were trying to mint their Pioneer badges while the community awaited the Sentry node sale and mainnet progress. Pioneer badge minting failed for many people. Night Watchman treated these as two different kinds of waiting: an individual mint needed time to complete, while the project still had a sequence of steps ahead.
Read reportAs people kept asking about the Sentry sale and mainnet timing, players also began using the roadmap to guess when a game might be playable. One player pulled up the roadmap and asked whether the game had to wait for mainnet, perhaps even until January 2024. The question drew players' attention from node sales back to the game itself and exposed the gap between a roadmap and a playable release.
Read reportAs November began, Odyssey's second phase still drew participants through daily tasks, while the Sentry sale gave the community another date to count down to. BTC remained high at around USD 34,500. The tasks had not changed, but anxiety shifted from finishing each day's mint to knowing when progress would be fixed.
Read reportAs October drew to a close, Xai testnet traffic and the Sentry key sale arrangements had become everyday subjects in the community. BTC closed the month at USD 34,400, up nearly 30% in October. Two clear threads remained at month's end: the testnet had carried a heavier load, and the sale now had a price, a supply, and a date.
Read reportA key was necessary for a Sentry node to accumulate rewards, and the community was asking what other hurdles remained. BTC consolidated around USD 34,500, and market attention shifted to the November ETF window. The reward rules now extended beyond buying a key and running software to identity, location, and continued operation.
Read reportAs the Sentry key sale rules became clearer, some in the community treated a key as a ticket that would produce rewards as soon as it was bought. The most common question remained, “What is a key for?” The key's role had become more precise: it was required for a node to earn rewards, but purchase alone did not make rewards accumulate.
Read reportOver the weekend, discussion shifted from the mainnet launch date to Sentry rewards. The team went through its existing explanations point by point. The discussion now had a more concrete focus than “When will mainnet launch?”, though the explanations had not settled every doubt.
Read reportAfter the Sentry license key sale was announced, the community was studying nodes while worrying that talk of games would be pushed aside. Today the team opened a creator program for people who understood both games and blockchain. Creators now had a way to contribute content, and the terms of Sentry participation were clearer.
Read reportWith the tokenomics and Sentry sale details newly released, the community shifted from asking “when does it go on sale?” In response to repeated questions, officials said there would be 50,000 keys in total, with a fixed cap. The supply of keys and the fate of testnet efforts had clearer answers, but the argument continued.
Read reportThe Odyssey’s second phase was still using daily tasks to stress the testnet. A daytime report said the testnet had handled 1.4 million transactions per day for two consecutive days. The same announcement also placed the stress test alongside the project’s path: the testnet had exceeded one million transactions in a day, which officials called one of the largest testnets in the industry’s history and attributed to an experience requiring neither a wallet nor gas fees.
Read reportAfter BTC’s sharp rise, the market began talking about altcoins, and the community grew more eager to know when Xai’s mainnet would arrive. The market was still feverish, and altcoins were beginning to stir. The discussion returned from market gains to specific checks.
Read reportAfter the Sentry plan was announced, the Odyssey’s daily tasks kept loading the testnet. BTC surged past USD 34,000, with developments in the Grayscale case and ETF expectations driving market sentiment. One week’s volume now equaled half of the preceding seven-week total, putting the testnet under a different level of pressure.
Read reportContributor-role claims had just opened. Many people stopped at “Please verify your Discord account first.” The claim page was open, yet verification had become the practical barrier, consuming much of the weekend.
Read reportThe first-phase ranking was locked, and the community could now turn a place on the leaderboard into a visible contributor role. Claims for the contributor role opened. A leaderboard qualification now had a claim page, along with the risk of a permanent account choice.
Read reportThe Odyssey had entered its phase of daily task resets, and the testnet was under sustained load. BTC rose above USD 30,000, and this time nobody in the group called it fake news. The price and testnet traffic stirred conversation, but eligibility rested on an earlier ranking; doing more tasks today could not change the first-phase result.
Read reportXai was still in its testnet phase, and the community talked daily about tasks and traffic. The narrator posted a short announcement: Xai had entered a strategic partnership with Team Secret, one of the world's top five esports teams. Until then, much of the attention had come from people doing Odyssey tasks.
Read reportIn the Odyssey's final stretch, tasks reset every day and avatars could be minted again, sending fresh activity through the testnet. The testnet reached 580,000 transactions in a day, as daily records kept falling. The 580,000 transactions showed that daily resets were putting pressure on the testnet; one million was still some distance away.
Read reportThe previous day's false ETF story had sent BTC up and then down. The false story still cast a shadow, while genuine expectations about an ETF continued to build. The market shifted from a violent swing to watchful waiting, and the discussion turned from chasing a headline toward waiting for information that could be confirmed.
Read reportAfter the first phase ended, participants still wanted to know whether their scores could change and when the commemorative NFT would arrive. The first-phase rankings became final, based on the snapshot taken at 10 a.m. on October 12; points and ranks would no longer change. Participants could finally treat their first-phase results as settled.
Read reportThe Odyssey reached its fiftieth day, and daily tasks had become a familiar routine. Officials listed the usual tasks, then disclosed at the end of a sentence that the number of Sentries released in November would be limited. Until then, people had been waiting to learn when Sentry would appear; now they also wondered whether they could get one.
Read reportThe Odyssey's daily tasks continued through the weekend, while Sentry remained a promise for November. Officials repeated the same advice: join the waitlist to hear about Sentry as soon as news arrived. The waitlist gave people something to do while they waited, but it answered none of his questions about equipment, costs, or operating arrangements.
Read reportThe Odyssey's first phase had just been sealed by the snapshot taken at 10 a.m. The final stretch began. The first phase now had a firm boundary, but participants could no longer follow a rhythm of finishing once and waiting for rankings.
Read reportThe window for claiming points from the first stage was nearing its end, and the community was already wondering what the Odyssey would ask of them next. Fewer than 23 hours remained to claim points. The close of the first stage and the entrance to the second met on the same day.
Read reportThe first Contributor commemorative NFTs would depend on results from this stage, so the community needed to know the limits for the last mint and for claiming points. Officials set the timing down to the hour: the Day 46 Pioneer avatar could be minted until 1 a.m. on October 13. The precise times let people plan their remaining tasks and separated two actions: finish any available minting first, then check points during the permitted window.
Read reportPaima Studios said Tarochi would deploy on Xai as the network reported nearly 200,000 connected wallets and more than 3.5 million testnet transactions.
Read reportThe Odyssey was approaching the point that would determine the first Contributor mementos. During the day, officials reposted Paima Studios’ decision to deploy its onchain role-playing game Tarochi on Xai, with a public beta coming soon. The narrator lingered over the nearly 200,000 wallets and more than 3.5 million transactions, all on a testnet with no direct earnings yet.
Read reportThe weekend’s conflict had left markets tense, and the community was only just returning to its routine after the points platform outage. BTC stabilized after a brief pullback, and funds began to bet on an ETF. The day offered no answer about where the market would go.
Read reportThe domain hijack had interrupted the community’s daily points claims. Once the points platform returned, officials shared cleanup steps and urged users to check their wallets for suspicious approvals before doing anything else. The Night Watchman had intended to check his rank first.
Read reportThe Odyssey had just been extended, and the points platform’s security problem was still unresolved. Geopolitical conflict broke out in the Middle East, lifting demand for safety and leaving markets on edge. The conversation moved from rushing through tasks to keeping in touch amid uncertainty.
Read reportThe Odyssey was still running on the testnet. In the afternoon, officials warned that the points platform’s domain had been hijacked: people should stay off the site and sign no transactions. The narrator read the two announcements side by side: one told people to avoid a compromised gateway, while the other asked them to keep stressing the testnet.
Read reportThe testnet had drawn integration ideas from external teams, but developers needed instructions they could actually follow beyond a proposal. The full testnet developer documentation went live, complete with sample code. Integration discussions had previously stalled at what someone wanted to deploy; developers now had a concrete place to start reading and trying things.
Read reportAhead of the snapshot, questions about task points and eventual rewards were often tangled together in the group. Someone asked the group outright whether there would be an airdrop. The airdrop question had an answer for the present, leaving participants to decide whether to keep investing their time.
Read reportThe scoring change at the end of September had made room for wallets that completed on-chain tasks without registering on the points platform. The organizers clarified in advance that the October 6 leaderboard snapshot would include those unregistered addresses' testnet task actions. Compared with relying only on points-platform records, the rule left a place for on-chain participants the platform had missed.
Read reportThe new month had barely begun, and testnet participants were still absorbing the minting page congestion and the rewritten queue. BTC climbed to USD 28,000, and “Uptober” returned to the conversation. The market lifted the group's mood and briefly pushed the technical queue issue into the background.
Read reportOctober opened with Pioneer avatar minting still a daily entry point to the testnet campaign. BTC recovered to USD 27,000. Participants who could only refresh an error page the day before now at least had a way to try again.
Read reportAs September ended, the testnet campaign had run for a full month, and mainnet had yet to appear. BTC closed the month at USD 26,900. A month's participation had made the queue feel crowded and the rule changes harder to gloss over with a slogan.
Read reportOn day 33 of the Odyssey, the previous day's announcement had distinguished minting a Pioneer avatar from actually gaining Pioneer status. Today, the organizers urged everyone to move faster, saying that reaching the “final form” required speed. The call to hurry shifted attention from daily tasks toward eventual status, without explaining how that status would be awarded.
Read reportBackground: After the previous night's scoring change, some in the group were conflating 'earning points' with 'becoming a Pioneer.' Today: The announcement said that minting a Pioneer NFT on the testnet was already good, but actually making it to Pioneer would be better. Impact and next steps: An NFT showed participation, while Pioneer status still depended on the event's criteria.
Read reportAfter platform tracking failures, Odyssey began crediting qualifying onchain actions from unregistered wallets while reserving Vanguard status for registered users.
Read reportBackground: By Day 31 of Odyssey, official tasks, onchain actions, and registration records on Galxe and Zealy did not always match. Today: The Day 31 task went out as usual, with the usual wording; the real change came that evening. Impact and next steps: That night, the Night Watchman described the revised rule to the group as two ledgers: the chain knew what a wallet had done, while platform registration recorded who had reported their work.
Read reportBackground: BTC was around USD 26,200, and the market was full of speculation about a fourth-quarter ETF decision. Today: The officials reposted the Day 29 announcement word for word. Impact and next steps: Market expectations did not spare participants the need to check their tasks.
Read reportBackground: By Day 29, participants had spent considerable time on Odyssey, and Pioneer status kept coming up. Today: Someone poured cold water on the talk: the whole effort might bring no airdrop, and might end with nothing more than eligibility to buy a node at a discount. Impact and next steps: The speculation changed no event rule, yet it exposed the gap between completing tasks and expecting a reward.
Read reportBackground: Participants still cared about Pioneer status in Odyssey, but they had already seen how many details could separate a task, an NFT mint, and a score. Today: The officials listed two conditions for being 'worthy of Pioneer': like the post on X, then complete the day's task. Impact and next steps: The light tone made participation inviting, but it could hide the pressure of a daily deadline.
Read reportBackground: More newcomers entered the Odyssey group over the weekend. Today: The group posted the Web3 Warriors download link again; no one could count how many times the same link had been shared that month. Impact and next steps: Reposting answered the immediate question and exposed how easily useful information disappeared in the chat.
Read reportBackground: Odyssey had entered its fifth phase. Today: The Day 26 task appeared with an increasingly urgent official warning: once a day passed, its task could no longer be done, and its points were lost. Impact and next steps: The event's calendar had grown longer; the deadline for each daily task had not.
Read reportOdyssey entered its fifth phase. At the opening of the fifth phase, officials did not lead with points. The emphasis moved from a single day's points to a shared experience, but a sense of belonging could not replace clear task rules.
Read reportThe Chinese-language Q&A had just ended, but Odyssey's daily tasks continued. The FOMC held rates steady but struck a hawkish tone. The previous evening's nearly hour-long introduction had not completed today's task for anyone, and the market's brief reversal could not answer practical questions.
Read reportThe first Chinese-language Q&A about an Orbit chain had reached its scheduled day. The Q&A began at 8 p.m. The spoken explanation brought the game plans and the current route into participation into one conversation, while the announcement kept urging quick action.
Read reportArbitrum's Chinese-language Q&A was set for the following day. Arbitrum's official account reposted the Q&A announcement and called it the first Chinese-language session ever about an Orbit chain. The session had moved from an announcement within the community to a more public Chinese-language entry point.
Read reportThe Day 16 minting page and Twitter authorization had both failed. Officials confirmed that a problem with the Twitter interface had trapped authorization in a loop. Removing the button took away a barrier that had trapped users, and the points rule gave those affected a way through.
Read reportOver the weekend, the Odyssey group was still dealing with the previous day's minting trouble. The same question kept coming back: if the Day 15 avatar was minted, why was its owner missing from the snapshot? The concern had shifted from whether minting worked to whether a successful mint counted.
Read reportThe Odyssey final challenge had just begun, but minting the Pioneer avatar was already stuck. The Day 16 Pioneer avatar would not mint, and the page said it was being updated. What first looked like a wait for a page update had become a problem with both access and authorization.
Read reportOdyssey had just been extended by two weeks. Stage Four opened as the “Ultimate Challenge.” The activity’s focus shifted from learning how to participate to competing for limited status through continued tasks.
Read reportOdyssey’s original schedule had established a daily rhythm for longtime participants, while newcomers worried they had arrived too late. A rebound in CPI unsettled the market, though crypto prices reacted sluggishly. The extension gave newcomers more future tasks to attempt and made people who had already planned their time reconsider their pace.
Read reportOdyssey had reached Day 16. The team reposted the rules most likely to trip people up: both platforms had to use the same wallet address; points for Galxe tasks would not appear immediately but would require the daily snapshot and a return the next day to claim them; and a Pioneer NFT missed on a given day could never be minted later—participants could only mint those for subsequent days. The rules drew a clear distinction between points appearing later and losing a day’s minting opportunity for good.
Read reportOdyssey’s daily tasks had reached Day 15. BTC fell toward the year’s low region around USD 25,000, and the market was pessimistic. The announcement made the scarcity feel sharper, but it fixed no one’s place in the rankings.
Read reportSunday brought no new activity milestone to the Chinese community, but people were still trying to connect Odyssey’s status system to the games themselves. Someone translated a substantial passage about Final Form into Chinese and posted it on the forum. It was the most serious long post of those days, but it could not be treated as an official plan.
Read reportOdyssey had accustomed participants to finding tasks and earning points each day, but to many newcomers, “Pioneer” was still just a name on the leaderboard. The Day 13 daily task went out as usual. The challenge drew people who had been quietly clicking through tasks into a public conversation.
Read reportOdyssey’s daily tasks were still underway, and Web3 Warriors had recently added a waiting message for minting battle tokens. BTC hovered around USD 26,000, while liquidity in altcoins was thin. The waiting message was meant to reassure players that the game was working, but this time it obscured a real fault.
Read reportThe first two stages of Odyssey had familiarized participants with tasks and rankings. The third stage of Odyssey opened with tasks to claim an NFT and deploy a personal NFT contract on the testnet. Participation was moving from completing platform tasks to creating a testnet contract, giving people something to do beyond collecting leaderboard points.
Read reportOdyssey used its leaderboard to encourage participation while bringing newcomers onto the testnet. The official account said on Twitter that the testnet had more than 80,000 wallet addresses and processed over 100,000 transactions a day. The published figures gave the testnet's load a scale, and the refreshed leaderboard made the competition more concrete.
Read reportWeb3 Warriors was still in testing. Update 1.1.4 added a "Please wait" button while battle tokens were being minted, so players would not mistake the delay for a frozen game. The wait now had visible feedback, and the two unexpected cooldown and death behaviors had been addressed.
Read reportMarkets were quiet on the U.S. Submissions for the community task closed at 9 a.m. The community had moved from carrying out assigned tasks to having a say in their content.
Read reportAccess had only just been restored when Odyssey participants ran into a different delay: they could finish tasks without seeing the wallet list or points on Galxe catch up at once. Galxe kept returning error 422 while updating the wallet list for completed tasks, leaving the snapshot unable to refresh. Yesterday's problem had been getting in; today's was accounting for work after completion.
Read reportThe first leaderboard had just appeared, and participants were trying to finish their Odyssey tasks. Cloudflare blocked a group of participants. The deadlines had moved from extended to temporarily suspended, relieving participants of the need to rush through tasks while the entrance was broken.
Read reportSeptember opened with BTC slipping to USD 25,800. The narrator announced an extension of the task deadlines and offered a brief thanks to the community for putting the testnet under load and reporting its faults one by one. Previously, participants could only check their points on each platform separately.
Read reportBy the end of August, Odyssey had given the community tasks to do each day, and newcomers no longer asked only when things would begin. BTC slipped back at the month's end, closing at USD 26,000. A month earlier, the group had no tasks for newcomers to ask about.
Read reportOnce Odyssey began, task pages could tell newcomers where to click, but they did not necessarily explain why they were taking part. Community members began writing longer posts that could be read in five minutes, unpacking Xai Odyssey: why Xai wanted to build a gaming network, and how it envisioned letting billions of traditional gamers own in-game items without first having to handle a crypto wallet. The conversation moved from following task-page instructions toward understanding what the tasks were meant to serve.
Read reportXai Odyssey had just begun, and the community was still working through the task and Pioneer identity rules. Grayscale won its case against the SEC, advancing the path toward an ETF, and BTC jumped to USD 28,000. The price move did not answer questions about eligibility or migration steps.
Read reportXai had been announced as a gaming chain, but its mainnet, token, and any fully launched game had yet to arrive. In the morning, the official account teased a major announcement for later that day. The waiting community now had a way to participate and an identity goal that could change with its ranking.
Read reportFinal Form was moving toward Arbitrum, its open beta had yet to arrive, and card staking continued. The newcomer asked three questions in succession: Was the chain live? His answer separated the current staking period from the coming period of play and showed the newcomer that the present choice had a deadline.
Read reportOver the weekend, some players tried to check the cards they had listed but could not find their listings on the marketplace page. An explanation finally arrived: the marketplace hosting the cards had been redesigned, with its entire page replaced, leaving listings invisible. The problem now pointed to an external marketplace page rather than players failing to find a button.
Read reportFinal Form was still awaiting its open beta, while conversation in the community revolved around card staking and release dates. The official account posted a line that sounded less like promotion: the best games let people escape reality and forget their troubles for a while, even if only for an hour a day. The conversation set no date for the open beta, but it showed the Night Watchman that players were waiting for more than an announcement.
Read reportQuestions about Final Form's migration, staking window, and card issues had arrived in quick succession. The group recommended Final Form's official account again and encouraged newcomers to look through the character reveals as they appeared. Newcomers now had a starting point for reviewing the game's material, and group explanations could begin from shared sources instead of rumors.
Read reportPlayers faced two issues at once: Final Form was moving toward Arbitrum, while their cards were still in the staking phase. Someone in the group confirmed that Final Form was being moved to Arbitrum. The migration direction and the staking deadline were finally stated together, giving newcomers a basis for deciding whether to participate now.
Read reportFinal Form was still in the period of card staking and waiting for open testing. Staking continued, and the Night Watchman said the group's most repeated phrase that month was “wait a bit longer.” “Wait a bit longer” became a set of questions that needed answers rather than a general reassurance.
Read reportA new week began with players still waiting for an open test schedule. Someone opened the announcements section several times and found only older posts. The silence supplied no progress update, but it led to a modest way of handling the wait: collect questions first, then look for announcements that could answer them.
Read reportThe previous day, a longtime player had offered rare pigeon cards to people who burned a legendary card to extract Chromos. A queue formed under the pigeon-card post. The small challenge made differences in card holdings visible in the conversation; a lively thread did not mean everyone could take part.
Read reportIn the Final Form group that weekend, staking cards and discussing items remained routine. The theft victim said they wanted to turn the remaining items into cash but had not settled on a way to handle them. The three questions exposed different pressures.
Read reportBTC had plunged the previous day, and the market was still absorbing the shock. Someone entered the group carrying the market's anxiety, but asked when open testing was scheduled. The conversation moved from prices back to whether people could get into the game.
Read reportFinal Form players were still waiting for the open test, but they continued calculating the cost of card combinations and Chromos. BTC plunged to USD 26,000 in a single day, and long liquidations exceeded USD 1 billion. The crash disrupted the rhythm of the chat but did not answer how players should use their cards.
Read reportA day after the validator post, the Final Form group's routine was still dominated by committed cards and Chromos. Screenshots of committed cards kept filling the chat, and nobody mentioned validators again. The previous day's chain-side message had not changed what the group was doing, but the exchange exposed a limit of communicating through screenshots: people unfamiliar with the process could read the same image differently.
Read reportPlayers were still focused on Final Form's Chromos and cards. The official account posted a short message with an almost provocative opening: if you knew what validators were, good; if not, go read. The message gave A-Zhen a definite question to pursue about who would operate the chain and how they would be rewarded, but offered no details on joining as a node or putting rewards into practice.
Read reportBTC moved in a narrow range around USD 29,400, with market volatility at a low. The newcomer asked what he could buy, or whether he should wait for the token launch. The conversation moved from finding a buying moment to identifying existing items and a safe entry point.
Read reportPlayers were waiting for news about Final Form's next steps, while DAG cards could already be traded on a secondary market. One player said he was uncomfortable leaving spare money idle and planned to complete a DAG set on the secondary market. A casual plan to buy became a decision to establish both a purpose and reliable information first.
Read reportFinal Form players were still committing cards and accumulating Chromos, but they had also begun weighing the cost of evolving their cards. One player brought out four epic cards and asked whether he had enough Chromos to combine them into the next tier. Until then, the player had focused on how much Chromos he still needed.
Read reportXai's explainer had appeared the day before and was formally posted again in the announcements today. After watching, someone still asked what the third layer added beyond the second. The question shifted the discussion from naming the layers to tracing the steps a player would actually take.
Read reportPlayers had been following Final Form's card commitments and character news while trying to understand Xai's relationship with Arbitrum. The official account released an explainer film describing Xai as a gaming Layer 3 network built on Arbitrum together with Offchain Labs. The film gave people discussing the network's structure a shared picture; the new character gave waiting players something concrete to discuss in the game.
Read reportThe conversation sparked by the short film faded, and summer heat settled over a quiet Final Form group. Only a handful of people were checking their records, counting how many cards they had committed and how much Chromos they had accumulated. The check produced no new update for the waiting group, but it made the next choice more deliberate: confirm the cards and Chromos already accounted for before committing more.
Read reportThe day before, the official account had explained the division of work between Xai and Arbitrum One, prompting players to ask where the game studio fit in the chain's story. The official account released a short film introducing several Ex Populus founders and their position as founding contributors to Xai L3. The film gave the studio's relationship with the network a human history and a shared starting point for explaining the project.
Read reportWhile waiting for Final Form's next steps, players were also trying to understand how Xai and Arbitrum One would divide the work. The official explanation was plain: Xai was not competing on total value locked; it wanted users and transaction counts. The conversation moved from the value of committing a single card to whether game actions and asset transfers would fit together.
Read reportThe group still had no explanation for why a full DAG set's listings had been invisible on the market page the day before. One player withdrew his DAG listing and chose to wait for clarity. The withdrawal turned the previous day's question into a real cost of waiting: the seller gave up a chance to sell for now but kept room to reconsider.
Read reportFinal Form's DAG cards were still circulating on the market, and players used listings to judge whether they could buy or sell. He raised the question in the group. The incident showed cardholders how much they still needed to check between what a market page displayed and the status of their assets.
Read reportFinal Form players were still learning how to commit cards and claim Chromos. The official advice was to keep at least 0.2 SOL in the wallet before committing cards or claiming Chromos. That gave players a concrete first step when troubleshooting.
Read reportDownloading, committing cards and getting Final Form to run were still the group's most immediate concerns, but the name LAMO had stirred curiosity. Someone asked when LAMO would be playable. LAMO remained an expectation without details.
Read reportFinal Form players had moved from card previews to their experience of using the game. Some praised the interface and audio; others said their laptops could not run the game well and that the Solana side sometimes stalled. The feedback put two problems in view.
Read reportAs August began, Final Form was using new cards to hold players' interest while practical questions about committing cards remained. The official preview introduced Arvandus, half human and half Xalorian. Arvandus added a wounded character to the game's world and exposed the distance between promotion and use: players were willing to follow a new card's story, but needed clear download instructions to proceed with their cards.
Read reportJuly was ending after days of discussion about node names, rewards and player documentation. BTC closed the month at USD 29,200. The freeze gave the team a common draft.
Read reportThe Xai community was still absorbing the order of testnet deployment and card bridging when weekend industry news interrupted the discussion. Curve's theft made for an alarming weekend in DeFi. The incident did not change Xai's deployment sequence, but it made players' questions more specific.
Read reportOver the weekend, Final Form players wanted to know when their cards could leave Solana, while those preparing Xai's testnet were still arranging its deployment. The official explanation was that the testnet would be deployed soon. The explanation gave the wait a sequence: testnet deployment, then a running mainnet, then batched card bridging.
Read reportXai's testnet was still being prepared. The stress test showed stable performance with transactions running concurrently at the tens of thousands level, and the gasless route met its target. The team now had a load test result it could build on, shifting its discussion from whether the route could bear the load to whether people could understand how to use it.
Read reportWork on the node documentation was underway, but the community was still asking questions using broad words such as “node” and “key.” The sentinel node's name was formally settled as Sentry Node, and its key was named Sentry Key. Shared names gave the team and community the same concepts to point to and made the order of operations easier to explain.
Read reportThe node documentation week had just begun when macroeconomic news drew part of the community's attention away. The FOMC raised rates by another 25 basis points, and markets reacted calmly. A calm market did not settle the path of future rates; the idea of an endpoint remained a possibility.
Read reportThe node model was finalized, and A-Zhen had moved to help with node software, but ordinary players still lacked instructions they could follow step by step. The week devoted to writing node documentation began with a clear goal: ordinary players should be able to understand it. The writing task shifted from collecting design material to checking whether a player could make sense of it.
Read reportExcitement over the XRP ruling had lifted market sentiment, but the Xai community was still waiting for testnet and node information. BTC slipped back to USD 29,000, and the XRP rally faded. As the rally faded, the group's tone cooled and concrete unresolved questions regained space.
Read reportWith the node economic model settled, the team was moving from broad design to details for later implementation. The second version of the attention challenge protocol passed review, and the referee contract design was frozen. The protocol and contract design now had a stable version, so later writing and implementation would no longer have to guess at the same definitions.
Read reportThe node model had been finalized, and A-Zhen was helping with node software in the hope that newcomers could install it smoothly. He asked the official team about node hardware requirements ahead of time, hoping to judge whether he should prepare his equipment. The inquiry produced no specification sheet, but it turned the community's broad worry about whether a node would run into questions that could be answered.
Read reportEx Populus had just been formally introduced as the first developer to deploy a game on Xai, with Final Form as its first game. BTC traded sideways near USD 30,000 on shrinking volume, a familiar summer lull. The market could not answer the launch question, but the wait brought a difference in priorities into view: some cared about price, while others wanted to know how they could take part.
Read reportXai had explained its direction as a gaming chain, but the community was still waiting for a network it could try. An official video formally introduced Ex Populus for the first time as the first developer set to deploy games on Xai, with Final Form positioned as the chain's first game. Players could now connect the roles of Final Form, Ex Populus, and Xai, and discussion shifted from who was building the game to when they could try it.
Read reportThe node model now had rules, but the software still had to work for players unfamiliar with onchain procedures. A-Zhen took on the node software's onboarding problem, aiming to let a beginner finish installation in ten minutes. Node work moved beyond model discussions toward ease of use.
Read reportWith esXAI chosen as the vehicle for node rewards, the team next had to explain what recipients could do with it. An internal review settled three principles for esXAI: soulbinding, a discount on redemption, and deflation through burning. The reward design became a mechanism with boundaries rather than just a name, giving the writers of node materials conditions they had to explain.
Read reportXai's node plan was still being designed, and the team needed to explain how home computers could participate and how rewards would be allocated. The node economic model was finalized: an online lottery with staking based weighting, using esXAI as the reward vehicle. Work on nodes shifted from choosing a model to implementing its details, though the team still needed to explain online participation and weighting clearly to players.
Read reportThe community had just spent a weekend discussing the shared name, and search had become crowded too. The search index for Xai surged, but roughly half the interest came from people looking for Musk. The team saw both wider exposure and the people who had arrived by mistake.
Read reportAfter several days of talk about the shared name, the weekend community was more inclined to joke about it. A popular thread titled “What is it like to share a name with Musk?” The lively thread brought the naming issue into everyday community conversation and showed how a newcomer might follow search results to the wrong place.
Read reportExcitement over xAI's announcement still filled the community chat, but the Xai team faced a quieter question: could the two names confuse people later? Legal counsel left an internal memo calling for continued observation of xAI and no action for the time being. The team now had a basis for handling the naming question instead of improvising an answer whenever it came up in chat.
Read reportThe community had spent the previous night debating the consequences of Xai and xAI sharing a name, and many had no clear answer. XRP won a partial victory in the court ruling, the market erupted in celebration, and BTC climbed to USD 31,800. The ruling and the price move changed the day’s conversation, but settled nothing about the naming issue.
Read reportIt had been less than a month since Xai announced its gaming chain. That afternoon, Musk announced the creation of the artificial intelligence company xAI in a post that drew more than 59 million views; technology media around the world followed up overnight. Inside the company, work moved at two speeds.
Read reportQuestions about the previous day’s supply change were still circulating: if the rules could change, who would decide the next change? BTC moved sideways near USD 30,500, and the market was quiet. The explanation set a boundary around the previous day’s dispute.
Read reportCard evolution moved from lower to higher tiers, and collectors had arranged their holdings around the previous supply limits. The team changed card supply, lowering the total for each set while raising the legendary-tier allocation to leave room for epic cards to evolve. The revised allocation addressed a design bottleneck at the legendary cap, but it also made players more concerned about how clearly rule changes would be explained in advance.
Read reportPlayers were collecting Final Form cards while calculating the Chromos needed for evolution. The team explained that players could currently extract Chromos by staking cards. The two paths to Chromos were now distinct, prompting players to weigh today’s extraction against the future need to win matches.
Read reportThe announcement had brought many newcomers, and questions about the testnet, nodes, and Final Form crowded into the same chat. The Night Watchman organized the first community voice AMA. The voice session brought scattered concerns into one conversation for the first time.
Read reportAfter Xai’s announcement, players knew Final Form was expected to enter public beta in December, but had yet to see how a full match would run onchain. Final Form released a development log for its battle system. The log gave players something specific to discuss.
Read reportXai's chain and card play had been described as a vision, but players still wanted to know when they could actually play Final Form. BTC rose above USD 31,000 to a new high for the year, then fell back. Players had a month to refer to and knew that the team was also building a game library, making their wait more concrete.
Read reportThe chain team's hardening work after the announcement had reached the audit stage. The security audit formally began, and the repository was frozen for it. The freeze gave the audit a fixed starting point and made ad hoc changes harder to merge.
Read reportThe Independence Day holiday left markets quiet, but newcomers interested in Final Form cards often stalled at the Solana wallet step. They published a ten-minute starter guide that walked players unfamiliar with Solana through creating a wallet and buying their first Final Form card. The guide gave newcomers a sequence they could follow, while the bridge preview created a choice between getting a card now and waiting for a clearer route across.
Read reportAfter Xai's announcement, the chain team was turning an internal prototype for running a node on a home computer into a design it could debate. The first closed meeting on the node economic model asked how home computers could play a useful part. The meeting turned the node from a technical possibility shown in a demo into a product question about costs and incentives.
Read reportOn the first July weekend after Xai's announcement, the number of community newcomers had passed 10,000. Administrators called for volunteers. Passing 10,000 newcomers turned casual replies into a recurring task that required people to share the work.
Read reportJuly began with Xai preparing for a public testnet. Officials posted a single question on Twitter, asking the community to vote on whether it wanted a testnet with rewards. The question brought access to testing and rewards into the same conversation, while showing that the voting channel did not work for everyone.
Read reportAs June drew to a close, Xai had been announced and its trademark put into commercial use, while the team worked toward mainnet. BTC closed at USD 30,400. The announcement and trademark launch closed out the first half's work, with mainnet still ahead.
Read reportAfter Xai’s announcement, the business team received inbound messages from game teams. The business team sorted the leads and confirmed that dozens of game teams were in contact. Attention from the announcement had become concrete questions to handle one by one, but contact was still only contact.
Read reportThe public testnet was still being prepared, and A-Zhen and her colleagues on the chain team were exploring how ordinary people might eventually take part in the network. A-Zhen demonstrated the home-computer node prototype, and the room applauded. A way for home users to participate, previously only an idea, now had a form the team could discuss.
Read reportThe community was still learning whether it could trust Xai’s official voice after the announcement. The official account apologized publicly that day. The apology clarified the official intention, but it could not decide for the audience whether the tone was appropriate.
Read reportAfter the announcement, the community wanted to understand Xai’s technical relationship with Arbitrum and kept asking when a token might arrive. The live conversation with Arbitrum took place that evening, and the official account posted the recording afterward. The recording let people who missed the live session check the technical discussion.
Read reportBTC held above USD 30,000, but attention in the community turned to Final Form cards. Someone worked through the evolution rule: burn four lower-tier cards to make one higher-tier card. The group was asking more than how to get cards quickly.
Read reportXai had just been introduced as a chain for games. On the show, the narrator discussed account abstraction, higher smart contract limits, and extremely low fees. The console metaphor now had technical details people could question.
Read reportAfter Xai’s announcement, A-Zhen and her colleagues working on the chain turned from public explanations back to engineering plans. The chain team began its post-announcement hardening work and fixed the schedule for a security audit. The announcement had allowed the team to describe its aims; now each feature had to fit into a concrete review sequence.
Read reportThe quest contest was drawing new players toward the cards, but they did not yet understand where Chromos came from now or how it would be earned later. The official account brought back a version tested on Solana in 2022 and still playable: stake cards to refine Chromos, then evolve cards tier by tier to legendary status. The older version made the relationship between cards and Chromos more concrete and showed quest participants a choice they could make now; the full version's earning rules were still a plan for later.
Read reportWith the quest contest newly shortened, the chat was weighing how much time remained for tasks while also watching the market. BTC climbed back above USD 30,000, and BlackRock's name stirred a stronger reaction in the chat than other encouraging news. The market recovery made the chat livelier but did not settle how players should use their time.
Read reportThe quest contest had only just begun, and players were planning their tasks and leaderboard efforts around its original August 1 finish. The contest was abruptly shortened from six weeks to two, with July 3 as the new end date. The path from card rewards to Chromos was brought forward, but the shorter contest also left late arrivals less time to catch up.
Read reportAfter Xai's announcement, the community included longtime players eager to take part and newcomers who did not yet trust the project. The first post-announcement quest contest began: participants completed tasks to climb the leaderboard, and the top 20 would receive cards. The leaderboard gave people seeking cards a clear path, while putting reward rules and questions of trust into the same conversation.
Read reportBefore the announcement, A-Zhen, an engineer working on the chain, had been occupied with the demo environment and launch preparations. A-Zhen returned to her regular schedule and made the public testnet the next destination. The focus shifted from keeping the announcement-day demonstration stable to making independent trials possible for outside participants.
Read reportOn the first weekend after the announcement, newcomers were sorting through scattered messages, while longtime members kept explaining how Xai related to the games. Of his own accord, the Night Watchman wrote a long post collecting the announcement's main points: the chain's purpose, the parties involved, and the game plans already made public. The pinned post gave discussions a common starting point and temporarily made the Night Watchman an informal explainer.
Read reportXai had just been announced, and the foundation needed to explain its role to developers and players. The foundation published a lengthy explanation: it would recruit third-party developers, work on marketing, and provide funding. The explanation gave outsiders a sense of how the foundation intended to support games, while wallet verification gave cardholders something they could do immediately.
Read reportXai Foundation unveiled an Arbitrum-based layer-three network for games, supported by Offchain Labs and partnered with Ex Populus.
Read reportBackground: Two and a half years of planning, negotiations, and coding were about to be compressed into one press release. Today: Before dawn, the group received a cryptic preview: the server had changed, bigger news was coming, and members should explore the new layout. Impact and next steps: The release said nothing about a token, yet the group immediately asked whether the Ex Populus token had been dropped in favor of XAI.
Read reportBackground: The announcement was one night away. Today: The FOMC paused rate hikes. Impact and next steps: The economic news gave markets a moment to breathe, but A-Zhen’s anxiety came from work about to face public scrutiny.
Read reportBackground: The announcement was days away, and the team had decided not to rewrite its message around outside volatility. Today: CPI continued to ease, prompting talk that the rate-hiking cycle was nearing its end and giving the broader mood some warmth. Impact and next steps: Market discussion had a little more breathing room than in previous days, but project communications still rested on the approved material.
Read reportBackground: The announcement was close, and the release copy could no longer be changed, yet people involved in the launch might face different questions. Today: At the final all-hands meeting before the announcement, the team agreed to speak only about the chain and games. Impact and next steps: Each group knew where to start and which questions it could not answer on another group’s behalf.
Read reportBackground: Regulatory lawsuits had shaken the market, while the announcement team kept preparing on its existing schedule. Today: BTC traded weakly around USD 25,800, and regulatory lists frightened altcoin holders even more. Impact and next steps: The group’s anxiety did not vanish, but one guess was less likely to circulate as a decision.
Read reportBackground: The community was still waiting for official news over the weekend. Today: He posted that he had a feeling “something is happening next week.” Impact and next steps: The silence reminded him that a veteran member’s intuition could not answer questions for everyone else.
Read reportBackground: The announcement copy was locked, and the team had moved into external communications. Today: The advance briefing for the media session was complete, and the embargo agreements were signed. Impact and next steps: Reporters now had time to prepare, and the team had a shared publication boundary.
Read reportBackground: The materials had been through weekend review and two rehearsals, while external regulatory news made every sentence easier to overinterpret. Today: The final release copy was locked; no one could change even a punctuation mark. Impact and next steps: Publication and Q&A preparation could now use the same text, bringing the version disagreements caused by repeated edits to a halt for the moment.
Read reportBackground: After two consecutive days of regulatory lawsuits, the announcement had not been postponed. Today: The team carried out its second rehearsal as planned during the regulatory storm, keeping the pace of publication, question handoff, and response unchanged. Impact and next steps: The rehearsal showed that keeping the schedule did not mean every question could be answered at once.
Read reportBackground: The previous day's suit against Binance and CZ, along with BTC's sharp fall, had already made the announcement team feel that outside news was eclipsing the project. Today: The SEC sued Coinbase the next day, plunging the US crypto industry into one of its darkest weeks. Impact and next steps: The schedule held for now, but communication became harder.
Read reportBackground: The team was preparing answers for the approaching announcement, but external market news took over the community discussion first. Today: The SEC sued Binance and CZ, bringing thirteen charges, and BTC plunged to USD 25,700. Impact and next steps: Questions that had centered on the announcement began to mix with fears about the wider industry.
Read reportBackground: The announcement demo depended on a stable environment. Today: A-Zhen made a final backup of the demo environment and set up two machines in hot standby. Impact and next steps: The demo now had a backup path instead of depending on one machine, and the team set a boundary around last-minute changes.
Read reportBackground: The office was still preparing for the announcement over the weekend. Today: The team viewed the announcement materials on screens of different sizes and examined them pixel by pixel. Impact and next steps: The final review shifted the discussion from which image looked better to what readers could actually see.
Read reportBackground: With the announcement countdown underway, the legal team had assembled the trademark materials. Today: Commercial use of the XAI trademark in the United States formally began this month. Impact and next steps: What had been preparation for use now had a documented record of actual use.
Read reportJune was the planned month for the announcement. At the start of the month, BTC was trading on lighter volume around USD 27,000. The small disagreement clarified that a full explanation and reliable execution both mattered, and that the demonstration could not be casually changed so close to release.
Read reportMay was ending. At the end of May, BTC closed at USD 27,200 after moving sideways all month. Compared with the start of the month, the release process and materials now had a clear arrangement; for the community, the formal explanation still had not arrived.
Read reportAfter the first rehearsal, the team knew it could not search for files in the middle of releasing the statement, running the demonstration, and answering questions. Today, with sixteen days left until the announcement, all the materials were filed. Preparation moved from having made the materials to being able to select the right ones when needed.
Read reportThe team had completed its first rehearsal for the announcement and was still working through wording and likely questions during the freeze. Today a preliminary debt ceiling deal gave the market some relief. The easing of tension let the team return its attention to the release process it had rehearsed.
Read reportWhile the community waited for news, rumors in private messages and group chats traveled faster than official explanations. The next day, the official response did not promise to identify every scam. The conversation shifted from dwelling on the angry remark to checking before acting.
Read reportThe announcement had yet to arrive, and the community could see only scattered signs of preparation. Over the weekend, a rumor that “something big” would happen in June appeared in the group, but drew little attention. His response did not end the curiosity, but it kept the discussion within the bounds of speculation for now.
Read reportDuring the freeze before the announcement, the release and demonstration were being prepared on schedule. Today the documents needed for trademark registration were ready. Having the papers ready meant the team would not have to hunt for them at the last minute, but the date of first commercial use remained open.
Read reportBackground: The media list, translations, and attributed quote were falling into place, so announcement preparations were ready for a test of the process. Today: The team held its first announcement rehearsal, walking through the full sequence from releasing the statement to answering questions. Impact and next steps: The rehearsal turned an orderly plan on paper into actual handoffs and exposed details that needed consistent wording.
Read reportBackground: Announcement preparations continued, but the mood in the market outside the office was cooling. Today: BTC fell to USD 26,200, while the drawn-out dispute over the U.S. debt ceiling weighed on appetite for risk. Impact and next steps: The price drop made the coming announcement easier to misread, calling for more care with wording.
Read reportBackground: The announcement's positioning and media audience had been settled, but the named endorsement still awaited a final confirmation. Today: The endorsement quote completed the other party's internal approval process, with A.J. Impact and next steps: The quote now had approved attribution, settling one open point in the release.
Read reportBackground: The pre-announcement freeze was in its first week. Today: On Bitcoin Pizza Day, the office ordered pizza. Impact and next steps: The meal gave the tense team a short breather and clarified its priorities: the calm was worth celebrating, and the freeze still needed to hold.
Read reportBackground: Announcement preparations had moved from settling an internal draft to communicating it outside the office. Today: The team finalized the media list for announcement day and translated the release into three languages. Impact and next steps: The announcement now had a defined audience and language versions; it was becoming more than a document passed around the office.
Read reportBackground: On the weekend, the community was still talking about card mechanics and the games to come, while the formal announcement had yet to arrive. Today: The Night Watchman remarked that, after a year and a half of bear market, a project finally seemed to be building toward something big. Impact and next steps: His remark gave the quiet group a little energy, but reminded him how easily an excited comment from an old member could sound like a hint.
Read reportBackground: The announcement draft had gone through repeated internal revisions, and engineering work was reaching its own stopping point. Today: The remaining items were handled one by one until the list reached zero, and the project entered its pre-announcement freeze. Impact and next steps: The team moved from chasing old issues to protecting the version it had settled on.
Read reportBackground: The announcement was still being refined internally, and the game-chain plan had not been made public. Today: After looking over the quiet market conversation, someone in the office suggested making the announcement sound bolder. Impact and next steps: No outside attention arrived that day, but the discussion brought the team back to the questions readers would face on first seeing the announcement.
Read reportBackground: The announcement was undergoing line-by-line revision, and the choice of endorser also needed checking. Today: The team aligned announcement responsibilities with Offchain Labs and agreed that Offchain Labs would provide a named endorsement. Impact and next steps: With responsibilities assigned, the announcement had a clearer structure for describing support and a clearer boundary for review.
Read reportBackground: The announcement had a first draft and a settled scope: the chain and games. Today: Legal counsel checked the wording sentence by sentence. Impact and next steps: Review shifted from deciding what to say to checking how it could be said.
Read reportBackground: The team began turning its still-private game-chain plans into an announcement. Today: The first draft circulated internally, with 'decentralized gaming console' settled as its positioning. Impact and next steps: The draft now had a clear editorial boundary, giving reviewers a way to check its claims about positioning and game plans.
Read reportBackground: The internal testnet build had passed its smoke test, but outstanding issues remained. Today: She traced and fixed a memory leak over the weekend, joking that it was her 'gift for the announcement.' Impact and next steps: The fix removed one source of continuing resource use from internal testing.
Read reportBackground: Over the weekend, the Final Form group was still absorbing the previous day's lengthy rules. Today: The same sequence was explained again and again: stake a card, withdraw Chromos, then use it to evolve a limited card step by step. Impact and next steps: The group moved from repeating an announcement to helping newcomers think through their choices.
Read reportA product update detailed Final Form's deck-building, auto-battle, staking, Chromos rewards, and card-burning progression loop.
Read reportBackground: BTC fell back to USD 26,000 as the meme frenzy ebbed and the market quieted. Today: The team posted concept art of a card table alongside its fullest explanation of the rules that month. Impact and next steps: The explanation connected earning Chromos, winning with a deck, and burning cards to evolve them, but it did not settle cardholders' concerns.
Read reportBackground: Final Form’s early access led some players to think it had moved ahead of another game. Today: Someone asked outright whether Final Form was already further along than LAMOverse. Impact and next steps: That ordering checked the group’s speculation and gave future replies a clear boundary.
Read reportBackground: Markets were watching inflation data while the gaming community was still working out what early access did and did not offer. Today: CPI came in as expected, and BTC fluctuated around USD 27,000. Impact and next steps: The price gave the day a market reference point, but it did not tell players when they could play the full Final Form.
Read reportBackground: Early arrivals to Final Form were already exploring staking and card evolution, but the community could easily mistake an available interface for a nearly complete game. Today: Officials stated that Final Form was still in early access. Impact and next steps: The statement made the boundary of the current stage clearer and tied expectations to functions actually available.
Read reportBackground: The studio was still working through issues left from testing, while the community kept seeing news of Bitcoin congestion. Today: Bitcoin became congested enough for an exchange to suspend withdrawals, bringing scaling back to the center of discussion. Impact and next steps: The discussion cleared no network congestion, but it showed the team how much explanation lay ahead.
Read reportBackground: Players could already stake cards, extract Chromos, and evolve their cards, but the burning step gave holders pause. Today: Someone worried that a burned card could never return. Impact and next steps: The explanation clarified how scarcity would arise, but it did not choose which card any holder should burn.
Read reportBackground: Over the weekend, the community’s discussion about getting cards into the game was interrupted by news of Bitcoin congestion. Today: BRC-20 inscriptions drove Bitcoin fees sharply higher, drawing complaints across the network. Impact and next steps: The fee surge did not solve the players’ login limitation, but it exposed steps hidden in the simple instruction to move the cards.
Read reportBackground: PEPE reached a major exchange, and meme trading dominated the group’s conversation. Today: Amid the excitement, the Night Watchman said that money was not his and he did not envy those making it. Impact and next steps: The discussion returned from market excitement to the cards players held, but the display did not explain why those eleven included no legendary card.
Read reportBackground: Final Form players were already weighing whether to keep, stake, or burn ordinary cards, so the ordinary edition of Iron Pigeons was more than a name to them. Today: Someone asked whether issuance of the ordinary edition would depend on how many cards were burned, how many would be issued in total, and what conditions would govern distribution. Impact and next steps: Players wanted those answers to decide what to do with their cards.
Read reportBackground: May's integration work continued, while community members kept looking for hints about the project in market news. Today: The FOMC raised rates by 25 basis points and signaled a possible pause in further increases; BTC barely moved. Impact and next steps: The market showed little movement after the news, but the community's wait did not grow shorter.
Read reportBackground: After the internal build passed its smoke test, seventeen outstanding issues became the working list ahead of the May demonstration. Today: The outstanding list fell from seventeen items to nine. Impact and next steps: The lower count showed that the team had cleared a set of identifiable obstacles.
Read reportBackground: The chain team had an internal demonstration target for May, and the game team was waiting for another integration round. Today: BTC was around USD 28,500, while the noise around meme coins drowned out discussion of games. Impact and next steps: The two rhythms became tangible: outside, attention followed fleeting topics; inside, game requests still had to connect with chain responses.
Read reportBackground: As April ended, the team was working toward an internal demonstration in May. Today: BTC closed April at USD 29,400, and the internal testnet build advanced to v0.9. Impact and next steps: v0.9 gave the team a shared internal build to refer to, so discussions need not be about different versions.
Read reportBackground: The project had not been announced publicly, but the community was already guessing how the games and a chain might connect. Today: A vague tip that “a game chain is coming to Arbitrum” circulated in the group, with no solid confirmation. Impact and next steps: The speculation gave waiting players something to discuss, but it also made answers more likely to sound like promises.
Read reportBackground: The chain and game teams were integrating their work for an internal demonstration in May. Today: The internal build passed its smoke test, showing that the planned basic flow could run. Impact and next steps: The team had been trying to establish whether the build could run end to end; now it could set a repair order for known issues.
Read reportThe previous day's staking guidance had players reconsidering what to do with their pigeons. Fresh trouble at US regional banks made headlines, and BTC swung back and forth. Players began addressing a practical barrier to entering the game.
Read reportFinal Form was still in its early experience phase. Officials published a new staking process: players could stake cards to draw Chromos, then use Chromos to evolve those cards to higher rarities. The easier period for obtaining Chromos now had a stated endpoint, though no date to count down to.
Read reportWith the foundation established, development of the chain and preparations for public communication were moving forward together. The team and Offchain Labs agreed on the main terms of a cooperation framework covering three areas of support: infrastructure, marketing, and product. The cooperation now had a shared framework, so the team no longer had to begin every discussion by defining its scope.
Read reportA public test of Final Form had been announced, and its cards and evolution mechanics were drawing newcomers. More people pressed for a launch time. Players now knew the order of the test version and the launch, but could not plan around a firm date.
Read reportThe foundation's registration was complete, and work on the chain's development network continued. The first draft of the announcement was scheduled for mid-May, with legal review of its wording underway at the same time. Public communication now had a dated writing schedule, but a deadline for the draft was not a publication date.
Read reportThe weekend group chat was still circling around the market, while the chain and game teams were working toward an internal demonstration. A-Zhen told the group, “The louder the market gets, the more we need to write code.” Her remark gave the weekend discussion a practical boundary: people could talk about the market, but development concerns needed concrete steps.
Read reportThe chain team was working toward an internal testnet version it could demonstrate in May. BTC fell below USD 28,000, hurting leveraged long positions. The team kept its attention on the work needed for a demonstrable version and did not adjust its plans in response to the market move.
Read reportBackground: The chain and game teams had spent the week working together, so problems were no longer explained only within separate teams. Today: At the engineering meeting, the team set a May goal: make the internal testnet build ready to demonstrate. Impact and next steps: “Keep developing” had become an internal demonstration requirement that could be assessed, giving both teams a basis for choosing what to tackle.
Read reportBackground: Players knew that staking cards could produce Chromos for evolution, but some were still weighing a cash sale against keeping their cards. Today: The meme coin PEPE surged and dominated attention, while BTC fell back to USD 29,000. Impact and next steps: A stated purpose let players weigh immediate cash needs against the possibility of evolving cards later, instead of deciding solely amid PEPE's excitement.
Read reportBackground: Final Form had just set out a waiting period for its public test. Today: BTC rose to USD 30,600 and then retreated. Impact and next steps: The reversal made the difference in pace between immediate price moves and slower game preparation more visible.
Read reportThe project outlined a burn-based progression from more than 111,000 distributed pigeon cards toward a terminal supply of 800 legendary cards.
Read reportBackground: Final Form's cards had made players familiar with evolution and burning, but newcomers kept asking when the public test would begin. Today: The official team announced a countdown to Final Form's public test, describing it as “a few months away,” and opened another giveaway. Impact and next steps: The narrator drew the route from more than 100,000 cards to 800 legendary ones on paper and saw that the draw was not just the prize: players had to choose to destroy cards they already held.
Read reportBackground: A Final Form deck test had already passed through the chain interface, but the two teams still needed to compare what appeared in the game with what the development network recorded. Today: Joint integration week began, and the chain and game teams moved into one room. Impact and next steps: Problems that once required messages back and forth could now be reproduced and compared on the spot.
Read reportBackground: The foundation had just been registered, but the game chain had not been explained publicly. Today: Over the weekend, the Night Watchman asked in the group, “If there were a game chain, would you run a node?” Impact and next steps: The question showed him that interest in playing a game could not be counted as a commitment to run a node.
Read reportBackground: The foundation documents had been awaiting a final signature, while the chain team was still working on a development network. Today: Registration was completed, and the Xai Foundation formally came into existence. Impact and next steps: The unresolved question of the entity now had an answer, giving the team a common name around which to prepare its public account.
Read reportThe first response to the Shanghai upgrade had not matched the group's most urgent predictions of a sell-off, yet the argument continued. ETH rose above USD 2,000, disproving, in the immediate price action, the fear that opening withdrawals would trigger an instant plunge. The conversation shifted a little from choosing sides on price direction toward separating observation from prediction.
Read reportThe market had been waiting for Ethereum's Shanghai upgrade. The Shanghai upgrade was completed and staking withdrawals opened. A fear previously summed up in one phrase began to be discussed in terms of available actions and individual choices.
Read reportThe announcement draft was still being coordinated, while the community waited for clearer news about the game and chain work. BTC crossed USD 30,000 for the first time in a year, and social feeds grew lively. The price drew people back into the conversation, but it did not settle the publication date or the review of the announcement.
Read reportThe announcement outline had been opened for work, but the team still had to agree on what it would say, who would stand behind it and when it could go out. The Offchain Labs marketing team attended the regular meeting for the first time, and the two sides discussed how to coordinate the announcement. Questions that had been scattered across technical work and the draft announcement now had a place for joint discussion.
Read reportDiscord was quieter than usual on Easter, but the game instructions still had to make sense to internal testers. She fixed the typo, then read the passage aloud to a colleague on the game team. The quiet day moved the documentation a little closer to being usable by someone following it, rather than only by its author.
Read reportFinal Form was still being tested within the team, and changes to a deck could affect the interface between the game and the chain. The team tested a new deck internally, and for the first time the chain interface completed the whole run without an error. A trial that had previously been liable to stop at the interface now ran from start to finish, giving the game team a procedure it could repeat.
Read reportIt was Good Friday, and US stock markets were closed. Crypto trading continued, as did work on the chain. The team treated the open market as no reason to demand an answer from everyone that day.
Read reportThe foundation paperwork was nearing its final signature, and the chain project's public story needed to move from internal discussion toward a draft. Work formally began on an outline for the announcement release, starting with three questions: what to say, who would endorse it, and when it should appear. Scattered verbal ideas became an outline that could be revised point by point, giving disagreements a place to land.
Read reportBTC's near-term direction was unclear, and community attention turned to the approaching Ethereum Shanghai upgrade. BTC moved sideways around USD 28,000 as the market waited for the Ethereum Shanghai upgrade. The conversation yielded a more manageable thread alongside the price bets: the team could prepare technical questions, but it could not know the market's reaction in advance.
Read reportThe previous day's art brief had helped players understand what Chromos was for, but the abstract rules still needed an image newcomers could recognize. An image of Chromos was posted for the first time: this was the thing fed to cards to bring about evolution. Chromos changed from an unfamiliar term into a recognizable game item, and discussion moved from “What is it?”
Read reportThe game community had encountered cards and staking, but many had only heard the name Chromos without understanding how it connected to evolution. They chose Chromos as the subject: staking cards in the game produces this substance; more staked cards and higher rarity mean greater daily output. Information previously scattered across explanations of staking and evolution now had a shared subject players could discuss.
Read reportOver the weekend, the community was still absorbing March's market moves and airdrop excitement. Someone steered the conversation toward the second-quarter market, asking how long the excitement might last and whether the game team would make use of it. The group shifted from betting on the market to asking why a game needed a chain, a more concrete question than a slogan.
Read reportAs April began, the team was still preparing an unannounced chain project; neither the public wording nor the release date had been settled. BTC steadied around USD 28,500. The rumor showed the team that outsiders were already piecing together clues, making the choice of words more urgent.
Read reportAs March drew to a close, Ex Populus was preparing its game and chain work in parallel. BTC closed at USD 28,500, up roughly 70 percent for the first quarter; the foundation documents needed only a final signature. The market gave people a reason to talk about the future, but the player's choice brought the discussion back to costs: what evolution consumes and what waiting demands.
Read reportNews of the CFTC lawsuit against Binance was still working through the market. BTC fluctuated around USD 28,000 as the market continued to absorb the regulatory news. The price gave the team no direction for its month-end work, but it became clearer which questions could be answered immediately and which needed checking.
Read reportThe ARB airdrop had sharpened the team's interest in how the Arbitrum stack performed in practice and prompted another look at chain arrangements for its games. An evaluation of a plan to migrate Iron Pigeons to Arbitrum began. The project moved from general talk about Arbitrum to examining a specific path for Iron Pigeons.
Read reportThe team was advancing a partnership arrangement that had not yet been announced while also revising community levels. The main substance of the partnership terms was agreed, with the remaining details moving through legal review. On the partnership side, agreeing on the main terms left legal details before anything could be finalized.
Read reportThe excitement from the ARB airdrop had not entirely faded. The CFTC sued Binance, another heavy regulatory blow, and the market seemed weary of bad news. Regulatory uncertainty now sat beside the brief lift from the airdrop.
Read reportThe development network was in a phase of bug fixes and documentation. A-Zhen organized the observations from that high-load day and wrote an internal report. Until then, her observations had lived on her screen and in conversations.
Read reportOn the weekend after the airdrop, the community was still talking about ARB. The Night Watchman called ARB a “bear-market allowance” and left his holdings untouched. His decision was his alone, but it gave the weekend conversation another thread.
Read reportThe ARB airdrop was still drawing attention. Projects across the Arbitrum ecosystem drew attention, and the team felt some of that warmth. The airdrop had lifted morale the day before, but the continuing attention called for more careful language.
Read reportBackground: Before the Arbitrum airdrop, the group had been checking eligibility, and traffic in anticipation of the event had already congested the bridge. Today: The ARB airdrop went live. Impact and next steps: Night Watchman received ARB and shared a screenshot in the group.
Read reportBackground: The ARB airdrop was due tomorrow, and community members who had spent days studying eligibility were preparing to claim. Today: People preparing for the airdrop crowded the chain, and the bridge became congested. Impact and next steps: The airdrop had not begun, yet congestion had already put the assumption of smooth use under pressure.
Read reportBackground: After the feature freeze, the development network was still being tested internally, and the minimal node prototype A-Zhen maintained required someone to watch it. Today: A-Zhen added block production monitoring alerts to the node prototype. Impact and next steps: The prototype no longer depended entirely on her watching it overnight; alerts could now draw attention to anomalies, leaving her waking hours for bug fixes and documentation.
Read reportBackground: The development network was in its bug fixing and documentation phase, while the foundation papers were final but still awaited signatures and submission. Today: The meeting tentatively set the announcement window for midyear. Impact and next steps: The team now had a time frame for its work instead of a vague expectation, though it was only an initial window, not an announcement already made.
Read reportBackground: Airdrop eligibility was still being discussed in the group, while the market had swung sharply away from the fear of the banking crisis. Today: BTC touched USD 28,000, and someone in the chat asked, “Is this still a bear market?” Impact and next steps: The argument remained open, but the group drew a useful boundary: sentiment could recover while eligibility still required checking each condition.
Read reportBackground: Over the weekend, the group’s conversation shifted from the banking turmoil to the Arbitrum airdrop. Today: He guided members through Arbitrum airdrop eligibility, and the group felt lively for the first time in a while. Impact and next steps: The discussion brought quiet members back into the conversation and exposed a habit of treating personal experience as a promise.
Read reportBackground: The development network had just entered a feature freeze, and A-Zhen’s chain team was fixing bugs and filling gaps in the documentation. Today: BTC reached USD 27,000, seeming to push through another layer of the bear market’s ceiling. Impact and next steps: The debate gave the group’s excitement a practical outlet and showed the developers which explanations the community needed most.
Read reportBackground: The internal development network had just entered its bug fixing and documentation period, while another line of preparation was reaching the end of its drafting stage. Today: The foundation documents were finalized, with signatures and submission still outstanding. Impact and next steps: After repeated revisions, there was finally a version ready for signatures; preparation shifted from editing text to completing procedures.
Read reportBackground: Since setting the March goal in late February, the chain team had been moving the internal development network toward a feature freeze. Today: Features on the development network were formally frozen, and work shifted to bug fixing and documentation. Impact and next steps: The freeze shifted attention from adding functions to testing and explaining those already in place.
Read reportBackground: The weekend's banking scare had not fully faded, but markets had turned to inflation data. Today: CPI came in relatively mild, and BTC approached USD 26,000. Impact and next steps: The calmer atmosphere outside did not give the engineers more time.
Read reportBackground: The bank crisis had just shown the community that even a stablecoin could lose its peg. Today: BTC climbed back to USD 24,000, and “banks cannot be trusted; code can” became a refrain. Impact and next steps: The rebound changed fear in the channel to excitement, but it could not remove the team's unfinished weekend checks.
Read reportBackground: The day before, USDC had fallen to USD 0.88, the team was checking its banks account by account, and questions were piling up in Discord. Today: Regulators moved to protect Silicon Valley Bank depositors, and USDC returned to its peg. Impact and next steps: The return to peg relieved the immediate pressure from USDC's slide, but it did not erase two days of confused information.
Read reportBackground: On the weekend after Silicon Valley Bank was taken over, the team was still checking its funding arrangements. Today: USDC fell to USD 0.88. Impact and next steps: The review turned an abstract banking risk into questions that had to be answered account by account, but the team could not judge accounts it had yet to verify.
Read reportBackground: The team was approaching its March feature freeze for the internal development network, while the community was absorbing another run of bad market news. Today: As the news spread, discussion shifted from project progress to banking risk. Impact and next steps: Until now, the pressure had come mainly from markets; ordinary banking channels were now in question too.
Read reportBad news about banking access and successive price declines weighed on the community, while the game's and chain team's work still had to continue. BTC fell below USD 21,000, bringing fear back to the market. The contest gave players a way to make and discuss something from the game, extending the points-for-rewards route opened at the start of the month; it could not remove the market's fear.
Read reportThe previous day's decline had unsettled the community, while the team kept working on the development network and cooperation terms. Silvergate announced its liquidation, removing part of the crypto industry's banking access. Market anxiety had become concern about actual routes for funds, and community questions grew more specific.
Read reportThe development network was still moving toward its March feature freeze, while the community watched the market. Powell's congressional testimony struck a hawkish tone, and BTC fell back to USD 22,000. The price decline added anxiety to the community, but it did not itself change the team's development schedule.
Read reportTalks with Offchain Labs had moved from regular meetings to a clause-by-clause review, while the team was also busy with its March development-network target. They went through three kinds of support: infrastructure, marketing, and product. The discussion had moved beyond a general wish to cooperate and into the categories of support and how responsibilities were expressed, but the terms were not agreed.
Read reportFinal Form had a first version of its on-chain card asset data structure, and the development network was heading toward a feature freeze. The LAMOverse team came in to coordinate on the chain-side interfaces, and meeting rooms briefly became scarce. The chain team had previously been able to advance around its own implementation; now the game's intended use was part of the design discussion.
Read reportDiscord was quieter on the weekend, though the Night Watchman was still talking with community members. Someone posted an Arbitrum ecosystem map and asked, “Where is the next breakout?” The weekend exchange settled nothing about any project, but it showed the Night Watchman that the community needed a more specific question than “the next breakout.”
Read reportThe internal development network had run steadily for a month, and the engineering team was working toward a March feature freeze. A-Zhen began writing a minimal node software prototype and limited its first use to the team. Until now, the team had mainly gathered experience through the development network; they now had a path toward a node prototype people could run themselves.
Read reportBackground: The foundation charter had reached a second draft, but its governance provisions remained open. Today: Counsel returned comments on revisions to the foundation documents, bringing the exchanges to a fourth round. Impact and next steps: The fourth round moved the documents closer to a final text, while exposing choices that legal phrasing could not make for the team.
Read reportBackground: March opened with BTC at USD 23,500. Today: Starting today, the project allowed Crew3 points to be exchanged for rewards. Impact and next steps: Task points now had a defined path to rewards.
Read reportBackground: As February ended, the chain team needed to review the internal development network and set priorities for the planned March feature freeze. Today: BTC closed February at USD 23,100 and moved sideways. Impact and next steps: A month of operation gave the team a foundation for narrowing its work in March, but the feature freeze had not yet taken place.
Read reportBackground: The development network had been running, and the sequencer had met its stress-test target. Today: At an all-engineering meeting, the team set a March goal: freeze the features of the internal development network. Impact and next steps: Tasks that had been advancing separately now pointed toward the same deadline.
Read reportBackground: The foundation preparations had reached the drafting stage. Today: The second draft of the foundation charter was completed. Impact and next steps: The document had moved from an initial draft to one the team could review together, but governance responsibilities and authority remained unsettled.
Read reportBackground: Bear market nerves still hung over the weekend community after BTC had climbed and fallen back. Today: The Night Watchman said the best position in a bear market was “sleeping.” Impact and next steps: The chat found no answer about trading, but it made room for a more sustainable way to participate: members did not have to watch the market all night to show they were still around.
Read reportBackground: The Final Form team had accepted a draft of the game-side SDK. Today: The team produced the first version of a data structure for onchain card assets. Impact and next steps: The SDK discussion now had something concrete for the game team to examine.
Read reportBTC had touched USD 25,000 a few days earlier, bringing more market talk into the community. BTC lost the USD 25,000 level it had recently touched, and the market whipsawed both long and short positions. The earlier excitement quickly became anxiety, making it more useful to separate known development progress from price guesses.
Read reportA-Zhen had previously fixed a problem in which the sequencer lost blocks on restart, and the test environment had moved to a new cluster. The sequencer met the stress-test target. The result gave the team more confidence in the current setup and gave A-Zhen a rare light moment in her report.
Read reportThe Tuesday meetings with Offchain Labs had become a regular channel for engineering questions. At the meeting, the two sides began negotiating the terms clause by clause. The cooperation discussion had moved from broad principles to individual items, giving the next meeting concrete points to address.
Read reportInternal development still centered on the bridge, game interfaces, and chain stability, while the community saw market prices more readily. BTC touched USD 25,000, and altcoins also looked poised to move. The market gave the previously quiet discussion more voices, without completing any of the team's technical work.
Read reportThe cross-chain bridge's asset mapping plan was settled and testing had moved to its next stage. The bridge's first testnet transfer succeeded, and the group filled with rocket emojis. The bridge had previously rested on a design and tests of its separate parts; it now had one complete route that had worked on the testnet.
Read reportEx Populus's game preparations and the chain work were still proceeding internally, leaving the community with scattered clues. Someone started a guessing game in the group: “What is Ex Populus working on?” The quiet exchange exposed a useful distinction: community members were not all asking the same question.
Read reportThe Final Form team had given the game-side SDK draft an initial nod. An internal review approved the gas abstraction plan: players would not have to deal with gas fees directly, and an on-chain mechanism would cover them. The teams now had a shared plan for refining the interface, allowing the game team to keep designing the player flow.
Read reportThe chain's framework was taking shape, with bridge and sequencer tests still under way, but the team lacked a name it could put into documents and eventually use in public. Discussion converged on “Xai.” Compared with the whiteboard repeatedly filled and erased, the project now had a clearer naming direction and a shared term for engineering and writing discussions.
Read reportRecent regulatory news had pulled community discussion toward risk, while the engineers kept working through the bridge, sequencer, and game integration. BTC rose above USD 24,000, on-chain activity picked up, and the group's mood brightened. The mood was easier than it had been during the run of regulatory news, but no engineering check had been completed by the price move.
Read reportDiscord was particularly quiet on Valentine's Day, and outsiders still knew little about the chain team's progress. She gave the testnet a codename known only inside the team and asked testers to use it when identifying the environment they meant. The codename did not become a public name, but it gave internal discussions a clearer reference.
Read reportThe shutdown of Kraken's staking service was still being discussed, and the chain team was considering how assets would appear on the bridge. Paxos was ordered to stop issuing BUSD, another regulatory blow that made discussion of stablecoins more tense. The news did not directly rewrite the bridge under test, but it made technical compatibility and lasting reliance two separate questions.
Read reportThe sequencer's lost-block problem on restart had recently been fixed, and bridge testing had entered its second phase. She moved the test environment to the new cluster and ran the planned failure drill. The new cluster took over testing, allowing the engineers to move past repeated investigation of the old environment.
Read reportOn the weekend, the community was still digesting speculation about whether a chain was being built. The argument grew louder in the group. The industry dispute offered no answer for the internal chain design, but it reminded the community that technical choices would be felt during play.
Read reportThe bridge's asset mapping plan had just been finalized, while the chain team was still refining the sequencer and game integration. The engineers walked through the game-side SDK draft item by item, and the Final Form team gave its first nod. The two teams now had a draft they could examine together instead of discussing integration in separate terms.
Read reportBackground: Engineers were advancing bridge and sequencer work while the community watched a stream of US regulatory news. Today: Kraken reached a settlement with the SEC over its staking service and shut that service down, deepening the sense of regulatory uncertainty in the United States. Impact and next steps: The news widened the discussion from whether the technology could run to how a service should be described, but there was too little information to judge a future design.
Read reportBackground: The bridge was one of February's engineering priorities. Today: Bridge testing entered its second phase, and the team finalized the asset mapping scheme. Impact and next steps: The rules moved from a debatable draft to a reference for testing, giving bridge investigations a shared vocabulary.
Read reportBackground: The team had chosen Arbitrum One as its settlement chain, and its contact with Offchain Labs had moved beyond a single technical question and answer session. Today: The two sides made their regular meeting a standing Tuesday appointment. Impact and next steps: A fixed meeting time gave the cooperation talks a predictable place and reduced the need to restate the background each time.
Read reportBackground: Foundation documents had entered the law firm's process, but the name was still undecided. Today: The first chain naming session filled a whiteboard, then wiped it clean. Impact and next steps: The first discussion produced no official name, but made the disagreement concrete: the name had to hold the engineering purpose and be something players would actually say.
Read reportBackground: The development network's sequencer restart fault was still under investigation. Today: She spent the night tracing the restart sequence and fixed the missing block problem. Impact and next steps: The fix let testing move forward and shifted attention from locating the fault to checking that it would not recur.
Read reportBackground: The team had yet to announce its chain plans, but Discord players were already asking why these games needed another chain layer. Today: Over the weekend, he drew a diagram in the group to explain the difference between L2 and L3. Impact and next steps: The drawing gave players unfamiliar with chain architecture a place to begin asking questions, though it could not settle the team's eventual design.
Read reportBackground: February had just become a month of intensive work on the bridge and sequencer, and the engineers' time was already committed to development network faults. Today: US nonfarm payrolls came in far above expectations, and BTC fell back. Impact and next steps: Market doubts remained, but they did not reorder the day's work.
Read reportA first draft of the foundation’s registration papers had been completed, with the name field still blank at that point; legal counsel had argued that a foundation entity should lead the chain. The jurisdiction for registering the foundation was chosen, and the papers entered the law firm’s process. Compared with the earlier stage of studying possible structures, the foundation now had a defined route through the legal process.
Read reportAs January ended, the chain’s basic framework was in place, but the interfaces and validation needed for game integration were not yet worked through. February opened with BTC fluctuating around USD 23,000 and the market still unsure of the recovery. February’s focus was more specific than January’s work of building a framework: the team needed to put two core components through connected checks.
Read reportDuring January, the team chose Arbitrum One as the settlement base chain and began working through the interface with the game team. January closed with BTC above USD 23,000, up about 40 percent for the month; the chain’s basic framework had also taken shape. The market had shifted from the chill of early January toward optimism, and the internal question had moved from whether to build a chain to how its parts would connect.
Read reportThe chain team had placed the cross-chain bridge, sequencer, and gas abstraction on parallel tracks, while the game team waited for usable interfaces. Management reviewed the budget and questioned how each expense related to current development. The budget discussion turned a technical list into a set of choices: parallel work did not mean every track could receive resources at the same pace.
Read reportThe Final Form team wanted a clear chain-side interface, while engineering had to work out how assets would cross the bridge, how transactions would be sequenced, and how players could avoid paying gas fees directly. In her weekly report, A-Zhen listed three tracks running in parallel: the cross-chain bridge, the sequencer, and gas abstraction. The report turned the vague complaint that “the interface is undefined” into a set of questions the joint meeting could address.
Read reportThe studio was making games while a chain-side plan advanced internally, but the community had received no formal explanation. Over the weekend, someone asked in Discord, “Are you building a chain?” The silence preserved the boundary around an unfinished plan while leaving the person who asked with no answer.
Read reportThe Final Form team was still waiting for the chain-side interface to be defined, and the engineering and game teams had only begun working through their requirements together. BTC had risen nearly 40 percent during the month, and media outlets began declaring that the bottom was past. The rally made the pressure of time tangible, but it supplied no answer to the engineering questions.
Read reportBackground: The previous day, the game director had put controls and player expression before the audience. Today: The Final Form team complained that the chain-side interfaces were still undefined, so the two groups convened a joint meeting. Impact and next steps: The complaint moved from separate work areas into a shared discussion, where both sides could at least test chain assumptions against game flows.
Read reportBackground: The postponed LAMOverse Q&A was set for 9 a.m. Today: The Q&A began on schedule at nine. Impact and next steps: The narrator recorded those two developments side by side: the legal entity had draft paperwork but no name, while someone on the game side was working through the camera and controls in detail.
Read reportBackground: The second conversation with Offchain Labs had moved beyond technology to product and market matters, but the team still had no clear public wording for the relationship. Today: For the first time, someone inside the team used the phrase “the first Orbit chain in direct partnership.” Impact and next steps: The phrase gave the partnership discussion a recognizable direction while showing that the wording had to match actual arrangements.
Read reportBackground: In their first formal technical meeting, the team and Offchain Labs had discussed Orbit, an L3 architecture, and settlement on Arbitrum One. Today: Their second meeting widened from technology to market and product support, though discussing support did not amount to a commitment. Impact and next steps: The internal and community conversations now touched the same difficulty: how to describe an engineering plan as a product players could understand and question.
Read reportBackground: The settlement chain had just been chosen, but the game's needs for gas-free play, wallet abstraction, and large contracts still required repeated checks on the development network. Today: A-Zhen stress-tested the development network, and its throughput figure made people in the room laugh with relief for the first time. Impact and next steps: That laugh briefly eased the long architectural debate and gave the team confidence to keep testing.
Read reportBackground: Even in the bear market, the game community was watching for new uses of blockchains, while the team's immediate task was to make its own chain architecture workable. Today: Ordinals inscriptions were beginning to appear on Bitcoin, drawing discussion in a small circle of technically minded people. Impact and next steps: The exchange produced no product decision, but it exposed a communication problem for the Night Watchman.
Read reportBackground: The team had decided to build a chain for games, and A-Zhen and the other engineers were turning game requirements into an architecture. Today: At the engineering meeting, the team settled on Arbitrum One as the chain on which their chain would settle, ending the back-and-forth between candidates. Impact and next steps: The chain team now shared a settlement premise, allowing the next discussion to focus on concrete integration questions.
Read reportAfter the Q&A was postponed, the community needed a definite new time and wanted to know who would speak about LAMOverse. Genesis formally filed for bankruptcy protection, another shock in the chain of troubles around DCG. The previous day's open ended delay now had a firm date, and the community knew who would take its game questions.
Read reportAfter the town hall, community members were still asking about LAMO in the question area. The team postponed the scheduled Q&A until the following week, giving just one reason: the materials needed to be better prepared. The delay gave the team time to organize the questions and made those awaiting answers wait another round.
Read reportThe chain team could now check basic flows on a local development network, but the game team cared about what players would encounter when they entered a game. The game team added three requirements to the chain design: gasless play, wallet abstraction and large contracts. The design moved a step from “the chain runs” toward “players can use it smoothly,” but written requirements were not yet working features.
Read reportThe technical meeting a week earlier had covered Orbit, L3 and settlement to Arbitrum One; a local development network was also running. BTC reached USD 21,000. That consensus set the order of work without offering a shortcut through the technical problems.
Read reportAfter the town hall, Discord had returned to its quiet weekend rhythm. The Night Watchman spoke up on Discord: “Everyone still here is family.” His words warmed a quiet chat, but they also made him see that closeness could not take the place of a clear reply.
Read reportAt the start of the year, the studio was still planning a game chain amid a bear market, and the community had just heard its town hall account. BTC surged above USD 20,000 overnight, opening a crack in the bear market's gloom. The price move eased the mood while bringing pressure to explain the project sooner.
Read reportThe studio had decided to build a chain for games, and its technical group was studying the architecture. Legal counsel proposed that a foundation entity should lead the chain and asked the team to study the corresponding structure. The project document had defined what the studio wanted to build.
Read reportBackground: The first public conversation of the new year was at hand. Today: In the morning, the team opened a question area where people could write their questions and mark those they considered important. Impact and next steps: Questions collected in the announcement area became a live conversation, and the team could see who was willing to come and ask on a weekday morning.
Read reportBackground: With the town hall approaching, the community was still discussing which chain LAMO should use. Today: The official team promoted the poll about LAMO's chain again, this time from the game's own account so its followers could see it. Impact and next steps: Players had another way into the discussion, while the engineering team had a local environment it could operate directly.
Read reportBackground: After the technical meeting, the office had a direction for building its own chain. Today: Two announcements followed. Impact and next steps: A proposed meeting time became a firm appointment, and players gained a place to state their deployment preferences.
Read reportBackground: The proposed game chain had reached technical review. Today: In their first formal technical meeting with Offchain Labs, the two sides spent three hours at a whiteboard discussing the Orbit technology stack, an L3 architecture, and settlement to Arbitrum One. Impact and next steps: The technical discussion produced a framework for further questions, while the community gained a say in when the conversation would take place.
Read reportBackground: The new year had begun under bear market pressure, while the office prepared for a technical discussion with Offchain Labs. Today: BTC crossed USD 17,000, triggering short liquidations, yet no one in the office looked up at the chart. Impact and next steps: The market's brief relief made the day feel lighter, but unresolved architecture questions still set the team's priorities.
Read reportBackground: On a bear market weekend, Discord was quieter than usual. Today: He checked in as usual and found casual conversation nearly at a standstill. Impact and next steps: His presence did not end the quiet, but he stopped treating a lack of posts as a lack of interest.
Read reportBackground: Ex Populus had just committed to building a chain for games. Today: The team archived its list of public blockchains it had evaluated. Impact and next steps: The project now had a reasoned answer to why it could not simply adopt an existing public blockchain.
Read reportThe chain team had a project goal and research leaning toward Arbitrum, but still needed to discuss the reasons for its choice directly with the technical team. A formal technical meeting with Offchain Labs was scheduled for the following week, with an agenda spanning three pages. Putting the meeting on the calendar gave the group's internal assumptions a place to be examined, while the three-page agenda showed how much remained unresolved.
Read reportWith the project goal newly set, the studio was still pursuing its chain research at a cautious bear-market pace. BTC quietly rose above USD 16,800, and no one dared call it a rebound. The price brought a little motion to a subdued new year, but it did not answer how the team should build the chain.
Read reportBack at the studio after the holiday, the chain team needed to finish revising its project proposal. The proposal was finalized with a one-sentence goal: build their own chain for games. The document became a project direction rather than a record of exploration.
Read reportOn the last day of the holiday, A-Zhen, an engineer on the chain research team, was working through the technical choices. She kept reading the Arbitrum Nitro source code and filled 20 pages of notes. The 20 pages gave the group something more precise than a general technology preference to discuss, while reminding them that reading code was not the same as testing it in operation.
Read reportAs the new year began, Ex Populus had decided to explore building its own game chain, but the idea was still taking shape in a project proposal. BTC hovered around USD 16,600, the wreckage left by FTX was still being cleared, and no one dared make easy wishes for 2023. The third draft kept the research moving through the darkest stretch and put the disagreement on paper for the team to address.
Read reportNo matching reports.