> For the complete documentation index, see [llms.txt](https://soundprotocol.gitbook.io/soundprotocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://soundprotocol.gitbook.io/soundprotocol/content-node/content-permissioning/unlock-conditions.md).

# Unlock conditions

Artists can tie ability to unlock any piece of content to any condition they choose—some unlock conditions native to the protocol, if the community chooses, could include:

* A payment being made
* Sufficient holding of an token
* Past streaming behavior attested by a discovery node, including but not limited to:

-following the artist

-streamed artist’s work more than a given number of times

-reposted artist’s content more than a number of times

The content node would look for the specified condition to be satisified to issue a proxy re-encryption key at the fan’s request.

By running their own content node, a artist could permission content in any additional way they see fit. Their node software can be modified to add new unlocking permission modules, serving as a testbed for modules to make their way into the core protocol too.