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
  • Introduction
  • Allowlist
  • Allowlist on testnet
  1. For Developers
  2. API

Encryptor Allowlist

PreviousAPINextEncrypt & Decrypt

Last updated 3 months ago

Introduction

The Encryptor Allowlist is a simple access control mechanism that only allows specific data producers, or encryptors, to access a given DKG ritual, cohort of TACo nodes, and associated public key. In practice, it means that developers can limit who can use TACo to encrypt the data using the persistent public key.

The entity that can authorize encryptors is called the authority. Each ritual has an authority which corresponds to the address of the wallet that initiated the ritual.

Allowlist

In TACo's genesis era, the process of initializing the ritual and managing the allowlist is simplified to the following steps:

  1. User shares their authority address with the testnet operator.

  2. The testnet operator initiates the ritual for the user, marking them as the authority for that ritual.

  3. Now, the user can manage their encryptor allowlist using their authority. So the user adds a new encrypter to the allowlist.

  4. The user can now use the encryptor in taco to encrypt their data.

Allowlist on testnet

In the early era, it is possible to use one of the premade rituals on the testnet without any extra steps outlined in the setup above. You can simply configure taco to use one of those rituals and use any encryptor (wallet address) to perform the encryption.

The current ritual configurations are located in the section.

Testnet integration