SOLO mining no work ? my config{ "pools" : [ { "url" : "127.0.0.1:14022", "user" : "user", "pass" : "pass" } ] , "intensity" : "20,20,20,18", "worksize" : "128,128,128,128", "kernel" : "myriadcoin-groestl", "lookup-gap" : "2,2,2,2", "thread-concurrency" : "8192,8192,8192,8192", "shaders" : "0,0,0,0", "gpu-threads" : "2,2,2,2", "gpu-engine" : "1000,1000,1000,925", "gpu-fan" : "80,80,80,80", "gpu-memclock" : "170,170,170,150", "gpu-memdiff" : "0,0,0,0", "gpu-powertune" : "0,0,0,0", "gpu-vddc" : "0.000", "temp-cutoff" : "95,95,95,95", "temp-overheat" : "85,85,85,85", "temp-target" : "75,75,75,75", "api-mcast-port" : "4028,4028,4028,4028", "api-port" : "4028,4028,4028,4028", "expiry" : "28,28,28,28", "failover-switch-delay" : "60,60,60,60", "gpu-dyninterval" : "7,7,7,7", "gpu-platform" : "0", "log" : "5,5,5,5", "no-pool-disable" : true, "queue" : "1,1,1,1", "scan-time" : "7,7,7,7", "tcp-keepalive" : "30,30,30,30", "temp-hysteresis" : "3,3,3,3", "shares" : "0,0,0,0", "kernel-path" : "/usr/local/bin" } and my bat no connect set GPU_MAX_ALLOC_PERCENT=100 setx GPU_MAX_ALLOC_PERCENT 100 sgminer -I 20,20,20,18 -g 4 -w 256 -k myriadcoin-groestl --no-submit-stale -o 127.0.0.1:14022 -u user -p pass --lookup-gap 2 --gpu-fan 80,80,80,80 --thread-concurrency 8192,8192,8192,8192 my digibyte.conf from roaming rpcuser=user rpcpassword=pass rpcport=14022 rpcallowip=127.0.0.1 server=1 daemon=1 gen=0 txindex=1 algo=groestl Help me please for solo mining!! on pool all work good Hi we already had this discussion early on Telegram.
You need new rpcauth method!https://github.com/digibyte/digibyte/tree/6.14.0/share/rpcuserThis was some days ago on DigiByte Offical Chat hope it helps: Gary Mckee, [25.03.17 16:06] that branch is ahead of 5.4.2 Gary Mckee, [25.03.17 16:06] rpcuser/rpcpassword should still work twebit, [25.03.17 16:06] the thing is I mine with the old deamon no problem but the new way of mining has changed something and rpcuser/rpcpassword doesn't work now Gary Mckee, [25.03.17 16:06] https://github.com/digibyte/digibyte/tree/6.14.0/share/rpcuserGary Mckee, [25.03.17 16:07] so ./rpcuser user Gary Mckee, [25.03.17 16:07] will generate an auth for you to put in your digibyte.conf twebit, [25.03.17 16:07] I generated the .cookie file and put it in my config twebit, [25.03.17 16:08] already twebit, [25.03.17 16:08] rpcauth=_cookie_:numbers Gary Mckee, [25.03.17 16:08] whats your digibyte.conf look like twebit, [25.03.17 16:09] server=1 listen=1 deamon=1 algo=sha256d rpcauth=__cookie__:thenumber rpcpassword=thepw rpcallowip=192.168.1.12/24 rpcport=14022 port=12024 maxconnections=10 addnode=46.4.66.6 Gary Mckee, [25.03.17 16:10] what are you using for bfgminer password Gary Mckee, [25.03.17 16:10] should be no need for rpcpassword Gary Mckee, [25.03.17 16:11] if you have rpcauth twebit, [25.03.17 16:11] thepw (its a long number) Gary Mckee, [25.03.17 16:11] so if you run the script i linked before Gary Mckee, [25.03.17 16:11] the output is Gary Mckee, [25.03.17 16:11] String to be appended to digibyte.conf: rpcauth=user:5958c94d2bfd7eca2db5cfd126fc7eb1$2b2b0f060afc89ce848d7a9a006eecbe4776e3271d533665e1504f3236ea20ef Your password: C-lqqs6x3gayJwBqPr_wxjAoQ3Gm82L45HQ6zN6l6d8= Gary Mckee, [25.03.17 16:11] rpcauth=user:5958c94d2bfd7eca2db5cfd126fc7eb1$2b2b0f060afc89ce848d7a9a006eecbe4776e3271d533665e1504f3236ea20ef Gary Mckee, [25.03.17 16:11] is what you would put in digibyte.conf Gary Mckee, [25.03.17 16:11] but Gary Mckee, [25.03.17 16:11] C-lqqs6x3gayJwBqPr_wxjAoQ3Gm82L45HQ6zN6l6d8= Gary Mckee, [25.03.17 16:11] is what you would use for bfgminer twebit, [25.03.17 16:12] oh no I copied it from the text file cookie eg; __cookie__:the long number Gary Mckee, [25.03.17 16:12] yeah that's probably why Gary Mckee, [25.03.17 16:12] try adding the rpcauth command i just posted into digibyte.conf Gary Mckee, [25.03.17 16:13] close/restart wallet Gary Mckee, [25.03.17 16:13] and use C-lqqs6x3gayJwBqPr_wxjAoQ3Gm82L45HQ6zN6l6d8= as your bfgminer password twebit, [25.03.17 16:13] ok so user:longnumber into the config ah ok and the pw for bfgminer OK I'll be back in 10 minutes while I startup again Gary Mckee, [25.03.17 16:14] also remove rpcpassword twebit, [25.03.17 16:15] what about the bfgminer user still the same I have digibyterpc as the user now twebit, [25.03.17 16:15] ok Gary Mckee, [25.03.17 16:15] user will be 'user' twebit, [25.03.17 16:15] ok twebit, [25.03.17 16:21] and then that same long number in my bfgminer for pw? twebit, [25.03.17 16:22] starting now will be 10 miutes Gary Mckee, [25.03.17 16:22] nah Gary Mckee, [25.03.17 16:22] gonna PM you twebit, [25.03.17 16:22] ok Mike Jumbley, [25.03.17 16:50] Don’t forget to document it all twe. 😊 twebit, [25.03.17 16:50] I won't 😊 |
|
|
|
I rest my case. Everyone has said their piece and anyone with a cent of common sense can see what there is to see here and make their appropriate decisions.
When someone attacks you publicly accusing you of trying to extort them when they actually turned down the business deal of their lives, and then so calmly turns the world upside down and calls you the attacker, well, we all know what that is, or at least those of us who are successful do (because being successful means staying clear of those types).
Good luck Jared.
_______________________________________________________________________________ ________________
I made lots of money with DGB and I'll always remember it fondly, something that could have been great, but it's time to say goodbye. Always best to leave while you're a winner.
Oh, by the way, did anybody think to ask just how DigiByte got on CryptoID? They're soooo busy that they can't even document what they're doing (not even release notes? that should be a cut and paste of the coding . . . more or less . . . anybody with just a little exposure to that knows what I'm talking about), can't get anything right with lightweight wallets, DiguSign, etc., and complain about you reporting the issues, do you think it was DigiByte? Hell no! They don't want you to have that much blockchain info. They don't want you to have a rich list. Has anyone checked to see if what Jared said yesterday really jives with the real data rich list?
If you are answering these questions with a "no", or "don't know", do yourself a favor and do a reality check. That's just one of many examples too. And if you're asking what the others are, go back and read again, starting in 2014. And if you're too lazy, then save yourself the pain and start looking at the 2nd generation cryptocurrencies - many are already doing what DigiByte says it wants to someday do (without a road map of course, we all know the drill by now, maybe it'll change again, but by that time someone else will have it implemented - a day late, a dollar short). With these kinds of attitudes, complacency and arrogance, they wouldn't be able to make this thing successful even if someone gave it to them.
Just my assessment. Good luck with yours.
And don't blame me. 350 is still a phenomenal cash out level.
Cheers
HR it was a pleasure to had you here. You always welcome back. The Internet wont forget! Here is a song for all you effort! https://vimeo.com/164867542http://www.azlyrics.com/lyrics/tremonti/unabletosee.html |
|
|
|
so i love the digibyte gaming thing. i already got it hooked up to my LoL account.
i was wondering if they plan to add overwatch in there.
playing solo que competitive is soul shattering, but knowing i may be earning some DGB when playing can make these games less anger inducing i think.
I think its still locked because of api hacking css etc... only LOL is save with api but i guees they will fix it soon. Im on DGB Gaming as well and waiting till CSS will go again! |
|
|
|
DGB Up again  Last Price 0.00000097 24hr Change 7.78% 24hr High 0.00000112 24hr Low 0.00000087 24hr Volume: 1400.83349072 BTC / 1404432065.16573250 DGB Kryptowährung/Münze Code Kurs Marktkapitalisierung Handelsvolumen Digibyte DGB 0,00000097 ฿ 7.863,8 ฿ 1.583,7 ฿ |
|
|
|
When is DGB Gaming Back? and please watch your gramma! We are pausing all payouts until we fix some issues with exploits in payout API interface. Than you for your understanding. ThanK you!  |
|
|
|
Yes, please add other nodes and start your client with the -reindex command-line option46.4.66.6
134.255.221.7
178.33.228.14
95.47.155.37
176.9.61.40
54.89.21.44
68.63.19.64
108.61.10.90
213.73.136.90
60.205.112.102
104.238.187.114
86.31.44.129
86.31.245.140
185.128.41.158
162.243.59.178
176.31.126.191
104.131.142.198
173.212.199.201
130.240.22.202
93.113.101.229
The new wallet currently being tested will overcome your issues but for now you need patience. Anyone having trouble with core wallet connecting, you may need to add seed nodes. 1. Help 2. Debug window 3. Console and enter addnode “[any of the above IPs]” “add” eg. addnode “93.113.101.229” “add”
|
|
|
|
★★DigiByte Gaming is down! ★★Please fix ASAP. THX
500 Internal Server Error
If you are the administrator of this website, then please read this web application's log file and/or the web server's log file to find out what went wrong. BTW digibyte IRC also down... |
|
|
|
★★DigiByte Gaming is down! ★★Please fix ASAP. THX
500 Internal Server Error
If you are the administrator of this website, then please read this web application's log file and/or the web server's log file to find out what went wrong. |
|
|
|
If DGB is so into gaming then we need to some how try to get Digibyte integrated here, this is the new App for Gamers & its one of the best places to be...If DGB could get the tipping thing going on here its going to be onto a winner, The list of games on its front page should look very familiar https://discordapp.com/Cool app. Would be nice if they dip into this! |
|
|
|
Just for the community and nerds.... Im mining cpu with crazy speed. Using DataLiquid  |
|
|
|
By the way, sorry for my english |
|
|
|
And no need to create a new wallet in order to reset the transaction history, right?
Thank you guys for your fast and qualitive answers.
I dont think so, should work wihtout reset. If you want to clear transactions you can do it, but would not recommand it. Never tried it -zapwallettxes Clear list of wallet transactions (diagnostic tool; implies -rescan) |
|
|
|
I am unable to get the iOS wallet to sync still. Does anyone else have this problem?
sorry no ios only VM but would take a while till setup. Guess you are on mobile, which ios version? |
|
|
|
Yup it sure will, it will basically reduce the size of the transaction allowing it to be included in a block.
Yep, |
|
|
|
Hi guys,
A friend have actually a really strange problem with his desktop DGB wallet : he's limited by a max amount of DGB to sent. Moreover, his fees are huge compared of mine.
Eg : Yesterday, I have transfered 336 000 DGB for a total fees of 42 DGB. My friend need to pay 96 DGB for a transfer of 38 000 DGB only. Have I missed something? Is there a rule that increase the fees to be paid the more you make transaction? This doesn't sound logic at all, and I've never read anything related to this.
We are both on the 4.0.3 wallet, 64 bits... on Windows.
You can set in your wallet! Maybe you changed it or he changed something!?Note that getting a transaction relayed across the network does NOT guarantee that the transaction will be accepted by a miner; by default, miners fill their blocks with 50 kilobytes of high-priority transactions, and then with 700 kilobytes of the highest-fee-per-kilobyte transactions. The minimum relay/mining fee-per-kilobyte may be changed with the minrelaytxfee option. Note that previous releases incorrectly used the mintxfee setting to determine which low-priority transactions should be considered for inclusion in blocks. The wallet code still uses a default fee for low-priority transactions of 0.1mBTC per kilobyte. During periods of heavy transaction volume, even this fee may not be enough to get transactions confirmed quickly; the mintxfee option may be used to override the default. These are the options in the wallet:-paytxfee=<amt> Fee per kB to add to transactions you send -mintxfee=<amt> Fees smaller than this are considered zero fee (for transaction creation) (default: 1.00) -minrelaytxfee=<amt> Fees smaller than this are considered zero fee (for relaying) (default: 1.00) -blockprioritysize=<n> Set maximum size of high-priority/low-fee transactions in bytes (default: 50000) Maybe he changed this setting in his wallet! |
|
|
|
|
Show Posts
