You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This iteration of managed budget tracks BoostCore deployments that the
budget targets over time, and allows managers to interact with
deprecated versions via overloaded functions. Since much of the security
model for boosts is contained in BoostCore, managers cannot access a
boost core deployment that was not already set by an admin.
management fee payouts on BoostCore against boosts not
deployed by a budget fail thanks to pre-existing logic that tracks
disbursements and stores the incentive address. If the incentive address
in the boost does not match that of the disbursement, it will fail, and replays against multiple BoostCore deployments will fail
This iteration of managed budget tracks BoostCore deployments that the
budget targets over time, and allows managers to interact with
deprecated versions via overloaded functions. Since much of the security
model for boosts is contained in BoostCore, managers cannot access a
boost core deployment that was not already set by an admin.
management fee payouts on BoostCore against boosts not
deployed by a budget fail thanks to pre-existing logic that tracks
disbursements and stores the incentive address. If the incentive address
in the boost does not match that of the disbursement, it will fail.
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Are you sure you want to be submitting a change without including a changeset? If you're just changing docs or tests, you probably don't need to. See the publishing section of the README for more info.
Are you sure you want to be submitting a change without including a changeset? If you're just changing docs or tests, you probably don't need to. See the publishing section of the README for more info.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This iteration of managed budget tracks BoostCore deployments that the
budget targets over time, and allows managers to interact with
deprecated versions via overloaded functions. Since much of the security
model for boosts is contained in BoostCore, managers cannot access a
boost core deployment that was not already set by an admin.
management fee payouts on BoostCore against boosts not
deployed by a budget fail thanks to pre-existing logic that tracks
disbursements and stores the incentive address. If the incentive address
in the boost does not match that of the disbursement, it will fail, and replays against multiple BoostCore deployments will fail