Glossary
| Term | Preview |
|---|---|
| Project | TLDR: A Juicebox project is an NFT (ERC-721) representing ownership and permissions for managing project-specific transactions. Each Juicebox project's 721 is managed in the |
| Ruleset | TLDR: A set of configurable, time-locked rules that define how a Juicebox project operates. A project is expressed in terms of rulesets. A ruleset outlines the time-locked rules according to which a project wishes to operate. It is represented as a |
| Tokens | TLDR: Tokens minted for a project based on its ruleset, optionally issued as ERC-20 tokens or integrated with a custom token. The Juicebox protocol keeps track of tokens for each project. When a payment is made to a project, the protocol mints tokens for a specified beneficiary according to the rules of the project's current ruleset. Tokens are managed in the Projects can also bring their own token, so long as it adheres to the |
| Surplus | TLDR: Funds exceeding a project's payout limit, reclaimable by its community through token cash-outs. The |
| Weight cut percent | TLDR: Defines how a project's token distribution changes over time by reducing its weight in each ruleset cycle.
|
| Cash out tax rate | TLDR: A project's configurable tax rate on surplus funds when tokens are cashed out.
|
| Reserved tokens | TLDR: A percentage of newly minted tokens reserved for specific addresses or allocations.
|
| Splits | TLDR: Preprogrammed distributions of funds or tokens to addresses, contracts, or Juicebox projects. A Split is used to send a percent of a total amount to a preprogrammed address, Juicebox project, contract that inherits from |
| Split hook | TLDR: A contract that processes specific actions when splits are distributed. A project can preconfigure splits to be directed to any contract that adheres to |
| Ruleset approval hook | TLDR: A contract specifying conditions for approving or reconfiguring a project's ruleset.
An approval hook contract can be written to incorporate strict community review times or voting requirements in order to make ruleset changes, or to simply add a required wait period between when a change is proposed and when it can take effect. Learn more |
| Terminal | TLDR: A contract managing a project's incoming and outgoing funds, with support for multiple terminals and primary terminal settings. A project can be configured to use any contract that adheres to |
| Data hook | TLDR: Custom logic executed during payments or cash-outs, defined in a project's ruleset.
Including a data hook allows projects to customize what happens when a payment is attempted to the project during a ruleset, and what happens when a token is attempted to be cashed out during a ruleset. Learn more |
| Pay hook | TLDR: A contract triggered after payments are processed for additional project-defined logic. When a project receives a payment, its ruleset's data hook can specify the address of a contract that adheres to the |
| Cash out hook | TLDR: A contract triggered when project tokens are cashed out, enabling custom redemption behavior. When a project's tokens are being cashed out, its ruleset's data hook can specify the address of a contract that adheres to the These can be used by projects to customize what happens when it receives payments and when someone redeems its tokens. Learn more |
| ERC721 reward tiers | TLDR: Allows projects to distribute tiered NFTs to contributors, optionally usable for token cash-outs. A project can use the tiered ERC721 hook if it wishes to distribute NFTs from any number of tiers to addresses who contribute during a particular set of rulesets. These 721s can optionally then be used for cash outs instead of the standard project tokens. Learn more |
| Operator | TLDR: Delegated addresses with specific permissions to act on behalf of another address in the Juicebox ecosystem. Addresses can give permissions to any other address to take specific actions throughout the Juicebox ecosystem on their behalf. These addresses are called Operators, and are managed through the |