Topic: Decentralised bitcoin address book (Read 344 times)

That doesn't stop the fact launch attack is cheap and people with motive other that economy still could attack the side-chain such as intentionally don't include specific transaction (or address/name set in this case). I doubt people would do such attack for minor cryptocurrency, but IMO you should think about this attack vector.


While the idea is great, it's barely used and the community almost non-existent (at least on reddit/medium).

I think too that what you (OP) are talking about is not far from what Namecoin offers. The project is not actually trying, but does work and provides .bit domains, but most of the people use DNS servers that does not resolve those .bit domains and that's why they are not used.
Like what the Ethereum Foundation is trying to do with ENS, you can use domains to make friendlier addresses for an end-user. I remember Dash is trying to provide something similar but I haven't dived in it.

I think phone based messengers such as WhatsApp also rely on SMS verification though?

https://faq.whatsapp.com/en/android/20970873/

Which would put us back to the problem of centralized SMS gateways.

Good point nonetheless, maybe there's a way to associate a phone number to a user via SIM card access. I have no idea what SIM data is available to apps however.



Got any experience with Namecoin? I remember this project trying to solve the problem of decentralized name-derivation vs human readability but I never looked into the technical aspects to be honest.

Actually, in that case, a system such as whatsapp could be used for verification.
If you make it more email based then it'll work better.

I've often thought Bitcoin has a similar issue to TOR, no one without money can derive an address they can easily remember. Facebook had to devote an entire datacentre to mine Facebookcorewwwi.onion for example for a week.

I know some of the seeds that store fudns in my wallet from memory and it seems odd that it's easier to remember my private keys more than I can my public keys (most of those seeds don't hold anything any more because it's not very secure if you can remember them).

---

Currently there are 2048 words in the wordlist for bip32
This means that there would be ceiling(log(2^256)/log(2048))=24 words...

If I use a few dictionaries and add Welsh and German and potentially a few other languages, that number can be reduced. With three languages, it becomes a length of 20 words - although that would be a stupid idea as welsh is evolving into english or it evolved from the same language (I'm not sure which is true, I think it's the first because it doesn't sound as western european as german and french do).

The oxford dictionary supposedly has 171476 words in it, I get that to be 15 words for an address and then you would obviously need two checksums for such a thing so it would come to about 17 words all in all but it might be a bit confusing...

I don't think phone / email verification / association is possible without some form of centralized oracle.

Both phone numbers and SMS gateways are centrally controlled, so there's no way to decentralize phone verification in an automated manner (similar to how converting crypto- to fiat-currencies requires cooperation with the classical banking system).

Decentralized email verification should be possible in theory, as anyone can run an email server; but good luck reaching any inboxes without being whitelisted by major providers.

I guess one could create a decentralized public-key cryptography based messenger system, similar to BitMessage, but without needing the private key for deriving the recipient's address? Ie. some form of decentralized storage for messages encrypted using public keys associated with Bitcoin addresses. I'm not sure if that would be all that useful though, at least for the use case as described by OP.

It's easy to link it to email it social media though.

The old forms of usernames systems with Facebook meant you could write an email to facebook.com/random.name.3, by writing the email to [email protected].

Following conventions like the others have said leads to catastrophies. If we had have left Bitcoin without a few of the upgrades, we'd have blocks where 1billion bitcoins get spent...

I agree/have nothing to say about the upper half of your reply but :


Mmmmhhh I never disagreed with something so much If everyone thought like you we'd never have progress Especially for software development, every pull request that introduces something new but breaks backwards compatibility needs to be defended by sweat and blood if it's a genuine improvement.. I don't follow bitcoin development up close but I'm sure this is exactly the same for all Bitcoin improvement proposals.

Of course this specific issue doesn't "improve" bitcoin so I can agree with you in this specific case. But it's not a bad idea on its own from a user standpoint, so I radically disagree with your philosophy, and the answer to WHY it shouldn't be implemented is very different for the both of us.


Goddamnit dude, have some faith! No one said it was easy, this exact issue does seem impossible to work around, but I am willing to bet money we're going to have a solution for this in the future.

You can drop the extra stuff and use some sort of coding. for example add 1 byte (256 options) indicating which Email provide it belongs to. For example 0x01 can mean gmail.com, 0x02 can mean protonmail.com so you effectively replace 9 bytes and 14 bytes respectively with only 1 byte.

There is nothing wrong with reusing addresses but it is not "recommended", not to mention that by design, a bitcoin address is a single use token.
Read more: https://en.bitcoin.it/wiki/Address_reuse

When you sign anything with your private key, you are revealing your public key. This operation is a one way operation but if there is any weakness in the implementation you are using or some day a weakness in the algorithm itself is found then your funds will be at risk compared to if you never revealed your public key.

It is never "negative" when you follow the best practice even if you don't know the reason for it.

I've already pointed out this flaw and also pointed out that it is the same with any other decentralized way of doing it. You can't prevent people from registering any address with any name no matter what method you use.

Satohsi used a lot of different addresses for each block he mined. But the use of different addresses is for privacy, the use of one address or address groupings (like I use) is something that should be more widely encouraged as it keeps blocks quite clear. Also there are things like when the genesis block is paying to a pool and the rest of the transactions in the block are of zero fee, you can kind of guess they're all from that pool... Pools addresses are already fairly publicly known and they mine to their same addresses each time (and based on the speed of their support, I wouldn't doubt I is easy to be able to control one of those for 12 hours and get more money or find an address with a large sum on it).
All you actually know in this system is how mcuh an address has, if the funds are then mixed or something then the funds could have been escrowed or the funds could have been bought or something.


