Namecoin v0.3.80
https://forum.namecoin.info/viewtopic.php?f=8&t=2123
zip please?
Topic: [ANN][NMC] Namecoin Wallet (QT) with integrated Name Registration v3.75 - page 4. (Read 78564 times)
December 23, 2014, 10:39:23 PM
November 23, 2014, 11:23:21 PM
You can now do NEW_NAME , FIRST_UPDATE, and UPDATE_NAME with a javascript Namecoin wallet. forked from bitcoinjs-lib
you can try it at https://djswallet.com/wallet.php
you can try it at https://djswallet.com/wallet.php
October 29, 2014, 01:53:58 PM
Will namecoin ever be fixed?
Is it broken for you? October 29, 2014, 01:19:04 PM
Will namecoin ever be fixed?
October 08, 2014, 11:53:33 AM
We believe in crypto and offer 20% off all orders paid for via Bitcoin or Namecoin! Just enter the coupon code 'BITCOIN' at checkout to apply!
Prices if paying in Bitcoin:
Bitcoin Proof = $80
Litecoin Proof = $80
Namecoin Proof = $80
Peercoin Proof (w/o 24k gold highlights) = $80
Cryptogenic Bullion Bar Proofs = $80
Peercoin Proof (w/ 24 k gold highlights) = $100
Primecoin Proof (Batch 2) = $68
DOGE Proofs (copper or nickel) = $20
Buy precious metal, limited mint, physical crypto-proofs via Bitcoin, Litecoin, Namecoin, Peercoin, Primecoin, Dogecoin, Darkcoin, Vertcoin, Cryptogenic Bullion, NXT, Worldcoin or PayPal!
Exclusively from Finite By Design!
Exclusively from Finite By Design!
October 01, 2014, 07:46:42 AM
I removed all the port numbers from all my config files a week ago so the clients would just use the port it wants use.
September 27, 2014, 07:30:45 PM
Damn I can't remember where I read that. He basically said now you can lookup addresses but getting them in is very tricky.
September 17, 2014, 05:16:35 PM
Right. It compiled fine if I left the option out completely, but using either =0 or =1 wouldn't work. It would be nice if users were able to choose weather to use it or not, depending on their network conditions of course...
Hmm I think it is activated in the Windows binaries. Never ran into any issues with it.I'm using Xubuntu.....
September 17, 2014, 03:17:06 PM
Right. It compiled fine if I left the option out completely, but using either =0 or =1 wouldn't work. It would be nice if users were able to choose weather to use it or not, depending on their network conditions of course...
Hmm I think it is activated in the Windows binaries. Never ran into any issues with it. September 16, 2014, 11:03:10 AM
Right. It compiled fine if I left the option out completely, but using either =0 or =1 wouldn't work. It would be nice if users were able to choose weather to use it or not, depending on their network conditions of course...
September 16, 2014, 07:06:06 AM
Is there an issue with compiling the latest v0.3.76 with upnp enabled? I can only compile it without upnp. Huntercoin compiles fine with upnp enabled.
I always disable upnp. But I think I saw some problems, too, when I tried it last time. I think it is "just" some problem with #include's or like that - but without experience with libminiupnp, I can't really tell.
September 16, 2014, 07:03:52 AM
Is there an issue with compiling the latest v0.3.76 with upnp enabled? I can only compile it without upnp. Huntercoin compiles fine with upnp enabled.
August 28, 2014, 07:34:09 AM
If anyone is interested, I built a BIP32 Namecoin(And other coins) javascript wallet. It is currently in Alpha. No name registration yet (Just send and receive for now), but it is in the works.
Try it out and click on the discussion tab to post any issues
https://djswallet.com/wallet.php
(Self signed cert while in alpha release stage)
Try it out and click on the discussion tab to post any issues
https://djswallet.com/wallet.php
(Self signed cert while in alpha release stage)
August 27, 2014, 11:24:16 PM
I know the client says you are supposed to keep it open during name registration (for ~3 hours), is there likely to be a way around this in the future? It seems less than ideal that everyone has to leave their client open for hours waiting for confirmation.
Also what happens if the client is closed after the name_new but before the name_update? Does it cancel/void the registration process?
Also what happens if the client is closed after the name_new but before the name_update? Does it cancel/void the registration process?
August 24, 2014, 06:23:31 AM
OK, I recompiled using the older source, changing the main.h file as you suggested &.....voila! Up and running again without issues - thanks.
As for question about what I did - nothing actually
I noticed namecoind was using very high cpu (blockchain was already downloaded) & was unresponsive for about 5 minutes after issuing the stop command before throwing me the message & closing.
All seems to be well now though, it's been running for 24hrs no problem. Thanks again
As for question about what I did - nothing actually
I noticed namecoind was using very high cpu (blockchain was already downloaded) & was unresponsive for about 5 minutes after issuing the stop command before throwing me the message & closing.All seems to be well now though, it's been running for 24hrs no problem. Thanks again
August 22, 2014, 07:24:06 PM
locked up & gave me this error when I tried to stop it:
...
posix_recursive_mutex()
The mutex message when trying to stop the client is a well-known nuissance since one of the boost library version changes. Domob said he'll have a look at it but it is low priority....
posix_recursive_mutex()
A different kettle of fish is the lock-up problem. What did you do exactly?
I recommend you recompile the source code you had used before and simply change that single line in main.h according to
http://blog.namecoin.org/post/95263343235/restart-your-daemons
August 21, 2014, 04:44:50 PM
Excellent! Many thanks for the heads up
EDIT: Not working for me, locked up & gave me this error when I tried to stop it:
" namecoind: /usr/include/boost/interprocess/sync/posix/recursive_mutex.hpp:77: boost::interprocess::ipcdetail::posix_recursive_mutex::~posix_recursive_mutex(): Assertion `res == 0' failed."
August 21, 2014, 04:39:23 PM
August 21, 2014, 04:31:44 PM
Any news/ideas on this little problem yet guys?
August 18, 2014, 05:52:40 PM
There were some very large blocks, could it be processing just takes longer?
Hey phelix, I'm not sure how having large blocks would cause a time out error - could you elaborate? It's still giving the same error....
Jump to: