I will have it fixed shortly or at least will prevent the UI from going forward with the send. But evidently it needs to process them so that tests like yours will succeed. Bitmessage currently does not process its own messages and public key requests- it only broadcasts them to other nodes. Quote from: HostFat on February 13, 2013, 09:09:27 PMĪre you trying to send a message from one identity to the other on the same machine?ĮDIT:I assume this is the case. I have already wrote the same on your forum, but I didn't get a reply. but he whinges about a lot of things, so who's to know how serious he is?ĥ) Sent a message from the first identity to the secondĦ) The message remain on status "Sending public key request. Yeah, gmaxwell has had some sort of vendetta going against namecoiners for a while now. it would be bigger but it seems it's too boring to even bother attacking right now. (nmc's database is about 1.1gb right now) Atheros2: well it could be but you currently would need a copy of the whole namecoin chain, which is small compared to bitcoin but _huge_ compared to the actual amount of namecoin usage. none of them even bother to backport critical security fixes from bitcoin) (it seems that all altchains get more or less technically abandoned. I was thinking about why it couldn't be (or hasn't been) used to alias Bitcoin addresses but I guess that is the reason. though its fundimentally possible to create.
LITE WALLET BITMESSAGE FULL
it's not possible today to have a lite (not full blockchain) namecoin resolver which is secure. There are some fundimental challenges, e.g. Which is quite sad, because it's a useful idea. it's been sort of spammed to death because they massively lowered the cost to get names, so there is effectively no anti-dos in it anymore. It's more or less dead now— pretty much abandoned by its creators. Quote from: marcus_of_augustus on January 16, 2013, 10:37:43 PM Namecoin is still working but just waiting for more applications, this will be an excellent one. Namecoin blockchain is tiny compared with bitcoin at present and is lightweight to run on pc, or you can make calls to the namecoin enabled DNS servers out there if you trust them. all dictionary, names, etc in all languages. Not sure who you were talking to on IRC but there are only total of 70,000 names registered on namecoin blockchain, hardly "spammed to death" considering the size of the namespaces available, i.e. it's been sort of spammed to death because they massively lowered the cost to get names, so there is effectively no anti-dos in it anymore." Unfortunately, I asked a 'hero member' (I forget who) on IRC about this possibility and why no one was doing it with Bitcoin addresses yet and he said that Namecoin is "more or less dead now.
end-to-end secure, autonomous look-up, authenticated, human-readable messaging system. Now you could store those Bitmessage/Bitcoin keys in a namecoin 'alias' namespace and have the Bitmessenger client just send to a human-readable name from the namecoin blockchain. It seems to me that Bitmessage addresses could be turned into Bitcoin addresses but not the other way around. Thus Bitcoin addresses (which are only a hash of a signing key) wouldn't be sufficient for Bitmessage. However Bitmessage will use two keys- one for encryption and one for signing. Today I coded the key generation sections Bitmessage will even save keys in Wallet Import Format. Why not make it so one can use a Bitcoin address / keypair for messaging?īitcoin and Bitmessage keys will be interchangeable. Quote from: casascius on January 16, 2013, 04:31:44 AM
Quote from: marcus_of_augustus on January 16, 2013, 09:34:08 PM Bitmessage - P2P Messaging system based partially on Bitcoin
0 kommentar(er)
