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

[bathrobehero]

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

Not being able to solomine any algos with a GPU is a serious issue imo.

well, a pool is opening right now for x17, so if pools are open with 4 of the algos already, you can certainly mine solo with a gpu.

im just saying solo mining probably wont get you blocks, since people prefer to gather on pools and we have ALOT of people mining now.

Pools always have some issues (I have issues just now on both idcray pools) and solomining should be a very basic feature. It also helps with decentralization.

I only know of one other coin which you can't solomine out of hundreds. Please add it, it's a must.

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

Not being able to solomine any algos with a GPU is a serious issue imo.

well, a pool is opening right now for x17, so if pools are open with 4 of the algos already, you can certainly mine solo with a gpu.

im just saying solo mining probably wont get you blocks, since people prefer to gather on pools and we have ALOT of people mining now.

Pools always have some issues (I have issues just now on both idcray pools) and solomining should be a very basic feature. It also helps with decentralization.

I only know of one other coin which you can't solomine out of hundreds. Please add it, it's a must.

what do you mean add it? if you want to solo mine scrypt, lyra2rev2, or groestl, you can. im not sure what you are talking about.

i am looking into the blake issue he posted to see if its just a matter of it being a cpu and work not meeting the target, because so far i have not heard anyone solo mining with a gpu having any issues yet.

solo mining & pool mining works for scrypt, lyra2rev2, and groestl that i can confirm. i am going to work on blake2 and x17 right now to make sure its functioning. if not, we'll fix it and push an update.

[Dogedarkdev]

this explorer shows blocks that are found and which algo found them.

http://yiimp.ccminer.org/explorer?id=561


we're looking into blake2s and x17 right now to make sure they are functioning properly.

[madmartyk]

Any news when Bittrex will update and reopen for trading?

[Dogedarkdev]

Any news when Bittrex will update and reopen for trading?

they're working on it. they are aware the fork went smooth and are updating.

[bathrobehero]

what do you mean add it? if you want to solo mine scrypt, lyra2rev2, or groestl, you can. im not sure what you are talking about.

i am looking into the blake issue he posted to see if its just a matter of it being a cpu and work not meeting the target, because so far i have not heard anyone solo mining with a gpu having any issues yet.

solo mining & pool mining works for scrypt, lyra2rev2, and groestl that i can confirm. i am going to work on blake2 and x17 right now to make sure its functioning. if not, we'll fix it and push an update.

My bad, I started with x17 and it didn't work and getmininginfo also didn't include the different algo difficulties and the current algo so I though solomining as a whole didn't work.
Digibyte for example shows that info:

"blocks" : 2175941,
"currentblocksize" : 1486,
"currentblocktx" : 1,
"pow_algo_id" : 2,
"pow_algo" : "groestl",
"difficulty" : 207.04372401,
"difficulty_sha256d" : 5381002.45466870,
"difficulty_scrypt" : 205.70335585,
"difficulty_groestl" : 207.04372401,
"difficulty_skein" : 715.15841829,
"difficulty_qubit" : 31.87288053,
...

But yeah solomining lyra2v2 works. Thank you.

[p75formula]

Using CPU-miner multi.

How do I set the number of cores?

[Beachguy]

Backedup up wallet.dat., deleted everything else in verge folder in roaming
wallet synched smoothly.
Pointed miners to suprnova, mined new coins, old coins in that account and the new ones
auto transferred to new wallet.

All's good and nice to be mining again.
Good Job Dev!  
Thanks

[daveolake]

Backedup up wallet.dat., deleted everything else in verge folder in roaming
wallet synched smoothly.
Pointed miners tosuprnova, mined new coins, old coins in that account and the new ones
auto transferred to new wallet.

All's good and nice to be mining again.
Good Job Dev! 
Thanks

yes great job, same here, got my first new mined coins to wallet from supernova.

[andronick83]

Hi all. Good job

Which super-nodes is best to use in VERGE.conf? What are you using? Or is it not necessary?
"addnode=..."

[chey]

I tested blake mining and this is what I'm getting.

04/11/16 19:18:35 ERROR: VERGEMiner : proof-of-work not meeting target

v2.0.0.0-41a7feb-funky-beta

edit: my bad dev already knows

i am going to work on blake2 and x17 right now to make sure its functioning. if not, we'll fix it and push an update.

[p75formula]

Using CPU-miner multi.

How do I set the number of cores?

Nevermind. Found it.

--threads=N

[Beachguy]

Before you mine a pool, don't assume they are on the right version.

