Skip to content

Instantly share code, notes, and snippets.

Namecoin developer meetings are on the first and third Saturday of every month at 5PM UTC. This requires two different Google calendar events:
* [First Saturday](https://www.google.com/calendar/event?action=TEMPLATE&tmeid=cmZldmY1N3V1dDJsZzkzMDZiaHVsdnIwYzRfMjAxNTAyMDdUMTcwMDAwWiBpbmRvbGVyaW5nQG0&tmsrc=indolering%40gmail.com).
* [Third Saturday](https://www.google.com/calendar/event?action=TEMPLATE&tmeid=bjBzbmVyN29wbjAyNnFvcGtzdGtkOTZwcmdfMjAxNTAxMTdUMTcwMDAwWiBpbmRvbGVyaW5nQG0&tmsrc=indolering%40gmail.com)
bts@bitshares:~/bitshares$ make
Scanning dependencies of target leveldb
[ 1%] Building CXX object CMakeFiles/leveldb.dir/libraries/leveldb/db/table_cache.cc.o
[ 1%] Building CXX object CMakeFiles/leveldb.dir/libraries/leveldb/db/log_writer.cc.o
[ 1%] Building CXX object CMakeFiles/leveldb.dir/libraries/leveldb/db/repair.cc.o
[ 2%] Building CXX object CMakeFiles/leveldb.dir/libraries/leveldb/db/dumpfile.cc.o
[ 2%] Building CXX object CMakeFiles/leveldb.dir/libraries/leveldb/db/log_reader.cc.o
[ 2%] Building CXX object CMakeFiles/leveldb.dir/libraries/leveldb/db/version_edit.cc.o
[ 3%] Building CXX object CMakeFiles/leveldb.dir/libraries/leveldb/db/version_set.cc.o
[ 3%] Building CXX object CMakeFiles/leveldb.dir/libraries/leveldb/db/dbformat.cc.o
Namecoin rebooted development about a year ago, and we are working on the following Tor related functionality:
* transaction anonymity (via CoinJoin and Zerocash);
* floating domain prices;
* increasing domain prices and introducing non-trivial renewal fees;
* and UTXO+SPV lightclients.
We were planning on approaching the project regarding deeper integration in 2015 or 2016. However, we consider Tor our single most important use case and we can deliver a fully capable, UTXO based lightclient relatively quickly.
The above feature list and timeline are based on informal discussions with Tor developers. Waiting for the above features mainly improves UX and makes it easier for domain owners to purchase domains anonymously. We are aware of recent research regarding the use of Bitcoin SPV clients over Tor and are working on the SPV threat model for Namecoin (which is slightly different).
> So, I'm not really sure what you actually mean by NMControl client libraries. It's JSON-RPC, every language worth mentioning already has libs for this. What exactly do you want the libs to accomplish?
Not much, nothing like what I was proposing before. Maybe discovery and parsing of namecoin.conf and a few language specific niceties. As you said, new abstractions should be done through NMControl.
The impetus for this is my experiences porting an JSON-RPC Bitcoin library and trying to write one from scratch. The Bitcoin library came complete with unit tests, so it should have just worked. However, I had to chase down weird bugs which required implementing dirty hacks within the JSON-RPC library. The issues I ran into with the Haxe library were bad enough that I had to use Wireshark to figure out what was wrong.
Maybe that's a trivial task for real programmers, but it was really hard for me. Providing libraries removes that upfront gruntwork and a improves the overall development experience. Namecoin ha
g++ -c -O2 -Wno-invalid-offsetof -Wformat -D_MT -DNOPCH -DFOURWAYSSE2 -DUSE_SSL -DMAC_OSX=1 -DCRYPTOPP_DISABLE_ASM=1 -DBOOST_THREAD_USE_LIB -DUSE_UPNP=1 -I/usr/local/opt/openssl/include -I/usr/local/opt/boost/include -I/usr/local/opt/miniupnpc/include/miniupnpc -o obj/nogui/auxpow.o auxpow.cpp
g++ -c -O2 -Wno-invalid-offsetof -Wformat -D_MT -DNOPCH -DFOURWAYSSE2 -DUSE_SSL -DMAC_OSX=1 -DCRYPTOPP_DISABLE_ASM=1 -DBOOST_THREAD_USE_LIB -DUSE_UPNP=1 -I/usr/local/opt/openssl/include -I/usr/local/opt/boost/include -I/usr/local/opt/miniupnpc/include/miniupnpc -o obj/nogui/util.o util.cpp
g++ -c -O2 -Wno-invalid-offsetof -Wformat -D_MT -DNOPCH -DFOURWAYSSE2 -DUSE_SSL -DMAC_OSX=1 -DCRYPTOPP_DISABLE_ASM=1 -DBOOST_THREAD_USE_LIB -DUSE_UPNP=1 -I/usr/local/opt/openssl/include -I/usr/local/opt/boost/include -I/usr/local/opt/miniupnpc/include/miniupnpc -o obj/nogui/key.o key.cpp
g++ -c -O2 -Wno-invalid-offsetof -Wformat -D_MT -DNOPCH -DFOURWAYSSE2 -DUSE_SSL -DMAC_OSX=1 -DCRYPTOPP_DISABLE_ASM=1 -DBOOST_THREAD_USE_LIB -DUSE_UPN

@phelixbtc I've got a list of pools that don't mine Namecoin, why don't you try getting them to mine Namecoin? None of them were hostile to the idea, they just gave up in frustration. Then all the pools would be Namecoin friendly. Why do you point people to P2Pool when merge-mining is basically solo mining?.

@JeremyRand Are you seriously suggestion people don't already rely on Google for most of their navigation? I've done user studies on documentation, I've watched users struggle with an interface and skip the finely curated docs I created for a quick Google search. I was wrong about how I thought users would interact with documentation because of how much effort I put into it.

If you insist on design-by-committee then I'm going to insist on processes designed to protect the UX from death-by-committee. The way we handle this in UX land is through personas, a concensus and data driven process for cre

The bandaid patch used to mitigate an issue with complex transactions is no longer working. We were hoping it would by us time for our two lead developers to return from vacation.

We are working on a more permanent fix but, until then, mining operators are advised to restart their Namecoin mining deamons hourly. This is an ugly hack, but it's slightly less ugly than pushing out a new binary everyday.

ATTN POOL OPERATORS
We have a baindaid fix for recent issue affecting Namecoin please either:
Recompile namecoind using the relay_temp_fix tree
Download the binary (hash, PGP sig, and Tor link, mega.co.nz mirror):
https://archive.org/download/namecoind-bandaid/namecoind-bandaid.zip
If you are unable to get these solutions working, restarting namecoind will clear the offending jobs from the system. However, you must continually restart namecoind when things slow down (every couple of hours should work too).
[
"00f954de83a1651d2f2a2bc062720df5dc1639e2b69985f75861f0a7c7ce0c36",
"01462a86cf5d34bb8e17869f1dad3b9934438698e009363aee72a51e782ddcc7",
"02e4c5248b8d8b7c36cc645df597a629694ffb9b1ae1e267b4d8a71eda59492b",
"034bf2209cf2250fc05a4816261c6571137f2296acb9b979011f00fe025de7b9",
"043846221acf5f233bba3829598c1636be6c2ffc80564fbe2ae0fa47e48eacd5",
"0d7c8094ce6db02be0c3ce6793daeba8d23d1a7e035e244dfbb62d9240c02cdb",
"0e41d2b229dc36a248ad1ea3c57b8450c260d5e35d4db76f113514b6a91d3492",
"0f8daab57d20da71424ea2b4c910547f3959d5265d30ad090e56f777212927e4",
"139035659dfee417d2af4ae18bdb14916580710036f4f492a6c464e65da53bde",

#Restart Your Daemon Recently, someone tried consolidating a large amount of NMC which gummed up the miners. This was not a deliberate attack but we need all pool operators to restart their daemons, this should get the network functioning properly again.

This will only work for a few hours, we are trying to coordinate a response on IRC. If you are a pool operator please get on #namecoin or contact zachlym@indolering.com.

##Bandaid Patch Edit main.h to change

MIN_RELAY_TX_FEE = 10000