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

Adds 'should reject and refund a legacy pegin from a multisig account… #99

Conversation

jeremy-then
Copy link
Contributor

Adds 'should reject and refund a legacy pegin from a multisig account with the value exactly minimum' test.

This test asserts that doing a legacy pegin from from a multisig will be rejected with rejection reason 2 (legacy pegin multisig sender), and the funds will be refunded back to the sender and the transaction will be marked as processed by the Bridge.

@jeremy-then jeremy-then self-assigned this Sep 25, 2024
@jeremy-then jeremy-then requested a review from a team as a code owner September 25, 2024 02:15
@jeremy-then jeremy-then force-pushed the add-pegin-v1-below-minimum-test branch from 737bb82 to 87238e9 Compare October 1, 2024 01:27
@jeremy-then jeremy-then force-pushed the add-legacy-pegin-from-multisig-test branch from f0c37e5 to 8082c93 Compare October 1, 2024 16:35
…ere we create multiple accounts to avoid issues of one uxto being used to fund the other account and leaving the first account without funds.
Copy link

sonarqubecloud bot commented Oct 1, 2024

@jeremy-then
Copy link
Contributor Author

#109

@jeremy-then jeremy-then closed this Oct 2, 2024
@marcos-iov marcos-iov deleted the add-legacy-pegin-from-multisig-test branch October 8, 2024 15:52
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.

1 participant