Perfect - stopped my notebook from mining for now - the noise was peskyOK, solo mining 2.5Mhs.
Never experienced such behaviour... i guess it will stop after a whileIs 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...
Same for me, faucet does not work - let me know your address and i will send you some loveis 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 ?
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![]()
myq6VMGP3PHvrjNW8HA47jfH1rEEF7SBj2
![]()
sentmgYfKt1j4QxM1H2gRVMadzWM4f4MN2t7Dy
thanks
Awesome. The binary switched to testnet version and I already added "setgenerate true". Please send me tDRK: mxsZhDvXNvqZ4bh1rfxDtsBCbVoZQovaPXYou can download the file here - just put it in the folder %APPDATA%\DarkCoin
http://static.darkcoin.qa/doc/darkcoin.conf
BumpGood to know.
How about your masternode tool, are that going to public any time soon?
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.So am I setting up a normal masternode with a testnet wallet & chucking testnet=1 in the darkcoin.conf file? Port 9999 or 9998?
Correct, testnet p2p port is 19999, default rpc port is 19998 (just add 10000 to the mainnet ports)Isn't testnet port 19999?
sentAwesome. The binary switched to testnet version and I already added "setgenerate true". Please send me tDRK: mxsZhDvXNvqZ4bh1rfxDtsBCbVoZQovaPX
Easy tiger, you guys are on another level.i.e from remote terminal
darkcoind getaccount address 0 (send 1000 tDrk to that address)
etc etc
Added missing step in case of unaware.Easy tiger, you guys are on another level.
I stop my wallet in windows, rename the wallet.dat, put testnet=1 in the conf file, let it create a new wallet, send t1000 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...
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.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...
No, that's fine, it just means your VPS can theoretically be accessed by someone else. Your local wallet is safe.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?
Are we still talking about testnet? You don't need to fear theft of testnet coins - i run every testnet node as hotI 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.
Where are you renting your hashing from?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.
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![]()