v0.10.15.x Testing
- Thread starter eduffield
- Start date
- Status
Is it normal that the testnet wallet that I'm using for solo mining is always synching and reporting that it is 0 hours behind? Only when I'm mining though...
Just stopped mining, let QT catch up and then started mining again. You never know, I may have failed to check it was synced in the first place.
is there a problem with the test faucet ? (https://drkipn.com/test/faucet/)
I'm getting no errors while using it but it doesnt show up in my darkcoin adress.
Is that faucet still in sync ?
I'm getting no errors while using it but it doesnt show up in my darkcoin adress.
Is that faucet still in sync ?
Same for me, faucet does not work - let me know your address and i will send you some love
myq6VMGP3PHvrjNW8HA47jfH1rEEF7SBj2Same for me, faucet does not work - let me know your address and i will send you some love
mgYfKt1j4QxM1H2gRVMadzWM4f4MN2t7DySame for me, faucet does not work - let me know your address and i will send you some love
thanks
Edit : got it.. thanks
Last edited by a moderator:
myq6VMGP3PHvrjNW8HA47jfH1rEEF7SBj2
sent
You can download the file here - just put it in the folder %APPDATA%\DarkCoin
http://static.darkcoin.qa/doc/darkcoin.conf
http://static.darkcoin.qa/doc/darkcoin.conf
Awesome. The binary switched to testnet version and I already added "setgenerate true". Please send me tDRK: mxsZhDvXNvqZ4bh1rfxDtsBCbVoZQovaPX
So am I setting up a normal masternode with a testnet wallet & chucking testnet=1 in the darkcoin.conf file? Port 9999 or 9998?
RPC port can be anything. Your firewall needs to be open to 19999 though.
Normal masternode except that you can run with a hot wallet without fear.
Correct, testnet p2p port is 19999, default rpc port is 19998 (just add 10000 to the mainnet ports)
i.e from remote terminal
darkcoind getaccount address 0 (send 1000 tDrk to that address)
etc etc
darkcoind getaccount address 0 (send 1000 tDrk to that address)
etc etc
Easy tiger, you guys are on another level.
I stop my wallet in windows, rename the wallet.dat, let it create a new wallet, send 1000 DRK to that wallet and FTP it into my VPS then change permissions...
All my Masternodes are hot wallets, I just use a long password...
I don't have a static IP and I wanna use AWS for remote for setting up MNs. Is it OK to set IP at "Anywhere" (0.0.0.0 or somehting like this) instead of "My IP"? Can this be used to steal the coins in my local wallet? Or as long as the local wallet encrypted, I shouldn't worry about it.
Last edited by a moderator:
Sorry mate. I might be on another level but that level is probably below most people. I'm half informed, loaded, safety off and ready to fire off bad advice.
No, that's fine, it just means your VPS can theoretically be accessed by someone else. Your local wallet is safe.
If you know the IP range(s) your ISP hands out, you can put those in to at least limit access to your own ISP's users... but for testnet I wouldn't worry too much about it.
Are we still talking about testnet? You don't need to fear theft of testnet coins - i run every testnet node as hot
nope. I am not worried about test coinsAre we still talking about testnet? You don't need to fear theft of testnet coins - i run every testnet node as hot
I was asking that about mainnet MNs setup. edit: Right now I am setting up testnet MNs to learn and once I feel comfortable will switch to mainnet.
- Status