Recently, I had a conversation with a few friends who brought up a very practical concern. They want to allocate part of their funds on-chain, but their biggest headache isn’t volatility—it’s that once positions and strategies are on-chain, they become publicly visible to everyone. You can prove you have sufficient reserves and comply with identity requirements, but your specific holdings and trading patterns? Those can’t be hidden. Transparency is great for retail users, but for institutions, it’s essentially going naked. After looking into @primus_labs’ approach, I think they’re addressing exactly this gap. They’re not building a new chain—they’re adding a layer on top of existing financial infrastructure. Institutions don’t need to move assets around; they can still verify what needs verification and keep what they want private—all on the same chain. They rely primarily on two technologies: zkTLS to prove that off-chain data is authentic (e.g., account balances, API responses) and that the source is legitimate—without revealing the full raw data. FHE to enable computation and verification on encrypted data, minimizing exposure of sensitive information. For the BNB ecosystem, if these capabilities are successfully implemented, the barrier for institutional capital to participate on existing chains will drop significantly. Privacy is preserved—without sacrificing verifiability. If you’re interested, check out their task portal: https://t.co/egqtcsAqA1 @primus_labs #PrimusLabs @KaitoAI