[ANN][VRM] Verium PoWT | CPU mining | scrypt² | Scaling | New Roadmap Released

[wgd]

something is wrong with the pollinator, my hashrate fell in one day in half ..  

from time to time workers:

[2016-11-08 01:12:29] Total: 365.41 H/m
[2016-11-08 01:13:32] Total: 365.49 H/m
[2016-11-08 01:14:08] stratum_recv_line failed
[2016-11-08 01:14:08] Stratum connection interrupted

--

[1714321548]

1714321548

[1714321548]

1714321548

[1714321548]

1714321548

[testbug]

something is wrong with the pollinator, my hashrate fell in one day in half ..  

from time to time workers:

[2016-11-08 01:12:29] Total: 365.41 H/m
[2016-11-08 01:13:32] Total: 365.49 H/m
[2016-11-08 01:14:08] stratum_recv_line failed
[2016-11-08 01:14:08] Stratum connection interrupted

--

vrm.poolinat0r.com - pool maintenance

Hashrate increased a lot on the pool so it might be again CPU issue. Should be solved with implementation of new stratum host.

The pools wallet will be moved to a new host. I am moveing the wallet becaue i have figured out why backups are causing the cronjobs to stop. Problem should be solved on the new machine.
The new stratum host is almost ready. Before i am moveing the wallet and change the stratum i will inform all miners on the pools "message of the day section". I will also post here on the

[wgd]

we have again botnets, and starts dumping

[schlip]

One address has over 50% off the last 100 blocks

[wgd]

One address has over 50% off the last 100 blocks

Yet this address pool, probably pollinator. Mine this coin pay % miners

[submine88]

I have many coins on vrm.cpuminers.com are unconfirmed from 2016-11-05. What happen?
I want to get own coins.

[testbug]

I have many coins on vrm.cpuminers.com are unconfirmed from 2016-11-05. What happen?
I want to get own coins.

Best thing would be if you contact the pool op: https://bitcointalk.org/index.php?action=profile;u=899751

If you see many coins pending as "unconfirmed" it's most likely that the payoutsystem is not running due to an error, but i only can speek for poolinat0r


**vrm.poolinat0r.com - planed downtime: 09:00pm Berlin time,10th Nov**
The new stratum server is ready. The new address is: eu.poolinat0r.com. The old stratum proxy will go offline, so you have to change your proxy address from poolinat0r.com to eu.poolinat0r.com. CPU problems or time outs should be solved then.
The verium wallet will also be moved to a separated host. If you have poolinat0r.com as a node, the IP wont change and no changes are required. I wast running a small testnet with the new host and the disabled crons didn't appear on my network yet
You can use this website to convert your local time to Berlin time: http://www.timeanddate.com/worldclock/converted.html?p1=37&p2=44

Please note that not switching your miners address will cause a temporal loss of hashing power.
If you have any questions, feel free to pm me here or send me an email.

[BitRookie]

Whats happening with Verium? Why is it so low for a coin with only 700 000 supply

[wgd]

ask effectsToCause, I am sad. We have new miners, the supply is high and nobody is buying. Dev has not published anything for a month, it's a bad joke; /

[Anthbs]

I have many coins on vrm.cpuminers.com are unconfirmed from 2016-11-05. What happen?
I want to get own coins.

Sorry cron tasks had frozen for checking block status.
Have resolved now and all the blocks are showing that were mined by the pool and payouts that were requested in that period have been processed.
Feel free to pm me if there's any more issues.

[zcashcoins]

I have many coins on vrm.cpuminers.com are unconfirmed from 2016-11-05. What happen?
I want to get own coins.

Sorry cron tasks had frozen for checking block status.
Have resolved now and all the blocks are showing that were mined by the pool and payouts that were requested in that period have been processed.
Feel free to pm me if there's any more issues.

http://vrm.cpuminers.com/index.php seems ok!

[testbug]

I have many coins on vrm.cpuminers.com are unconfirmed from 2016-11-05. What happen?
I want to get own coins.

Best thing would be if you contact the pool op: https://bitcointalk.org/index.php?action=profile;u=899751

If you see many coins pending as "unconfirmed" it's most likely that the payoutsystem is not running due to an error, but i only can speek for poolinat0r


