The Boost V2 Docs are under active development and will be subject to changes.
Smart Contract
Read the smart contracts
Typedoc
See technical documentation
SDK Implementation
See the source
Unless you’re an advanced user, you will likely never need to deploy your own and
registry
contract. The SDK
comes preconfigured with the correct contract addresses for all deployed core implementations.Registry
is just that, a registry of valid Action
, AllowList
,
Budget
, Incentive
and Validator
implementations that can be utilized and
extended by clients of the protocol.
Going forward, the term
component
in reference to a Boost, refers to any Action
, AllowList
, Budget
, Incentive
or Validator
.Action
, AllowList
, Budget
, Incentive
or Validator
interfaces that can then be leveraged in the creation of new Boosts.
In most cases, you’ll be interacting with the registry to initialize budgets that you can then use and reuse in your Boosts. For example,
What does it mean to clone
a base
implmentation?
Boost components aren’t instantiated traditionally, with parameters supplied to the contract’s constructor on deployment. Instead, to ensure each Boost component is compliant with a registered base implementation, and save on gas, components are either cloned from a deployed base contract and initialized ahead of time through registry before being referenced in Boost creation, or, for some components, initialized at time of Boost creation, like Incentives
.
A base implementation is any deployed contract registered with the registry, thus valid for use with Boost creation, that satisfies the interfaces for either Action
, AllowList
, Budget
, Incentive
or Validator
. For example, ManagedBudget is a base implementation that satisfies the Budget interface.