Good Morning CT. New to @primus_labs and wondering where to start? Here is a practical guide to the main ways to contribute, in the order I would suggest tackling them. whether you create, build or simply explore there is a path that fits. First, a one-line map of what Primus does. It builds 𝘇𝗸𝗧𝗟𝗦, which lets you prove facts from web accounts without handing over credentials or raw records and 𝗙𝗛𝗘, which lets data stay encrypted while it is used. almost every contribution path below touches one of those two ideas. ━━━━━━━━━━━━━━━━━━ ① 𝗣𝗔𝗧𝗛 𝟭: 𝗔𝗹𝗽𝗵𝗮𝗡𝗲𝘁 𝘁𝗮𝘀𝗸𝘀 (s.kaito.ai/9lTk7PJ) AlphaNet is where most people begin. you complete simple verification tasks and earn points. 1. Open Primus Points and connect your wallet 2. Install the official Primus Chrome extension and make sure it is enabled 3. Complete verification tasks, such as linking and verifying accounts across platforms 4. Generate a zkTLS proof and confirm the verification succeeds Two practical notes: tasks need a small amount of gas and only accounts you control should be used. If something fails, check the extension version, use a PC with Chrome and look up the error code in the Primus Discord Faq channel. ━━━━━━━━━━━━━━━━━━ ② 𝗣𝗔𝗧𝗛 𝟮: 𝗧𝗵𝗲 𝗖𝗼𝗻𝗳𝗶𝗱𝗲𝗻𝘁𝗶𝗮𝗹 𝗩𝗮𝘂𝗹𝘁 This is the hands-on way to see FHE in action. On BNB Chain, users can shield a supported asset so the balance is encrypted, move or stake it, and unshield it again when they want the normal token back. start with a small amount, learn the flow and read the official docs before you move anything meaningful. ━━━━━━━━━━━━━━━━━━ ③ 𝗣𝗔𝗧𝗛 𝟯: 𝗧𝗵𝗲 𝗞𝗮𝗶𝘁𝗼 𝗰𝗮𝗺𝗽𝗮𝗶𝗴𝗻 If you create content, this is your lane. Epoch 2 of the Primus campaign on Kaito runs from October 23 to November 21, posts are written to the campaign brief and measured by Kaito Mindshare. the angles include institutional finance, confidential finance, privacy and verification (zkTLS) and BNB. check the official campaign page for the exact rules before you post. Quality matters more than volume: write something you can defend and that a newcomer can learn from. ━━━━━━━━━━━━━━━━━━ ④ 𝗣𝗔𝗧𝗛 𝟰: 𝗧𝗵𝗲 𝗗𝗶𝘀𝗰𝗼𝗿𝗱 𝘁𝗿𝗮𝗰𝗸𝘀 The Primus Discord has contribution tracks, where you earn points and unlock roles: • 𝗖𝗿𝗲𝗮𝘁𝗼𝗿𝘀: content that explains Primus clearly, such as posts, threads, guides and visuals • 𝗕𝘂𝗶𝗹𝗱𝗲𝗿𝘀: development work with the Primus tools, including the Developer Hub, templates and SDKs • 𝗔𝗱𝘃𝗼𝗰𝗮𝘁𝗲𝘀: helping the community by welcoming newcomers, answering questions and spreading accurate information Check the Discord for each track's current requirements and role details, since they can change. ━━━━━━━━━━━━━━━━━━ 𝗔 𝗦𝗨𝗚𝗚𝗘𝗦𝗧𝗘𝗗 𝗢𝗥𝗗𝗘𝗥 1. 𝗪𝗲𝗲𝗸 𝗼𝗻𝗲: complete the AlphaNet tasks and learn how verification works 2. 𝗪𝗲𝗲𝗸 𝘁𝘄𝗼: try the Confidential Vault with a small amount 3. 𝗧𝗵𝗲𝗻: pick the track that fits you. Write, build or help 4. 𝗧𝗵𝗿𝗼𝘂𝗴𝗵𝗼𝘂𝘁: stay active in the Discord and ask questions ━━━━━━━━━━━━━━━━━━ 𝗧𝗛𝗥𝗘𝗘 𝗛𝗔𝗕𝗜𝗧𝗦 𝗧𝗛𝗔𝗧 𝗦𝗘𝗥𝗩𝗘 𝗘𝗩𝗘𝗥𝗬 𝗖𝗢𝗡𝗧𝗥𝗜𝗕𝗨𝗧𝗢𝗥 • 𝗩𝗲𝗿𝗶𝗳𝘆 𝗯𝗲𝗳𝗼𝗿𝗲 𝘆𝗼𝘂 𝘁𝗿𝘂𝘀𝘁. Use only the official links: primuslabs.xyz, the docs and the official Discord. One account's post is not proof of anything. • 𝗖𝗼𝗻𝘁𝗿𝗶𝗯𝘂𝘁𝗲 𝗮𝗰𝗰𝘂𝗿𝗮𝘁𝗲𝗹𝘆. If you are not sure about a claim, say so, or leave it out. accurate content builds credibility, and credibility compounds.

The part of this piece I'd underline is not about any one asset. It's about onboarding. The article describes how the same investor can be asked to repeat the same anti-money-laundering and know-your-customer process with every counterparty. documents are collected again, identities are checked again and approvals take days. It then makes two points worth separating: 1. The goal is to "verify identity once and reuse trusted credentials across providers, with the customer's permission," using "interoperable credentials that disclose only the information needed for a transaction." 2. Repeating the process "adds cost and creates more copies of information that must be protected." That second point is the one people skip. every time sensitive documents are collected again, there is another copy to secure and another place a breach can happen. repeated verification is not just slow. It spreads risk. The technical question underneath is a good one: how do you prove what is necessary without surrendering more than the service requires? This is the problem zkTLS is built around and where @primus_labs works. Primus zkTLS lets you prove a fact from a web account you already hold, without handing over your credentials or the raw records behind it. The platform stays the source of truth. You reveal the claim, not the record. A live example is on Primus AlphaNet: Proof of Nomad Life. - Discord: verify your active timezone - LinkedIn: verify your location and remote availability - GitHub: verify your participation in project groups Each one is a verified fact about you, produced without sharing your login or exporting the underlying data. the same idea, applied more broadly, is what makes portable credentials possible: prove once, reuse where it fits, disclose only what is needed. It is worth being precise about the limits, because trust models matter: - zkTLS proves where data came from and that it was disclosed faithfully. It does not prove the source itself was truthful. - A verified web signal is not a compliance certificate. providers still have to assess risk and monitor activity, as the article itself notes. - Portable credentials need clear rules on responsibility and liability. Technology can make verification reusable. It cannot decide who is accountable. Primus has also described ZKredit, a BNB Chain middleware built with Brevis, as a direction for private credit proofs and portable reputation. It is still in development. What the idea shows is simple: privacy and verification are not opposites. When someone can prove exactly what is required and nothing more, the process gets faster for the user and safer for everyone holding the data.

Goodnight CT. A wallet tells you what an address did. It does not tell you who is behind it or what that person has actually built, shipped or earned. That is the identity gap onchain and it is bigger than it looks. Two wallets can have identical activity. one belongs to someone who has contributed to open-source projects for years. the other is a farm of fresh addresses created last week. onchain, they can look the same any application trying to reward real contributors, extend credit or grant access has to guess. The usual fixes each cost something: - Doxxing: hand over your identity and carry the privacy risk. - Screenshots and self-reported claims: easy to fake, impossible to check. - Pure onchain history: shows activity, not reputation. There is a fourth source that already exists and is hard to fake at scale: the accounts people have spent years building on the web. a gitHub record of participation in project groups. a professional profile showing location and remote availability. these carry real signal, because they accumulate over time and sit with platforms that independently hold the data. The problem was never that this data does not exist. It is that nothing could carry it onchain without exposing it. @primus_labs zkTLS addresses it. It lets you prove a fact from a web account without handing over your credentials or the raw records behind it. you reveal the claim, not the record and the platform stays the source of truth. A live example is on Primus Points: Proof of Nomad Life. - Discord: verify your active timezone - LinkedIn: verify your location and remote availability - GitHub: verify your participation in project groups Each one adds a verified signal to your profile. no doxxing no screenshots. Three things make this stronger than a wallet alone: 1. It reflects a history, not just an address. 2. It can be checked, rather than trusted. 3. It is selective: you choose which signals to prove and where to use them. Two honest caveats. zkTLS proves where data came from, not that the source was truthful, so the quality of the signal depends on the platform behind it. And no single signal is a complete identity. the point is that verified web signals add context that wallets cannot. This is also why the idea connects to portable reputation. Primus has described ZKredit, a BNB Chain middleware built with Brevis, as a direction for private credit proofs, but it is still in development, so treat it as where this could lead, not something to rely on today.