The version Dev released that had the block time error was what many grabbed and installed and missed the follow up...

For instance AIKApools, they're stuck at 340005, that update juat ran for so far after the fork, so guys are there happily mining away thinking the chain is slow/stuck like the old days.

Easy to tell, check the block numbers in your dashbopard.
Currently over 340600.

This has been a public service announcement. 

[giantkin]

Before you mine a pool, don't assume they are on the right version.

The version Dev released that had the block time error was what many grabbed and installed and missed the follow up...

For instance AIKApools, they're stuck at 340005, that update juat ran for so far after the fork, so guys are there happily mining away thinking the chain is slow/stuck like the old days.

Easy to tell, check the block numbers in your dashbopard.
Currently over 340600.

This has been a public service announcement. 

You forgot one part:

BBEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE EEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE EEEEEEEEEEEEEEEEEEE

lol

[ShadowBits]

Before you mine a pool, don't assume they are on the right version.

The version Dev released that had the block time error was what many grabbed and installed and missed the follow up...

For instance AIKApools, they're stuck at 340005, that update juat ran for so far after the fork, so guys are there happily mining away thinking the chain is slow/stuck like the old days.

Easy to tell, check the block numbers in your dashbopard.
Currently over 340600.

This has been a public service announcement. 

You forgot one part:

BBEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE EEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE EEEEEEEEEEEEEEEEEEE

lol

Seems like this might of been the reason for Trex delays too.  Seems like they are syncing correct version now.  Trex traders standby =]

[CryptoRekt]

Before you mine a pool, don't assume they are on the right version.

The version Dev released that had the block time error was what many grabbed and installed and missed the follow up...

For instance AIKApools, they're stuck at 340005, that update juat ran for so far after the fork, so guys are there happily mining away thinking the chain is slow/stuck like the old days.

Easy to tell, check the block numbers in your dashbopard.
Currently over 340600.

This has been a public service announcement.  

You forgot one part:

BBEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE EEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE EEEEEEEEEEEEEEEEEEE

lol

Seems like this might of been the reason for Trex delays too.  Seems like they are syncing correct version now.  Trex traders standby =]

As per the bittrex slack -

bittrex-richie [11:50 AM]
"version" : "v1.2.0.0-beta",
   "protocolversion" : 60017,
   "walletversion" : 60000,

[11:50]
thats what i'm running

[11:50]
i'm currently resyncing from scratch

He was made aware that he was on the wrong version as seen here -- One minute later --



Romes BOT [11:51 AM]
v2.0.0.0-unk-beta

bittrex-richie [11:51 AM]
sigh.. fml


So i would suspect that Bittrex is on top of it and has a bit of work left to do on their end. Just be patient -- i mean unless you are in a hurry to feed my buy walls that will instantly be up then be my guest.


Cheers-

Rekt

[Beachguy]

Guess I need to learn more about blockchains and pools. Some pools may be reporting "current block" as THEIR current block that the pool is trying to solve. in that fiels of their dashboard that is the number that appears...

But like suprnova, seems to be reporting current block as the current one in the chian itself. unless they're snagging and solving them faster than everyone else.

After i left a pool that I thought was "stuck".....lo and behold the one miner left solved the block but I got shares from it. it took a tough amount of shares and percentage was like 1800%+ so it took a while to solve. And the block number in its field for "current block" is the one the pool just solved.

The block explorers show block releasing nice and smooth at the 30 sec target. Oh and coin transfers are behaving as they should as well becasue the chain is moving! Yay

I dunno...

[ShadowBits]

Guess I need to learn more about blockchains and pools. Some pools may be reporting "current block" as THEIR current block that the pool is trying to solve. in that fiels of their dashboard that is the number that appears...

But like suprnova, seems to be reporting current block as the current one in the chian itself. unless they're snagging and solving them faster than everyone else.

After i left a pool that I thought was "stuck".....lo and behold the one miner left solved the block but I got shares from it. it took a tough amount of shares and percentage was like 1800%+ so it took a while to solve. And the block number in its field for "current block" is the one the pool just solved.

The block explorers show block releasing nice and smooth at the 30 sec target.

I dunno...

Yeah, I've never seen the blockchain move this smooth and with haste until now.  Even if dev needs to tweak one or two of the algos a little in the near future, the main objective has been achieved it seems.  No stalls have happened yet.

[Beachguy]

Refreshing isn't it.

[Vegetablepin]

+1 for a good coin heading, in what seems to be, the right direction