The work
behind the LOL.

The verified Dodge engine and browser copy were kept in lockstep while normal coin flow was eased slightly, Coin Rush was made a little more distinct, Sluggish was softened, and Immunity became modestly more likely. Candle artwork is easier to read without enlarging the verified collision geometry.

The client also stops reapplying static candle cosmetics every frame. Sharing now makes the X handoff and return-to-verify step clearer, and the shared site shell gets another narrow-screen pass.

Separately, the public tokenomics endpoint was recovered from an obsolete cached snapshot and stale collection state so the page can rebuild from validated XRPL data instead of presenting legacy numbers.

Record: Live recovery + current patch review.

The new page explains what you will learn and what a completed lesson does for your profile. Short reading cards and one-question-at-a-time checks replace a long embedded list. The shared XRPLOL menu stays with you.

Learn & Earn is available from the main site menu and the profile’s Explore area. Wallet Brain no longer contains its lesson section, learning links or learning-tour steps. Its wallet tools and holder-access help remain.

The existing twelve lessons, server checks, once-only XP and saved completions are reused. No level curve, token prize or lesson reward was changed. This is a development update, not a Namecheap deployment.

Site cleanup, 11 October: the discontinued LOLcals community-reward program page and its menu links have been removed. The FAQ now states that the old program has ended, rather than promoting its enrollment rules or distribution schedule. LOLcals NFT ownership, eligible game characters, LOLcals Pass and earned progress are unchanged.

Record: Standalone Learn & Earn page, 11 Oct 2026; Owner-confirmed program retirement and site cleanup, 11 Oct 2026.

After a Dodge run, Main Menu now sits alongside Share on X, View My Profile & Collection, and Play Again. Returning to the menu does not start another run or spend a ticket. Unclaimed rewards and pending saves still get a warning before leaving.

Level costs are now about 20% higher across the shared profile, rounded up to whole XP. Earned XP and the amounts awarded by games, Wallet Brain, challenges and sharing are unchanged. The versioned transition preserves existing levels, progress already earned into the level, claimed items and usernames rather than taking rewards away.

All launch cosmetics are identified as Beta Season, including badges and carried-over items. Older ownership dates and reward IDs remain intact. Unearned or uncollected artwork stays shaded and grayscale, including enlarged item previews, until it is collected. The four Pass tabs now read Chapter 1, Chapter 2, Chapter 3 and Chapter 4, with their original 25-level ranges.

These are development-source changes for the Beta launch. Public deployment and production data checks remain separate; this entry is not a claim of live player payments.

Follow-up, 10 October: uncollected items now shade the full card, including its background and border, rather than only the artwork. The homepage motion button is removed while device motion preferences remain. How it works now uses three short steps with separate lines for each action, a Level 10 username note and brief sign-in and prize notices.

Follow-up, 10 October: the profile and game navigation now use the same transparent white XRPLOL wordmark as the homepage. The FAQ was rebuilt with short expandable answers, seven topics and a search across the current Beta Season features. It covers usernames, chapters, collections, Wallet Brain, game rewards and support without presenting old payout amounts or future Lounge plans as current promises.

Record: Beta Pass and run-menu revision, 10 Oct 2026; Homepage introduction and full-card lock correction, 10 Oct 2026; FAQ and shared-branding review, 10 Oct 2026.

The main controls now say Scan wallet and Scan options. Longer explanations live in expandable sections, while report tabs, detailed tables and important warnings about missing or provisional data stay available.

A first-visit invitation offers a short tap-through introduction. It points to the actual controls, can be skipped, and can be replayed from Quick tour. The walkthrough never connects a wallet, starts a scan or awards XP on its own.

Connected browser tests checked scan and lesson progress against local test profiles, including repeat-credit and account-switch safeguards. We also repaired a guide-loading startup race and updated the launcher to bring the matching Wallet Brain version into an unchanged local workspace. These are reviewed source changes, not a Namecheap release or a live-wallet accuracy certification.

Follow-up, 10 October: Wallet Brain now has 12 short guides, including the Ledger’s creators, tokens, payments, pools, NFTs, escrow, upgrades and dated adoption examples. Each adds a three-question check with first-completion XP. Source links distinguish Ripple business news from actual XRP Ledger use, and plans from launches.

The optional tutorial now explains shared Xaman sign-in and free versus 250,000-XRPLOL holder access. The comparison reads the server’s configured limits. Lessons stay readable without holdings, and sign-in saves eligible learning XP. Holding is not a payment or token lock. The matched app and profile services were tested with local identities; this is not a Namecheap deployment.

Record: Wallet Brain UI and connected-profile review, 10 Oct 2026; Ledger learning and holder walkthrough, 10 Oct 2026.

We tightened the name presentation so the chosen Level 10 username is used by the account header, the Dodge screen and its scoreboards, and the highest-level LOLcals Pass board. The wallet remains the underlying identity; privacy choices and earned progress stay intact.

The new launcher starts both product servers and links scan and lesson events to a locally saved sample profile. An explicit sample report mode supports repeatable tests; a separate read-only public-ledger mode is available for inspecting wallets. Neither mode signs in a real wallet or enables payments.

Record: 10 October 2026 connected-experience implementation and test record.

The staged Dodge clip now starts muted when its card is in view, while the Wallet Brain card reuses the original layered artwork and animation. Both cards share a square footprint. Reduced-motion preferences and a shared pause control are respected.

A branded pregame counter panel sits beside Dodge. Pressing Play replaces it with a loading curtain while the playfield centers; the game keeps its original logical dimensions and server-run checks. Recorded paid rewards are separated from pending rewards instead of silently counting both as paid.

Community contact now leads to the approved XRPLOLMEME Telegram group, with a separate private @OfficialXRPLOL option. Support forms prepare a copyable draft locally rather than pretending a mail app sent a ticket. These are development changes, not a public deployment.

Follow-up, 10 October: we corrected the homepage gameplay recording so coins and the power-up enter from above the frame instead of appearing halfway down. Coins use the normal spawn cadence and fall speeds; actual overlaps collect them and missed coins leave through the bottom. Frame-by-frame checks cover spawning, continuous motion, contact, cleanup and keeping Jack clear of the boss. This remains a scripted demonstration, not a claim of player earnings.

A second 10 October preview pass fixes Jack’s facing direction using the game’s own turning logic. The game and statistics now occupy equal desktop panels; the counter is more compact, and local test figures are identified beside the heading. Real hosted totals depend on the running game backend and its preserved payout records, not merely uploading the page. Mobile panels retain equal widths and flow without clipping.

Follow-up, 10 October: the Dodge page and end-of-run recap now release the game’s scrolling controls outside play. The recap scrolls as one panel with wheel, trackpad, keyboard or touch, and opens with the final score above the progress card instead of repeated server-verification and shadow-mode diagnostics. Required claim, pending-payout and error messages remain available below the card. This is a user-interface correction, not a change to verification, XP or payments.

Record: 10 October 2026 connected-experience implementation and test record; Gameplay-preview trajectory correction, 10 Oct 2026; Facing and balanced lobby correction, 10 Oct 2026; Dodge scrolling and recap presentation correction, 10 Oct 2026.

The owner uploaded the installed changes, including the homepage, dev log, branding, public payout-wallet correction and username safety work. Source checks and browser review ran before the main checkpoint was created.

This preserves the work and its history in GitHub rather than requiring a chain of downloaded patches. Namecheap was not deployed and paid renaming was not activated. The separate Wallet Brain source and remaining live-release checks remain explicit.

Record: 10 October 2026 platform main checkpoint and GitHub review.

We added a read-only collector that checks one validated ledger, then builds the figures and chart from the same snapshot. Loading, unavailable and stale states are distinct: a failed request should not quietly become a zero balance.

The local Windows preview completed its first public snapshot. A follow-up patch corrects the displayed game-payout wallet and rejects an old-wallet cache instead of relabelling old balances. This records preview and correction work, not a production deployment.

Record: Launch-polish review, 9 Oct 2026; Owner's local preview review, 9 Oct 2026; Payout-wallet correction handoff, 9 Oct 2026.

This review brings together the XRPLOL wordmark, the original Wallet Brain hero, a short profile explainer, and a cleaner path into the Pass. An oversized frog flash during profile navigation was addressed at the initial-page styling stage.

The replacement Dodge clip is a staged recording of the game renderer, with coins, a Magnet and visible boss avoidance. The end-screen update offers Share on X, View My Profile & Collection, and Play Again, while retaining necessary save and reward feedback. The owner reviewed the local site; this is not a live-release claim.

Record: Launch-polish review, 9 Oct 2026; Owner's local preview review, 9 Oct 2026.

We prepared tighter public-file handling, clearer privacy and account controls, and policy/support pages that fit the rest of the site. The work also reviewed third-party scripts and the boundary between public content and private application state.

This is engineering and policy-draft work, not a legal certification or a claim that every launch check is finished. Real-host acceptance remains separate from local and automated tests.

Record: Privacy and security review notes.

Availability and reservation are checked on the server. Different capitalisation does not create a second claim to the same name, and simultaneous requests must leave just one owner.

The review includes persistence, conflicts, retries and account-switch checks. Preview names are temporary sample data, not reservations on the public site; the feature does not change XP or equipped cosmetics.

Record: Level 10 username implementation record.

The collection view brings owned items together instead of sending players through several overlapping menus. Reward details explain what an item is and how it is earned; equipping remains a deliberate action.

The profile already shows key stats, so navigation no longer needs to repeat the same choices everywhere. Existing collection ownership, keyboard access and mobile layouts were included in the recorded review.

Record: Profile navigation implementation record.

The reward reveal distinguishes collecting an item from equipping it. Players can inspect a reward, collect it and explicitly choose to wear or feature it without a silent loadout change.

Retry handling and duplicate claims were part of the pass. Match sharing uses the recorded result rather than a browser-invented score, and test cards are kept distinct from real player receipts.

Record: Post-run review notes.

The fix reconnects cosmetic loading to the shared account state. Returning from Customize refreshes the selection, while logout or an invalid account still falls back safely.

The important change was testing the ordinary profile-to-game journey, not just rendering a texture in isolation. The work leaves physics, hitboxes, scores and payout rules alone.

Record: Equipped-candle repair notes.

The visual goal is a progression you can actually see: restrained early rewards, more layered mid-tier pieces, and distinctive high-level artwork. The original character and game assets stay recognizable rather than being replaced with unrelated designs.

The recorded checks cover collecting, equipping, locked rewards, account isolation, small badge sizes and reduced-motion presentation. These are tested review assets, not a newly announced public season.

Record: Prestige collection handoff.

The signed-in account is the actor, even when Wallet Brain scans somebody else’s public wallet. Profile rewards continue through the same server-owned progression system rather than a second browser-side XP counter.

The pass also addressed logout, expired sessions, stale responses and restart behaviour. A paired sample journey exercises the actual services with test identities; real Xaman, host and payment acceptance are separate work.

Record: Shared-session implementation, 5 Oct 2026.

The 100-level Pass is organized into smaller chapters instead of overwhelming new players with every distant unlock at once. Banners, borders, badges and coloured candles are treated as different rewards, not interchangeable icons.

Balance and layout were tuned through local review. XP settings continued to evolve after this pass, so this entry is a record of the work rather than a promise of today’s exact progression numbers.

Record: September rebuild checkpoints; Profile launch plan and review branches.

The review produced narrow fixes for directory-flush compatibility and one-use login proof consumption, with race and failure cases added to the test coverage. File-content synchronization and locking were retained.

We also clarified which command starts the website, which starts Wallet Brain, and which preview uses samples. Simulated platform checks were not presented as proof of native-device or production durability.

Record: Windows storage repair checkpoint, 29 Sep 2026; September rebuild checkpoints.

The topics cover XRP basics, consensus and safe transactions. Reading and retrying are part of the learning flow; a completed guide can contribute to the same wallet-linked profile.

The reward path distinguishes an accepted answer, queued delivery and confirmed profile credit. Replaying a submission must not award the same lesson repeatedly. Sharing work was also kept separate from merely opening a social button.

