-
Notifications
You must be signed in to change notification settings - Fork 107
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Validate V5 transactions with Sapling shielded data (#2437)
* Make `verify_sapling_shielded_data` more generic Prepare to support V5 transactions which have a shared anchor. * Verify Sapling shielded data in V5 transactions Call the `verify_sapling_shielded_data` method and add the respective asynchronous checks to the set of V5 checks. * Fix expect message in V4 transaction test It was using the same message as the previous test, even though the test searches with different criteria. * Test V5 transaction with Sapling spends Create a fake V5 transaction that has Sapling spends and check that the verifier accepts the transaction. * Ignore rejected V5 transaction test for now Because now it needs the `sighash` implementation for V5 to be ready. * Reference V5 `sighash` PR in comment So that it is easier to check if it's possible to remove the `should_panic` or not. Co-authored-by: Alfredo Garcia <oxarbitrage@gmail.com> * Remove `sapling shielded pool` TODO V5 transactions now have Sapling shielded pool properly validated. * Link to some extra issues in TODO comment Some other issues are also necessary for full V5 validation. * Add a TODO in the main code to fix the tests Some tests are blocked due to missing features required for full V5 validation. Once those features are implemented, they should be updated to remove the `#[should_panic]` attribute so that they actually run and check the code correctly. Co-authored-by: Alfredo Garcia <oxarbitrage@gmail.com>
- Loading branch information
1 parent
d30b95d
commit f5bc527
Showing
2 changed files
with
76 additions
and
13 deletions.
There are no files selected for viewing
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 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