★★DigiByte|极特币★★[DGB]✔ Core v6.16.5.1 - DigiShield, DigiSpeed, Segwit - page 1292.

DubFX

sr. member

Activity: 434

Merit: 250

Quote from: tdcooper99 on August 17, 2014, 04: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

I'm not sure but i think that it's not working as it should also be showing that it's submiting shares, no?

ycagel

hero member

Activity: 924

Merit: 1000

Look at the DarkCoin decline!

http://coinmarketcap.com/currencies/darkcoin/

ycagel

hero member

Activity: 924

Merit: 1000

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

Quote from: DigiByte on August 16, 2014, 05:17:07 PM

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

GitHub Source Code

Windows Wallet 64-bit DigiByte.co | Windows Wallet 64-bit Dropbox | Windows Wallet 64-bit Mega

Windows Wallet 32-bit DigiByte.co | Windows Wallet 32-bit Dropbox | Windows Wallet 32-bit Mega

Mac OSX Wallet DigiByte.co | Mac OSX Wallet Dropbox | Mac OSX Wallet Mega

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

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

Updated DigiByte v3.0.1 Exchanges

None Yet

Old DigiByte v2.0 & v2.9.1 Exchanges

Moolah (USD) | CryptoCzar (FinCEN) | Cryptsy (FinCEN)

MintPal | COMKORT | All Crypt

Updated DigiByte v3.0.1 MultiAlgo Pools

None Yet

Old DigiByte v2.0 & v2.9.1 DigiShield Pools

P2P Pools Updated to DigiByte v3.0.1 MultiAlgo

None Yet

Old DigiByte v2.0 & v2.9.1 DigiShield P2P Pools

EU P2-Pool P2P | P2P Hash Pool | Secure Nova | P2P E-Pool

RJF

hero member

Activity: 616

Merit: 500

Online since '89...

Quote from: thefrog on August 17, 2014, 09:10:13 AM

Quote from: RJF on August 17, 2014, 09: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....

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....

Kayahoga

full member

Activity: 146

Merit: 100

@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?

24hralttrade

hero member

Activity: 756

Merit: 500

Community Liaison,How can i help you?

Win. x64 tested.

Sync. ✔
receive. ✔
send. ✔

A small dutch language thing i mentioned.

Youghoor

sr. member

Activity: 1036

Merit: 275

Quote from: RJF on August 17, 2014, 09: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....

no it is not working as you might face some problem if you use it

munky87

jr. member

Activity: 30

Merit: 10

UPDATED TO DIGIBYTE v3.0.1

LIMP2POOL.FR:9022

Based in Strasbourg (France)
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!

thefrog

sr. member

Activity: 393

Merit: 250

Quote from: RJF on August 17, 2014, 09: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....

You could try to mine on my p2pool node...
seems to be working, scrypt.

RJF

hero member

Activity: 616

Merit: 500

Online since '89...

Does anyone know if http://dgb.blazinghashes.com/ is working? I would like to get some SCRYPT hashs in while waiting for SHA256....

appbox

sr. member

Activity: 421

Merit: 250

Quote from: ,./,./ on August 17, 2014, 07:32:04 AM

Quote from: DigiByte on August 17, 2014, 04:44:59 AM

Quote from: Rocou on August 17, 2014, 04: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) Cool

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

halinyo

legendary

Activity: 1106

Merit: 1000

The future is bright with DigiByte.

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 Cheesy

I look forward to it.... LTC will continue plummeting and maybe one day DGB will replace LTC

Why not ?

,./,./

sr. member

Activity: 392

Merit: 250

Quote from: DigiByte on August 17, 2014, 04:44:59 AM

Quote from: Rocou on August 17, 2014, 04: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) Cool

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)

thefrog

sr. member

Activity: 393

Merit: 250

p2pool node DGB
with 3000100 digibyted
algo=scrypt
http://eu.p2pool.sk:9022

I checked just briefly if it works (cpuminer) and it seems to.

DigiByte

legendary

Activity: 1722

Merit: 1051

Official DigiByte Account

Quote from: Rocou on August 17, 2014, 04: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) Cool

Thanks for the feedback! That is great to hear!

Rocou

legendary

Activity: 3202

Merit: 1181

Mac Wallet (MultiAlgo) works fine on my Mac (iMac 3.4 Ghz Intel Core i7, 16 Go RAM, OS X 10.9.4) Cool

tdcooper99

full member

