Testnet

Testnet exists to help developers familiarize themselves with the taco-web API, and prototype an integration before deploying on TACo Mainnet. Testnet should not be utilized in production with any expectation of a trust-minimized integration.

Hence, the trust assumptions are strictly worse than the Mainnet version, particularly with respect to the nodes managing decryption fragments, signing wallets, and validating condition fulfillment. Testnet nodes are are operated primarily by the TACo team, and are not subject to a crypto-economic protocol nor required to stake any collateral.

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" network

• DEVNET domain, or lynx, is a bleeding-edge developer network that supports the upcoming taco release.

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 [email protected]), which TACo currently requires.

Lynx (bleeding-edge)

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

Domain	Network	L1	L2	Open Ritual ID	Cohort
DEVNET	lynx	Sepolia (11155111)	Amoy (80002)	27	2-of-3

Open Ritual ID refers to a DKG cohort & public key with no restrictions on encryptors – i.e. any device or address can use the public key to encrypt data. See the encryptor allowlist section to learn more.

It should be noted that the blockchains used as L1 and L2 in the various TACo domains (DEVNET, MAINNET) do not determine the blockchains supported by the TACo conditions. For example, the DEVNET can be used to define conditions on Ethereum mainnet.

Threshold Signing

Domain	Network	L1	Open Cohort ID	Cohort	Supported Chains
DEVNET	lynx	Sepolia (11155111)	1	2-of-3	84532 (Base) 11155111 (Sepolia)

Open Cohort ID refers to a signing cohort with a policy condition that always passes and therefore there are no restrictions on what it will sign – i.e. any signing request will be fulfilled.

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:

• lynx.json