---
name: Trezu
description: Use when helping teams set up multisig treasuries, manage team members and roles, create and vote on payment/governance proposals, swap assets, or configure voting rules. Reach for this skill when users need to manage shared crypto wallets with governance controls, handle treasury requests, or set up confidential treasuries for private financial operations.
metadata:
    mintlify-proj: trezu
    version: "1.0"
---

# Trezu Skill

## Product Summary

Trezu is a non-custodial multisig treasury platform that lets teams securely manage crypto assets across multiple blockchains (Ethereum, Solana, Bitcoin, Polygon, NEAR, Sui, TON, Cardano, and 20+ others) through a shared wallet with role-based governance. Teams create treasuries, assign members with specific roles (Requestor, Finance, Governance), and require consensus voting to execute actions like payments, swaps, and configuration changes. Trezu supports both public treasuries (transparent transactions) and confidential treasuries (private shard on NEAR for financial privacy). Access the platform at https://trezu.app and comprehensive documentation at https://docs.trezu.org.

## When to Use

Reach for this skill when:
- A team needs to set up a multisig wallet with role-based permissions and voting thresholds
- Users want to create payment requests or bulk payments requiring team approval
- Members need to vote on financial or governance proposals
- Teams need to swap assets across blockchains
- Governance members must manage team membership, roles, or voting rules
- Users want to keep financial data private using confidential treasuries
- Teams need to connect hardware wallets (Ledger) for secure signing
- Users need to manage an address book for frequent payment recipients
- Teams want to fund or withdraw from treasuries on private shards

## Quick Reference

### Core Roles & Permissions

| Role | Can Create | Can Vote | Can Manage |
|------|-----------|----------|-----------|
| **Requestor** | Payments, swaps, staking requests | ❌ No | ❌ No |
| **Finance** | ❌ No | Payment/swap requests | ❌ No |
| **Governance** | Member/voting changes | Config requests | Members, voting rules |

### Key Workflows

| Task | Who | Steps |
|------|-----|-------|
| Create payment | Requestor | Payments → Fill recipient/token/amount → Review → Submit |
| Vote on payment | Finance | Requests → Click request → Approve/Reject → Confirm |
| Add team member | Governance | Members → Create request → Specify role → Submit for vote |
| Update voting threshold | Governance | Voting Settings → Create request → Set new threshold → Submit |
| Swap assets | Requestor | Exchange → Select from/to tokens → Enter amount → Review → Submit |
| Fund treasury | Any | Get deposit address → Send funds → Wait for confirmation |

### Voting Configuration

- **Voting Threshold**: Minimum approvals required for a proposal to pass (set separately for Governance and Finance)
- **Voting Duration**: Time window for members to vote (applies to all proposal types)
- **Finance Threshold**: Approvals needed for payments/swaps
- **Governance Threshold**: Approvals needed for member/rule changes

### Supported Chains

Ethereum, Solana, Bitcoin, Polygon, NEAR, Sui, TON, Cardano, Arbitrum, Aurora, Avalanche, Base, BNB Chain, Gnosis, Optimism, Starknet, and 10+ others.

## Decision Guidance

### When to Use Public vs Confidential Treasury

| Aspect | Public Treasury | Confidential Treasury |
|--------|-----------------|----------------------|
| **Financial visibility** | Anyone can see balances, payments, swaps | Only team members see details |
| **Proposal content** | Public can see what was proposed | Public sees proposal exists, not details |
| **Use case** | Open organizations, public funds | Private teams, sensitive payroll, confidential operations |
| **Funding method** | Direct deposits to treasury | Temporary deposit addresses or near.com confidential accounts |
| **Transaction execution** | Public blockchain | Private NEAR shard |

### When to Assign Each Role

| Situation | Role | Reasoning |
|-----------|------|-----------|
| Daily payment requests | Requestor | Creates proposals without voting power |
| Approving payments | Finance | Reviews and votes on financial requests |
| Team changes | Governance | Controls membership and voting rules |
| Operational separation | Requestor + Finance | Different people propose and approve |
| Small team | Requestor + Finance + Governance | One person handles all duties |

### Voting Threshold Strategy

| Treasury Size | Recommended Threshold | Rationale |
|---------------|----------------------|-----------|
| 2-3 members | 2 approvals | Prevents single-person control |
| 4-5 members | 2-3 approvals | Balances security and speed |
| 6+ members | 3+ approvals | Higher security for larger teams |
| Governance changes | Higher than Finance | Protect treasury rules from casual changes |

## Workflow

### Creating a Treasury and Setting Up Team

1. **Navigate to trezu.app** and click "Create Treasury"
2. **Choose treasury type**: Public (transparent) or Confidential (private shard)
3. **Add initial members**: Specify wallet addresses and assign roles (Requestor, Finance, Governance)
4. **Set voting thresholds**: Define minimum approvals for Finance and Governance proposals
5. **Set voting duration**: Choose time window for voting (e.g., 3 days)
6. **Review and confirm**: Verify all settings before creating

### Creating a Payment Request

