Post
Topic
Board Announcements (Altcoins)
Re: [ANN][DRK] Darkcoin | First Anonymous Coin | Inventor of X11, DGW and Darksend | Instant TX
by
georgem
on 24/09/2014, 05:34:23 UTC

You can do that, but you'll need to generate a unique pwd for each user - otherwise you'll have a bunch of users with the same rpc credentials which is probably not a great idea. What I did was to check for an existing .conf file, and if it didn't exist, or if it threw an error anyway as it didn't include an RPC user/pwd, run the daemon, take the suggested name/pwd and... stick it in the .conf file. Smiley

 Smiley
Ofcourse, didn't the daemon create the unique password for you in the first place?
This is all rather obvious.
My frontend.exe decides the rpc password randomly. On the fly, even for every start of the daemon a new rpc password, why not. It's just an rpc password, not your walletpassphrase.

I was just making an example with your rpc credentials. And you assumed it will be the same for all users?  Grin

I am not sure yet, but I think there is even a parameter with which you can tell darkcoind to NOT use RPC at all.
I assume the reason why it keeps bitching about the missing rpc password/username is because rpc has not been deactived.

Basically I look at it like when I enter mining credentials into cgminer and tell it password=x. Useless but still necessary. It's not like the password has any meaning in this case, but the pool will bitch if you don't add the password parameter.
It will be a similar thing with the frontend and RPC, because who needs a password if the frontend.exe is located right next to the darkcoind.exe on the same machine controlled by the same user, and they are directly talking to each other.

Therefor if it still needs those parameters I will just do:

Code:
>E:\darkcoin/darkcoind -rpcuser=x -rpcpassword=y -testnet=1

rpc username and password is mainly for when you allow outside access to your server.