It would be cool to have complete integration of Namecoin IDs with Bitmessage such that wherever possible/available a Bitmessage address is replaced by the ID.
To do so it will be necessary to sign the Bitmessage address in the ID value with the Bitmessage private key (should be similar to a Bitcoin key) to prove the id holder also actually holds the Bitmessage address.
Further Bitmessage Integration
Forum rules
Warning !
Avoid using binary softwares from untrusted users.
Prefer compiling it yourself and verify sources.
Warning !
Avoid using binary softwares from untrusted users.
Prefer compiling it yourself and verify sources.
-
mightbemike
- Posts: 57
- Joined: Fri Apr 25, 2014 4:40 am
Re: Further Bitmessage Integration
There are private signing keys in the .dat file, but no support in the GUI for signing.
What are you thinking of, something like this?
id/
{
"bitmessage": {
"address": "BM-blahblahblah",
"signed": "k1K7geEokrok4sblahblahblah"
}, ....
}
What are you thinking of, something like this?
id/
{
"bitmessage": {
"address": "BM-blahblahblah",
"signed": "k1K7geEokrok4sblahblahblah"
}, ....
}
NMC: NFhmGAqzRpZbGs3uCPPo7DJKuscuL4Aap2
id/mightbemike
id/mightbemike
Re: Further Bitmessage Integration
The keys should be similar to Bitcoin so it should be quite easy to use them for signing in python.mightbemike wrote:There are private signing keys in the .dat file, but no support in the GUI for signing.
yeah
What are you thinking of, something like this?
id/
{
"bitmessage": {
"address": "BM-blahblahblah",
"signed": "k1K7geEokrok4sblahblahblah"
}, ....
}
That way it can be used in both directions.