Change Details

In order to make it posible to update some parameters of a proof without having to sign the stakes again, we need to reduce the scope of what is signed by the stake. This means that we need to compensate this lack of stake signature score, and this diff creates a new proof signature to achieve that. The proof signs the limited proofid with the key corresponding to the master key, so that no one but the master key owner can update the proof without having the stake to sign again. Ref T1676. Depends on D10179.

In order to make it posible to update some parameters of a proof without having to sign the stakes again, we need to reduce the scope of what is signed by the stake. This means that we need to compensate this lack of stake signature score, and this diff creates a new proof signature to achieve that. The proof signs the limited proofid with the key corresponding to the master key, so that no one but the master key owner can update the proof without having the stake to sign again. The tests are updated to reflect the changes, however there is no information of what the proof master private key is for the cases cloned from the legacy vectors. As a consequence: - There is a comment to tell what key is used, so anyone can update the tests in the future - The tests cloned from the legacy vectors have their proof master key updated to make it possible to use a valid proof signature and keep the expected error the same - As a consequence to the master key change, there is one test case (Changing the master key affect ProofId) which is no longer relevant, as changing the key will raise a proof signature error and no longer a stake signature error, and ends up duplicated. This test case has been removed. Ref T1676. Depends on D10216.

In order to make it posible to update some parameters of a proof without having to sign the stakes again, we need to reduce the scope of what is signed by the stake. This means that we need to compensate this lack of stake signature score, and this diff creates a new proof signature to achieve that. The proof signs the limited proofid with the key corresponding to the master key, so that no one but the master key owner can update the proof without having the stake to sign again. The tests are updated to reflect the changes, however there is no information of what the proof master private key is for the cases cloned from the legacy vectors. As a consequence: - There is a comment to tell what key is used, so anyone can update the tests in the future - The tests cloned from the legacy vectors have their proof master key updated to make it possible to use a valid proof signature and keep the expected error the same - As a consequence to the master key change, there is one test case (Changing the master key affect ProofId) which is no longer relevant, as changing the key will raise a proof signature error and no longer a stake signature error, and ends up duplicated. This test case has been removed. Ref T1676. Depends on D10179216.