feat: add first version of the prover of sent UTXO#903
Conversation
|
I wonder if there's a integration test that also verifies a successfully generated proof-of-transfer? I don't see it but I might be missing something. |
|
@aszepieniec |
|
Have a look at |
3ee2de8 to
946a7d7
Compare
aszepieniec
left a comment
There was a problem hiding this comment.
I should like to try to send you a proof-of-transfer of a payment that never happened.
- If I fail, then that helps to convince me that the construction is sound.
- If I succeed, then that ought to convince you that the construction is not sound.
However, as far as I can see, all changes are in neptune-core/. I don't see how you would process that proof-of-transfer, even if I managed to generate one. I would have expected a neptune-cli command, or a new option in neptune-dashboard. Just exposing a new RPC interface is not enough. It doesn't make any sense to have proofs-of-anything if no-one is capable of verifying them.
|
Let me add this there. Is there any way to see sent txs? I have not found last time I checked. An answer would help to make this smoother, as without that I could offer only what will come to my snall mind. P.s. Probably it's because I struggle a bit to wrap my head around those starting from why it's a different crate instead of maybe a feature of the core. I guess I was trying to get it at #861 . |
Not presently, no. I guess this is the down side of a privacy preserving ledger. There is no link between the individual user-initiated transactions and the aggregate transactions that appear in blocks on the blockchain. So a minimalistic client that deals just with blockchain data doesn't know what to show the user. I recall articulating a desire once for a |
this version is limited to native coin without the time-lock it's the first Non-consensus Triton program in the system available to an user
d072a6e to
ea3fd05
Compare
skaunov
left a comment
There was a problem hiding this comment.
Added both commands (prove-an-transfer, verify-transfer, sorry for the names - just change any after merging). I started to document it too but stopped myself: probably something will change again, and you will be reviewing the code anyway which seems to be self-explaining. And I'm glad to provide docs/explanations if/where those would help. In short proving command takes optional args and without these it just proves all the coins (except change) for last sent via the tip of the node.
Let's try this out like you said, pls!
to save all succesful proofs in different files
this version is limited to native coin without the time-lock
it's the first Non-consensus Triton program in the system available to an user
it was already discussed in depth since I did not know with which part to start (the other part is the reserves proving)