This repository stores dynamic data consumed by the Aragon application. It provides up-to-date information such as featured DAOs and sanctioned addresses.

The list of featured DAOs is available at: featured-daos.json

Each DAO entry is a JSON object with the following fields:

The list of sanctioned addresses is available at: sanctioned-addresses.json

This list is used to identify blockchain addresses that are restricted from accessing certain features of the Aragon application. The list is derived from the official OFAC Specially Designated Nationals (SDN) List.

Feature flags allow controlling feature visibility across different environments without code changes.

The feature flags configuration is available at: feature-flags.json

Feature flags can be configured in three formats:

{
    "subDao": true
}

{
    "subDao": {
        "local": true,
        "preview": false,
        "development": false,
        "staging": false,
        "production": false
    }
}

{
    "debugPanel": true,
    "subDao": {
        "local": true,
        "preview": false,
        "production": false
    }
}

• local - Local development
• preview - Preview deployments
• development - Development environment
• staging - Staging environment
• production - Production environment

1. Feature flags are first defined in code with default values
2. CMS overrides can modify these defaults per environment
3. Local cookie-based overrides (for debugging) take highest priority

Priority order:

Local override (cookie) > CMS override > Environment-specific (code) > Default (code)

1. The flag must first be defined in the codebase (featureFlags.config.ts)
2. The flag key must be added to the FeatureFlagKey type
3. Optionally, add the flag to this CMS file to override defaults

For more details, see the Feature Flags README in the application codebase.