Testnets
Testnets exist to help developers familiarize themselves with the taco-web API, and prototype an integration before deploying on TACo Mainnet. Testnets 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 NuCypher 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
domains.TESTNET // "tapir" network
DEVNET
domain, orlynx
, is a bleeding-edge developer network that supports the upcomingtaco
release.TESTNET
domain, ortapir
, is a stable testnet environment that supports the currenttaco
public release.
We encourage you to use the TESTNET
domain for developing TACo-based apps, and to use DEVNET
to test compatibility with the upcoming TACo release and new, experimental features.
Both DEVNET
and TESTNET
domains are unsuitable for use in a production setting. Testnet domains have no trust minimization or stability guarantees, which makes them unfit for production or real-world data payloads. Learn more about this in the trust assumptions section.
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 testnets can be found in their respective contract registries:
Last updated