Thanks to Jared for answering my questions about the wallet!
YC
Topic: ★★DigiByte|极特币★★[DGB]✔ Core v6.16.5.1 - DigiShield, DigiSpeed, Segwit - page 1292. (Read 3059029 times)
August 17, 2014, 02:36:27 PM
August 17, 2014, 02:04:05 PM
I got rid of my failover pools in my config and removed failover only so now I am ONLY pointing at my Debian box for solo mining and no longer using the failover pools for longpoll... and now I am getting this which seems positive... as in it's detecting difficulty changes and block changes? Is this working as far as you guys can tell?
I'm not sure but i think that it's not working as it should also be showing that it's submiting shares, no?Code:
cgminer version 4.3.5 - Started: [2014-08-17 07:33:51]
--------------------------------------------------------------------------------
(5s):0.000 (1m):0.000 (5m):0.000 (15m):0.000 (avg):0.000h/s
A:0 R:0 HW:0 WU:0.0/m
Connected to 10.x.x.175 diff 18.8M without LP as user xxxxxxxxx
Block: 8e52c6c4... Diff:287 Started: [07:55:44] Best share: 0
--------------------------------------------------------------------------------
[U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit
0: ZUS ttyUSB0: 256 chips 220 MHz | 0.000 / 0.000h/s WU:0.0/m
--------------------------------------------------------------------------------
[2014-08-17 07:33:47] Started cgminer 4.3.5
[2014-08-17 07:33:50] Found Zeus at /dev/ttyUSB0, mark as 0
[2014-08-17 07:33:50] ZUS0 opened on /dev/ttyUSB0
[2014-08-17 07:33:50] Probing for an alive pool
[2014-08-17 07:33:50] Solo mining to valid address: DLA9xQiGV99Vzf79aWcXVGhAkBv
1pGt9sG
[2014-08-17 07:33:50] Block change for http://10.20.30.175:14022 detection via
getblockcount polling
[2014-08-17 07:33:51] Network diff set to 431
[2014-08-17 07:33:56] API running in IP access mode on port 4028 (13)
[2014-08-17 07:55:44] Block height change to 141803 detected on pool 0
[2014-08-17 07:55:44] Network diff set to 287
--------------------------------------------------------------------------------
(5s):0.000 (1m):0.000 (5m):0.000 (15m):0.000 (avg):0.000h/s
A:0 R:0 HW:0 WU:0.0/m
Connected to 10.x.x.175 diff 18.8M without LP as user xxxxxxxxx
Block: 8e52c6c4... Diff:287 Started: [07:55:44] Best share: 0
--------------------------------------------------------------------------------
[U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit
0: ZUS ttyUSB0: 256 chips 220 MHz | 0.000 / 0.000h/s WU:0.0/m
--------------------------------------------------------------------------------
[2014-08-17 07:33:47] Started cgminer 4.3.5
[2014-08-17 07:33:50] Found Zeus at /dev/ttyUSB0, mark as 0
[2014-08-17 07:33:50] ZUS0 opened on /dev/ttyUSB0
[2014-08-17 07:33:50] Probing for an alive pool
[2014-08-17 07:33:50] Solo mining to valid address: DLA9xQiGV99Vzf79aWcXVGhAkBv
1pGt9sG
[2014-08-17 07:33:50] Block change for http://10.20.30.175:14022 detection via
getblockcount polling
[2014-08-17 07:33:51] Network diff set to 431
[2014-08-17 07:33:56] API running in IP access mode on port 4028 (13)
[2014-08-17 07:55:44] Block height change to 141803 detected on pool 0
[2014-08-17 07:55:44] Network diff set to 287
stratum+tcp://eu.p2pool.sk:9022
username 'your DGB address'
password 'x'
you can check if you get your miner listed and if shares are being submitted
http://eu.p2pool.sk:9022
algo=scrypt
August 17, 2014, 12:42:38 PM
I'm not sure but i think that it's not working as it should also be showing that it's submiting shares, no?
Yeah I think so... I should have enough hashpower to solo discover blocks reasonably quickly, yet I get nada.... it's really frustrating as it seems I am doing everything right. Whatever, just finishing off an Ubuntu build to see if that makes any difference, but in the meantime I'm back on P2Pool for the moment...
August 17, 2014, 12:38:54 PM
I got rid of my failover pools in my config and removed failover only so now I am ONLY pointing at my Debian box for solo mining and no longer using the failover pools for longpoll... and now I am getting this which seems positive... as in it's detecting difficulty changes and block changes? Is this working as far as you guys can tell?
I'm not sure but i think that it's not working as it should also be showing that it's submiting shares, no? Code:
cgminer version 4.3.5 - Started: [2014-08-17 07:33:51]
--------------------------------------------------------------------------------
(5s):0.000 (1m):0.000 (5m):0.000 (15m):0.000 (avg):0.000h/s
A:0 R:0 HW:0 WU:0.0/m
Connected to 10.x.x.175 diff 18.8M without LP as user xxxxxxxxx
Block: 8e52c6c4... Diff:287 Started: [07:55:44] Best share: 0
--------------------------------------------------------------------------------
[U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit
0: ZUS ttyUSB0: 256 chips 220 MHz | 0.000 / 0.000h/s WU:0.0/m
--------------------------------------------------------------------------------
[2014-08-17 07:33:47] Started cgminer 4.3.5
[2014-08-17 07:33:50] Found Zeus at /dev/ttyUSB0, mark as 0
[2014-08-17 07:33:50] ZUS0 opened on /dev/ttyUSB0
[2014-08-17 07:33:50] Probing for an alive pool
[2014-08-17 07:33:50] Solo mining to valid address: DLA9xQiGV99Vzf79aWcXVGhAkBv
1pGt9sG
[2014-08-17 07:33:50] Block change for http://10.20.30.175:14022 detection via
getblockcount polling
[2014-08-17 07:33:51] Network diff set to 431
[2014-08-17 07:33:56] API running in IP access mode on port 4028 (13)
[2014-08-17 07:55:44] Block height change to 141803 detected on pool 0
[2014-08-17 07:55:44] Network diff set to 287
--------------------------------------------------------------------------------
(5s):0.000 (1m):0.000 (5m):0.000 (15m):0.000 (avg):0.000h/s
A:0 R:0 HW:0 WU:0.0/m
Connected to 10.x.x.175 diff 18.8M without LP as user xxxxxxxxx
Block: 8e52c6c4... Diff:287 Started: [07:55:44] Best share: 0
--------------------------------------------------------------------------------
[U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit
0: ZUS ttyUSB0: 256 chips 220 MHz | 0.000 / 0.000h/s WU:0.0/m
--------------------------------------------------------------------------------
[2014-08-17 07:33:47] Started cgminer 4.3.5
[2014-08-17 07:33:50] Found Zeus at /dev/ttyUSB0, mark as 0
[2014-08-17 07:33:50] ZUS0 opened on /dev/ttyUSB0
[2014-08-17 07:33:50] Probing for an alive pool
[2014-08-17 07:33:50] Solo mining to valid address: DLA9xQiGV99Vzf79aWcXVGhAkBv
1pGt9sG
[2014-08-17 07:33:50] Block change for http://10.20.30.175:14022 detection via
getblockcount polling
[2014-08-17 07:33:51] Network diff set to 431
[2014-08-17 07:33:56] API running in IP access mode on port 4028 (13)
[2014-08-17 07:55:44] Block height change to 141803 detected on pool 0
[2014-08-17 07:55:44] Network diff set to 287
August 17, 2014, 12:17:56 PM
August 17, 2014, 12:14:08 PM
Hate to keep asking the same question on wallet upgrades, but do we just run the installer and let it overwrite the existing contents of the old version? Do we need to delete any app/roaming folders or specific files?
YC
Please give us feedback if everything worked for you, especially with the OSX wallet. Mining pool, exchange & block explorer operators please notify us when you have updated your DigiByte wallet.
It is very important we get everyone updated before block 145,000 as at that point sending coins from a v3.01 wallet to a v2.9.1 wallet or earlier could result in problems.
As always, backup your wallet.dat before upgrading! (File -> Backup Wallet -> Select location to save to)
1) To update DigiShield and speed the blockchain back up to normal.
2) It is the most fair POW mining option out there (embraces ASICs & GPU miners alike on an even playing field).
3) More secure than a single POW mining scheme (much harder to 51% attack).
4) Speed block timing up to 30 seconds to facilitate faster merchant transactions (ties in with DigiPay LLC development).
5) Tap into used Bitcoin ASIC miners market. (Use those old ASICS to help secure the DGB blockchain)
If you can think of another reason multi-POW is better, let us know!
You need to set the algo you want to mine in the digibyte.conf:
Once multi-algo mining kicks in you need one of these settings in your .conf to solo mine whichever algo you choose:
YC
Introducing DigiByte v3.0.1 MultiAlgo
Mandatory Update before block 145,000
Please give us feedback if everything worked for you, especially with the OSX wallet. Mining pool, exchange & block explorer operators please notify us when you have updated your DigiByte wallet.
It is very important we get everyone updated before block 145,000 as at that point sending coins from a v3.01 wallet to a v2.9.1 wallet or earlier could result in problems.
As always, backup your wallet.dat before upgrading! (File -> Backup Wallet -> Select location to save to)
DigiByte v3.01 Wallet Downloads
Note: It may be necessary to reindex/rebuild the chain after upgrading.
Why did DigiByte switch to Multi-Algo mining?
1) To update DigiShield and speed the blockchain back up to normal.
2) It is the most fair POW mining option out there (embraces ASICs & GPU miners alike on an even playing field).
3) More secure than a single POW mining scheme (much harder to 51% attack).
4) Speed block timing up to 30 seconds to facilitate faster merchant transactions (ties in with DigiPay LLC development).
5) Tap into used Bitcoin ASIC miners market. (Use those old ASICS to help secure the DGB blockchain)
If you can think of another reason multi-POW is better, let us know!
MultiAlgo DigiByte.conf & Options
You need to set the algo you want to mine in the digibyte.conf:
Code:
rpcallowip=*
rpcuser=yourusername
rpcpassword=yourpassword
server=1
daemon=1
txindex=1
debug=1
algo=scrypt
rpcport=14022
port=12024
addnode=216.250.125.121
addnode=74.208.230.160
addnode=74.112.204.202
addnode=46.4.32.220
addnode=198.27.109.88
addnode=54.204.36.33
addnode=198.41.184.140
addnode=144.76.94.182
addnode=95.85.50.188
addnode=162.159.240.70
rpcuser=yourusername
rpcpassword=yourpassword
server=1
daemon=1
txindex=1
debug=1
algo=scrypt
rpcport=14022
port=12024
addnode=216.250.125.121
addnode=74.208.230.160
addnode=74.112.204.202
addnode=46.4.32.220
addnode=198.27.109.88
addnode=54.204.36.33
addnode=198.41.184.140
addnode=144.76.94.182
addnode=95.85.50.188
addnode=162.159.240.70
Once multi-algo mining kicks in you need one of these settings in your .conf to solo mine whichever algo you choose:
Code:
algo=scrypt
algo=sha256d
algo=groestl
algo=qubit
algo=skein
algo=sha256d
algo=groestl
algo=qubit
algo=skein
Updated DigiByte v3.0.1 Exchanges
None Yet
Old DigiByte v2.0 & v2.9.1 Exchanges
Updated DigiByte v3.0.1 MultiAlgo Pools
None Yet
Old DigiByte v2.0 & v2.9.1 DigiShield Pools
More Coins | Crypto Pool Mining | Dedicated Pool | Coinium | Coin King
Chunky Pools | Palmetto Miners
Chunky Pools | Palmetto Miners
P2P Pools Updated to DigiByte v3.0.1 MultiAlgo
None Yet
Old DigiByte v2.0 & v2.9.1 DigiShield P2P Pools
August 17, 2014, 12:02:10 PM
Does anyone know if http://dgb.blazinghashes.com/ is working? I would like to get some SCRYPT hashs in while waiting for SHA256....
You could try to mine on my p2pool node...
seems to be working, scrypt.
Thx. I'll send a little bit over and see how it goes....
August 17, 2014, 11:48:17 AM
@Digibyte
I think it was when you were in Japan that we discussed how many transactions per second the blockchain could handle. If I remember correctly I thought it was 7. Has this been increased in this new version? What other fixes were made in order to prepare for the micro-transactions?
I think it was when you were in Japan that we discussed how many transactions per second the blockchain could handle. If I remember correctly I thought it was 7. Has this been increased in this new version? What other fixes were made in order to prepare for the micro-transactions?
August 17, 2014, 10:36:31 AM
Win. x64 tested.
Sync. ✔
receive. ✔
send. ✔
A small dutch language thing i mentioned.
Sync. ✔
receive. ✔
send. ✔
A small dutch language thing i mentioned.
August 17, 2014, 09:51:45 AM
Does anyone know if http://dgb.blazinghashes.com/ is working? I would like to get some SCRYPT hashs in while waiting for SHA256....
no it is not working as you might face some problem if you use it
August 17, 2014, 09:50:13 AM
UPDATED TO DIGIBYTE v3.0.1
Based in Strasbourg (France)
DDoS resistant
Up 24h/24h
No registration needed
NEW : difficulty automatically adjusts for each miner (best for small miners)
DDoS resistant
Up 24h/24h
No registration needed
NEW : difficulty automatically adjusts for each miner (best for small miners)
Difficulty adjustment based on source code from https://github.com/roy7/p2pool/tree/vardiffbyaddress
It enables small miners to make more shares and to receive more regular payments.
It seems that there is less DOA too.
LIMP2POOL node works with no problem since 2 months.
@Digibyte : can you please add my node to the list of p2pool nodes. Thanks!
August 17, 2014, 08:10:13 AM
Does anyone know if http://dgb.blazinghashes.com/ is working? I would like to get some SCRYPT hashs in while waiting for SHA256....
You could try to mine on my p2pool node...
seems to be working, scrypt.
August 17, 2014, 08:08:46 AM
Does anyone know if http://dgb.blazinghashes.com/ is working? I would like to get some SCRYPT hashs in while waiting for SHA256....
August 17, 2014, 07:13:06 AM
Mac Wallet (MultiAlgo) works fine on my Mac (iMac 3.4 Ghz Intel Core i7, 16 Go RAM, OS X 10.9.4) 
Thanks for the feedback! That is great to hear! 
send digbytes is working on the mac!
one thing: works the mac wallet also on 10.10.0 yosmite? (that's system in coming in 2/3 weeks)
yes, its ok
August 17, 2014, 07:10:31 AM
I got a great feeling about DGB When ASICs came in very soon, most of the coins will have a down trend and people will jump those ships and join DGB 
I look forward to it.... LTC will continue plummeting and maybe one day DGB will replace LTC Why not ?
When ASICs came in very soon, most of the coins will have a down trend and people will jump those ships and join DGB I look forward to it.... LTC will continue plummeting and maybe one day DGB will replace LTC
Why not ? August 17, 2014, 06:32:04 AM
Mac Wallet (MultiAlgo) works fine on my Mac (iMac 3.4 Ghz Intel Core i7, 16 Go RAM, OS X 10.9.4)
Thanks for the feedback! That is great to hear! send digbytes is working on the mac!
one thing: works the mac wallet also on 10.10.0 yosmite? (that's system in coming in 2/3 weeks)
August 17, 2014, 05:58:13 AM
I checked just briefly if it works (cpuminer) and it seems to.
August 17, 2014, 03:44:59 AM
Mac Wallet (MultiAlgo) works fine on my Mac (iMac 3.4 Ghz Intel Core i7, 16 Go RAM, OS X 10.9.4)
Thanks for the feedback! That is great to hear! August 17, 2014, 03:29:34 AM
Mac Wallet (MultiAlgo) works fine on my Mac (iMac 3.4 Ghz Intel Core i7, 16 Go RAM, OS X 10.9.4)
August 17, 2014, 03:02:13 AM
I got rid of my failover pools in my config and removed failover only so now I am ONLY pointing at my Debian box for solo mining and no longer using the failover pools for longpoll... and now I am getting this which seems positive... as in it's detecting difficulty changes and block changes? Is this working as far as you guys can tell?
Code:
cgminer version 4.3.5 - Started: [2014-08-17 07:33:51]
--------------------------------------------------------------------------------
(5s):0.000 (1m):0.000 (5m):0.000 (15m):0.000 (avg):0.000h/s
A:0 R:0 HW:0 WU:0.0/m
Connected to 10.x.x.175 diff 18.8M without LP as user xxxxxxxxx
Block: 8e52c6c4... Diff:287 Started: [07:55:44] Best share: 0
--------------------------------------------------------------------------------
[U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit
0: ZUS ttyUSB0: 256 chips 220 MHz | 0.000 / 0.000h/s WU:0.0/m
--------------------------------------------------------------------------------
[2014-08-17 07:33:47] Started cgminer 4.3.5
[2014-08-17 07:33:50] Found Zeus at /dev/ttyUSB0, mark as 0
[2014-08-17 07:33:50] ZUS0 opened on /dev/ttyUSB0
[2014-08-17 07:33:50] Probing for an alive pool
[2014-08-17 07:33:50] Solo mining to valid address: DLA9xQiGV99Vzf79aWcXVGhAkBv
1pGt9sG
[2014-08-17 07:33:50] Block change for http://10.20.30.175:14022 detection via
getblockcount polling
[2014-08-17 07:33:51] Network diff set to 431
[2014-08-17 07:33:56] API running in IP access mode on port 4028 (13)
[2014-08-17 07:55:44] Block height change to 141803 detected on pool 0
[2014-08-17 07:55:44] Network diff set to 287
--------------------------------------------------------------------------------
(5s):0.000 (1m):0.000 (5m):0.000 (15m):0.000 (avg):0.000h/s
A:0 R:0 HW:0 WU:0.0/m
Connected to 10.x.x.175 diff 18.8M without LP as user xxxxxxxxx
Block: 8e52c6c4... Diff:287 Started: [07:55:44] Best share: 0
--------------------------------------------------------------------------------
[U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit
0: ZUS ttyUSB0: 256 chips 220 MHz | 0.000 / 0.000h/s WU:0.0/m
--------------------------------------------------------------------------------
[2014-08-17 07:33:47] Started cgminer 4.3.5
[2014-08-17 07:33:50] Found Zeus at /dev/ttyUSB0, mark as 0
[2014-08-17 07:33:50] ZUS0 opened on /dev/ttyUSB0
[2014-08-17 07:33:50] Probing for an alive pool
[2014-08-17 07:33:50] Solo mining to valid address: DLA9xQiGV99Vzf79aWcXVGhAkBv
1pGt9sG
[2014-08-17 07:33:50] Block change for http://10.20.30.175:14022 detection via
getblockcount polling
[2014-08-17 07:33:51] Network diff set to 431
[2014-08-17 07:33:56] API running in IP access mode on port 4028 (13)
[2014-08-17 07:55:44] Block height change to 141803 detected on pool 0
[2014-08-17 07:55:44] Network diff set to 287
Jump to: