Friendly addresses with enhanced privacy - Revision history

Amincd: /* UnSpammable Publication of Friendly Address Owners' Public Keys */

2012-04-12T02:17:37Z

UnSpammable Publication of Friendly Address Owners' Public Keys

← Older revision		Revision as of 02:17, 12 April 2012
Line 69:		Line 69:
	==UnSpammable Publication of Friendly Address Owners' Public Keys==		==UnSpammable Publication of Friendly Address Owners' Public Keys==

	Using the Namecoin block-chain, it is possible ~~for~~ the friendly address owner to publish their pubkey for secure communication with their friendly address, without also enabling an attacker to make large numbers of desirable user accounts of any given domain unavailable by publishing ownership over them in the bitcoin block-chain without the domain owner's permission. The scheme, proposed by Amincd [https://bitcointalk.org/index.php?topic=74572.msg847022#msg847022 here], would work as follows:		Using the Namecoin block-chain, it is possible to enable the friendly address owner to publish their pubkey for secure communication with their friendly address, without also enabling an attacker to make large numbers of desirable user accounts of any given domain unavailable by publishing ownership over them in the bitcoin block-chain without the domain owner's permission. The scheme, proposed by Amincd [https://bitcointalk.org/index.php?topic=74572.msg847022#msg847022 here], would work as follows:

	*A relay server registers example.bit in the namecoin block-chain.		*A relay server registers example.bit in the namecoin block-chain.

Amincd: /* UnSpammable Publication of Friendly Address Owners' Public Keys */

2012-04-11T21:38:23Z

UnSpammable Publication of Friendly Address Owners' Public Keys

← Older revision		Revision as of 21:38, 11 April 2012
Line 79:		Line 79:
	* Once Bob finds the spend, he considers the pubkey used for the spend as example.bit's official pubkey for signature verification		* Once Bob finds the spend, he considers the pubkey used for the spend as example.bit's official pubkey for signature verification
	* Bob asks example.bit for a digital signature of alice@example.bit, and uses example.bit's published pubkey to verify the signature was made by example.bit's official privkey		* Bob asks example.bit for a digital signature of alice@example.bit, and uses example.bit's published pubkey to verify the signature was made by example.bit's official privkey
	* Bob scans the bitcoin block-chain for the earliest spend to base58(ripemd160(example.bit-signature("alice@example.bit") +checksum), and ~~obtain's~~ Alice's pubkey		* Bob scans the bitcoin block-chain for the earliest spend to base58(ripemd160(example.bit-signature("alice@example.bit") +checksum), and obtains Alice's pubkey
	* There is no way the owners of example.bit could have cheated and given Bob a different signature for alice@example.bit than they gave to Alice when she published her pubkey, because every namecoin domain can only ever have one official pubkey, that can never be altered		* There is no way the owners of example.bit could have cheated and given Bob a different signature for alice@example.bit than they gave to Alice when she published her pubkey, because every namecoin domain can only ever have one official pubkey, that can never be altered

	[[Category:Technical]]		[[Category:Technical]]

Amincd at 21:35, 11 April 2012

2012-04-11T21:35:11Z

← Older revision		Revision as of 21:35, 11 April 2012
Line 69:		Line 69:
	==UnSpammable Publication of Friendly Address Owners' Public Keys==		==UnSpammable Publication of Friendly Address Owners' Public Keys==

	Using the Namecoin block-chain, it is possible for the friendly address owner to publish their pubkey for secure communication with their friendly address, without also enabling an attacker to make large numbers of desirable user accounts of a domain unavailable by publishing ownership over them in the bitcoin block-chain without the domain owner's permission. The scheme, proposed by Amincd [https://bitcointalk.org/index.php?topic=74572.msg847022#msg847022 here], would work as follows:		Using the Namecoin block-chain, it is possible for the friendly address owner to publish their pubkey for secure communication with their friendly address, without also enabling an attacker to make large numbers of desirable user accounts of any given domain unavailable by publishing ownership over them in the bitcoin block-chain without the domain owner's permission. The scheme, proposed by Amincd [https://bitcointalk.org/index.php?topic=74572.msg847022#msg847022 here], would work as follows:

	*A relay server registers example.bit in the namecoin block-chain.		*A relay server registers example.bit in the namecoin block-chain.
Line 81:		Line 81:
	* Bob scans the bitcoin block-chain for the earliest spend to base58(ripemd160(example.bit-signature("alice@example.bit") +checksum), and obtain's Alice's pubkey		* Bob scans the bitcoin block-chain for the earliest spend to base58(ripemd160(example.bit-signature("alice@example.bit") +checksum), and obtain's Alice's pubkey
	* There is no way the owners of example.bit could have cheated and given Bob a different signature for alice@example.bit than they gave to Alice when she published her pubkey, because every namecoin domain can only ever have one official pubkey, that can never be altered		* There is no way the owners of example.bit could have cheated and given Bob a different signature for alice@example.bit than they gave to Alice when she published her pubkey, because every namecoin domain can only ever have one official pubkey, that can never be altered

			[[Category:Technical]]

Amincd: /* UnSpammable Publication of Friendly Address Owners' Public Keys */

2012-04-11T21:27:51Z

UnSpammable Publication of Friendly Address Owners' Public Keys

← Older revision		Revision as of 21:27, 11 April 2012
Line 80:		Line 80:
	* Bob asks example.bit for a digital signature of alice@example.bit, and uses example.bit's published pubkey to verify the signature was made by example.bit's official privkey		* Bob asks example.bit for a digital signature of alice@example.bit, and uses example.bit's published pubkey to verify the signature was made by example.bit's official privkey
	* Bob scans the bitcoin block-chain for the earliest spend to base58(ripemd160(example.bit-signature("alice@example.bit") +checksum), and obtain's Alice's pubkey		* Bob scans the bitcoin block-chain for the earliest spend to base58(ripemd160(example.bit-signature("alice@example.bit") +checksum), and obtain's Alice's pubkey
	* There is no way the owners of example.bit could have cheated and given Bob a different signature for alice@example.bit than they gave to Alice when she published her pubkey, because every namecoin ~~address~~ can only ever have one official pubkey, that can never be altered		* There is no way the owners of example.bit could have cheated and given Bob a different signature for alice@example.bit than they gave to Alice when she published her pubkey, because every namecoin domain can only ever have one official pubkey, that can never be altered

Amincd: /* UnSpammable Publication of Friendly Address Owners' Public Keys */

2012-04-11T20:36:28Z

UnSpammable Publication of Friendly Address Owners' Public Keys

← Older revision		Revision as of 20:36, 11 April 2012
Line 69:		Line 69:
	==UnSpammable Publication of Friendly Address Owners' Public Keys==		==UnSpammable Publication of Friendly Address Owners' Public Keys==

	Using the Namecoin block-chain, it is possible for the friendly address owner to publish their pubkey for secure communication with their friendly address, without also enabling an attacker to make large numbers of desirable user accounts of ~~domains~~ unavailable by publishing ownership over them without the domain owner's permission ~~in the bitcoin block-chain~~. The scheme, proposed by Amincd [https://bitcointalk.org/index.php?topic=74572.msg847022#msg847022 here], would work as follows:		Using the Namecoin block-chain, it is possible for the friendly address owner to publish their pubkey for secure communication with their friendly address, without also enabling an attacker to make large numbers of desirable user accounts of a domain unavailable by publishing ownership over them in the bitcoin block-chain without the domain owner's permission. The scheme, proposed by Amincd [https://bitcointalk.org/index.php?topic=74572.msg847022#msg847022 here], would work as follows:

	*A relay server registers example.bit in the namecoin block-chain.		*A relay server registers example.bit in the namecoin block-chain.

Amincd: /* UnSpammable Publication of Friendly Address Owners' Public Keys */

2012-04-11T20:31:42Z

UnSpammable Publication of Friendly Address Owners' Public Keys

← Older revision		Revision as of 20:31, 11 April 2012
Line 69:		Line 69:
	==UnSpammable Publication of Friendly Address Owners' Public Keys==		==UnSpammable Publication of Friendly Address Owners' Public Keys==

	Using the Namecoin block-chain, it is possible for the ~~sender~~ to publish their pubkey for secure communication with their friendly address, without also enabling an attacker to make large numbers of desirable user accounts of domains unavailable by publishing ownership over them without the domain owner's permission in the bitcoin block-chain. The scheme, proposed by Amincd [https://bitcointalk.org/index.php?topic=74572.msg847022#msg847022 here], would work as follows:		Using the Namecoin block-chain, it is possible for the friendly address owner to publish their pubkey for secure communication with their friendly address, without also enabling an attacker to make large numbers of desirable user accounts of domains unavailable by publishing ownership over them without the domain owner's permission in the bitcoin block-chain. The scheme, proposed by Amincd [https://bitcointalk.org/index.php?topic=74572.msg847022#msg847022 here], would work as follows:

	*A relay server registers example.bit in the namecoin block-chain.		*A relay server registers example.bit in the namecoin block-chain.

Amincd: /* UnSpammable Publication of Friendly Address Owners' Public Keys */

2012-04-11T20:25:53Z

UnSpammable Publication of Friendly Address Owners' Public Keys

← Older revision		Revision as of 20:25, 11 April 2012
Line 69:		Line 69:
	==UnSpammable Publication of Friendly Address Owners' Public Keys==		==UnSpammable Publication of Friendly Address Owners' Public Keys==

	Using the Namecoin block-chain, it is possible for the sender to publish their pubkey for secure communication with their friendly address, without also enabling an attacker to make large numbers of desirable user accounts of domains unavailable by publishing ownership over them without the domain owner's permission in the bitcoin block-chain. The scheme, proposed [https://bitcointalk.org/index.php?topic=74572.msg847022#msg847022 here], would work as follows:		Using the Namecoin block-chain, it is possible for the sender to publish their pubkey for secure communication with their friendly address, without also enabling an attacker to make large numbers of desirable user accounts of domains unavailable by publishing ownership over them without the domain owner's permission in the bitcoin block-chain. The scheme, proposed by Amincd [https://bitcointalk.org/index.php?topic=74572.msg847022#msg847022 here], would work as follows:

	*A relay server registers example.bit in the namecoin block-chain.		*A relay server registers example.bit in the namecoin block-chain.

Amincd: /* UnSpammable Publication of Senders' Public Keys */

2012-04-11T20:25:02Z

UnSpammable Publication of Senders' Public Keys

← Older revision		Revision as of 20:25, 11 April 2012
Line 67:		Line 67:
	If we can define a good way to publish Alice's pubkey into the blockchain and use it further to authenticate and encrypt the exchange, we are making progress towards a working protocol. Coin destruction and spamming should be kept to a minimum or zero.		If we can define a good way to publish Alice's pubkey into the blockchain and use it further to authenticate and encrypt the exchange, we are making progress towards a working protocol. Coin destruction and spamming should be kept to a minimum or zero.

	==UnSpammable Publication of ~~Senders~~' Public Keys==		==UnSpammable Publication of Friendly Address Owners' Public Keys==

	Using the Namecoin block-chain, it is possible for the sender to publish their pubkey for secure communication with their friendly address, without also enabling an attacker to make large numbers of desirable user accounts of domains unavailable by publishing ownership over them without the domain owner's permission in the bitcoin block-chain. The scheme, proposed [https://bitcointalk.org/index.php?topic=74572.msg847022#msg847022 here], would work as follows:		Using the Namecoin block-chain, it is possible for the sender to publish their pubkey for secure communication with their friendly address, without also enabling an attacker to make large numbers of desirable user accounts of domains unavailable by publishing ownership over them without the domain owner's permission in the bitcoin block-chain. The scheme, proposed [https://bitcointalk.org/index.php?topic=74572.msg847022#msg847022 here], would work as follows:

Amincd: /* UnSpammable Publication of Senders' Public Keys */

2012-04-11T20:23:25Z

UnSpammable Publication of Senders' Public Keys

← Older revision		Revision as of 20:23, 11 April 2012
Line 80:		Line 80:
	* Bob asks example.bit for a digital signature of alice@example.bit, and uses example.bit's published pubkey to verify the signature was made by example.bit's official privkey		* Bob asks example.bit for a digital signature of alice@example.bit, and uses example.bit's published pubkey to verify the signature was made by example.bit's official privkey
	* Bob scans the bitcoin block-chain for the earliest spend to base58(ripemd160(example.bit-signature("alice@example.bit") +checksum), and obtain's Alice's pubkey		* Bob scans the bitcoin block-chain for the earliest spend to base58(ripemd160(example.bit-signature("alice@example.bit") +checksum), and obtain's Alice's pubkey
	* There is no way ~~for~~ the owners of example.bit could have cheated and given Bob a different signature for alice@example.bit than they gave to Alice when she published her pubkey, because every namecoin address can only ever have one official pubkey, that can never be altered		* There is no way the owners of example.bit could have cheated and given Bob a different signature for alice@example.bit than they gave to Alice when she published her pubkey, because every namecoin address can only ever have one official pubkey, that can never be altered

Amincd: /* UnSpammable Publication of Senders' Public Keys */

2012-04-11T20:23:02Z

UnSpammable Publication of Senders' Public Keys

← Older revision		Revision as of 20:23, 11 April 2012
Line 69:		Line 69:
	==UnSpammable Publication of Senders' Public Keys==		==UnSpammable Publication of Senders' Public Keys==

	Using the Namecoin block-chain, it is possible for the sender to publish their pubkey for secure communication with their friendly address, without also enabling an attacker to make large numbers of desirable user accounts of domains unavailable by publishing ownership over them without the domain owner's permission in the bitcoin block-chain. The scheme, proposed here, would work as follows:		Using the Namecoin block-chain, it is possible for the sender to publish their pubkey for secure communication with their friendly address, without also enabling an attacker to make large numbers of desirable user accounts of domains unavailable by publishing ownership over them without the domain owner's permission in the bitcoin block-chain. The scheme, proposed [https://bitcointalk.org/index.php?topic=74572.msg847022#msg847022 here], would work as follows:

	*A relay server registers example.bit in the namecoin block-chain.		*A relay server registers example.bit in the namecoin block-chain.