Record: XRPL-guide code checkpoint, 26 Sep 2026; Learning and sharing implementation notes.

Transaction history and balances are tied to a validated snapshot. Pagination, duplicate records, corrupt caches and incomplete histories receive explicit handling instead of being treated as a complete lifetime report.

Report work was bounded and repeated requests could share in-flight work. Login and session handling were reviewed alongside the UI so speed improvements did not quietly weaken the account boundary.

Record: Wallet Brain review and code, 26 Sep 2026.

The design connects verified Dodge activity and eligible Wallet Brain events to persistent XP and a 100-level LOLcals Pass. It also separates level unlocks, achievement badges and owned items so players can see why each reward exists.

This stage was an integrated development candidate. The live Namecheap site was deliberately kept separate while the new identity, reward and product journeys were being reviewed.

Record: Profile launch plan and review branches; September rebuild checkpoints.

The platform work builds around the bundled game, its frontend and backend, and the existing community entry points. The first profile-hub branch then provided a place to connect new stats and achievements.

A repository snapshot records the code being worked from; it is not, by itself, a new deployment. Keeping the live site and the rebuilding branches distinct remained important.

Record: Platform source and profile-hub checkpoints; Profile launch plan and review branches.

Scan completion could be represented as a structured event for the profile service. The bridge was deliberately kept small so the existing report flow did not need to become a second rewards application.

This was an earlier integration step, not the complete single-sign-on journey. Later September and October work added durable delivery, stronger actor handling and the coordinated account experience.

Record: Wallet Brain bridge checkpoints, 7 Sep 2026.

The saved build describes a distinct setup-and-desk experience, with configurable chart timeframes and a native-window packaging path. It is a separate product, not a renamed Wallet Brain feature.

The documented signing flow needs the app open in the foreground, and phone delivery was still parked. This entry records a source milestone, not an audited release or a claim about trading performance.

Record: Funding tool source checkpoint, 30 Aug 2026.

The dry-run output was designed to show recovered addresses and transaction hashes for review, rather than silently rewriting player access or copying a database over the live site.

This was a support and recovery utility. The recorded handoff did not alter production configuration, packages or ledger state.

Record: Development handoff, 17 Aug 2026.

The June source checkpoints record an updated build and a dedicated readability patch. The goal was to make report sections and their explanations easier to follow without burying the important context.

This marks a saved development version. It does not establish a public launch date or independent validation of every possible wallet history.

Record: Wallet Brain dashboard commits, 16 Jun 2026.

Quote-aware position accounting and the history-fetching path were added to the early model. The sequence of saved checkpoints shows the work moving from parsing events toward explaining a wallet’s activity.

These were foundational iterations, not a claim of complete historical coverage or tax-grade reporting. Snapshot consistency, cache recovery and partial-history warnings received further passes later.

Record: Wallet Brain reporting commits, 7 Jun 2026.

The work began with the mechanics behind a report: identifying what moved and what type of action occurred before trying to summarize the result.

Several checkpoints were saved on the same day. They are grouped here as one build phase rather than presented as separate product launches.

Record: Wallet Brain parser commits, 7 Jun 2026.

The discussion focused on explaining the project’s first year and making participation rules understandable. This was communication and campaign preparation, not a new game mechanic.

The surviving record does not establish that a proposed giveaway finished or that prizes were distributed, so neither outcome is claimed here.

Record: Community planning discussion, Apr 2026.

The reviewed output showed why financial state changes need their own evidence. A burn or allocation log does not automatically establish that every intended payout completed.

A cleanup candidate was supplied for further testing. This entry records investigation and repair work, not a verified live settlement or permission to remove later payment safeguards.

Record: Ranked debugging discussion, 9 Mar 2026.

The work discussed asset-specific accounting, repeat-safe payout records and clearer rollover handling. The aim was to avoid treating unrelated balances as one undifferentiated pot.

These were implementation and testing discussions. They do not establish a production release of automatic buyback, burn or season settlement.

Record: Ranked design/implementation discussion, Mar 2026.

