Skip to content

Conversation

UdjinM6
Copy link
Contributor

@UdjinM6 UdjinM6 commented May 7, 2025

Bumping the limit for the upcoming version.

Copy link
Member

@PastaPastaPasta PastaPastaPasta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Concept ACK; I see no reason to not increase this in accordance with previous versions. This continues the trend from 1k initially to 2k, now to 4k.

Copy link
Collaborator

@knst knst left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM a91ffcf

@@ -142,6 +142,10 @@ Asset Unlock transactions might not be mined for multiple reasons. For example,
As a way to avoid a catastrophic failure if Platform is compromised, Core will limit credit pool withdrawals for at least the first release of Platform. The withdrawal limits may be re-evaluated and updated periodically as the system matures. To evaluate withdrawal validity, withdrawal amounts from the last 576 blocks should be tallied. The withdrawal should not be mined if:

* It requests more DASH than the credit pool contains
* The withdrawal would result in more than a 4000 DASH reduction in the credit pool over the past 576 blocks
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should consider moving the limits into a table with either this update or the next one. We're getting enough entries where that will make sense.

@thephez thephez merged commit 809e01d into dashpay:master May 21, 2025
PastaPastaPasta added a commit to dashpay/dash that referenced this pull request Jul 9, 2025
274000a feat: implement a fork to double withdrawals limit (UdjinM6)

Pull request description:

  ## Issue being fixed or feature implemented
  Implements dashpay/dips#165

  ## What was done?
  Bump the limit via new fork, add tests

  ## How Has This Been Tested?
  run test

  ## Breaking Changes
  n/a

  ## Checklist:
  - [ ] I have performed a self-review of my own code
  - [ ] I have commented my code, particularly in hard-to-understand areas
  - [ ] I have added or updated relevant unit/integration/functional/e2e tests
  - [ ] I have made corresponding changes to the documentation
  - [ ] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_

ACKs for top commit:
  kwvg:
    utACK 274000a

Tree-SHA512: 522224bf4770f64c887655dcc283dd7f729999338066af7c4211a77608222e370ac6154e4112fb476f1326555b38b2cf841f41a0998998ecdd641eb542adbbd0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants