Skip to content

Update JBRulesetConfig.md, pass in approvalHook as contract, not address #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jaderiverstokes wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update JBRulesetConfig.md, pass in approvalHook as contract, not address #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/v4/api/core/structs/JBRulesetConfig.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,9 +21,9 @@ project owner hasn't queued the subsequent ruleset with an explicit `weight`. If
equal weight. If the number is 90%, the next ruleset will have a 10% smaller weight. This weight is out of
`JBConstants.MAX_WEIGHT_CUT_PERCENT`.

- member: approvalHook An address of a contract that says whether a proposed ruleset should be accepted or
rejected. It
can be used to create rules around how a project owner can change ruleset parameters over time.
- member: approvalHook A contract which implements IJBRulesetApprovalHook and says whether a proposed ruleset
should be accepted or rejected. It can be used to create rules around how a project owner can change ruleset
parameters over time.

- member: metadata Metadata specifying the controller-specific parameters that a ruleset can have. These
properties cannot change until the next ruleset starts.
Expand Down