Tree: 1516ad3012

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 '1516ad3012'

${ noResults }

Commit Graph

6 Commits (1516ad3012a027f2346510a3d211488d84efd895)

Author	SHA1	Message	Date
Ryan X. Charles	1bda566679	stealth address to/from JSON	10 years ago
Ryan X. Charles	cfd509f859	make receivePubkey compatible with dark wallet I had been using this formula for the receiveKeypair: scanKeypair + payloadKeypair + sharedKeypair However, Dark Wallet uses this formula: payloadKeypair + sharedKeypair It is not actually necessary to add the scanKeypair in order to have all the features of stealth addresses, at least as far as I can tell. So in order to bring my implementation closer to Dark Wallet's, I have removed the scanKeypair from this calculation.	10 years ago
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.	10 years ago
Ryan X. Charles	d1a570135d	getSharedKeypair & getReceivePubkey	11 years ago
Ryan X. Charles	48ae69cab0	convenience: StealthAddress(str) or StealthAddress(buf)	11 years ago
Ryan X. Charles	139fe02355	StealthAddress	11 years ago