Activity: 215

Merit: 100

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

sammy007

legendary

Activity: 1904

Merit: 1003

Quote from: thefrog on August 17, 2014, 03:43:17 AM

You know that Ubuntu is based on Debian, right ? Uses the same packages and so on...
But yes, Ubuntu has nice fancy GUI, right.

GUI does not matter. With ubuntu you will get up to date packages and don't screw yourself with stale "stable" code. It's a pain to build something successfully nowadays, especially crypto stuff on Debian.

tdcooper99

full member

Activity: 215

Merit: 100

Quote from: thefrog on August 17, 2014, 03:31:43 AM

What miner do you have there ?
Is it maybe a bitcoin miner -sha256 asic- and you try to mine scrypt with it ?

Nah... they're Zeusminers... I mine DGB using the normal P2 and standard pools.... just stopped for a bit while the algo gets sorted out so I'm selling Scrypt on Nicehash for the moment.

@ Digibyte, as I PM'd I had no issues compiling on Debian, but I'll build another VM with Ubuntu and do a comparison. What version are you using yourselves? I prefer headless SSH only... but can use a GUI too if need be.

thefrog

sr. member

Activity: 393

Merit: 250

Quote from: DigiByte on August 17, 2014, 03:34:39 AM

Quote from: thefrog on August 17, 2014, 03:31:43 AM

Quote from: tdcooper99 on August 17, 2014, 03:26:23 AM

Bloody solo mining Angry

I'm sure once I get it working I'll be happy... but at the moment I'm confused. I got the Linux wallet compiled on a new 64bit debian VM I built specifically for this. All synced up without issue... so one success! So when I point my miner at it I get the following, which on the surface looks ok... it's seeing it and appears to be talking, I've removed the IP address and username, although probably didn't need to:

Nothing scrolls... no info... just sits there.... but I think that's ok too... someone wrote on another forum that the problem with solo mining is you never know it's working until you actually solve a block and cgminer tells you Huh

Code:

cgminer version 4.3.5 - Started: [2014-08-17 07:05:44]
--------------------------------------------------------------------------------
(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 x.x.x.x diff 28.3M with LP as user xxxxxxxxxxxx
Block: 881ed2b0... Diff:431 Started: [07:05:43] 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:05:43] Solo mining to valid address: DLA9xQiGV99Vzf79aWcXVGhAkBv
1pGt9sG
[2014-08-17 07:05:43] Block change for http://10.20.30.175:14022 detection via
getblockcount polling
[2014-08-17 07:05:43] Pool 1 difficulty changed to 16.2
[2014-08-17 07:05:43] Pool 3 difficulty changed to 1024
[2014-08-17 07:05:43] Pool 2 difficulty changed to 41.1
[2014-08-17 07:05:43] Network diff set to 431
[2014-08-17 07:05:49] API running in IP access mode on port 4028 (12)
[2014-08-17 07:05:59] Found Zeus at /dev/ttyUSB0, mark as 0
[2014-08-17 07:05:59] ZUS0 opened on /dev/ttyUSB0
[2014-08-17 07:05:59] Hotplug: Zeus added ZUS 0

But the output of ./digibyted getmininginfo is:

Code:

{
   "blocks" : 141802,
   "currentblocksize" : 4758,
   "currentblocktx" : 6,
   "pow_algo_id" : 1,
   "pow_algo" : "scrypt",
   "difficulty" : 323.41127711,
   "difficulty_sha256d" : 0.00024414,
   "difficulty_scrypt" : 323.41127711,
   "difficulty_groestl" : 0.00024414,
   "difficulty_skein" : 0.00024414,
   "difficulty_qubit" : 0.00024414,
   "errors" : "",
   "genproclimit" : -1,
   "pooledtx" : 6,
   "testnet" : false,
   "generate" : false,
   "hashespersec" : 0
}

No hashespersec Is this normal?? Is there another parameter I can output to get an indication it's doing something? A log file perhaps?

What miner do you have there ?
Is it maybe a bitcoin miner -sha256 asic- and you try to mine scrypt with it ?

Debian=Disaster... Go Ubuntu

You know that Ubuntu is based on Debian, right ? Uses the same packages and so on...
But yes, Ubuntu has nice fancy GUI, right.

Topic: ★★DigiByte|极特币★★[DGB]✔ Core v6.16.5.1 - DigiShield, DigiSpeed, Segwit - page 1292. (Read 3058812 times)