# Yearn Offchain Accounts Custodian Terms

## Overview

The **Accounts Custodian** is a single person with a 3-month renewable budget who maintains all offchain assets:
- Domains (AWS, Namecheap)
- Hosting (Vercel)
- Social accounts (X, Discord)
- Team infrastructure (Telegram, Google)

**Risk Acknowledgment**: Centralizing control under one person is a deliberate choice to avoid doxxing multiple team members while maintaining operational efficiency.

The 3-month budget renewal serves as the primary control mechanism for Custodian performance and trust, the same process that other yearn teams follow.

## Responsibilities

The Accounts Custodian:
- Has access over the "owner role" all offchain accounts. **`ychad.eth` is the owner of the assets, but it allows the custodian to operate the accounts on `ychad.eth`'s behalf.**
- Grants access to team members as directed by `ychad.eth`
- Can delegate admin rights only with `ychad.eth` approval
- Executes all `ychad.eth` decisions regarding accounts
- Ensures service continuity and team access

The delegation chain will be maintained in an internal document for yearn contributors to consult, and can only be changed with `ychad.eth` approval.

Example delegation chain:

- Custodian → Marketing Lead → Marketing Team (for X)
- Custodian → Web Lead → Developers (for Vercel)
- Custodian → Support Lead → Moderators (for Discord)

## Security Requirements

### Authentication (in order of preference)
1. **Hardware keys** (mandatory where available)
2. **App-based TOTP**
3. **SMS** (last resort only)

> The Account Custodian shall provide a complete list of Platforms and authentication security level, but at the moment all platforms are at least secured with app-based 2-factor.

### Device Policy
- **Dedicated device** used exclusively for account management
- Clean Linux or macOS installation (no Windows)
- Minimal software: secure browser only
- Prompt security updates

### Account Standards
- All accounts use @yearn.finance email
- Mandatory 2FA on all accounts
- 24-hour response for audit log requests

## Emergency Response

### Response Times
- **Emergency**: 2 hours (via emergency line)
- **Standard requests**: 24 hours

### Emergency Line Setup
- Custodian maintains 24/7 emergency line (e.g., PagerDuty)
- Any `ychad.eth` member can trigger emergency alerts
- Emergency alerts bypasses all notification suppressors

### Backup Coverage
- One backup person per platform (unnamed in public docs)
- Extended absence (>24h) requires team notification via Cantina

## Account Recovery & Legal Protection

### The Trust Problem

Since all accounts use @yearn.finance Gmail, **whoever controls Google controls everything.**

### Solution
The Custodian signs a legal contract with `ychad.eth` BORG establishing:
- @yearn.finance belongs to `ychad.eth`, not the Custodian
- The Custodian role is to execute `ychad.eth` decisions and abide by the terms of this contract

The contract should serve as legal grounds for `ychad.eth` to perform a Google account recovery if Custodian fails to abide by the terms of this contract.

# Documents mentioned across the term

- Assets Security Level Spreadsheet (TBD)
- Delegation Chain (TBD)

I will provide these documents (maybe as a single document) in the next week as I need to gather around the information to make it.