Testnets
Last updated
Last updated
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 node array managing decryption fragments and validating condition fulfillment. Testnet nodes are are operated primarily by members of the NuCypher core developer team, and are not subject to a cryptoeconomic protocol nor required to stake any collateral.
To run TACo on testnet, it needs to be configured to use one of the two available domains:
DEVNET
domain, or lynx
, is a bleeding-edge developer network that supports upcoming taco
release.
TESTNET
domain, or tapir
, is a stable testnet environment that supports the current taco
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 .
DEVNET
Sepolia (11155111)
Amoy (80002)
2-of-3
TESTNET
Sepolia (11155111)
Amoy (80002)
3-of-5
Contract addresses for testnets can be found in their respective contract registries:
The source code for contracts used on testnet can be found in repository.