Testnet
Threshold Access Control is not currently supported by active/available infrastructure, including testnets. The network will be relaunched by WEDF in Q3 2026.
Until then, this page serves solely as a open source reference and blueprint for the community.
Testnet domains
To run TACo on testnet, it needs to be configured to use one of the two available domains:
import { domains } from '@nucypher/taco';
domains.DEVNET // "lynx" networkDEVNETdomain, orlynx, is a bleeding-edge developer network that supports the upcomingtacorelease.
DEVNET is unsuitable for use in a production setting since it does not have any trust minimization or stability guarantees, which makes it unfit for production or real-world data payloads. Learn more about this in the trust assumptions section.
Quick reference
Copy-paste these values to get started immediately. These examples use ethers v5 (npm install ethers@5.7.2), which TACo currently requires.
import { domains } from '@nucypher/taco';
import { ethers } from 'ethers';
const domain = domains.DEVNET;
const ritualId = 27; // Open ritual, no encryptor allowlist needed
// Provider must connect to Polygon Amoy (where DKG contracts live)
const provider = new ethers.providers.JsonRpcProvider(
'https://polygon-amoy.drpc.org'
);The provider configured above reads DKG coordination contracts on the L2 chain (Polygon Amoy for testnet, Polygon for mainnet). It is required by encrypt() and can also be used with decrypt(). In browser contexts, decrypt() typically uses a Web3Provider connected to the user's wallet instead. Neither provider determines which chains your conditions can target — conditions can reference any supported EVM chain.
Testnet configuration
Threshold Decryption
Threshold Signing
Contracts
The source code for contracts used on testnet can be found in nucypher/nucypher-contracts repository.
Contract addresses for testnet can be found in their respective contract registries:
Last updated