I have created two different test addresses, i sent coins from one to the other, is there a command to check the balance of both addresses? dcrctl --testnet -u user -P pass --wallet getbalance --notls ...........???????? thx
Btw, in case anyone cares - here's what my CPU mining generates: 2 cores Xeon E5-2673 v3 2.4Ghz 97,959 hashes per sec or 0.1 Gh/s. That's about 10% of a GPU. Putting aside the argument about whether or not this is a good thing, I would say that botnets would have a chance at mining this successfully. Does anyone disagree? Edit: I've been pointed out that my math is off by a factor or 1000. Should be 0.01% of a GPU and not a concern.
How long is the delay for wallet syncing? I saw another one come in but nothing yet after 25 mins? 09:44:20 2016-01-28 [INF] RPCS: Block submitted via getwork accepted: 00000000009c3e2331ab04a57de6d38450836c90d10c6673d203b0029acd715c *** Update *** Of course as soon as I post something it comes in. Working! c:\1.TEMPfileCopy\cgminer-decred-w32_27012016>dcrctl /notls --testnet -u ***** -P ***** --wallet getbalance 82.99700001 c:\1.TEMPfileCopy\cgminer-decred-w32_27012016>dcrctl /notls --testnet -u ***** -P ***** --wallet getbalance 97.99700001
You're totally right. Remind me to never do basic math before coffee. OK so, that's about .0001 GH/s or 0.01% of what a GPU can do. That makes the botnet impact pretty negligible even with optimizations.
OK here we go again. Explain to me what is happening here please? It is like it is sending 12dcrd rather than 1 dcrd?!? c:\1.TEMPfileCopy\cgminer-decred-w32_27012016>dcrctl /notls --testnet -u ***** -P ***** --wallet getbalance 97.99700001 c:\1.TEMPfileCopy\cgminer-decred-w32_27012016>dcrctl /notls --testnet -u ***** -P ***** --wallet sendtoaddress TsXuEFgAWCB3yCeW5oRL9eX6NzjsD1rWXdg 1 f488246d682ef72b017e05e0e9ff7f36e770ce2b32d5a56b6093a4cef8b0d69c c:\1.TEMPfileCopy\cgminer-decred-w32_27012016>dcrctl /notls --testnet -u ***** -P ***** --wallet getbalance 85.99700001 *** UPDATE *** And now it is right. Why the big deduct and then actual transaction value discrepancy? c:\1.TEMPfileCopy\cgminer-decred-w32_27012016>dcrctl /notls --testnet -u *****-P ***** --wallet getbalance 85.99700001 c:\1.TEMPfileCopy\cgminer-decred-w32_27012016>dcrctl /notls --testnet -u *****-P ***** --wallet getbalance 96.99699001
OKAY. Got a bit of a strange problem. Last night I was installing/running this stuff as I learnt, which is dumb so I of course missed something somewhere (I think it was a notls flag in one of the bat files I made) and eventually started over. Manually deleted everything the client and wallet created in AppData/Local in Win7. Ran everything again, properly this time, left it running all night and no errors that I could find. But now when I try to check my balance, the wallet can't find rpc.cert. I remember seeing the old one when I deleted everything, and sure enough it isn't there now. For some reason it didn't create a new one. There IS one if /dcrd/ but not /dcrwallet. I'm pretty sure this happened cause I deleted the old installed testnet files, but is there a way to fix/avoid this? EDIT: Should point out I used a different user/pass the second try. edit AGAIN: Well, getbalance is working now. Still had the rpc cert in my recycle bin, so I just restored it.
I ran through setup just fine and am mining away on testnet, but my rpc.cert did not get created and can't check wallet balance. Anyone know why or how I can create it? Thanks
Code: [2016-01-28 21:06:02] Started cgminer 3.7.2 [2016-01-28 21:06:02] Started cgminer 3.7.2 [2016-01-28 21:06:02] Probing for an alive pool [2016-01-28 21:06:05] Pool 0 slow/down or URL or credentials invalid Someone there had trouble with Windows? I'm having some problems, I think we are stupid.
Check out Anondran's comprehensive guide to setting up a testnet address and doing some basic tests. https://forum.decred.org/threads/br...d-receiving-coins-windows-only.355/#post-4802
I found out that the simnet option does NOT put it on the "official" testnet! I thought it did at first, but I still see no need to retract my earlier post because it's actually still correct - it does put you on testnet - A testnet, just not THE testnet. Taking a moment for a side note: I LOVE THIS SHIT! I've often wanted to use the capability of Bitcoin & clones that's referred to as "testnet-in-a-box" - but I always found it so tedious to get working that I never actually did. One reason I wanted to was to test miners for coins with few/no pools, or before launch - in the former case, the mainnet diff may be too high, causing the time required (on average) to pop a block to become too long for testing, and in the latter case, there's no mainnet at all. But this shit is awesome! You can set up your own testnet-in-a-box effortlessly - for any purpose you may need it for! Anyways, tangent over - let me clarify how I've gotten up and running on the current official testnet and mined some tDCR for myself! This is to be done on the system with which you wish to run your main (real) instance of dcrd, as well as dcrwallet and where you plan to access it using dcrctl. All Decred-related binaries are assumed to be in PATH (I like to stuff 'em in /usr/local/bin, chown them to root, and chmod them to 711.) Screen is used in my examples so that you don't need to keep open a shitton of terminals/tabs (I love screen; I use it myself for this and other purposes, too.) Code: screen -dmS decred dcrd --notls --testnet --rpcuser=Slut --rpcpas=x This won't put you in the screen - it will run the command in a detached one for you, which you may access at any time using: Code: screen -dr decred To detach yourself from the screen you're in, hold down Ctrl, press and release a, then d, and then you may let go of Ctrl. To create a wallet - first open a screen for it and attach, then run dcrwallet. I don't have a detailed walkthrough on getting you through the prompts, as I created mine a while ago, but you should be fine. Code: screen -S dcrwallet dcrwallet --noservertls --noclienttls -u Slut -P x --create I'm not totally sure on that dcrwallet command, but it's something on that order - the help output is your friend. Note that I DIDN'T use "--testnet" - testnet is apparently the default, at least for the binary I have. Finally, you should be ready to use your wallet/daemon using dcrctl - this will get you a new address; for other commands, as I said, see the help outputs. Code: dcrctl -u Slut -P x --notls --testnet --wallet getnewaddress If you opted for hiding the wallet details behind another password during wallet creation, you'll need to provide this to dcrwallet on the command line. Nitpick: You know what I don't get? Security is *so* important that we can't bind the RPC server to anything except localhost without TLS - and this is ENFORCED, currently, by the code - yet the password for the wallet information (which is admittedly less sensitive than the main wallet pass) can be passed to dcrwallet on the COMMAND LINE. If you don't get why it's funny - try running it on a linux-based machine under your account, then sudo su to an unprivileged account (I used the git account, because it had a shell that wasn't /sbin/nologin or /bin/false), and then run ps ax and pipe it to grep dcrwallet. Oops, any unprivileged user now knows the password for the (less sensitive) wallet information just by listing the active processes. Note that this CAN be fixed simply by using a config file (I THINK - I still haven't really gotten into using those with Decred yet), but I just find it kind of funny that TLS is enforced in the damned binary because apparently we can't make that security decision for ourselves... yet the accidental leak I just mentioned I haven't even seen a warning about, let alone a straight up action from the devs that disallows it.
What you're doing wrong is not fixing the code yourself to properly check network difficulty before displaying that in some cases. It IS checked before submissions, though - watch the accepted/rejected/HW error counters, as these should indicate real shit going on.
Also at 1 gigahash, i'm always accepting 0 shares and receiving "share above target", massages!!! is anything wrong wiht my setup? Is also 1 gigahash too low as hashrate? cgminer version 3.7.2 - Started: [2016-01-31 11:11:09] -------------------------------------------------------------------------------- (5s):1.118G (avg):1.017Gh/s | A:0 R:0 HW:0 WU:6.2/m ST: 4 SS: 0 NB: 10 LW: 0 GF: 0 RF: 0 Connected to 127.0.0.1 diff 796 without LP as user xxxx Block: c2274200... Diff:836 Started: [11:27:25] Best share: 41 -------------------------------------------------------------------------------- [P]ool management [G]PU management ettings [D]isplay options [Q]uit GPU 0: | 1.113G/1.018Gh/s | A:0 R:0 HW:0 WU:6.2/m I: 8 GPU 1: | OFF /867.3Kh/s | A:0 R:0 HW:0 WU:0.0/m I: 2 -------------------------------------------------------------------------------- [2016-01-31 11:27:21] New block detected on network [2016-01-31 11:27:21] (5s):1.026G (avg):1.013Gh/s | A:0 R:0 HW:0 WU:6.2/m [2016-01-31 11:27:22] Share above target [2016-01-31 11:27:25] Share above target [2016-01-31 11:27:25] New block: 00000000c2274200fd52a69be3f8051e2d4726a57b731d 5b0153748716e00e7b... diff 836 [2016-01-31 11:27:25] New block detected on network [2016-01-31 11:27:26] (5s):1.145G (avg):1.015Gh/s | A:0 R:0 HW:0 WU:6.3/m [2016-01-31 11:27:31] (5s):1.133G (avg):1.015Gh/s | A:0 R:0 HW:0 WU:6.3/m [2016-01-31 11:27:36] (5s):1.125G (avg):1.016Gh/s | A:0 R:0 HW:0 WU:6.3/m [2016-01-31 11:27:41] (5s):1.119G (avg):1.016Gh/s | A:0 R:0 HW:0 WU:6.2/m [2016-01-31 11:27:46] (5s):1.118G (avg):1.017Gh/s | A:0 R:0 HW:0 WU:6.2/m
Before we address that no one can answer whether or not your hashrate is "good" without knowing the hardware you're running, let's talk about the share above target issues. What driver version are you running?
my hardware is: AMD Radeon 5850 my driver version: Catalyst 15.7.1 Windows 7 i've been running the testnet for two hours, and the cgminer A: value is always at 0