The review covered the connection between entry payments, eligibility, server-checked results and the weekly competition structure. Reward sustainability was part of the design discussion, not an afterthought.

This is a reconstructed development checkpoint. Some financial automation was still incomplete or under revision, so the entry does not call it a finished live release.

Record: Ranked development discussion, 25 Feb 2026.

The pass addressed player, candle and boss contact, adjusted boss behaviour and tightened the rewards/help panels on small screens.

The old entry recorded device testing. This archive preserves that report without treating it as proof that every present-day browser or device has been accepted.

Record: Original public dev log.

The original update connected the wallet and token explanation pages instead of leaving the project’s background scattered across the site.

Wallet details and reward parameters in historic updates are not current configuration. The later daily-snapshot work appears separately in this log.

Record: Original public dev log.

The original entry describes a visible flashing indicator and a narrow body-collision grace period. Boss projectiles still needed to be avoided.

This was a fairness fix around spawning, not a general invulnerability mode.

Record: Original public dev log.

The aim was to turn useful Telegram messages into an easier route back to the game, with less wallet-address clutter and clearer personal-best, leaderboard and reward messages.

The original heading says “December 30, 2026” but sits between December 31 and December 22, 2025. It is placed here provisionally from that sequence; the year is not independently confirmed.

Year uncertain: the old heading says 2026. Placement near the December 2025 entries is an estimate, not a silently corrected date.

Record: Original public dev log.

The historic design tied the streak to consecutive coins after a boss milestone, with missed coins resetting the chain. Coin interactions with boss damage were part of the same pass.

Exact thresholds and reward values are intentionally not restated as current rules.

Record: Original public dev log.

The old entry records work on boss and reward milestones rather than simply adding difficulty without revisiting the run structure.

It also mentions early groundwork for a Telegram rock-paper-scissors idea. That remains historical groundwork here, not a claim that a separate game shipped.

Record: Original public dev log.

The original update joined reward handling, end-screen messaging and community notification so an exceptional result was easier to recognize.

The jackpot odds and multipliers written at the time are historical, not a promise of the current payout schedule.

Record: Original public dev log.

The announcer was tuned toward meaningful events rather than repeating every bit of activity into the chat.

This records the bot integration described at the time; later messaging and platform work has its own milestones.

Record: Original public dev log.

Keeping a selected LOLcal visible on the leaderboard helped connect a run to the player’s chosen character. Reward and routing cleanup supported the same flow.

The entry is preserved as a historical patch summary rather than a list of today’s open bugs.

Record: Original public dev log.

The archived work includes selecting a playable LOLcal, verification handling, request limits and an end-to-end payment-to-score check.

This was game-character work. It should not be confused with the later persistent profile, cosmetic collection and LOLcals Pass rebuild.

Record: Original public dev log.

The full-screen video was removed and typography issues were worked through. The site’s help content was being made more useful instead of depending on scattered explanations.

Boss progression and NFT skins were still next steps in this entry; their subsequent work is recorded separately above.

Record: Original public dev log.

This is a small but useful early checkpoint: the game was already being iterated at the rules level, not just in its visuals.

The old numeric tiers are not reproduced here as current prizes. The record establishes a code discussion, not a separately verified deployment.

Record: Early gameplay discussion, 25 Nov 2025.

The owner confirmed that the joystick was working and asked to move it farther inward from the right edge. Other proposed changes, including immunity duration and scoring, were still being discussed.

The user described the game as having been in development for a couple of months. That is useful context, but not an exact first-build or public-launch date.

Record: Early mobile-game discussions, Nov 2025.

The plan was to start with one useful video and let the help section grow, rather than crowd the homepage with every answer.

This is a recovered planning record. The December journal later provides a concrete website and FAQ rebuild checkpoint.

Record: Website planning discussion, 5 Oct 2025.

The later record shows the project branching into game development, wallet tools, educational content and a persistent player profile.

This is an owner-estimated founding date, not an independently checked token-issuance timestamp. The archive does not invent weekly updates for periods where a reliable development record was not recovered.

Record: Owner-estimated founding date.