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
      • Waku + Codex
      • 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
      • Protocol Architecture
      • Protocol Flow
      • UML Use Case Diagram
      • 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
  1. For Node Operators
  2. Getting Set Up

Minimum System Requirements

PreviousGetting Set UpNextRun a TACo Node with Docker

Last updated 3 months ago

TACo nodes are very light and can be run inexpensively on a remote instance or local machine. Specs similar to (or greater) than the following will suffice:

  • Debian or Ubuntu (recommended distributions)

  • 20GB storage

  • 4GB RAM

  • x86 architecture

  • Static IP address

  • Exposed TCP port 9151

TACo can be run on cloud infrastructure. For example, a Digital Ocean satisfies the requirements listed above.

Additionally, the operator account (i.e. not the provider) must be funded with at least 15 POL (Polygon POS) to connect to the Threshold Network and participate in DKG initialization rituals. Transfer these funds before running your node.

Note that TACo is currently in an invite-only beta phase, which implies a low volume of DKG rituals, and consequently, of POL spending, but the volume may increase in the future. Concerning this, DKG ritual costs may be reimbursed to node operators in later versions.

4GB Basic Droplet