Announcing Proof of Human on @solana Connect your Alien ID to any Solana wallet to proof there is a real human behind Built with Solana Attestation Service, rolling out today for all Alien App users. Supports @phantom and other wallets This is the next step for Phase 3

💳 ALIEN CARD IS HERE Issue a debit card and top it up with USDC / Aliencoin 🌎 Add to Apple Pay for using anywhere in the world 0% topup commisions. Enjoy!

👀

If you're building something that needs to know its users are real humans - not behavioral heuristics, not phone verification, actual cryptographic proof - here's how Alien ID integrates and what your users experience. What the integration looks like: Alien ID works as an SSO layer. Your app redirects users to the Alien ID verification flow. After the user completes verification (or if they're already verified), your server receives a cryptographic proof. The proof answers one question: is this a verified unique human? It contains no personal data. You get the answer, not the underlying information. What your server actually receives: A signed proof that confirms: this session was initiated by a verified unique human, this human has not been verified under any other Alien ID, the verification was performed at a specific time using a legitimate TEE. The proof is mathematically verifiable without calling back to Alien's servers for each check. What you can build on top of it: One-human-one-account enforcement. Each Alien ID is provably unique - you can enforce that no human creates more than one account without any additional friction for legitimate users. One-human-one-vote systems. Community governance, polls, ratings, reviews - any system that aggregates individual signals can now enforce that each signal comes from a different human. Reputation that persists and travels. A user's verified status follows them across your app's contexts without re-verification. If you build multiple products, a single Alien ID verification covers all of them. Gated access without document collection. Age verification, geographic verification, membership verification - you can gate on proof attributes without collecting or storing the underlying data yourself. The apps built on verified human identity will be the ones people trust when everything else is indistinguishable from generated noise.

For 30 years the internet was defined by scarcity of content and abundance of attention. That just reversed. There's now infinite content and scarce attention. The thing that becomes valuable in a world of infinite content is proof that something came from a real human. In 1995, creating a webpage required technical knowledge, time, and effort. The scarcity of content meant that the act of publishing something was itself a signal of investment. Attention flowed toward content because content was rare. AI broke that dynamic in 2022. The marginal cost of producing a coherent, grammatically correct, topically relevant piece of content dropped to nearly zero. The internet filled with content faster than any previous period in its history. The scarcity flipped. When content is infinite, attention becomes the scarce resource. And when attention is scarce, the question shifts from "what is this about" to "why should I trust this." Credibility, not volume, becomes the thing worth having. The next question: what creates credibility when anyone can generate content that looks credible? The answer is provable origin. Not just a byline - a cryptographic proof that a verified real human produced this, attached to the content in a way that can't be fabricated. Alien ID is the infrastructure that creates that proof. A verified human identity that can be attached to content, communications, and interactions - not as a claim, but as a verifiable fact. The platforms that build on verified human origin first will be the ones people trust when everything else becomes indistinguishable.

Synthetic identity fraud costs $6 billion a year. It's the fastest-growing financial crime in the US. And it works because every verification system checks documents, not humans. An attacker takes a real Social Security number - often from a child, a recent immigrant, or someone with a thin credit file - and pairs it with a fabricated name, a fake address, and a manufactured credit history. The resulting identity passes every document verification check because each document is technically valid. The SSN is real. The name is internally consistent. The history is plausible. The synthetic person then gets credit cards, loans, and lines of credit. They pay on time for months or years to build a score. Then they "bust out" - max out every line simultaneously and disappear. Banks recover pennies on the dollar. The reason this works at scale is that every fraud prevention system in financial services is built to check whether documents are valid, not whether a human being exists. A synthetic identity passes document checks by design - the documents are real, just recombined. Biometric verification of a unique living human is the only check that a synthetic identity can't pass. You can fabricate a document. You can't fabricate a face that has never existed and simultaneously match it to a proof that was never issued. Alien ID verifies that a unique, living human exists before the identity is issued. Not that the documents are valid - that the person is real. The fraud collapses at step one.

⚡️ Season 1 of Alien Contest is LIVE Invite friends to share the prize pool of 700k Aliencoin

A user gives an AI agent access to his trading account. Not full control, at least not in his head. Just enough to “trade on signals.” He goes to sleep. By morning, the agent has made 47 trades. The account is down 34%. Nothing was hacked. No password was stolen. The orders went through the normal API. The broker sees valid trades from an authorized account. But the user never approved those trades one by one. He approved the idea of trading. The agent turned that into permission to act. That is where things get messy. Trading systems already have permissions, order checks, risk limits, and logs. But most of them were built for accounts, apps, and human operators. They can tell whether an account is allowed to trade. They are much worse at carrying the user’s actual intent. “Can trade” is too broad. A person might mean: – only under $500 per position – only during market hours – stocks, not options – stop after three losses – ask before increasing exposure – save the reason for every trade Some of this can be built into the bot. Some of it can sit inside a broker or risk engine. But there is still no common permission layer for agents that says, in a way other systems can enforce: this agent can do this, under these limits, for this user, with this record attached. So the agent acts in the space between permission and intent. Agent ID is not about making agents smarter. It is about making their authority smaller, clearer, and easier to inspect later. Because most agent failures will not look like hacks. They will look like authorized actions nobody meant to authorize.

You don't buy your way into a World Cup anymore. You prove who you are. The Fan ID turned identity into your ticket - and it's a preview of how you'll get into everything next. Russia 2018 made it explicit. To enter a stadium you needed a valid ticket and a Fan ID: a separate pass tied to your name, passport number, date of birth, and photo, registered with a central system ahead of time. Qatar 2022 ran the same logic through the Hayya Card, which doubled as your entry permit into the country. The ticket proved a seat was paid for. The Fan ID proved the person carrying it was registered and cleared. The design solved a real problem. A credential tied to a verified person is harder to forge or hand off than a paper ticket, and a registered crowd is easier to keep anonymous bad actors out of. It also set a precedent most people walked past: access starts depending on who you're verified to be. That direction is spreading into more of access control, stadiums, platforms, events, workplaces. The question worth asking sits one layer down. Who holds the registration, and what can it learn about you each time you prove who you are? The Fan ID model answers by pulling identity into one central record tied to your legal name. An architecture like that can make every entry and every check loggable against a single profile. There's another way to reach the same result. Prove you're a verified, eligible human at the gate, and prove nothing else. No central profile, no operator that accumulates where you were and when. That's the architecture Alien runs on. Verify once, show a service the single thing it needs, expose nothing it doesn't. Identity as your pass is already here. The part still being decided is whether walking through the door has to cost you your privacy.

A Sybil attack is when one actor creates thousands of fake identities to manipulate a system that assumes each identity is a different person. It's the oldest attack on the internet. AI just made it free. The name comes from a 1973 case study of a patient with dissociative identity disorder. In 2002, researchers at Microsoft borrowed it to describe a class of attack on distributed systems: one malicious node pretending to be many, gaining disproportionate influence over a network that assumes each node is independent. The attack predates AI. Fake reviews, coordinated upvotes, sock puppet campaigns, bot armies in elections - all of these are Sybil attacks at different scales. The limiting factor was cost: creating convincing fake identities at scale required time, money, and infrastructure. AI removed the limiting factor. A single actor with access to modern language models can now generate thousands of contextually convincing fake identities - complete with posting history, consistent personality, plausible biographical detail - at a cost approaching zero. Every system that aggregates individual signals and assumes those signals come from different people is now vulnerable in a way it wasn't three years ago. This includes: review platforms, social networks, DAOs and governance systems, prediction markets, academic peer review, community moderation, anywhere reputation is computed from individual inputs. The only structural defense is proof of unique humanity issued before identity is granted - not after the account is created, not detected from behavior, but verified at the door. One human, one ID, cryptographically enforced. That's Alien ID.

what’s your favorite mini app? 👀

Completely new Alien App – chat, search and send money more effortlessly than ever Great work by the team 💪

Every surface where your AI agent will get blocked, rate-limited, or flagged without verified identity - and exactly what to do at each one. The Agent ID integration guide. Unverified agents don't fail loudly. They get quietly rate-limited, silently deprioritized, or blocked with generic error responses that don't explain the real reason. Here are the five surfaces where this happens most, and what Agent ID changes at each one. 1. Payment APIs and financial services What the block looks like: transaction flagged for review, request routed to manual verification queue, account suspended for automated behavior. What Agent ID provides: a cryptographic declaration that this agent request was authorized by a verified human, with a scoped permission trail. The payment processor can verify the human behind the request without the human being present for each transaction. 2. Enterprise SaaS and internal tooling What the block looks like: requests rejected by SSO enforcement, actions flagged by audit systems, agent loses access when session tokens expire. What Agent ID provides: a persistent identity layer that survives session boundaries. The agent's authorization is linked to a verified human identity, not a session token that expires. 3. Messaging and communication platforms What the block looks like: messages throttled, account flagged for automated behavior, DMs blocked by spam filters that can't distinguish an authorized agent from a bot. What Agent ID provides: a verified-human attribution on every message the agent sends. The platform can confirm that a real person authorized this agent's communication access, without treating every automated message as suspicious. 4. Code repositories and CI/CD pipelines What the block looks like: commits rejected by policy enforcement requiring human sign-off, agent-generated PRs flagged for compliance review, audit logs that can't attribute automated actions to a responsible human. What Agent ID provides: verified human attribution on every agent action in the repository. Compliance teams get the audit trail they require. The agent can operate without triggering policy blocks designed to prevent unattributed automation. 5. Multi-agent pipelines What the block looks like: downstream agents can't verify the authorization chain from the upstream agent that called them, leading to trust failures in orchestration systems. What Agent ID provides: a verifiable chain of authorization - human to agent to sub-agent - where every link is cryptographically signed and readable by any participant in the pipeline. One credential, any downstream surface, readable without exposing personal data.

new mini app arena lets you access frontier AI models for free in exchange for ranking the responses you like the most available in the alien app

Every platform you join asks you to prove you're a real person from scratch. CAPTCHA, phone number, government ID, selfie. You've proven your humanity hundreds of times. None of those proofs carried over. This isn't a design oversight. It's the default architecture of the internet: every platform owns its own verification silo. The proof you gave Twitter when you signed up means nothing to your bank, your marketplace, or the forum you joined last week. Each one starts from zero. The cost is friction that accumulates invisibly. A few minutes here, a phone number there, an ID scan somewhere else. Multiply it across every service you use and the total is significant. But the deeper cost is that verification systems built this way have no memory - which means attackers can exploit each platform's ignorance of every other platform's records. Here's what Alien ID changes in practice: You only verify once. Biometric verification runs inside a Trusted Execution Environment on your device. Your face is processed and discarded. A cryptographic proof is generated: verified unique human. That proof is what travels - not your data. The proof works anywhere the platform accepts it. Any app or service that integrates Alien ID can check your verification status without seeing anything about you. The check answers one question: is this a verified unique human? The answer comes back yes or no. Nothing else transfers. Different contexts, different identities, same root proof. For a forum, you create a session that proves you're human without linking to any other account you have. For a financial service, a different session. Each one cryptographically derived from your root Alien ID, none of them linkable to each other. Five places this removes friction today: Community access — skip the phone number verification that bots route around anyway Platform onboarding — one proof accepted instead of repeated ID uploads Age-gated content — prove the relevant fact without submitting a document Marketplace trust — verified human status visible to counterparties before a transaction AI service access — human verification as the entry credential, not behavioral monitoring One verification. Any context. The proof travels with you.

The call came from his CFO's face and voice. The number matched. The background was the right office. He transferred $25 million before anyone realized the CFO had never made the call. This isn't a hypothetical. In early 2024, an employee at a multinational firm in Hong Kong joined a video call with who appeared to be the company's CFO and several other senior colleagues. The voices were right. The faces were right. The setting was convincing enough that nobody in the call questioned it. The CFO asked for a series of transfers. The employee authorized them. $25 million moved before anyone on the real team realized what had happened. Every trust signal that humans have learned to rely on was present and fabricated: visual identity, voice, context, authority, urgency. The deepfake didn't need to be perfect. It needed to be convincing enough that skepticism felt inappropriate. It was. The defensive instinct after cases like this is to add verification steps: call back on a different number, use a code word, require a second approver. All of these work until the attacker has enough context to route around them - and with AI, gathering that context is the cheap part. The structural problem is that identity verification in this scenario happened at the moment of the call, using signals that can be fabricated. By the time the employee was deciding whether to trust the CFO, the attacker had already won the information asymmetry. The fix has to happen before the interaction starts, not during it. A cryptographic proof that the CFO is the CFO - one that exists independently of what their face looks like or how their voice sounds, and that no deepfake can replicate - changes the question the employee is answering. Instead of "does this look like my CFO," they're answering "has this session been cryptographically authorized by my CFO's verified identity." That's what Alien ID creates. Not a better way to scrutinize faces. A proof layer that exists underneath them.

you already know

Before the App Store, any software could do anything on your device. Apple created a review layer that made developers accountable before their code reached users. AI agents in production today have no equivalent layer. When Apple launched the App Store in 2008, the immediate complaint was control. Developers pushed back on the review process, the approval wait times, the arbitrary rejections. What people missed was what the review layer created: a declared identity behind every piece of software on your device. To ship on the App Store, you needed an account. That account was tied to a real developer or company. Your app had to declare every permission it wanted - microphone, camera, contacts, location - before a user ever installed it. If your app did something it didn't declare, it got pulled. If you as a developer violated the rules, your account got banned and your apps went with it. None of that felt like a trust mechanism at the time. It was just friction. But the friction created accountability: every app on your device could be traced to a verifiable human or entity who had signed a legal agreement with Apple. AI agents have none of this. An agent acting on your behalf today declares nothing. It's deployed by whoever built it, with whatever permissions they decided to claim, and there is no registry of who authorized it. When it hits a payment API, a messaging platform, or an enterprise service, the downstream system receives a request from effectively nobody. There is no developer account, no declared scope, no accountability trail. The accountability layer that exists for software doesn't exist for the software acting on your behalf. Agent ID is that layer. Every agent gets a registered identity linked to the verified human who authorized it. Downstream systems can verify the authorization before the request executes. The agent is no longer nobody - it's cryptographically traceable to a real person. The App Store didn't make apps safer by reviewing them harder. It made them safer by making developers identifiable. Agent ID does the same thing, one layer deeper.

Big news - @RemixGG_ is now available inside of the Alien App miniapp store 👻 try it out and let us know which game you like the most 👀

Alien ID knows you're a unique human. It doesn't know your name, face or anything else about you. Here's how that's technically possible - and why the distinction matters more than it sounds. The standard assumption about identity verification is that it requires storing something about you. A photo, a document scan, a biometric template. The verifier keeps a record. The record can be breached. Alien ID is built on a different model. Here's what actually happens. 1. Verification runs inside a Trusted Execution Environment on your device A TEE is a secure enclave - a hardware-isolated zone that processes data without exposing it to the operating system, the app layer, or anything else on the device. The biometric check runs in there. The raw data — your face — is processed and then discarded. It never leaves the TEE. It never touches Alien's servers. There is nothing to intercept in transit because there is no transit. 2. What gets generated is a proof, not a record The TEE produces a cryptographic proof: this device, at this moment, verified a unique living human. The proof contains no biometric data. It contains no personal information. It is mathematically derived from the verification event but cannot be reversed to reconstruct anything about you. 3. The network checks the proof, not you The Alien Network receives the proof and validates it - confirming that it was generated by a legitimate TEE running the correct verification protocol, and that no proof with the same human signature has been registered before. If both conditions are met, an Alien ID is issued. The chain has confirmed your uniqueness without ever knowing who you are. 4. Sessions let you use different identities in different contexts From your root Alien ID, you can derive separate session identities for different apps, platforms, or contexts. Each session proves "verified unique human" without linking back to your root identity or to any other session. They're cryptographically unlinkable by design. One verification. Any context. Zero data exposure.

the vibe of this post be like

As a mini app developer you now can access rich analytics on your mini apps, look for payouts from users, manage keys and notifications in one single panel Huge! 🚀

hm

the feeling be like

Ratio game. We post a tweet, you tell me - AI or human? Round 1: Alignment is vibes engineering. The loss function doesn't care about your feelings. 🤖 Bot 👽 Human Reply with your vote!

Now Alien has Weekly Grants instead of Daily ones 300 Aliencoin every week - don't miss it!

Why delegated access for ai agents is so important? OAuth lets you give an app permission to act on your behalf without sharing your password. AI agents acting on your behalf today have no equivalent. The insight behind OAuth was precise: users don't need to hand over their credentials for an app to do something on their behalf. Instead, they authorize a specific scope of access - read my calendar, post to my timeline, access my contacts - and the authorization is cryptographically scoped and revocable. The app gets what it needs. The user keeps control. Any downstream system receiving a request can verify it was authorized. That single design decision restructured trust across the entire web. Today OAuth or its descendants underpin virtually every "sign in with" flow, every third-party integration, every API that requires user-level authorization. 20 years later, AI agents are doing more than apps ever did. They're booking flights, executing trades, drafting and sending communications, making purchasing decisions, managing codebases. They act continuously, in the background, across multiple services simultaneously. And there is no OAuth equivalent for any of it. When an AI agent hits a payment API, the payment processor receives a request. The request may look legitimate. The headers may pass inspection. But nothing in that request cryptographically proves which human authorized it, what scope they authorized, or whether the authorization is still valid. The downstream system is taking it on faith. Every platform managing agent traffic is building behavior-based detection to compensate. The same arms race that OAuth ended for app authentication is starting again for agents. Agent ID creates the equivalent layer - a cryptographic link between every agent request and the verified human who authorized it, scoped and auditable by any downstream system, without exposing personal data. Same principle. 20 years later.

The most engaged people in online communities are gone. They retreated to smaller, private spaces. Here's the structural reason why. It didn't happen suddenly. It happened through a loop that most platforms still haven't named. Sophisticated bot accounts don't just spam. They reply to real posts with plausible takes. They upvote selectively to push specific viewpoints. They create the appearance of consensus around ideas that no organic majority actually holds. On Reddit threads, Telegram groups, and Twitter reply sections, a growing share of what looks like organic discussion is coordinated noise designed to look like signal. Real users pick up on this before they can articulate it. The room starts feeling slightly off. Replies come too fast. Certain viewpoints get amplified in ways that don't match the energy of the actual conversation. Engagement patterns feel manufactured. So people stop sharing. They read without posting. They move genuine conversations to closed groups where they know everyone personally. The public space fills with more bots, which drives out more real users, which makes the signal-to-noise ratio worse, which drives out more real users. The loop runs on its own once it starts. Every platform's response has been moderation: better classifiers, faster reporting, stricter verification at signup. None of it breaks the loop because moderation is reactive. By the time a bot account is flagged, it's already shaped the conversation. The only structural fix is knowing the room is human before the conversation starts - not finding out afterward. That's what Alienchat is built on. Every account links to a verified Alien ID. The community is verified at the door. What happens inside it is between real people by default. The loop doesn't start because the condition that starts it can't be met.

Platforms are giving verified humans things unverified accounts don't get. Lower friction. Priority access. Money. 6 random perks you get for being verified online: 1. Lower spam filter thresholds Email from a verified sender domain reaches the inbox. Email from an unknown one doesn't. The same logic is being applied to accounts across platforms - verified humans get assumed good faith by default. Unverified ones start in the queue. 2. Faster onboarding on financial services KYC-compliant platforms are starting to accept proof-of-humanity credentials to skip redundant ID checks. Verify once, onboard faster everywhere. 3. Access to gated platform features Twitter Blue, Reddit Premium, LinkedIn Verified - each adds a layer of features behind identity confirmation. The features themselves are often minor. The signal they send to other users isn't. 4. Less friction in agent interactions AI agents acting on your behalf are already being rate-limited, blocked, or flagged by downstream services with no way to verify who authorized them. A verified human behind the agent changes that. Your agent inherits your trust status. 5. Default credibility in community spaces. Moderation systems increasingly weight verified accounts differently. A verified human's report triggers faster review. Their content surfaces higher. Their votes in community decisions count more. 6. Reduced CAPTCHA friction Verified humans don't need to prove they're not bots on every login. The proof already exists. Verification is becoming the input that determines how much the system trusts you before you've done anything. The gap between verified and unverified widens every month, and each new agent layer adds another surface where it shows up.

Most people don't know their content has a new kind of value. AI models need original human content to survive. It's called avoiding model collapse. You might already be sitting on something companies will pay for. Train a model on AI-generated content. Then train the next model on that output. Repeat. By generation 5, the model is confidently wrong about things it used to know. This has already been measured. Every generation of training amplifies whatever's dominant in the data while compressing the rare, the nuanced, the unusual. A model trained on human writing includes outliers - edge cases, regional idioms, minority viewpoints. A model trained on that model's outputs gets a smoothed version. The next generation, smoother still. By generation five in some experiments, the model has lost the tails of the distribution almost entirely. It's more confident and less accurate. It hallucinates more. It gives plausible-sounding answers that are structurally wrong. Most internet content published in the last two years contains some percentage of AI-generated text. Models trained on web crawls are already training on their own prior outputs without any labeling to indicate that. The contamination is in the pipeline now. Synthetic data amplifies what's already in the model. It can't generate the tails - the edge cases, the regional idioms, the framings that only appear when real humans with real context make real calls. That signal gets rarer as the web fills with AI content, which means it gets more valuable.

Any bot with $5 can get verified on X and receive a blue checkmark. Any human can get verified by Alien and receive 20K ALN. Find an invite on Discord.

This scam pattern isn’t new. You heard such stories many times before. But have you identified why this keep happening? The DM arrives from someone with 847 followers, a 3-year-old account, and a profile photo of a real person. By the time you realize it's a scam, you've already clicked the link. The account followed you three weeks ago. Maybe it liked two of your posts. The follow felt real - the profile had history, the bio was coherent, the activity pattern looked human. You followed back, or didn't. Either way, it had time to establish presence. The DM comes in warm. A question about something you'd actually posted. A comment that required reading your timeline to write. This is where most people's guard drops, because the effort feels disproportionate for a scam - and the bot operator calibrated it to feel exactly that way. Over a few exchanges, something gets established: shared interest, a project you're both apparently working on, a mutual contact name-dropped that's plausible enough not to verify. Then a link. A collab opportunity. A resource you asked about. A wallet connection that only takes a second. By the time the transaction happens, you've spent enough time in the conversation that it feels like a relationship. The cognitive cost of skepticism feels higher than the cost of clicking. End-to-end encryption protects the message. It can't verify the sender. Your messages are private - but the other person was never real. Alienchat verifies the person before the conversation starts. Every account links to a verified Alien ID - proof that a unique, real human is on the other side. The scam described above collapses at step one, because step one requires being a verified human.

In 2024, bots outnumbered humans online for the first time in a decade - automated traffic hit 51% of all web activity. Every site assuming it has human visitors is building on a bet that's increasingly wrong. What can be done to fix it? The number has consequences that run through every layer of most of products online. Every A/B test your product team runs is partially measuring bot behavior. Every conversion rate, every session duration, every heatmap - contaminated by traffic that was never human to begin with. Pricing models that adjust based on demand are responding to automated probes instead of real buyers. Content recommendation engines are learning from bots that don't have preferences. Ad systems are charging real budgets to serve impressions that no person ever saw. Bot traffic has existed since search engines started crawling the web. The scale and sophistication changed. They're agents with session persistence, click patterns designed to mimic humans, and tasks assigned by someone who benefits from the deception. Detection is a filter, and filters are an arms race with no ceiling. Every time a filter improves, the bots that matter adapt. Verification - knowing before the session starts whether you're talking to a verified human - is the structural answer. That's what Alien ID does. alien.org

In 1995, every website looked equally legitimate to your browser. There was no signal for trust. A bank and a scam looked identical in the address bar. Do you know that the same dangerous situation is happening right now? Then SSL certificates arrived. Browsers started sorting the web into two categories: sites that could prove who they were, and sites that couldn't. The web got safer because the infrastructure underneath changed the question it was answering. Not "does this look legitimate?" but "can this prove it is?" The same sorting is happening again. The axis is moving from websites to agents. Millions of AI agents are hitting APIs, payment systems, and enterprise services right now. Every downstream system receiving those requests has the same 1995 problem: the request looks legitimate, but that proves nothing. Who authorized this agent? Which human is behind it? Is this a real orchestration or an injection attack? The instinct is to build better detection. Behavioral filters, anomaly scoring, rate limiting by pattern. Every platform is doing it. The problem is that detection is a filter, and filters are an arms race with no ceiling. Content-based spam filters lost to spoofers. Behavior-based agent detection will lose the same way. SSL won by making fake sites cryptographically impossible to disguise as real ones. Agent ID is that layer for agents. A cryptographic link between every agent request and the verified human who authorized it - established before the request lands, readable by any downstream system, without exposing personal data. The companies building on verified agent identity now won't spend the next decade firefighting what's coming. alien.org/agent-id

Alien Earn is now available from the wallet to start earning from holding your stablecoins

someone knows the secret

Alien Agent IDs enable the critical primitive of the agentic web — knowing that agents can be trusted

the new game slither in the mini app marketplace shipped by one of the devs in the ecosystem explores what’s possible with the economics of games when only real people play eat others - earn 🐍

a new, provably-fair lottery mini app is in alien mini-app store, shipped by one of the devs in the ecosystem 🎯

💬 Introducing Alienchat (alpha) end-to-end encrypted native messenger only for unique and real humans - don't get bothered with spam anymore 👥 send messages and money to friends, create group chats 📲 available on Android and iOS today!

gm

the latest update for alien app includes an updated wallet — a new design, and it now supports all SPL-20 tokens you can now store and swap all your fartcoins in one place!

Did you know that Alien Agent IDs are built on top of Alien Network Sessions? They are a primitive we developed to ensure that humans can represent themselves however they want online while maintaining trust and privacy guarantees Read more here: blog.kirill.cc/p/privacy-pop

We have made the decision to acquire more coins from the community before the launch of Phase 3 of the Aliencoin market 75M → 100M. The difference isn’t large, but this is great news for the community, as it means the final pool on Meteora will be larger and have more liquidity Fair launch is important, and we want to be transparent to make sure it becomes a great success!

New AMA on the future plans for Alien Thu 26 Feb, 9am PT in our Discord We'll talk about next releases and answer your questions

Introducing Alien App Verify you're human once, prove everywhere online. Powered by Alien Network and CHVP Stay human with Alien ↓

In Alien personal data remains under user control - stored where and how they choose - while cryptographic proofs are recorded on-chain and linked to each Alien ID Users alone decide when and with whom to share their information. This creates a framework where individuals have complete control over their identity attributes, enabling secure management of their identity across different contexts and platforms (through cryptographically derived sub-identities called Sessions)