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

[DigiByte]

Had to rebuild the block chain after installing the Windows 64 wallet, but other than that it seems to work fine.

Yes, we have had to do the same so we will note that above. Thanks for the feedback!

[DigiByte]

It looks like we are making the multi-algo switch just in time: http://www.coindesk.com/kncminer-final-phase-titan-asic-chip/

[racer2012]

HI JARED,
when can we expect digipay? caused we want digibyte its own value and people around the world can use any currency to purchase digibyte not just from bitcoin to digibyte like dollar. Today bitcoin value went down to $487 and came back up, but based on that if bitcoin price drop to $100 per coin or less than imagine millions of digibyte owner who bought at higher rate of bitcoin will have few hundreds $$ worth of digibyte in hand because of bitcon.
so lets have this digibyte have its own status besides bitcoin around the world!

GO DIGIBYTE THE BEST COIN AND BEST DEV AND BEST COMMUNITY EVER!!!!!!!!

[appbox]


> getmininginfo



Code:

{
"blocks" : 141778,
"currentblocksize" : 0,
"currentblocktx" : 0,
"pow_algo_id" : 0,
"pow_algo" : "sha256d",
"difficulty" : 0.00024414,
"difficulty_sha256d" : 0.00024414,
"difficulty_scrypt" : 421.89206860,
"difficulty_groestl" : 0.00024414,
"difficulty_skein" : 0.00024414,
"difficulty_qubit" : 0.00024414,
"errors" : "",
"genproclimit" : -1,
"pooledtx" : 0,
"testnet" : false,
"generate" : true,
"hashespersec" : 0
}

I want to get the networkhashrate... but always zero

[Toninho]

MultiAlgo v3.0.1 officially released...Here ?  after block 145,000 ? 

[Ryven Cedrylle]

I was at the Cryptolina convention this weekend doing promo for Prypto and bought a small 32-40 GHs 256-SHA miner to support DigiByte. Just need to get the power supply and figure out how the flip to use this thing and we'll be in business. Maybe I'll point it at Myriad until we hit the magic block number.

[birdonwheels5]

After you guys go multi-PoW, will the block reward stay at 8000 DGB per block solved? And you're going with a 2.5 min/algo approach, right?

I'm not sure if you guys will be able to handle that much new currency being minted every day at 8000 DGB @ roughly 30 sec/block. That's basically doubling the current coin production.

I'll still mine some though

Oh, and guys, tomorrow I'm gonna be working on getting P2Pools up for the new algos. I'll let you all know here & on reddit if I succeed. I'll try and pick ports that'll make sense. I'll post links to the github repos when I'm done. (I've set up p2pools for the Myriad algorithms, you can see my work at http://birdspool.no-ip.org:5567/static/MyrNodeHub.html. You can bet that you're gonna get a similar hub page!)


Do you guys have an Insight block explorer? Rich list? If not I may be able to work some of my MYR magic for you if you're interested

[Alvarero]

I've installed wallet 3.01 OSX, like 2 hours ago,  and still it's not synchronizing 

[tdcooper99]

Bloody solo mining  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

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?

[thefrog]

Bloody solo mining  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

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 ?

[DigiByte]

I've installed wallet 3.01 OSX, like 2 hours ago,  and still it's not synchronizing 

Delayed blockchain. All is well.

[DigiByte]

Bloody solo mining  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

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

[thefrog]

Bloody solo mining   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

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.

[tdcooper99]

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.

[sammy007]

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]

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

[Rocou]

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

[DigiByte]

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!

[thefrog]

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.

[,./,./]

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)