From 7aed67a60589e1078bff5b34d0070f16bfd174bc Mon Sep 17 00:00:00 2001 From: Arr00 <13561405+arr00@users.noreply.github.com> Date: Sat, 21 Feb 2026 17:19:33 -0700 Subject: [PATCH] Update zama config link --- content/confidential-contracts/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/confidential-contracts/index.mdx b/content/confidential-contracts/index.mdx index c70adf4c..f0df7c9b 100644 --- a/content/confidential-contracts/index.mdx +++ b/content/confidential-contracts/index.mdx @@ -5,7 +5,7 @@ title: Confidential Contracts A library of smart contracts that use ciphertext for amount, allowing for a wide variety of confidential use-cases, such as confidential tokens, auctions, vesting, voting etc. While the contracts are not written in an opinionated method (other than using the standard encrypted values published by Zama), for testing and examples in the documentation, the [Zama fhEVM](https://github.com/zama-ai/fhevm-solidity) will be used to operate on and decrypt [FHE](https://www.zama.ai/introduction-to-homomorphic-encryption) ciphertext. -All contracts must set their respective co-processor configuration during construction (or initialization). This can be done automatically by inheriting contracts in [`ZamaConfig`](https://github.com/zama-ai/fhevm/blob/v0.7.12/library-solidity/config/ZamaConfig.sol#L47-L73). +All contracts must set their respective co-processor configuration during construction (or initialization). This can be done automatically by inheriting https://github.com/zama-ai/fhevm/blob/e446c370002f62f193bbb5eb4075dea5d29a6996/library-solidity/config/ZamaConfig.sol#L96-L104[`ZamaEthereumConfig`]. ## Security