**vrm.poolinat0r.com - planed downtime: 09:00pm Berlin time,10th Nov**
The new stratum server is ready. The new address is: eu.poolinat0r.com. The old stratum proxy will go offline, so you have to change your proxy address from poolinat0r.com to eu.poolinat0r.com. CPU problems or time outs should be solved then.
The verium wallet will also be moved to a separated host. If you have poolinat0r.com as a node, the IP wont change and no changes are required. I wast running a small testnet with the new host and the disabled crons didn't appear on my network yet
You can use this website to convert your local time to Berlin time: http://www.timeanddate.com/worldclock/converted.html?p1=37&p2=44

Please note that not switching your miners address will cause a temporal loss of hashing power.
If you have any questions, feel free to pm me here or send me an email.

There have been some problems with importation of original pool wallet. The wallet will remain on the original host for this evening. I will try to fix it without real downtime by tomorrow.

eu.poolinat0r.com:(same ports)

Sorry for the downtime, but new stratum seems to be working. For now only 3-4 users switchted their miners stratum.

I will be monitoring this for a while now.

*edit*
first block with new stratum host found.

[wgd]

hmmm

Code:

2016-11-11 11:13:25] CPU #0: 372 H, 6.09 H/s
[2016-11-11 11:13:25] CPU #2: 384 H, 6.30 H/s
[2016-11-11 11:13:26] CPU #1: 348 H, 5.76 H/s
[2016-11-11 11:13:26] CPU #3: 360 H, 5.99 H/s
[2016-11-11 11:14:26] CPU #0: 372 H, 6.11 H/s
[2016-11-11 11:14:26] CPU #1: 348 H, 5.76 H/s
[2016-11-11 11:14:26] CPU #2: 384 H, 6.25 H/s
[2016-11-11 11:14:27] CPU #3: 360 H, 5.97 H/s
[2016-11-11 11:15:04] stratum_recv_line failed
[2016-11-11 11:15:04] Stratum connection interrupted
[2016-11-11 11:15:05] CPU #2: 240 H, 6.26 H/s
[2016-11-11 11:15:05] CPU #3: 228 H, 5.98 H/s
[2016-11-11 11:15:05] CPU #0: 240 H, 6.10 H/s
[2016-11-11 11:15:06] CPU #1: 228 H, 5.77 H/s
[2016-11-11 11:16:09] CPU #1: 348 H, 5.78 H/s
[2016-11-11 11:16:09] CPU #3: 360 H, 5.97 H/s
[2016-11-11 11:16:10] CPU #0: 372 H, 6.08 H/s
[2016-11-11 11:16:10] CPU #2: 384 H, 6.24 H/s
[2016-11-11 11:17:09] CPU #1: 348 H, 5.78 H/s
[2016-11-11 11:17:09] CPU #3: 360 H, 5.99 H/s
[2016-11-11 11:17:11] CPU #0: 372 H, 6.11 H/s
[2016-11-11 11:17:12] CPU #2: 384 H, 6.25 H/s
[2016-11-11 11:18:09] CPU #1: 348 H, 5.76 H/s
[2016-11-11 11:18:10] CPU #3: 360 H, 5.92 H/s
[2016-11-11 11:18:12] CPU #0: 372 H, 6.07 H/s
[2016-11-11 11:18:13] CPU #2: 384 H, 6.28 H/s
[2016-11-11 11:19:10] CPU #1: 348 H, 5.76 H/s
[2016-11-11 11:19:10] CPU #3: 360 H, 5.99 H/s
[2016-11-11 11:19:13] CPU #0: 372 H, 6.10 H/s
[2016-11-11 11:19:14] CPU #2: 384 H, 6.27 H/s
[2016-11-11 11:20:10] CPU #1: 348 H, 5.76 H/s
[2016-11-11 11:20:10] CPU #3: 360 H, 5.97 H/s
[2016-11-11 11:20:15] CPU #0: 372 H, 6.07 H/s
[2016-11-11 11:20:15] CPU #2: 384 H, 6.27 H/s
[2016-11-11 11:21:11] CPU #3: 360 H, 5.98 H/s
[2016-11-11 11:21:11] CPU #1: 348 H, 5.75 H/s
[2016-11-11 11:21:16] CPU #0: 372 H, 6.09 H/s
[2016-11-11 11:21:17] CPU #2: 384 H, 6.24 H/s
[2016-11-11 11:22:11] CPU #3: 360 H, 5.95 H/s
[2016-11-11 11:22:11] CPU #1: 348 H, 5.73 H/s
[2016-11-11 11:22:16] CPU #0: 372 H, 6.11 H/s
[2016-11-11 11:22:17] CPU #2: 384 H, 6.33 H/s
[2016-11-11 11:23:11] CPU #3: 360 H, 5.99 H/s
[2016-11-11 11:23:12] CPU #1: 348 H, 5.76 H/s
[2016-11-11 11:23:18] CPU #0: 372 H, 6.07 H/s
[2016-11-11 11:23:19] CPU #2: 384 H, 6.23 H/s
[2016-11-11 11:24:11] CPU #3: 360 H, 6.05 H/s
[2016-11-11 11:24:11] CPU #1: 348 H, 5.86 H/s
[2016-11-11 11:24:18] CPU #0: 372 H, 6.15 H/s
[2016-11-11 11:24:33] CPU #2: 384 H, 5.21 H/s
[2016-11-11 11:25:13] CPU #3: 372 H, 5.98 H/s
[2016-11-11 11:25:14] CPU #1: 360 H, 5.77 H/s
[2016-11-11 11:25:16] stratum_recv_line failed
[2016-11-11 11:25:16] Stratum connection interrupted
[2016-11-11 11:25:17] CPU #2: 276 H, 6.25 H/s
[2016-11-11 11:25:17] CPU #3: 24 H, 5.99 H/s
[2016-11-11 11:25:17] CPU #0: 360 H, 6.11 H/s
[2016-11-11 11:25:18] CPU #1: 24 H, 6.14 H/s
[2016-11-11 11:26:20] CPU #3: 360 H, 6.01 H/s
[2016-11-11 11:26:21] CPU #0: 372 H, 6.10 H/s
[2016-11-11 11:26:23] CPU #1: 372 H, 5.83 H/s
[2016-11-11 11:26:24] CPU #2: 384 H, 5.99 H/s
[2016-11-11 11:27:23] CPU #2: 360 H, 6.07 H/s
[2016-11-11 11:27:25] CPU #3: 372 H, 5.72 H/s
[2016-11-11 11:27:30] CPU #1: 360 H, 5.43 H/s
[2016-11-11 11:27:44] CPU #0: 372 H, 4.48 H/s
[2016-11-11 11:28:25] CPU #3: 348 H, 5.77 H/s
[2016-11-11 11:28:26] CPU #2: 372 H, 5.96 H/s
[2016-11-11 11:28:31] CPU #1: 336 H, 5.48 H/s
[2016-11-11 11:28:35] CPU #0: 276 H, 5.48 H/s
[2016-11-11 11:29:26] CPU #2: 360 H, 5.98 H/s
[2016-11-11 11:29:26] CPU #3: 348 H, 5.72 H/s
[2016-11-11 11:29:33] CPU #1: 336 H, 5.43 H/s
[2016-11-11 11:29:34] CPU #0: 336 H, 5.68 H/s
[2016-11-11 11:30:25] CPU #2: 360 H, 6.08 H/s
[2016-11-11 11:30:27] CPU #3: 348 H, 5.72 H/s
[2016-11-11 11:30:35] CPU #1: 336 H, 5.37 H/s
[2016-11-11 11:30:41] CPU #0: 348 H, 5.21 H/s
[2016-11-11 11:31:28] CPU #3: 348 H, 5.67 H/s
[2016-11-11 11:31:29] CPU #2: 372 H, 5.86 H/s
[2016-11-11 11:31:36] CPU #1: 324 H, 5.33 H/s
[2016-11-11 11:31:56] CPU #0: 324 H, 4.29 H/s
[2016-11-11 11:32:30] CPU #2: 360 H, 5.90 H/s
[2016-11-11 11:32:31] CPU #3: 348 H, 5.54 H/s
[2016-11-11 11:32:40] CPU #1: 324 H, 5.11 H/s
[2016-11-11 11:32:54] CPU #0: 264 H, 4.59 H/s
[2016-11-11 11:33:30] CPU #2: 360 H, 5.95 H/s
[2016-11-11 11:33:31] CPU #3: 336 H, 5.66 H/s
[2016-11-11 11:33:39] CPU #1: 312 H, 5.25 H/s
[2016-11-11 11:33:59] CPU #0: 276 H, 4.20 H/s
[2016-11-11 11:34:30] CPU #2: 360 H, 5.98 H/s
[2016-11-11 11:34:32] CPU #3: 348 H, 5.68 H/s
[2016-11-11 11:34:44] CPU #1: 324 H, 5.03 H/s
[2016-11-11 11:34:51] CPU #0: 264 H, 5.05 H/s
[2016-11-11 11:35:30] CPU #2: 360 H, 6.09 H/s
[2016-11-11 11:35:32] CPU #3: 348 H, 5.78 H/s
[2016-11-11 11:35:38] stratum_recv_line failed
[2016-11-11 11:35:38] Stratum connection interrupted
[2016-11-11 11:35:39] CPU #1: 276 H, 4.99 H/s
[2016-11-11 11:35:39] CPU #2: 60 H, 6.14 H/s
[2016-11-11 11:35:40] CPU #0: 204 H, 4.24 H/s
[2016-11-11 11:35:40] CPU #3: 48 H, 6.04 H/s
[2016-11-11 11:35:46] eu.poolinat0r.com:4443 scrypt block 22418