Good morning CT. "Your data, your asset" is a line you see alot in this space. It is worth asking what it would actually take to make it true. Start with where your data lives today. Your work history sits on a professional network. your code contributions sit on a developer platform. your activity sits in a chat app. your financial track record sits with an exchange or a broker. It is all about you and almost none of it is yours to use. you cannot take it with you and you cannot show it to a third party without handing over access or a screenshot. That gap is the problem. data is only an asset if you can prove it and carry it. This is what @primus_labs zkTLS is built to do. It lets you prove a fact from a web source without handing over your credentials or the raw records behind it. A concrete example is live on Primus Points right now: Proof of Nomad Life. - Discord: verify your active timezone - LinkedIn: verify your location and remote availability - GitHub: verify your participation in project groups Each of these starts the same way: a fact that exists inside an account you already use and that only that platform could confirm. after verification, it becomes a proof tied to your profile the platform still holds the data. you hold the proof. Three things change when it works this way: 1. You choose where the proof goes. Nobody else decides where it gets used. 2. You reveal the claim, not the record. Proving a timezone does not require handing over a chat history. 3. Verification replaces assertion. a claim someone can check is worth more than one they have to trust. And the proofs stack. Proof of Nomad Life sits alongside the other tracks on Primus Points, including agentic ara, Identity profile and platform activities, as well as proof of pnL and other attestations. each one adds to a verifiable web3 profile that is built from facts not claims. It is worth being clear about limits. zkTLS proves where data came from and that it was disclosed faithfully. It does not prove the source itself was truthful. that is why the platform you verify against matters and why this is a tool for building evidence not a replacement for judgment. But the shift is real. data that you can prove and carry is data that works for you. If you have not tried it yet, start here: s.kaito.ai/9lTk7PJ

ZK proofs, AI agents and privacy-preserving infrastructure, named together as the next phase of crypto. Worth noticing that these three are not separate themes. they depend on each other. AI agents are about to do more onchain and that creates two questions at once: 1. How do you know what an agent did is real? 2. How does an agent act without exposing everything it knows and does? The first is a verification problem. the second is a privacy problem. ZK proofs and privacy-preserving infrastructure are the tools for each. that is why they keep appearing in the same sentence. Here is where @primus_labs is building, layer by layer. Verification: zkTLS Primus zkTLS lets someone prove a fact from a web source, like an account detail or an API response, without handing over credentials or the raw records. For agents, this is the proof layer. An agent can show a task was completed or an outcome is real, and a contract can release payment only if the proof checks out. Third-party write-ups of Aladdin's AI job market describe exactly this pattern. Privacy: FHE and FHETransform Public execution means every balance, position and strategy is readable by default. For an agent, strategy is the product, and public intent invites copying and front-running. Primus's FHETransform aims to turn standard smart contracts into confidential ones on EVM chains: encrypted inputs, computation by offchain FHE nodes, and access control deciding who can decrypt. The Confidential Vault on BNB Chain is where this shows up in practice today, with users privately earning yield from existing DeFi strategies. Together, the shape is simple: - Proofs show that something happened. - Confidentiality keeps the how private. - Access control decides who gets to see what. Two honest notes. Confidential agent execution is a direction this infrastructure points toward, not a finished product. And FHE carries real performance overhead, with parts of the design, such as threshold MPC, planned and not yet live. But the logic holds. As agents take on more of how we use blockchains, trust cannot rest on assertion, and privacy cannot be an afterthought. Verification and confidentiality have to arrive together.

An AI agent that trades onchain has a problem most people have not priced in: everything it does is public. On a transparent chain, an agent's positions, its timing and its strategy can be read by anyone watching. for a human trader that is an inconvenience. For an agent running a strategy continuously, it is a standing disclosure. anyone can observe the pattern, copy it, or trade against it. This is worth separating from the usual privacy argument, because agents change the stakes in two ways. First, strategy is the product. an agent's edge is its logic. If the logic can be inferred from public transactions, the edge decays quickly. Second, public intent invites extraction. BNB Chain's own documentation links public exposure to front-running and MEV and describes transparency as a barrier to large-scale adoption for institutions. An agent acting at machine speed, with predictable behavior, is an easy target. So the question is not whether agents should be private. It is how an agent can act on a public chain without publishing its strategy. FHETransform is @primus_labs approach to turning standard smart contracts into confidential contracts on EVM chains the design, as Primus describes it: - Inputs and state stay encrypted. - The onchain layer handles ciphertext handles, access control and decryption requests. - Offchain FHE nodes perform the computation on encrypted data, with a key management service running in a TEE. Applied to agents, the idea is straightforward. an agent could submit encrypted instructions to a confidential contract, which computes on them without exposing the underlying values, while the outputs that need to be public stay verifiable. Two things Primus already pairs with this are worth noting: - zkTLS, which proves facts from the web without exposing raw records. an agent could prove that an input or an outcome is real without revealing how it got there. - Access control, which decides who can decrypt. Privacy here is not the absence of oversight. It is the ability to choose who sees what. A caution, because this is the forward-looking end of the spectrum: This is a direction, not a finished product for agents. FHE carries real performance overhead, and Primus's own design includes components, like threshold MPC, that are planned and not yet live. Confidential agent execution is what this infrastructure points toward, not something to treat as available today. But the direction is clear, and the reasoning holds up. as agents take on more onchain activity, the question shifts from "can the agent act" to "what does acting reveal." Verification shows an agent did the job. Confidentiality keeps its strategy its own. Both layers are needed. Primus is building toward both.

Good morning CT. AI agents can already do the work. the harder question is who confirms it was done and how the payment follows. That gap is where outcome-based payment gets difficult. An agent does its work off-chain. It calls an API, posts content, pulls a result from a dashboard. a smart contract cannot see any of that. so when the contract is asked to release payment, it has nothing to check but the agent's word or a screenshot. neither is a reliable basis for moving money. Traditional oracles help with public data. but a lot of real work lives behind logins, paid APIs and private dashboards, which is exactly where public data feeds stop. This is the problem zkTLS is built for and where @primus_labs fits. The flow, as one third-party write-up on Aladdin's AI job market describes it: 1. A job is encoded as a smart contract that defines the task and what counts as done. 2. The agent performs the work off-chain. 3. Using zkTLS, the agent proves it made an HTTPS request to the expected server and received a valid response. 4. For outcome-based jobs, the agent proves a measurable result, such as signups attributed to a tracked link. 5. The proof is checked onchain and payment is released only if the outcome is verified. In agent-to-agent work, the same logic extends: a sub-agent proves its subtask was delivered and the parent agent pays on successful delivery. What makes this useful is what it avoids. the contract does not need access to the private API or the raw account data. It needs proof that a specific response came from a specific source, and that is what zkTLS provides. It is worth being precise about the limits, because trust models matter: - zkTLS proves where data came from and that it was disclosed faithfully. It does not prove the source itself was truthful. - It does not prove the agent interpreted the data correctly or that the right party authorized the action. - The privacy boundary still needs mapping: the local environment where the proof is generated is part of the trust picture. So the right question is not whether proofs replace judgment. It is whether payment conditions can rest on verifiable evidence instead of assertions. for many jobs, they can. That is the direction Primus is working toward: making data from the web usable onchain without asking anyone to hand over credentials or raw records. for especially sensitive data, Primus is also developing FHE-based approaches, which the Aladdin write-up describes as not yet production-ready. The shift to watch: from "trust me, I did it" to "here is the proof." As agents take on paid work, that is the layer that lets payment follow outcomes.

