Tree: d363956ba1

master

patch-1

patch-2

v0.1.10

v0.1.2

v0.1.3

v0.1.5

v0.1.6

v0.1.7

v0.1.9

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'd363956ba1'

${ noResults }

Commit Graph

5 Commits (d363956ba1f2a27262691619cbc1853e4c482ab5)

Author	SHA1	Message	Date
Ryan X. Charles	79d79012d4	fix bug where you can't use isForMe without payloadKeypair It should be possible to check to see if a message isForMe with only the scanKeypair, and not the payloadKeypair. There was a bug where only the scanKeypair was being used to produce the receiveKeypair, but this was a mistake. Both the scanPubkey and payloadPubkey should be necessary to produce the receivePubkey, and both the scanPrivkey and payloadPrivkey should be necessary to produce the receivePrivkey. If an online computer has only the public keys of both (and the scanPrivkey), then that is good enough to check for isForMe.	11 years ago
Ryan X. Charles	a095341a07	print the public key	11 years ago
Ryan X. Charles	8b875a5926	making a keypair is unnecessary	11 years ago
Ryan X. Charles	aa4251bff6	typo	11 years ago
Ryan X. Charles	88f3690ef6	StealthMessage example	11 years ago