[Dev] Private Blockchain Addresses (Dark Blockchain)
-
This guy has really got my interest… Wrapper, do you think it’s worthwhile contacting him and seeing if he can help us do it?
From what I understand this is kinda what we want…
https://medium.com/@octskyward/ecdh-in-the-payment-protocol-cb2f81962c1b
Once the above is implemented, it would be useful to define more BIP70 extensions to let people put (unauthenticated) names/pseudonyms, pictures and contact details into a payment request. People can then populate their wallets address books by loading up such files, and community run directory sites can make paying someone as easy as looking them up online. This does not require ECDH/stealth addresses of course because a wallet can always just constantly upload new versions of the payment request whenever a payment is received, but it does simplify things and avoids small amounts of reuse that could occur if a wallet was offline for a while.
The infrastructure I just talked about can be easily implemented by any reasonable programmer one step at a time, in layers. If you’re interested in experimenting with this, drop me a line: mike@plan99.net
Also, is there a way we can tie light addresses into this project at the same time?
Could we ask “Mike” if he thinks it could be achievable at the same time?
-
If I have time, I will promote this work.
-
Cheers Calem - interesting read,
I agree with him (mike@plan99.net) in his critique of stealth addresses. He certainly has thought about the subject from a technical point of view.
https://medium.com/@octskyward/ecdh-in-the-payment-protocol-cb2f81962c1b
I’d be interested to see how quickly he can trash private addresses. Although, PAs do seem to get over many of the problems he sees with the very similar “large public key” method of privacy.
e.g. being able to index the address, so the wallet can find relevant transactions. Also, where one option is to make the private addresses indistinguishable from normal transaction addresses.
As you know, I’ve outlined the idea in the best detail I can and the next step would be to some test coding to see if it at all viable.
I’m just getting round to learning more about the history and state of multi-signature wallets and BIP’s. Although that is to look at whether we can change the multisignature address start values, doing that work would get us more up to speed on how private addresses might be implemented.
I sent Mike an email to see what he thinks.
-
The main thing we need with private addreses etc, is that there needs to be an Audit Key that can be used to give to tax agents accountants or tax agencies/gov etc.
-
Just thought I would mention, on the opposite end of the spectrum here…
https://github.com/opennamesystem/openname-directory
https://openname.org/aboutOVERVIEW
The Openname System (ONS) is a protocol that extends DNS by supporting the registration and resolution of:
- user handles on the blockchain (DNS for people)
- domains on the blockchain (decentralized DNS)
…all with full DNS backwards-compatibility.
ONS = ICANN DNS + blockchain handles + blockchain domainsONS currently uses namecoin as a key-value store but the system is blockchain-agnostic.
I don’t want to add yet another project, but this is something that we need to sort out in time as well.
-
Develop a wallet option to have individual addresses for each transaction.
Mike says he thinks you can’t encrypt the address, in order to make each transaction individual, (he doesn’t explain why), but that we could use the same idea to make transactions more private, without encryption.
We could just do the “make it easier to have individual addresses” part of private addresses white paper. I can’t quite see how this would work, as my mechanism was to have an extra layer, that the receiver and sender would have access to, via their keys, to show the link behind the encrypted address.
As with private addresses, if each transaction uses individual addresses then there is much less information leaked. This would make each transaction more like cash, as Satoshi envisaged. It would depend how the individual address could be made and decoded by the wallet whether it would remove the need for a cryptographer to be involved with the software development to make any progress.
https://medium.com/@octskyward/ecdh-in-the-payment-protocol-cb2f81962c1b
-
Is this what Bush is currently working on?
-
Yes, Stealth Address start , me and Bush.
-
Stealth Address will was created in wallet, The use of it in much the same way as normal. Stealth Address ,The length of more than 35 .
-
after my pool confirm a stealth transaction, but I find a problem , I can not receive coin.
I check logfile.
FindStealthTransactions show a error “StealthSecret failed” in wallet.cpp,StealthSecret(sScan, vchEphemPK, it->spend_pubkey, sShared, pkExtracted)
StealthSecret show a error “StealthSecret(): Q EC_POINT_bn2point failed” in stealth.cpp
if (!(Q = EC_POINT_bn2point(ecgrp, bnQ, NULL, bnCtx)))
my a stealth transaction on blockchain.
http://block.ftc-c.com/tx/137455e27de1c7b3302c3b0c462fb0d904a831339aebf468e6e85c224362f51b
Block number:556535SX address f5QuGW2S8TvSqszejNxxTATHh4AgJC2VVvMf5Lc2tk6uR4k3F361kwM8oiLecHT4z4q7qmUgnUE47HsqpGX6uZnUghvgLN7iiSpeA7
-
Bugger…
-
Yes, I have fixed the bugger. I develop Stealth Address successful.
Look , This is first stealth transaction in blockchain ,It is at 566321 (Mainchain)
http://block.ftc-c.com/tx/85568ae1dacfdc6730b0d2ddeb2c4d7d07b0ac702e6d9a7f408293e2cd628d57
MyStealth Address is f5QuGW2S8TvSqszejNxxTATHh4AgJC2VVvMf5Lc2tk6uR4k3F361kwM8oiLecHT4z4q7qmUgnUE47HsqpGX6uZnUghvgLN7iiSpeA7
I send 0.01FTC to my Stealth Address ,then I receive them successful. :)
-
It’s working?
Amazing Job…
-
Yes, I have fixed the bugger.
-
We need to start testing this… Testnet time?
-
Count me in.
-
We need to start testing this… Testnet time?
No, It is working on main_net. Some SX transactions have been confirmed.
List:
Block # 556535 (Mainchain)
http://block.ftc-c.com/tx/137455e27de1c7b3302c3b0c462fb0d904a831339aebf468e6e85c224362f51b
http://block.ftc-c.com/tx/ff6179824ddad55fe0666b2f7f7a25958d12644a5563f776ddfda7aeda20cf12
Block #566321 (Mainchain)
http://block.ftc-c.com/tx/843cf93bebad1682b6385ba4c8b19f137d40d3f0808330b196057eaa6b445a98
http://block.ftc-c.com/tx/85568ae1dacfdc6730b0d2ddeb2c4d7d07b0ac702e6d9a7f408293e2cd628d57
Block #569270 (Mainchain)
http://block.ftc-c.com/tx/4305587958876434ba60af536a108f2adf2e99f3616b90ed8a1aec96b398817a
Block #582187 (Mainchain)
http://block.ftc-c.com/tx/530c29dffffeb8fe24a8b03f4ccbef0adc7008f5bdfbb29c8a3cf6f9cdcaf9a7
http://block.ftc-c.com/tx/1de36440571edf827920007704f9987389d1f9c7fe597377ae93c29508f70013
http://block.ftc-c.com/tx/d5005bb2cf68dbbdf23aa348742bf62e3056ab05bfc62f00a358b45c24e41a12
Block #556535,566321,569270,582187 make in my 0.9.3 core pool(pool.ftc-c.com). If my miners find a block, SX transactions will been confirmed.
-
SX transactions all right ^-^ , we can send FTC with SX address, then we can receive those coins.
-
So do we just download the new wallet and starts testing it?
-
Is it possible to add support to the android wallet?
Not sure if that’s required. Buy would any changes be needed to the wallet to make it compatible?