Skip to main content
The Color Palettes project is a community-driven initiative that maintains standardized brand colors for blockchain protocols, chains, and tokens used in Dune Analytics. Your contributions help analysts create consistent visualizations across their dashboards.

​
Why Contribute?

When creating visualizations on Dune, analysts frequently work with the same protocols and chains across different charts. Manually selecting colors for each visualization is:
  • Time-consuming
  • Prone to inconsistency
  • Difficult to maintain across multiple dashboards
By contributing to Color Palettes, you provide a single source of truth for protocol brand colors, ensuring consistency and saving valuable time for the entire community.

​
What You Can Contribute

New Protocol Colors

Submit brand colors for protocols not yet in the collection

Color Updates

Update existing color codes when brands refresh their visual identity

Alias Additions

Add new aliases for existing protocols to improve matching

Bug Reports

Report inconsistencies or issues with existing entries

​
Contribution Workflow

1

Fork the Repository

Create your own fork of the Color Palettes repository to work in.
2

Make Your Changes

Edit the color-palettes.json file following the schema requirements.See Adding New Protocol Colors for detailed instructions.
3

Test Locally

Validate your JSON changes are properly formatted and follow the schema.
4

Submit Pull Request

Create a pull request with a clear description of your changes.
Automated CI checks will run on your PR to validate schema compliance and detect alias conflicts.
5

Address CI Feedback

If CI checks fail, review the error messages and update your PR accordingly.See CI Validation Checks for details on automated validation.
6

Wait for Review

Maintainers will review your contribution and may request changes or clarifications.

​
Best Practices

​
Use Official Brand Colors

Always use the official brand colors when available. Check:
  • Official protocol websites
  • Brand guidelines and press kits
  • Protocol documentation
  • Official social media accounts
Avoid using colors from unofficial sources or making aesthetic choices. The goal is brand accuracy, not personal preference.

​
Choose Descriptive Aliases

Add aliases for common variations of the protocol name that users might search for:
Think about how the protocol appears in Dune query results:
Don’t use aliases that could refer to multiple protocols. For example, “BSC” could mean “Binance Smart Chain” or “Basis Cash”.See Understanding Alias Conflicts for resolution strategies.
All aliases should be lowercase as matching is case-insensitive:

​
Maintain Consistency

Follow Existing Patterns

Review existing entries to understand naming conventions and alias patterns

One Color Per Protocol

Use the primary brand color, not variations or secondary colors

Exact Hex Format

Always use 6-digit hex codes with the # prefix (e.g., #627EEA)

Alphabetical Order

While not required, maintaining alphabetical order helps readability

​
Pull Request Guidelines

​
PR Title Format

Use clear, descriptive titles:
  • ✅ Add Arbitrum Nova protocol colors
  • ✅ Update Ethereum brand color to match new guidelines
  • ✅ Add 'strk' alias for Starknet
  • ❌ Update colors
  • ❌ Fix

​
PR Description

Include in your PR description:
  1. What: Brief description of the change
  2. Why: Reason for the change (e.g., new protocol, rebranding, missing alias)
  3. Source: Link to official brand guidelines or documentation

​
Code of Conduct

Be Respectful and Collaborative

  • Be patient with review feedback
  • Engage constructively in discussions
  • Respect maintainer decisions
  • Help other contributors when possible

​
Getting Help

If you’re unsure about any aspect of contributing:
  1. Check existing issues and pull requests for similar cases
  2. Open a discussion issue before submitting a PR
  3. Tag maintainers for clarification
  4. Refer to the detailed guides:
Questions are always welcome! The community is here to help you contribute successfully.