Bitcoin Forum
May 06, 2024, 06:11:26 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 4 5 [6]  All
  Print  
Author Topic: BIP 17  (Read 9150 times)
interlagos
Hero Member
*****
Offline Offline

Activity: 496
Merit: 500


View Profile
January 30, 2012, 11:54:28 PM
 #101

I have a small question.
If two private keys always need to be kept separate,
how one would generate a single address which would combine both of them without having both of them on a single device at one point?
Even in the event that an attacker gains more than 50% of the network's computational power, only transactions sent by the attacker could be reversed or double-spent. The network would not be destroyed.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715019086
Hero Member
*
Offline Offline

Posts: 1715019086

View Profile Personal Message (Offline)

Ignore
1715019086
Reply with quote  #2

1715019086
Report to moderator
Costia
Newbie
*
Offline Offline

Activity: 28
Merit: 0



View Profile
January 31, 2012, 12:04:47 AM
 #102

for the address you only need the public keys and script - you can store those on the PC

for the redeeming transaction you need the signature, public key and script
you need the private key to make a signature
so:
PC creates <sig1> using key1
phone creates <sig2> using key2
phone sends <sig2> (not the key) to PC
the sig is valid only for this transaction, and it must belong to the public key in the address, this will end up being in the transaction anyway, so there are no "secrets" transmitted over the internet
PC puts everything together and creates a redeeming transaction
interlagos
Hero Member
*****
Offline Offline

Activity: 496
Merit: 500


View Profile
January 31, 2012, 12:13:34 AM
 #103

for the address you only need the public keys and script - you can store those on the PC

for the redeeming transaction you need the signature, public key and script
you need the private key to make a signature
so:
PC creates <sig1> using key1
phone creates <sig2> using key2
phone sends <sig2> (not the key) to PC
the sig is valid only for this transaction, and it must belong to the public key in the address, this will end up being in the transaction anyway, so there are no "secrets" transmitted over the internet
PC puts everything together and creates a redeeming transaction

Ok that explains it, thanks!
Pages: « 1 2 3 4 5 [6]  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!