[phantagram]

ask effectsToCause, I am sad. We have new miners, the supply is high and nobody is buying. Dev has not published anything for a month, it's a bad joke; /

the VRM ICO was just hype to get people to buy VRC. now the devs control all the VRC and the network is centralized in their hands.

VRM is just scrypt with changed parameters. 2014 coins tried this before and called it silly names like scrypt-n, scrypt-og, scrypt-jane. it's the same shit, just uses more memory. and VRM devs just called their bull shit scrypt². good joke.

over time this coin will die just like all the other scrypt coins which use so much memory the wallets eventually stop working.

do you enjoy this scam?

[wgd]

botnets welcome  

Rank               User              Name KH/s          VRM/Day
1                   wyh136          1,186                395,554.441

[Nik4691]

botnets welcome  

Rank               User              Name KH/s          VRM/Day
1                   wyh136          1,186                395,554.441

You know that these numbers are way out, right?
You know that there are only about 10,000 new coins everyday right?
If no, you know your IQ right? No you don't.

[wgd]

You know that these numbers are way out, right?
You know that there are only about 10,000 new coins everyday right?
If no, you know your IQ right? No you don't.

current parameter network:

block time: 4,7 min - reward: 6,5 vrm

~84vrm per hour, ~2028vrm per day

Nik4691 so  go son teaches math with mom and dad safest on their fingers

