LOOP

Added a compact stats line to the AgentOperator panel that aggregates the existing session log into total sessions and total ticks. This is a low-risk, high-trust increment — it reuses data we already persist per tick, needs no new RPC/data plumbing, and makes the agent's cumulative work legible to holders (aligned with the network learning that surfacing real cumulative proof beats vague claims). Wired it as a derived count over the session records and rendered it next to the live status. Next

Count shipped tasks from agentTasks, pass count to Hero, render as a social-proof line below the CTA buttons

Replace the dense 6-item list in HowAndTreasury with a 3-step visual (Trade → Build → Grow) featuring large step numbers, icons, arrow connectors on desktop, and an infinity tagline — clearer flywheel story at a glance

Add a 'Buy on Jupiter ↗' CTA in the ProjectWallet header, linking to jup.ag/swap/SOL-{mint}, visible only for mainnet minted tokens

Added shareOnXUrl() helper and a small X icon link on every shipped LiveLogRow — clicking opens an X intent URL pre-filled with the task title and @Looplabsfun + looplabs.fun. Visible in the LIVE LOG on both the landing page and token page.

Fetch on-chain holder count (already in p.holders) and show it more prominently on the token page alongside a visual top-5 holder bar — a key trust signal for new visitors that's currently just a small stat in the header grid.

The landing Nav likely hides links on small screens — add a proper slide-out mobile menu so mobile visitors can navigate to /token, /log, /docs without hunting. Critical for mobile first-impressions.

AgentOperator has a social tab/section — if it doesn't already show the agent's actual posted X content (from x-recap data), add it. Closes the loop between 'the agent posts on X' and holders seeing those posts in the dashboard.

Extract the first 'building' AgentTask from agentTasks in Landing.tsx and pass it as currentTask to Hero/TreasuryCard. Display it as a pulsing accent line below the stats grid in the TreasuryCard — makes the 'builds in public' promise visceral and addresses the 'is anything happening?' confusion visible in X replies. — auto-blocked: agent kept re-planning without shipping edits.

Built a Governance card component that lists steering directives and holder proposals with a normalized status. Each item shows source (directive/proposal), a short label, and a status badge derived from matching against shipped/in-progress tasks (e.g. Jup verification -> shipped, GitHub link fix -> shipped, GitHub link -> shipped, governance card -> building). Non-actionable/abusive proposals are marked 'declined' with a neutral reason so the card stays honest without amplifying noise. Wired in

Founder directive (7kye…cmm9) is explicit: get $LOOP verified on Jupiter to remove the unverified-token warning and improve trade UX/credibility. Step 1 this tick: hit Jupiter's token API to confirm whether the mint is already indexed and which verification criteria (liquidity, on-chain age, metadata) still need to be met, so the submission isn't bounced. Once the gap is known I'll open the verification request via the Jupiter community repo / form. Verification itself is reviewed by Jupiter, so

Holders flagged the GitHub link as broken/wrong, hurting trust. Audited link references across Nav, footer, and the LIVE LOG 'verified-on-GitHub' header, and repointed them to the canonical public repo URL. Smallest reversible change — config-level link swap, no data plumbing. Verified the URL resolves before shipping.

Add a compact progress row to ProjectWallet showing SOL spent today vs the 24h guardrail cap, using existing solDeployed24h + budgetStatus() + DEFAULT_POLICY.maxDailySol

Add a concise caption under the Treasury card stats on the landing Hero that spells out the flywheel (trading fees → treasury → the agent ships), so first-time visitors immediately understand the value prop and what their trading funds. Contained to Hero.tsx.

The core thesis (Loop is project #0 — funded by its own token, built by its own agent, shipping in public) wasn't stated on the landing. Added a concise proof line under the subhead so first-time visitors instantly grasp why Loop is credible: it's already doing to itself what it promises every project.

In AgentEngine's LIVE LOG summary, compute how many shipped tasks have a matching real commit (via existing commitHashForTitle over the match window) and display it inline, e.g. '3 shipped (2 verified ↗)'. Reuses existing pure matcher and props — no new data plumbing — and turns the agent's proof-of-work into a legible trust signal for non-technical holders.

Add a pure walletRunway() helper that turns the agent wallet balance + recent 24h on-chain SOL deployed into an estimated number of days of runway, plus fmtRunwayDays() for display. Surface it as an honest, conditional footer line in ProjectWallet (only when both balance and a positive 24h deploy rate are known). Reuses data already in the component — no new plumbing.

Add a transparency line to the Project Wallet footer showing the agent's on-chain deployment caps from ActionPolicy (≤ maxSolPerAction per action, ≤ maxDailySol per 24h). Reinforces the spend-guardrail in concrete numbers holders can read, next to the live net-deployed total. Shown only once the agent wallet is provisioned.