Skip to content
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.

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

New minimum values for peg-in and peg-out operations in the 2wp #219

Merged
merged 7 commits into from Oct 26, 2021

Conversation

pamgonzalez
Copy link
Contributor

@pamgonzalez pamgonzalez commented Mar 25, 2021

New minimum values for peg-in and peg-out operations in the 2wp

@SergioDemianLerner SergioDemianLerner added the Incomplete Incomplete Proposals label Mar 31, 2021
@marcos-iov marcos-iov force-pushed the peg-in-peg-out-set-minimums branch 2 times, most recently from 86a2521 to 7fb3098 Compare July 13, 2021 00:11
@marcos-iov marcos-iov requested review from SergioDemianLerner and a team July 13, 2021 00:13
IPs/RSKIP219.md Outdated Show resolved Hide resolved
IPs/RSKIP219.md Outdated Show resolved Hide resolved
@marcos-iov marcos-iov changed the title Draft for Minimum peg-in and peg-out New minimum values for peg-in and peg-out operations in the 2wp Jul 13, 2021
marcos-iov and others added 2 commits July 13, 2021 12:42
Co-authored-by: josedahlquist <jose.dahlquist@gmail.com>
@josedahlquist josedahlquist self-requested a review July 13, 2021 18:37
IPs/RSKIP219.md Outdated Show resolved Hide resolved
IPs/RSKIP219.md Outdated Show resolved Hide resolved
IPs/RSKIP219.md Outdated

After this RSKIP activation, the minimum value accepted to perform a peg-out is **0.004 RBTC**. If less than this amount is sent to the bridge address then those funds will be refunded to the user.
Additionally, a calculation of the fees to be paid by the user is made. If after subtracting the fees, the amount to be received by the user is less than the configured percentage of the total value trying to peg-out then the peg-out will not be completed and funds will be returned to the user.
The percentage is established on each network independently. The suggested value is 80%.
Copy link
Contributor

Choose a reason for hiding this comment

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

  • not sure what "each network" means
  • what does "suggested value" mean? Is it a default threshold that a user must explicitly override?

Copy link
Contributor

Choose a reason for hiding this comment

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

Each network -> regtest, testnet, mainnet

The value is defined in a constants file in rskj code, there is a different file for each network. It's currently set to %80 in mainnet

Copy link
Collaborator

Choose a reason for hiding this comment

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

At the current state of this RSKIP "suggested" should be replaced by the exact values that have been chosen for consensus for the different networks.

Copy link
Contributor

Choose a reason for hiding this comment

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

Updated

Copy link
Collaborator

@SergioDemianLerner SergioDemianLerner left a comment

Choose a reason for hiding this comment

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

Minor change requested, then ready to merge

IPs/RSKIP219.md Outdated

After this RSKIP activation, the minimum value accepted to perform a peg-out is **0.004 RBTC**. If less than this amount is sent to the bridge address then those funds will be refunded to the user.
Additionally, a calculation of the fees to be paid by the user is made. If after subtracting the fees, the amount to be received by the user is less than the configured percentage of the total value trying to peg-out then the peg-out will not be completed and funds will be returned to the user.
The percentage is established on each network independently. The suggested value is 80%.
Copy link
Collaborator

Choose a reason for hiding this comment

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

At the current state of this RSKIP "suggested" should be replaced by the exact values that have been chosen for consensus for the different networks.

@SergioDemianLerner SergioDemianLerner merged commit e4b4301 into master Oct 26, 2021
@marcos-iov marcos-iov deleted the peg-in-peg-out-set-minimums branch October 26, 2021 14:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Incomplete Incomplete Proposals
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants