A blogger earns $50,000 per month, but when applying for a loan at a bank, the bank may not recognize that income. The reason is straightforward. Their income comes from a platform—the backend can show exactly how much they earn each month, and they can even take screenshots to prove it. But banks don’t want screenshots; they want verifiable proof of income. Without pay stubs or documents recognized by the bank, no matter how much they earn, they might still be denied a loan. The same issue exists on the blockchain. Over the years, public blockchains have been recording transactions: who transferred how much, who bought which assets, and how much liquidity was deposited into which pool—all of this is publicly queryable. But some things are simply not recorded on-chain at all: whether a person’s income is stable, how many U.S. dollars are actually in a company’s account, or how a particular sum of money was generated in the real world. These pieces of information aren’t nonexistent—they just can’t be directly placed on-chain for others to verify. @primus_labs aims to solve exactly this problem. In simple terms, it enables off-chain data to generate verifiable proofs. Two key technologies underpin this. The first is zkTLS, which generates proofs locally in the browser to verify whether data originates from a legitimate website or API and hasn’t been altered during transmission. There’s no need to hand over your full account details or transaction history—others only need to verify the specific results they care about. For example, when applying for a loan, the lender doesn’t need to see every single income entry over the past six months—they just need confirmation that your average income over that period meets the requirement. The second is zkFHE, which takes this further: once data is brought on-chain, can it be used in computations without revealing the raw data itself? Together, these two technologies enable a practical use case: data can be verified without sacrificing privacy. I find this shift in Primus’s positioning particularly noteworthy. It was formerly called PADO, and its website previously emphasized a privacy data layer. Now, it has refocused on building confidential infrastructure for institutional on-chain finance. This isn’t just a rebranding. Individual users may care primarily about whether their data leaks—but institutions have more complex concerns. They want to place capital, trading strategies, and financial information on-chain without exposing every detail. On-chain transparency is one thing; exposing all commercial secrets is another. What institutions truly need isn’t a completely transparent chain, but the ability to prove facts when necessary—and preserve privacy when not. Primus is already applying its technology across several use cases: Cr3dentials uses it to verify freelance income; Unitas applies it to stablecoin reserve proofs; and 0G employs it for AI agent data validation, enabling traceability of the data sources used by agents. These applications may seem unrelated—but they all address the same core question: Why should anyone believe the data you provide? There’s also an easily overlooked boundary here. Proving that data comes from a legitimate source and hasn’t been tampered with doesn’t mean the data itself is accurate. If the original data provided by a platform is false, no verification technology will automatically correct it. These tools solve trust issues around data origin and transmission—not reality itself. In my view, what’s truly interesting about technologies like Primus isn’t about storing more data on-chain—it’s about enabling previously off-chain information to participate in on-chain finance. Previously, blockchains could record where money went—but struggled to understand what real-world circumstances that money represented. Now, someone is beginning to bridge that gap. Ledgers record what happened. Proofs explain why we can trust it. Together, these two elements allow on-chain finance to truly connect with real-world income, assets, and credit.