[Nik4691]

You know that these numbers are way out, right?
You know that there are only about 10,000 new coins everyday right?
If no, you know your IQ right? No you don't.

current parameter network:

block time: 4,7 min - reward: 6,5 vrm

~84vrm per hour, ~2028vrm per day

Nik4691 so  go son teaches math with mom and dad safest on their fingers

So it is not 395,554.441 VRM/Day as you said before? 
Why even post these numbers?

[wgd]

You know that these numbers are way out, right?
You know that there are only about 10,000 new coins everyday right?
If no, you know your IQ right? No you don't.

current parameter network:

block time: 4,7 min - reward: 6,5 vrm

~84vrm per hour, ~2028vrm per day

Nik4691 so  go son teaches math with mom and dad safest on their fingers

So it is not 395,554.441 VRM/Day as you said before?  
Why even post these numbers?

this is paste from poolinator, no comment http://vrm.poolinat0r.com/index.php?page=statistics&action=pool

[testbug]

You know that these numbers are way out, right?
You know that there are only about 10,000 new coins everyday right?
If no, you know your IQ right? No you don't.

current parameter network:

block time: 4,7 min - reward: 6,5 vrm

~84vrm per hour, ~2028vrm per day

Nik4691 so  go son teaches math with mom and dad safest on their fingers

So it is not 395,554.441 VRM/Day as you said before?  
Why even post these numbers?

this is paste from poolinator, no comment http://vrm.poolinat0r.com/index.php?page=statistics&action=pool

Oh, i thought i made it clear about poolinat0r.com stats.
All stats have a factor "1000". I decided to implement this x1000 because otherwise people wouldnt see any submitted shares on the backend because the difficutly  is so low. I was running it without the factor in the beginning and only after several hours i saw 1 submitted share. So if anyone is generateing 300,000 VRM per day, then this are actually 300 VRM per day. Simply remove "000" on your personal stats and you see your real VRM per day ratio.