Mainnet Fees

Adopting developers pay in advance for use of TACo mainnet by transacting with the relevant contract, triggering the cohort formation to have a group of TACo nodes under their exclusive control. There are two key roles associated with a given DKG ritual:

  • sponsor: This address sends the initial transaction, triggering the cohort formation, and also paying the upfront fees. This address does not have any special privileges or power over the cohort of nodes. Indeed, any EOA can create a new cohort or sponsor an existing cohort.

  • cohortAdmin: This address has unilateral control over the parameters governing the cohort of nodes. Note that the cohortAdmin address does not have to participate during the initiation process.

The sponsor and cohortAdmin roles can use the same address or use different addresses. For example, the cohortAdmin could be a cold wallet address, while the sponsor might simply be a one-off software address. External developers may also prefer to set a DAO, a Multisig, or any kind of smart contract as the cohortAdmin, which would reduce the trust burden on their end-users with respect to control over encryptors and the TACo cohort.

Currently, cohort formation is not permissionless and must be pre-approved in the Coordinator contract by the NuCypher team. Prospective sponsors should follow the instructions on the Mainnet Integration page.

Fee structure

Threshold Decryption

Adopting developers pay for the TACo service via a dual fee model, which covers:

  1. Availability of the service, via a duration-based fee Currently 0.75 DAI per node per day

  2. Usage of the service via a fee based on the number of unique data producer identities encrypting data at any one time Currently 2.5 DAI per encryptor slot per year Note that encrypting privileges can be added and removed from identities/addresses at will, without charge or limit, provided the sponsor has pre-paid for sufficient credits and there are encryptor slots available.

There is no charge, payment gate or limit on:

  • encryptions

  • types or combinations of conditions specified

  • unique requestor identities

  • throughput/number of requests

  • decryptions

  • condition validations/invalidations

  • additions/removals of addresses to/from the authAdmin list

  • additions/removals of addresses to/from the encryptor allowlist

  • any other communication with the network or API

Threshold Signing

TACo Threshold Signing is currently in alpha and available only on the DEVNET environment.

The fee structure is still TBD but may include:

  • Cohort rental duration-based fee

  • Tiers for number of chains

  • Add-on for persistent caching of previously valid signatures in spite of cohort rotation

There is not charge for:

  • signatures

  • types or combinations of conditions specified

  • throughput/number of requests

  • any other communication iwth the network or API

PreviousTrust levers & parameter packagesNextContract Addresses

Last updated