[$XVG] VERGE [POW][MultiAlgo][TOR/i2P][no premine/ico!]

[Beachguy]

https://www.blockexperts.com/xvg seems to handle it...
https://prohashing.com/explorer/ is confused...

Look at the network hash rate....thats what he was talking about.

[1714263192]

1714263192

[1714263192]

1714263192

[1714263192]

1714263192

[1714263192]

1714263192

[Dogedarkdev]

blake2s mining is broken.
can't mine with an external miner nor wallet itself:

ERROR: VERGEMiner : proof-of-work not meeting target

looking into this.. so far i can confirm myr-groestl is working.

[pallas]

blake2s mining is broken.
can't mine with an external miner nor wallet itself:

ERROR: VERGEMiner : proof-of-work not meeting target

looking into this.. so far i can confirm myr-groestl is working.

thanks.
question: I see that the algo diff changes even though blocks are mined on a different algo.
that looks to be a problem for "slower" algos like x17.
how do the algo diffs relate to each other?

[myriadcoin]

blake2s mining is broken.
can't mine with an external miner nor wallet itself:

ERROR: VERGEMiner : proof-of-work not meeting target

looking into this.. so far i can confirm myr-groestl is working.

thanks.
question: I see that the algo diff changes even though blocks are mined on a different algo.
that looks to be a problem for "slower" algos like x17.
how do the algo diffs relate to each other?

They don't. They difficulties are independent but they can retarget on a block found with any algo. If one algo gets stuck on high difficulty, the other algos can help it retarget instead of waiting for the next same algo block.

[pallas]

blake2s mining is broken.
can't mine with an external miner nor wallet itself:

ERROR: VERGEMiner : proof-of-work not meeting target

looking into this.. so far i can confirm myr-groestl is working.

thanks.
question: I see that the algo diff changes even though blocks are mined on a different algo.
that looks to be a problem for "slower" algos like x17.
how do the algo diffs relate to each other?

They don't. They difficulties are independent but they can retarget on a block found with any algo. If one algo gets stuck on high difficulty, the other algos can help it retarget instead of waiting for the next same algo block.

It must be wrongly reported, then:

    "pow_algo" : "x17",
    "difficulty" : 255.71905437,

Because no blocks have been found on x17 so far (it's way too high).
Same with blake2s.

EDIT: I think there is indeed a problem with diff. I'm mining on an algo (which didn't generate any block on the chain yet) for half an hour... doesn't make sense. Only groestl and lyra2 working so far.

[cryptofarmer]

www.mining-dutch.nl

We're online on scrypt algo.
Blocks rolling by smoothly

[Dogedarkdev]

www.mining-dutch.nl

We're online on scrypt algo.
Blocks rolling by smoothly

i can confirm scrypt is working. so scrypt, lyra2rev2, and myr-groestl are working that we know of so far.

[cryptofarmer]

somethings wrong
I think we've forked the chain. 

[Dogedarkdev]

somethings wrong
I think we've forked the chain.  

what makes you say that?

edit: what is ur current version?

since you run a pool, im guessing you have a linux daemon, and your version should be:
"version" : "v2.0.0.0-806a3d8-funky-beta", 

if not, i dont know why you didnt update

[madmartyk]

somethings wrong
I think we've forked the chain. 

Should we stop mining?

[cryptofarmer]

somethings wrong
I think we've forked the chain. 

what makes you say that?

edit: what is ur current version?

since you run a pool, im guessing you have a linux daemon, and your version should be:
"version" : "v2.0.0.0-806a3d8-funky-beta", 

if not, i dont know why you didnt update

VERGE version v2.0.0.0-1ab3489-funky-beta (2016-04-09 01:28:31 -0400)

[Dogedarkdev]

somethings wrong
I think we've forked the chain. 

Should we stop mining?

hes talking about his pool. i dont think he was on the correct update.

all is well on the rest of the pools. blocks being found on suprnova, and idcray so far

myrgroestl, lyra2rev2, and scrypt have blocks found.

all is looking good.

[pallas]

somethings wrong
I think we've forked the chain. 

Should we stop mining?

hes talking about his pool. i dont think he was on the correct update.

all is well on the rest of the pools. blocks being found on suprnova, and idcray so far

myrgroestl, lyra2rev2, and scrypt have blocks found.

all is looking good.

Lyra2RE or Lyra2REV2??

From readme:
Algorithms: scrypt, x17, Lyra2re, myr-groestl, & blake2s

thus it should be V1...

[Dogedarkdev]

somethings wrong
I think we've forked the chain. 

what makes you say that?

edit: what is ur current version?

since you run a pool, im guessing you have a linux daemon, and your version should be:
"version" : "v2.0.0.0-806a3d8-funky-beta", 

if not, i dont know why you didnt update

VERGE version v2.0.0.0-1ab3489-funky-beta (2016-04-09 01:28:31 -0400)

nope. pull the latest commits, or download the newest binary

[Dogedarkdev]

somethings wrong
I think we've forked the chain. 

Should we stop mining?

hes talking about his pool. i dont think he was on the correct update.

all is well on the rest of the pools. blocks being found on suprnova, and idcray so far

myrgroestl, lyra2rev2, and scrypt have blocks found.

all is looking good.

Lyra2RE or Lyra2REV2??

From readme:
Algorithms: scrypt, x17, Lyra2re, myr-groestl, & blake2s

thus it should be V1...

its 2. readme updated. http://xvg-lyra.idcray.com/index.php?page=statistics&action=pool

[cryptofarmer]

somethings wrong
I think we've forked the chain. 

what makes you say that?

edit: what is ur current version?

since you run a pool, im guessing you have a linux daemon, and your version should be:
"version" : "v2.0.0.0-806a3d8-funky-beta", 

if not, i dont know why you didnt update

VERGE version v2.0.0.0-1ab3489-funky-beta (2016-04-09 01:28:31 -0400)

nope. pull the latest commits, or download the newest binary

I've updated and can confirm we're on the same block as other pools and exchanges.
Problem solved.

[Dogedarkdev]

somethings wrong
I think we've forked the chain. 

what makes you say that?

edit: what is ur current version?

since you run a pool, im guessing you have a linux daemon, and your version should be:
"version" : "v2.0.0.0-806a3d8-funky-beta", 

if not, i dont know why you didnt update

VERGE version v2.0.0.0-1ab3489-funky-beta (2016-04-09 01:28:31 -0400)

nope. pull the latest commits, or download the newest binary

I've updated and can confirm we're on the same block as other pools and exchanges.
Problem solved.

excellent!

[Dogedarkdev]

i'd like to see an x17 and blake pool open up. if i dont see one in a few hours, ill create one that has both.

[pallas]

i'd like to see an x17 and blake pool open up. if i dont see one in a few hours, ill create one that has both.

ok but how come the wallet "internal" miner can't mine any of the two algos?

[Dogedarkdev]

i'd like to see an x17 and blake pool open up. if i dont see one in a few hours, ill create one that has both.

ok but how come the wallet "internal" miner can't mine any of the two algos?

well it uses the cpu for one, so im sure theres no way anyone is going to yolo mine blocks right now

i havent even tried to solo mine with a cpu in wallet. but i will look at it. it might make sense to just remove the miner from the wallet tbh..

but if an x17 pool or blake pool opened and we could point gpus.. that would be a diff story..