1. **Navigate to Payments** in left sidebar
2. **Fill in payment details**: Recipient address, token, amount, blockchain network
3. **Use Address Book** (optional): Save frequent recipients for quick selection
4. **Add comment** (optional): Provide context for approvers
5. **Review payment**: Double-check recipient address and amount (irreversible)
6. **Submit request**: Request moves to Pending status for Finance members to vote

### Voting on a Payment Request

1. **Navigate to Requests** in left sidebar
2. **Filter by Request Type** → "Payments" (optional)
3. **Click on pending request** to view details
4. **Review**: Check recipient, amount, token, and requester's comment
5. **Verify treasury has funds**: If insufficient, request top-up before approving
6. **Cast vote**: Click Approve or Reject
7. **Confirm on wallet**: Sign the vote with your connected wallet

### Managing Team Members

1. **Navigate to Members** in left sidebar
2. **Click "Add Member"** or select existing member to edit
3. **Enter wallet address** and select roles (can assign multiple)
4. **Submit request**: Creates a governance proposal
5. **Governance members vote**: Request must reach voting threshold
6. **Automatic execution**: Once threshold met, member is added/updated

### Updating Voting Rules

1. **Navigate to Voting Settings** in left sidebar
2. **Click "Update Threshold"** or "Update Duration"**
3. **Specify new values**: New voting threshold or duration
4. **Submit request**: Creates governance proposal
5. **Governance members vote**: Only Governance role can vote
6. **Automatic execution**: Changes apply once threshold reached

### Swapping Assets

1. **Navigate to Exchange** in left sidebar
2. **Select "from" token**: Asset you want to swap
3. **Select "to" token**: Asset you want to receive
4. **Enter amount**: How much to swap
5. **Review quote**: Check exchange rate and 0.7% fee
6. **Submit request**: Swap request valid for 24 hours
7. **Finance members vote**: Must reach voting threshold within 24 hours

### Funding a Confidential Treasury

**Option 1: Temporary Deposit Address**
1. Navigate to treasury settings
2. Click "Generate Deposit Address"
3. Send funds to temporary address from external wallet
4. Funds auto-bridge to private shard within 72 hours
5. Address is single-use for privacy

**Option 2: near.com Confidential Account**
1. Create confidential account on near.com
2. Transfer assets to treasury account ID
3. Funds arrive in private shard

## Common Gotchas

- **Irreversible payments**: Double-check recipient address before submitting—funds cannot be recovered if sent to wrong address
- **Voting threshold too high**: If threshold exceeds number of active members, proposals will never pass; set threshold ≤ number of members
- **Governance role is powerful**: Governance controls membership and voting rules; assign only to highly trusted wallets and use high voting thresholds
- **Temporary deposit addresses expire**: Confidential treasury deposit addresses valid for 72 hours only; create new address if needed
- **Swap requests expire in 24 hours**: If swap doesn't reach voting threshold within 24 hours, it's automatically rejected
- **Finance role cannot vote on governance**: Finance members cannot approve member additions or voting rule changes; only Governance can
- **Requestor cannot vote**: Requestors create proposals but cannot vote on any requests; need Finance or Governance role to vote
- **Ledger derivation path mismatch**: If using Ledger, use same derivation path originally used with account to avoid key mismatch errors
- **Confidential treasury visibility**: Only team members can see balances and proposal details; public can see member list and vote counts
- **Payment without funds**: Can create payment request even if treasury lacks funds, but approval requires sufficient balance before execution
- **Multiple roles required for separation**: Best practice is to assign Requestor and Finance to different people to maintain separation of duties

## Verification Checklist

Before submitting work with Trezu:

- [ ] **Roles assigned correctly**: Verify each member has appropriate roles (Requestor, Finance, Governance) for their responsibilities
- [ ] **Voting threshold set**: Confirm threshold is ≤ number of active members and appropriate for treasury size
- [ ] **Recipient address verified**: For payments, double-check wallet address and blockchain network
- [ ] **Sufficient funds**: Confirm treasury has required tokens before approving payment requests
- [ ] **Governance separation**: Ensure Governance role not assigned to Requestors or Finance members
- [ ] **Voting duration reasonable**: Check voting duration allows time for team to review (e.g., 3+ days)
- [ ] **Ledger setup correct**: If using hardware wallet, confirm derivation path matches original account setup
- [ ] **Confidential treasury funding**: For private treasuries, verify deposit address is valid (72-hour window) or use near.com account
- [ ] **Swap quote reviewed**: Check exchange rate and 0.7% fee before submitting swap request
- [ ] **Request filters applied**: When reviewing requests, use filters to find relevant proposals (by type, requester, status)
- [ ] **Comments added**: For complex requests, add context comments to help approvers understand rationale

## Resources

**Comprehensive navigation**: See https://docs.trezu.org/llms.txt for complete page-by-page documentation index.

**Critical documentation pages**:
- [What is a Treasury](https://docs.trezu.org/what-is) — Core concepts, roles, governance model, security
- [Members and Roles](https://docs.trezu.org/governance/members-and-roles) — Permission matrix, role definitions, best practices
- [Confidential Treasuries](https://docs.trezu.org/confidential-treasuries) — Private shard operation, funding, proposal privacy

---

> For additional documentation and navigation, see: https://docs.trezu.org/llms.txt