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

[Beachguy]

nope i see 339998 nope 340017!
Good bye hashinator


whoa to 340051 just that fast

[pallas]

someone with groestl did the rush! :-)
I couldn't get any block while the diff was low.... :-(

[yofevo1]

Network gH/s
0.00000000

 

[BITDV]

chain moving, fork soon

3 blocks away


{
"blocks" : 340062,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 10.63095842,
"errors" : "Warning: This version is obsolete, upgrade required!",
"generate" : true,
"genproclimit" : -1,
"hashespersec" : 2217491,
"pooledtx" : 0,
"testnet" : false
}
??
"version" : "v2.0.0.0-unk-beta",
"protocolversion" : 90001,

[Beachguy]

Network gH/s
0.00000000

 

Explorers and such have trouble reading network hash when a coin is multi algo, the hash is comping from5 different algos.
At least the diff is down to more normal numbers

[someredguy]

Network gH/s
0.00000000

 

Explorers and such have trouble reading network hash when a coin is multi algo, the hash is comping from5 different algos.
At least the diff is down to more normal numbers

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

[HarveyOne]

At 339996 right now!
Get ready to pop a cork. 

stuck at 339997...

No longer, Block 340000 has passed. Let the games begin!

[Dogedarkdev]

the obsolete error message is fine, and isnt breaking anything. ill fix it today

[yofevo1]

the obsolete error message is fine, and isnt breaking anything. ill fix it today

nice work dev  good luck

to the moon 

[wttbs]

fully synced but a message about the wallet is obsolete but version should be OK as DEV said earlier



I am sure everything is fine   otherwise.. DEV what should I do?

[CryptocurrencyNetwork]

A sight for sore eyes to see those blocks moving - well done Dev & team & the whole community.

Now we are open for business!

[pallas]

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

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

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

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