<aside> 🗣️

Network Name: Fhenix Nitrogen RPC URL: https://api.nitrogen.fhenix.zone Chain ID: 8008148 Currency Symbol: TFHE Block Explorer: https://explorer.nitrogen.fhenix.zone Websocket: wss://api.nitrogen.fhenix.zone:8548

Bridge: https://bridge.nitrogen.fhenix.zone/

</aside>

🔐 Key Features

• Introduces Security Zones for multiple encryption configurations
• Enables confidential smart contracts on public blockchain
• Computation on encrypted data without decryption (FHE)
• Connected to Sepolia testnet with bridge 🔄 Security Zones (New Feature)

🔄 What Are Security Zones?

• Multiple encryption key sets coexisting on single network
• Different security/performance trade-offs
• Use-case specific configurations
• Currently pre-generated (not dynamically created)

Available Zones in Nitrogen

1. Zone 0 (Default) - NEW Threshold Network
   • Uses 3-out-of-4 party consensus for decryption
   • Each party holds only partial key ("secret share")
   • Highest security level
   • No special code needed - default behavior
2. Zone 1 - Legacy Local Key
   • Similar to previous testnet behavior
   • Sequencer holds decryption key
   • Faster performance
   • Must be explicitly specified in code

Zone Usage Examples

function addSecZone0(n1 inEuint32, n2 inEuint32) {
    euint32 first = FHE.asEuint32(n1); // This implicitly uses Security Zone 0
    euint32 second = FHE.asEuint32(n2, 0); // This also uses Security Zone 0

    euint32 result = first + second; // `result` will be marked 'security zone 0' automatically
}

function addSecZone1(n1 inEuint32, n2 inEuint32) {
    euint32 first = FHE.asEuint32(n1, 1); // To use a non-default SZ, you have to be explicit
    euint32 second = FHE.asEuint32(n2, 1);

    euint32 result = first + second; // `result` will be marked 'security zone 1' automatically
}

⚡ Parallel Decryptions (New Feature)

• NEW: Asynchronous decryption with synchronous experience
• NEW: Special transaction queue for decryption requests
• NEW: Automatic handling of decryption coordination