## Onchain Exclusion Lists
### Problem Statement
The proliferation of zero knowledge products like mixers and rollups allow cryptocurrency users more opportunities for privacy than ever before. Unfortunately, it is often the case that tokens are deemed suspicious by default if associated with privacy enhancing technology of any kind. Projects, firms and individuals should feel comfortable accepting mixed or shielded funds, and have the option to reject funds that are associated with hacks, all while upholding the sender's privacy.

In order to know if mixed funds (such as onchain withdrawals from Tornado Cash, Railgun, zkBob, Aztec or others) are associated with hacks, any zero knowledge application (such as Proof of Innocence or Sandscreener) needs a definitive list of blocked addresses to reference. The integrity of the Exclusion List data is essential to the adoption of Exlist.

In order for public exclusion lists to be generally accepted and trusted, they require a reasonably reputable system to ensure that the addresses are 1) easily validated, 2) up-to-date and 3) not being added or removed by malicious actors.

The Sandscreener Public Exclusion Lists should be able to be stored in both a decrentalized and free (or cheap) manner. The lists should be maintained in a coordinated manner that is open source, well documented, standardized and technologically compatible with software that wishes to use it.