Mainnet Access

Developers should familiarize themselves with TACo's Testnet (Tapir) before requesting access to Mainnet TACo.

In order to use TACo in production – i.e. the fully decentralized version of TACo, with independent nodes managing access to data – adopting developers must be furnished with their own DKG public key. This persistent public key is used to encrypt application users' data, and is generated by a unique cohort of Threshold nodes via a DKG initialization ritual. Those same set of nodes then collectively manage access to data.

The public key – along with authority over the cohort – will be exclusively controlled by the developer until they decide to devolve that power to a DAO, multisig, or any kind of contract. Developers interested in their own mainnet DKG ritual must follow these steps:

(1) Make a request for a DKG ritual in the TACo discord server, which will be answered by TACo's core development team.

Once a DKG initialization commences, TACo's core dev team has no power to censor, block or control it in any way.

(2) Provide the Polygon wallet address you wish to designate as cohortAdmin. This address will exclusively control the cohort of nodes and public key. (3) Prepare the funds (in DAI) to pay mainnet usage fees. A single payment is made upfront, before the DKG initialization commences, and covers both parts of the fee model (duration & per-user). The total sum in DAI depends on: a. the number of nodes required (min. 30) b. the duration of node rental required (min. 12 months) c. the number of unique/reusable encryptors credits required (min. 100) For more details, see the Mainnet Fees section. (4) Complete the payment into a proxy contract, which will escrow the funds until the DKG initialization ritual is complete. When the ritual completes, the payment will be transferred.

The proxy contract address will be provided once the request for a Mainnet ritual is accepted.

In TACo's genesis era, the proxy contract will act as an temporarysponsorof the cohort. Note that the sponsor role does not have any power over the ritualID.Rather, the designated Polygon address – thecohortAdminrole – will have complete control.

(4) Complete the set-up by following the instructions in the TACo integration guide.