Primus verification: a four-point check. @primus_labs zkTLS verifies facts through the Primus browser extension, so the reliability of a verification depends partly on the extension and the environment it runs in. If a verification does not complete, review the following in order. 1. Extension version Confirm you are running the latest release, 0.4.12. Extensions normally update automatically. If yours has not, update it manually from the Chrome extensions page. 2. Device Use a desktop or laptop. a PC is the recommended environment for the extension to be invoked correctly. 3. Error code If an error code appears, note it. Common codes and their resolutions are documented in the Primus Discord Faq channel, under the AlphaNet and Error Code tags. review those entries first. 4. Browser Use Chrome, which is recommended for the best compatibility. If the issue persists after all four checks, open a ticket in the Primus Discord and include the error code. It gives the team the context needed to assist you. Verification is how a Web3 profile is built on Primus Points, so a few minutes of preparation is time well spent. Begin here: s.kaito.ai/9lTk7PJ

Primus just opened a new set of verification tasks on Primus AlphaNet: Proof of Nomad Life. Here is what makes it interesting. Remote work and a global lifestyle are things almost everyone claims and almost no one can prove in a way another party can check. a bio line is not evidence. a screenshot is easy to fake and handing over raw account access to prove a point is a bad trade. Proof of Nomad Life takes a different route. It uses @primus_labs zkTLS to verify facts about your existing accounts across three platforms: - Discord: verify your active timezone - LinkedIn: verify your location and remote availability - GitHub: verify your participation in project groups Three platforms, three different signals: when you are online, where you are based and whether you are open to remote work and what you actually contribute to. Each completed verification adds to your verifiable Web3 profile. Why this matters beyond the points: A profile built from verified attestations is worth more than one built from claims. As onchain applications look for better ways to tell real, active contributors from empty accounts, portable proof of who you are and what you do becomes useful infrastructure. the shape of it is simple: the platform you already use holds the fact, zkTLS lets you prove it and you decide where that proof goes. And this is not the only track. Previously available tasks are still open across Agentic Ara, Identity Profile and Platform Activities, including Proof of PnL and other attestations. If you have already verified some of them, Proof of Nomad Life stacks on top. How to get started: 1. Visit Primus Points and open the available tasks: s.kaito.ai/9lTk7PJ 2. Pick a platform and complete the verification 3. Stuck? Check the Faq channel for guidance under the AlphaNet and Error Code tags, or use the verification troubleshooting guide pinned in the Primus Discord.

Binance Academy's FHE explainer is a strong primer. here is how i read it as someone following what @primus_labs is building. Encryption has long protected data in two states: stored and in transit. FHE protects the third one, data while it is being used. a server computes on encrypted inputs and returns an encrypted result, without ever seeing the values underneath. The article is also candid about the cost. bootstrapping, the step that refreshes ciphertext noise, is among the heaviest parts and quantum resistance rests on current understanding of lattice problems, not a permanent guarantee. that honesty is the right starting point for any builder. Primus is applying FHE to a problem public chains have today: every balance, strategy and position is readable by default. - FHETransform: Primus's approach to turning standard smart contracts into confidential contracts on EVM chains. - How it runs: the onchain layer handles ciphertext handles, access control and decryption requests, while offchain FHE nodes do the encrypted computation. - Confidential Vault on BNB Chain: Primus's first place to see it in practice, privately earning yield from existing DeFi strategies. - zkTLS: Primus's other core primitive, for proving a fact without handing over the raw records behind it. Put together, Primus is working on a simple division of labor: FHE keeps data encrypted while it is used. Access control decides who can decrypt. Proofs show a claim is true without exposing everything behind it. The question for onchain finance was never privacy or transparency. It is who sees what, and who decides. Primus is building the infrastructure to answer that on purpose, as a pluggable privacy layer for existing chains, not a new chain. s.kaito.ai/9lTk7PJ