No that's true, anyone can sign a transaction with anything in the code. You also have to pay for that text you put in the transaction.

Can you convince me on why this would be a bad thing? The point of this whole idea is to avoid privacy and link every  address to a real life entity, so the only argument you would have would be the security of signing multiple transactions with the same key which is really getting less and less exploitable as an attack target the more time goes by.

I understand its good to follow best practices, but it becomes a negative feat when you do it without asking yourself why.


This doesnt solve the proof of identity problem. Anyone can sign a tx and include any email phone without proving themselves as the owner. I understand you want to keep the privacy of bitcoin, but know that not everyone cares about privacy. Solving this problem would definitely be worth creating something new.

I started to think of this from a slightly different perspective. The problem for charities is the difficulty in listing addresses for multiple coins. I decided that the best solution was to register a domain name, and then build all the info into a website. This lets you help new users, as well as the knowledgeable. I started to implement this on Bitcoin Patron. It isn't a simple concept though, and I'm about to change the template for the third time.

I appreciate that there are some centralised projects like this, but they seem to be starting to remove listings for sites that they deem to be politically incorrect. That's why I decided to create my own independent one.

So at the moment it can only be done in a centralised way (until decentralised phones come out). I think my email is greater than 20 chars also. What's wrong with reusing addresses other than the privacy issues, a lot of services mean you have to use them.

First of all this is encouraging address reuse which should be avoided.

Secondly you are complicating things by a lot! Try to think simpler and try to stick with what bitcoin already offers.
Let's see what you want to do.
You want to link a bitcoin address to another "information" which can be anything including Email, phone number, website link,...
So why not use OP_Return?

It offers all you want. It signs a "message" so the owner of the key would be clear and it can include any "information" in it. You just have to make a new transaction from that address and include that "information" inside a OP_Return output.
Like this (the link to my github page):
Then all the clients have to do is to search the blockchain for OP_Return outputs and build a local database from them.

It inherits the same flaws as your proposed system as it encourages address reuse and also it has no mechanism from stopping anyone from linking anything to anything because of decentralization!

Put it on a side chain and make the mining free. There will be no perks to attack the chain, there's no need to implement a protocol for orphaning a block imo.

I've been going through the idea of making my own currency relational to the person's name or phone number but it would be quite difficult. I suppose a chain that stores addresses and emails/phone numbers on the sidechains.

I'm trying to build a client that runs everything Bitcoin core does but I'm going to try to make some things a bit different... I've noticed areas of speed that I wouldn't want to test on the main Bitcoin network just in case something goes wrong and a tiny bit or parity might be lost too (but the places I want to remove it from should be pretty much negligible).

I also can't make something like that without an ico as I'd have to find the verifications (actually email verifications are free and I have scripts for those already).

---

The project stack is currently at:
Make a Bitcoin node software.
Make a version of the ethereum chain that works (ethereum's issue is that it stores money, I want to make the ethereum's virtual machine clone that instead is paid for with Bitcoin in some way as I feel ethereum should be two side chains but that's something I'm not sure whether to drop or not).

This is kind of similar to : https://bitcointalksearch.org/topic/m.48563244

You want to link one (or multiple) bitcoin addresses to a phone number or email. If I don't include the same issues in the post above, where you have to worry about who are the nodes that will host this sidechain of numbers/emails, etc.. you have other issues like people claiming emails and phone numbers without being theirs, if you do plan to add a verification system how would you implement this verification? There needs to be a centralised entity that sends "verification" emails/messages to the people trying to verify themselves, but mostly.. why bitcoin?

I understand the reason behind the "why" of what you want to do, but in case you can come up with a solution to the well known "Proof of Identity" problem, I'd recommend starting your own crypto and launching it. (I'm not kidding, it'd be revolutionary)

I'm wondering if there are any blueprints for such an idea, I think it would be quite easy to do and broadcast people's addresses from a client when an email or a phone number gets input.

This could be integrated with a few clients beyond that, I'm wondering if the solution already exists? The idea being someone takes an address and signed message from it in a way that verifies an email or phone number, a valid from date and a valid to date. Probably run similar to a DNS setup.