{"push_id":3298934066,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"bbcb0735495a403aadf18e8ca3e46a14a6377d9c","before":"d247e3faa7b0f9f19ac5e1e3945587bc95a70f67","commits":[{"sha":"bbcb0735495a403aadf18e8ca3e46a14a6377d9c","author":{"name":"Dusty Phillips","email":"c3ae6b62c08142dd15ecc9efb867edf8743f5631@phillips.codes"},"message":"Verify note commitment when decrypting\n\nJust decrypting a note on a receipt is not enough.\nOne must also verify that the note is\nreally the one associated with that receipt.\nThis prevents maliciousness, but I think the main reason\nis that the nonsense bytes that occur when decrypting a note\nusing an incorrect key\ncould actually form a valid, but nonsense, note.\nConfirming the commitment ensures that the correct note was decrypted.","distinct":true,"url":"https://api.github.com/repos/BeanstalkNetwork/sapling_rust_api/commits/bbcb0735495a403aadf18e8ca3e46a14a6377d9c"}]}
{"actor":{"display_login":"dusty-phillips"}}