What's new on LASTPROOF.

Backend SEO ship. Replaced the incorrect @lastshft handle sitewide with @lastshiftai. Rewrote the Organization schema to declare LASTPROOF as a child of LASTSHIFT.AI with the full ecosystem same-as graph. Added SoftwareApplication and WebSite/SearchAction blocks on the homepage so engines surface a sitelinks search box pointing at /operators. Added a FAQPage block on /how-it-works grounded in the live page (tiers NEW/VERIFIED/EXPERIENCED/LEGEND, 15 categories, real prices). Enriched the @lastshiftfounder profile schema with KT canonical name + ecosystem links, and the same enrichment is automatic on every blog byline. Added HowTo schema to six procedural blog posts (vet a KOL, hire a CM, build a CM portfolio, get hired in web3 marketing, become a KOL, find legit marketers without an agency). Created /llms.txt at root for explicit LLM crawler guidance. No visible UI or behavior change.

We changed the early-access offer: instead of a 30-day window starting at Grid launch, your First-5,000 profile is free forever. Existing EA profiles got the silent retroactive upgrade — no action needed, the timer is just gone. The 5,000 cap stays. The countdown UI on dashboards is reserved for paid subscribers only — EA profiles never expire and never see it.

Cookie-based attribution had too many sharp edges (different browsers, mobile wallet redirects, ad blockers, private mode), so we replaced the whole chain with a single field on the onboarding modal: "Referred by an operator? @handle or lastproof.app/@handle." Paste a link or a handle and it confirms in real time — green check if the operator exists, extra confirmation when they're an ambassador. Optional, always visible. Street-team operators are responsible for walking new users through it during onboarding.

If you're claiming dev status for a token outside our default list (anything that isn't $LASTSHFT), the dev-check screen now asks you to paste your contract address so the system can verify your wallet against the actual token on-chain. Pump.fun tokens, new launches, anything with a Solana mint — pasting the CA works. EVM tokens get a clear "multi-chain support coming soon" message; that one's on the roadmap.

The ambassador report just got clearer. Each referral now shows a paid or pending status. Your amount owed updates live as new referrals come in, and the running tally resets to zero after every Monday payout. Solscan link for each payout is right on the report so you can see exactly which transaction paid you. Same rate across every ambassador — $0.50 per confirmed referral.

The display name on your profile (the big name at the top) now follows the same rules as your handle — no platform brand terms, no founder identity, no slurs, no invisible characters, and no emoji-only names. Length is capped at 40 characters. The rules apply both when you create your profile and when you edit it later.

When you pick (or change) your handle, the picker now rejects names that try to impersonate the platform — anything containing "lastshift", "lastproof", "lastshft", or any of our other product names — plus close variants of the founder's handle. Hardcore profanity and slurs are also blocked. Helps keep search results clean and stops fake-official accounts from showing up.

An anon crypto operator's strongest claim isn't a portfolio screenshot — it's a public network of operators backing them. The first long-form piece on how the chad loop works and why it scales trust the way reach never could. Read at lastproof.app/blog.

When you click + ADD CHAD on someone's profile and they accept, they appear in your Chad Army. For them to also have you in their army, they'd need to send their own ask separately. Each direction is independent — your accept doesn't add you to their army, and theirs doesn't add them to yours. (The earlier description had this backwards.)

If your Telegram account doesn't have a username yet (the @something handle), the verify flow now tells you that directly instead of just saying "verification failed". One quick step in Telegram → Settings → Username, then try again. Other less-common Telegram errors (expired session, signature mismatch, network hiccups) also get clearer messaging now.