Can't seem to find miniupnpc/* even though I've copied it into the source tree. Dunno whats up with that.Having difficulty with this nmc registration process
Topic: [OLD] Eligius: ASIC, no registration, no fee CPPSRB BTC + 105% PPS NMC, 877 # - page 179. (Read 458487 times)
October 13, 2011, 06:06:59 PM
Anyone have a working 0.5.0 release for OSX ? Can't get mine to compile Can't seem to find miniupnpc/* even though I've copied it into the source tree. Dunno whats up with that.
Having difficulty with this nmc registration process
Can't seem to find miniupnpc/* even though I've copied it into the source tree. Dunno whats up with that.Having difficulty with this nmc registration process
October 13, 2011, 06:05:33 PM
welcome. 
October 13, 2011, 05:51:29 PM
how are you cutting and pasting the signature? directly from command prompt into eligius? or are you putting it into a notepad type program first?
just make sure no matter what its only one line when you copy / paste it
I had the same program and I suspect a CR was getting stuck in there when it started on the next line
that worked. Thank you. just make sure no matter what its only one line when you copy / paste it
I had the same program and I suspect a CR was getting stuck in there when it started on the next line
October 13, 2011, 05:47:50 PM
does it matter that i get a different signature everytime i run this?
October 13, 2011, 05:44:54 PM
how are you cutting and pasting the signature? directly from command prompt into eligius? or are you putting it into a notepad type program first?
just make sure no matter what its only one line when you copy / paste it
I had the same program and I suspect a CR was getting stuck in there when it started on the next line
just make sure no matter what its only one line when you copy / paste it
I had the same program and I suspect a CR was getting stuck in there when it started on the next line
October 13, 2011, 05:42:15 PM
can anybody advise how to sign this message?
I have 0.5 running. wallet.dat is correct for address of signature. I get a different signature every time i run the command. every signature is malformed when signing the message at eligius.
i have no idea how this works!
I have 0.5 running. wallet.dat is correct for address of signature. I get a different signature every time i run the command. every signature is malformed when signing the message at eligius.
i have no idea how this works!
October 13, 2011, 05:33:29 PM
alright thanks, it will be interesting when we can actually see how many namecoins we are mining, thanks!
October 13, 2011, 05:33:07 PM
malformed signature error, adinfinitum!
October 13, 2011, 05:11:09 PM
luke-jr: whats send threshold for namecoins?
tbd October 13, 2011, 05:04:33 PM
luke-jr: whats send threshold for namecoins?
October 13, 2011, 04:47:28 PM
Managed to get a cross-compiled static EXE for Windows users; it's linked from the 2nd page of the registration (ie, when you need to use it).
Thanks for putting it up, and thanks to whoever compiled it as well.
will this force me to convert the wallet with my current pool btc address to bitcoin client v0.5rc?
The wallet format only changed between 0.3.x and 0.4.x; 0.5.x does not change it. Either way, backup your old wallet-- I take no responsibility if it gets corrupted through some weird bug. October 13, 2011, 04:15:06 PM
so whats the send threshold for namecoins?
October 13, 2011, 04:13:13 PM
nevermind I figured it out, I was pasting it into and out of getdiz which was adding something to it,
thanks anyways
thanks anyways
October 13, 2011, 04:00:52 PM
eligius keeps giving me a malformed signature error message, any ideas?
October 13, 2011, 03:15:27 PM
will this force me to convert the wallet with my current pool btc address to bitcoin client v0.5rc?
You can leave your existing bitcoin client alone. Copy the wallet.dat to another machine with bitcoin client 0.5, do the signature, then destroy the copy of the wallet.dat.
Or if you don't have a separate machine/VM, then just backup your current bitcoin data directory and bitcoin installation and restore it after you finish messing with bitcoin 0.5.
thanx. should have thought of that
using local data directory ( -datadir=data ) and copied blockchain already...
October 13, 2011, 02:50:50 PM
will this force me to convert the wallet with my current pool btc address to bitcoin client v0.5rc?
You can leave your existing bitcoin client alone. Copy the wallet.dat to another machine with bitcoin client 0.5, do the signature, then destroy the copy of the wallet.dat.
Or if you don't have a separate machine/VM, then just backup your current bitcoin data directory and bitcoin installation and restore it after you finish messing with bitcoin 0.5.
October 13, 2011, 02:43:16 PM
Your being an OS racist by making us give a bitcoin signed message to add a namecoin address ! How many windows users have the neccesary compilers and libraries to compile their own binary?
How many Windows users have namecoin? At the time, it was my understanding (from the Namecoin docs) that only Linux was supported.Since the password field is not being used why not have the namecoin wallet address input as that?
That might be an option when the rewrite is done with an automated infrastructure, but wouldn't help for past work/shares, and not viable for doing payouts by hand. Also, there'd be no way for miners to confirm their software is submitting it properly (many cut off username+password too short for two addresses)will this force me to convert the wallet with my current pool btc address to bitcoin client v0.5rc?
October 13, 2011, 01:59:23 PM
Managed to get a cross-compiled static EXE for Windows users; it's linked from the 2nd page of the registration (ie, when you need to use it).
Thanks! I was registered NMC address, but how I can see that it using or will be using ?
October 13, 2011, 01:05:38 PM
Managed to get a cross-compiled static EXE for Windows users; it's linked from the 2nd page of the registration (ie, when you need to use it).
Awesome!
Thanks for putting it up, and thanks to whoever compiled it as well.
October 13, 2011, 12:50:57 PM
Managed to get a cross-compiled static EXE for Windows users; it's linked from the 2nd page of the registration (ie, when you need to use it).
Jump to: