Configuration Options

The Flodea Privacy Layer is designed to be fully modular and customizable per agent. Developers can configure privacy settings at the time of agent creation, during deployment, or through Flodea Controller after launch.

This section outlines how to enable, disable, and fine-tune the privacy features included in the Flodea Privacy Layer.

---

Modular Privacy Control

Each agent package includes a configuration file where privacy modules can be toggled individually.

Example Configuration (YAML)

privacy:
  network: tor
  wallet: stealth
  filesystem_encryption: true
  zk_access_control: true

Available values:

• network: none, tor, i2p, devpn

• wallet: standard, stealth, zk

• filesystem_encryption: true or false

• zk_access_control: true or false

---

Configuration Methods

Method	Description
Agent Manifest File	Configure privacy modules during agent build
Flodea SDK CLI	Apply settings via command-line arguments during packaging
Runtime Flags	Adjust privacy behavior dynamically at runtime
Controller Dashboard	Update settings for running agents in managed environments

---

Networking Options

Mode	Description
none	No privacy routing. Default for public agents
tor	Route traffic through the Tor network
i2p	Use the I2P anonymizing layer
devpn	Connect via decentralized VPN (if supported by node)

Additional settings:

• Custom bridges and hidden services (Tor)

• Peer-to-peer routing configuration (DeVPN)

---

Wallet Privacy Options

Mode	Description
standard	Basic EVM-compatible wallet
stealth	One-time stealth address generation and transaction masking
zk	Use of zk-based wallets for anonymous transfer and signing

Wallet configuration also supports:

• Multi-wallet rotation

• Integration with on-chain mixers

• Chain-specific zk wallet providers

---

File System Encryption

Option	Description
Enabled	All agent files are encrypted at rest
Disabled	Agent files are stored in plaintext

Key management:

• Encryption keys are auto-generated per agent

• Optional external key injection via environment variables or vault

---

Zero-Knowledge Access Control

This module allows agents to request or verify access to resources without revealing identity.

Configurable Parameters

• zk proof expiration duration

• Allowed credential schemas

• On-chain vs off-chain verifier endpoints

Use cases:

• DAO voting access

• Role-based compute execution

• Confidential content unlocks

---

Performance Considerations

While privacy modules add overhead, each feature is optimized for minimal performance impact.

Module	Estimated Overhead
Tor Networking	10–20 percent latency increase
Stealth Wallet	Minimal, depends on zk layer
Encrypted Storage	Moderate I/O penalty
ZK Access Control	Depends on proof generation complexity

---

Best Practices

• Only enable the modules needed for the agent’s mission

• Use encrypted filesystem and Tor together for confidential agents

• Rotate wallets periodically for long-running agents

• Validate zk proofs off-chain for faster execution when possible