Threshold Access Control (TACo)
  • Getting Started
    • Introduction to TACo
    • How TACo Works
    • Quickstart (Testnet)
  • For Developers
    • Integrate TACo Into Apps
      • Testnets
      • Mainnet Access
      • Mainnet Deployment
    • Ecosystem Integrations
      • OrbisDB
      • Waku
      • Irys
      • ComposeDB
      • Turbo
    • API
      • Encryptor Allowlist
      • Encrypt & Decrypt
      • Authentication
        • Condition Context
      • Access Control
        • TimeCondition
        • RpcCondition
        • ContractCondition
          • Use custom contract calls
          • Implement access revocation via smart contract
        • JSON Endpoint Conditions
          • JsonApiCondition
          • JsonRpcCondition
        • JWT Conditions
        • Logical Conditions
          • CompoundCondition
          • IfThenElseCondition
          • SequentialCondition
        • WIP / Feature Requests
          • Any (Major) EVM Chain Condition Support
    • Blueprints & Inspiration
      • Seed phrase recovery & transfer
      • Digital Rights Management for on-chain assets
      • Trustless channels for journalists, archivists & whistleblowers
      • Crowdsourcing real-world data with trustless contribution
  • For Product Leads
    • Value Propositions
    • Capabilities & Extensions
    • Use cases
      • Seed phrase recovery & transfer
      • Digital Rights Management for on-chain assets
      • Trustless channels for journalists, archivists & whistleblowers
      • Crowdsourcing real-world data with trustless contribution
    • Mainnet Fees
    • Trust Assumptions
      • Mainnet Trust Disclosure (Provider Answers)
      • Mainnet Trust Model Foundation
      • Trust levers & parameter packages
  • Reference
    • Contract Addresses
    • Architecture
      • Porter
    • Github
    • TACo Playground
    • TACo Scan
  • For Node Operators
    • Getting Set Up
      • Minimum System Requirements
      • Run a TACo Node with Docker
    • Operations
      • TACo Node Management
      • TACo Node Recovery
      • Stake Authorization
    • Duties, Compensation & Penalties
    • Run a Porter Instance
Powered by GitBook
On this page
  • Testnet domains
  • Testnet configuration
  • Contracts
  1. For Developers
  2. Integrate TACo Into Apps

Testnets

PreviousIntegrate TACo Into AppsNextMainnet Access

Last updated 3 months ago

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.

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, 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 .

Testnet configuration

Domain
Network
L1 (chain id)
L2 (chain id)
Open ritualID
Cohort

DEVNET

Sepolia (11155111)

Amoy (80002)

27

2-of-3

TESTNET

Sepolia (11155111)

Amoy (80002)

6

3-of-5

Open ritualID 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 section to learn more.

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

Contracts

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.

section
encryptor allowlist
nucypher/nucypher-contracts
lynx.json
tapir.json
lynx
tapir