As we all know, one of the main obstacles, and also one of the main advantages of blockchain—openness and transparency—for various institutions such as fund management companies to enter the blockchain field is transparency. To address this issue, the BNB ecosystem has partnered with @primus_labs, enabling Bsc to better meet the needs of institutions by achieving "privacy default + on-demand verifiability" through a pluggable privacy and verification layer. BNB Chain's approach is to build programmable confidentiality, combining zero-knowledge proofs (ZKP) and fully homomorphic encryption (FHE) to support selective disclosure for regulatory compliance. So how are these key technologies implemented in the BNB ecosystem? This is where @primus_labs comes in. 1⃣ zkTLS (Zero-Knowledge TLS) This proves that data originates from a genuine Web2 source (exchange API, bank balance, custodian account, etc.) without exposing the original data or credentials. In June 2026, the zkTLS verification layer (provided by Primus Labs) was launched on the BNB Chain. 2. FHE (Fully Homomorphic Encryption) This allows direct computation on encrypted data (transfers, yield calculations, balance updates), with only the ciphertext visible on the chain. For example, the Primus Confidential Vault (already launched on BSC) allows users to "hide" their stablecoins as a encrypted version of EU, privately transferring funds or depositing them into a vault to earn yield, with the balance and amount remaining confidential. These are all pluggable layers, allowing direct integration into the BSC ecosystem without switching chains or migrating liquidity. The official BSC documentation also emphasizes this: "From Privacy Pools and ZKredit to native FHE support, the goal is to enable institutions to run regulated finance, RWA, and complex DeFi on-chain without having to choose between 'fully public' and 'fully private'." For institutions, this offers significant benefits in terms of confidential finance/trust and compliance, as well as support for RWA/Agent, etc. All of this relies heavily on the technical support of @primus_labs.