Namecoin Forum

I like the idea (better than nothing, as they say) but I also dislike the high 10% fee. A project I contribute (non-dev) work to has BountySource integration, but the issue is it's too difficult for the average coder to contribute and I think Namecoin is in similar situation. But a lot could be done...

I've been working on wallet UI improvements (so that JSON expertise isn't needed), DNS improvements (based on Unbound), and TLS stuff (Firefox extension). I'm also working on some prototyping of improvements to NameID (so that you don't need a Firefox extension or to trust an OpenID server). These ...

Hi guys Every 2-3 weeks I visit the forum to see what's going on and I've been doing that for a while. In recent dev updates I see there's some activity related to the recent new bug, the Web site and some mining-related work. But the most important part - getting people to use the coin - doesn't se...

Updated OP. Previous version: Due to a bug in OpenSSL Linux and Mac 64bit Namecoin Classic (v0.3.80 and earlier) and Namecoin Core clients accept a wider range of cryptographic signature formats than other builds. This brings us into the dangerous situation of potentially forking the network. Miner...

Related to Core GUI > Alternatives, you can take a look at github.com/CounterpartyXCP/counterparty-gui, it's a Python-based wrapper that can support several back ends (currently Bitcoin Core 0.10) and it is easily extensible via plugins. It can use a local or remote server. It's built to be simple, ...

Why wouldn't you try several, such as Counterparty and Omni, instead of just one?
Or if you don't have the resources for several, list your requirements and pick one or two that meet those.

I don't think much of it, but shouldn't a new client be released to allow us to catch up with a newer version of OpenSSL? I figure the devs are probably trying to implement Bitcoin Core 0.10 based improvements and with them include other updates. If you're talking about the critical OpenSSL bugfix ...

I don't think much of it, but shouldn't a new client be released to allow us to catch up with a newer version of OpenSSL?

I figure the devs are probably trying to implement Bitcoin Core 0.10 based improvements and with them include other updates.

Thanks guys. I in fact tried the workaround offered by @cassini before, and also now (with datadir removed from the conf file), but it still doesn't help (exactly the same behavior as before). It's not a huge issue, but in terms of time I've blown 1 hour on it. I have a small SSD for C: drive so tha...

Here's how I run it: C:\"Program Files (x86)"\Namecoin\namecoin-qt.exe -conf=e:\blockchain_nmc\namecoin.conf In config file I specify walletpath and datadir. Neither of these three (conf, walletpath and datadir) have any effect. Log: namecoin version 0.3.80 Default data directory C:\Users\USER\AppDa...