[UNOFFICIAL] [VNL] Vanillacoin 0.4.1 | Instant ▱ Incentivized ▱ Innovative

[Jookly]

was fürn kack name
wann kommt der pump?
'sags mir einfach büdde
scheiß name---

today i learned that the words name and pump are the same in German and English.  I hope they aren't paying you too much! 

[PaidFudder]

 
ich will doch nur reich sein, reich wie die nazis! 

[Jookly]

ich will doch nur reich sein, reich wie die nazis! 

 

so edgy

[JuanHungLo]

I heard that Warren Buffet likes Vanilla:

[z0n0]

Da fuck am I doin wrong?


@echo off
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
sgminer.exe --algorithm whirlpoolx -o stratum+tcp://mine1.vnl.nonce-pool.com:4333 -u zono.zono -p abc -I 19 -g 2 -w 64 --gpu-platform 1 --no-submit-stale --failover-only





wolf0 is there some of your .bins out already?

~500+ MH/s > ~115 MH/s such a damn huge difference

HELP PLS!

[z0n0]

Da fuck am I doin wrong?


@echo off
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
sgminer.exe --algorithm whirlpoolx -o stratum+tcp://mine1.vnl.nonce-pool.com:4333 -u zono.zono -p abc -I 19 -g 2 -w 64 --gpu-platform 1 --no-submit-stale --failover-only





wolf0 is there some of your .bins out already?

~500+ MH/s > ~115 MH/s such a damn huge difference

HELP PLS!

Well, let's see. Not reading the README, using --no-submit-stale, not telling us your card type... am I close?

Close enough
I'm using 280X, "not reading README": guilty...

So I should remove "--no-submit-stale" ?

[z0n0]

Da fuck am I doin wrong?


@echo off
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
sgminer.exe --algorithm whirlpoolx -o stratum+tcp://mine1.vnl.nonce-pool.com:4333 -u zono.zono -p abc -I 19 -g 2 -w 64 --gpu-platform 1 --no-submit-stale --failover-only





wolf0 is there some of your .bins out already?

~500+ MH/s > ~115 MH/s such a damn huge difference

HELP PLS!

Well, let's see. Not reading the README, using --no-submit-stale, not telling us your card type... am I close?

Close enough
I'm using 280X, "not reading README": guilty...

So I should remove "--no-submit-stale" ?

Of course. If I've said it once, I've said it a thousand times: SGMiner doesn't know if a share is stale. It GUESSES. You have nothing to lose by submitting it, and by not doing so, you won't get paid for it even if it is valid.

I wrote the README for a reason.

I'm really bad with understanding all these words, I'm mining for fun/hobby, if I'm honest I don't even know what "submitting stale" means

Just found out this:
Okay, it's not perfect, but it'll never be. Sources that I've written or modified have been heavily commented to help out devs who are learning. The OpenCL was entirely written by me, and SGMiner itself was modified by me not just to run the modified kernel, but to clean it, remove algorithms besides WhirlpoolX for simplicity, and add comments. The horrid lib SPH is no longer used at all, instead, a SHA-256 implementation that was actually already there and never even compiled is used for several parts of SGMiner that used to call into lib SPH, and the CPU Whirlpool-512 implementation is a rather clean one I found here. That is also where I found seemingly the only copy of Whirlpool-512 done without tables, on which I based my bitsliced implementation. Another modification I made was to check the OpenCL version at runtime and use clCreateCommandQueueWithProperties() if the version is 2.0 or greater; it replaces clCreateCommandQueue(), and the latter is now deprecated and should not be used, but even the current official SGMiner isn't updated. Anyways, go look at the source for yourself. It will be here momentarily.

Screenshot of final hashrates, although you may find better configs (NSFW): https://ottrbutt.com/miner/whirlpoolxwolfpub-03222015.png

Win64 binaries have been made for release, of course. As you can verify on Bitcoin-OTC's database, my key ID is 0x88CBE71ADD5FB10F - check your GPG sigs. Statically compiled, linked against the beta version 3.0 of the AMD APP SDK, stripped, and signed. The cURL version used is a bit old, but it doesn't matter. ADL headers were whatever version I happened installed on my Linux machine - the headers themselves are portable, and the binary was cross-compiled. Archive contains the binary, the CL file, and a README.

https://ottrbutt.com/sgminer/whirlpoolx/win64/wolf-sgminer-whirlpoolx-03222015-win64.zip
https://ottrbutt.com/sgminer/whirlpoolx/win64/wolf-sgminer-whirlpoolx-03222015-win64.zip.sig

...which gives much better hashrate. I was using some "old" version

EDIT: Is this OK?
"sgminer.exe --kernel whirlpoolx -o stratum+tcp://mine1.vnl.nonce-pool.com:4333 -u zono.zono -p abc -I 19 -g 2 -w 64 --gpu-platform 1 --failover-only"
Should I add something more?

[tccd]

I think I got one low-hanging fruit but it was too obvious even for a person not involved in any kind of software development. I was doing 300MH/s with 290X@1000/1250 (15.3 beta) and now my hashrate is 316MH/s:

http://store.picbg.net/thumb/B9/34/368dc2228c7eb934.png

[z0n0]

Da fuck am I doin wrong?


@echo off
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
sgminer.exe --algorithm whirlpoolx -o stratum+tcp://mine1.vnl.nonce-pool.com:4333 -u zono.zono -p abc -I 19 -g 2 -w 64 --gpu-platform 1 --no-submit-stale --failover-only





wolf0 is there some of your .bins out already?

~500+ MH/s > ~115 MH/s such a damn huge difference

HELP PLS!

Well, let's see. Not reading the README, using --no-submit-stale, not telling us your card type... am I close?

Close enough
I'm using 280X, "not reading README": guilty...

So I should remove "--no-submit-stale" ?

Of course. If I've said it once, I've said it a thousand times: SGMiner doesn't know if a share is stale. It GUESSES. You have nothing to lose by submitting it, and by not doing so, you won't get paid for it even if it is valid.

I wrote the README for a reason.

I'm really bad with understanding all these words, I'm mining for fun/hobby, if I'm honest I don't even know what "submitting stale" means

Just found out this:
Okay, it's not perfect, but it'll never be. Sources that I've written or modified have been heavily commented to help out devs who are learning. The OpenCL was entirely written by me, and SGMiner itself was modified by me not just to run the modified kernel, but to clean it, remove algorithms besides WhirlpoolX for simplicity, and add comments. The horrid lib SPH is no longer used at all, instead, a SHA-256 implementation that was actually already there and never even compiled is used for several parts of SGMiner that used to call into lib SPH, and the CPU Whirlpool-512 implementation is a rather clean one I found here. That is also where I found seemingly the only copy of Whirlpool-512 done without tables, on which I based my bitsliced implementation. Another modification I made was to check the OpenCL version at runtime and use clCreateCommandQueueWithProperties() if the version is 2.0 or greater; it replaces clCreateCommandQueue(), and the latter is now deprecated and should not be used, but even the current official SGMiner isn't updated. Anyways, go look at the source for yourself. It will be here momentarily.

Screenshot of final hashrates, although you may find better configs (NSFW): https://ottrbutt.com/miner/whirlpoolxwolfpub-03222015.png

Win64 binaries have been made for release, of course. As you can verify on Bitcoin-OTC's database, my key ID is 0x88CBE71ADD5FB10F - check your GPG sigs. Statically compiled, linked against the beta version 3.0 of the AMD APP SDK, stripped, and signed. The cURL version used is a bit old, but it doesn't matter. ADL headers were whatever version I happened installed on my Linux machine - the headers themselves are portable, and the binary was cross-compiled. Archive contains the binary, the CL file, and a README.

https://ottrbutt.com/sgminer/whirlpoolx/win64/wolf-sgminer-whirlpoolx-03222015-win64.zip
https://ottrbutt.com/sgminer/whirlpoolx/win64/wolf-sgminer-whirlpoolx-03222015-win64.zip.sig

...which gives much better hashrate. I was using some "old" version

EDIT: Is this OK?
"sgminer.exe --kernel whirlpoolx -o stratum+tcp://mine1.vnl.nonce-pool.com:4333 -u zono.zono -p abc -I 19 -g 2 -w 64 --gpu-platform 1 --failover-only"
Should I add something more?

And you still haven't read it, because if you did, you would have known that -I 19 is way too low. Try --xintensity 2048.

Now ~260 MH/s...Still way off from yours ~500 mh/s  
Should I change -w 64 to -w 256?


With HD7850 I get 83 MH/s.

[traumschiff]

Now ~260 MH/s...Still way off from yours ~500 mh/s 

You won't get 500 mh/s with the public miner if you don't optimize it by yourself. That's his own private miner and you would know this if you would read back a few pages.

[z0n0]

Now ~260 MH/s...Still way off from yours ~500 mh/s 

You won't get 500 mh/s with the public miner if you don't optimize it by yourself. That's his own private miner and you would know this if you would read back a few pages.

Oh I see Thanks for info

[traumschiff]

Now ~260 MH/s...Still way off from yours ~500 mh/s  

You won't get 500 mh/s with the public miner if you don't optimize it by yourself. That's his own private miner and you would know this if you would read back a few pages.

Oh I see Thanks for info

Np, you can still play with -w and --xintensity to gain the maximum out of the current public miner. Currently I'm hashing with 123 MH/s with my 270x.

[elpis]

Wolf0 Does not work Auto-Switching Multi-Algorithm of sgminer (https://ottrbutt.com/sgminer/whirlpoolx/win64/wolf-sgminer-whirlpoolx-03222015-win64.zip). WhirlpoolX-perfectly. Others do not work?

[groggin]

Does not work Auto-Switching Multi-Algorithm of sgminer (https://ottrbutt.com/sgminer/whirlpoolx/win64/wolf-sgminer-whirlpoolx-03222015-win64.zip). WhirlpoolX-perfectly. Others do not work?

nope - it's just for VNL 

[elpis]

Does not work Auto-Switching Multi-Algorithm of sgminer (https://ottrbutt.com/sgminer/whirlpoolx/win64/wolf-sgminer-whirlpoolx-03222015-win64.zip). WhirlpoolX-perfectly. Others do not work?

nope - it's just for VNL 

Thank.

[jimlite]

Also remove gpu platform.

[yudhistira]

2 R280x

setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1

sgminer.exe -k whirlpoolx -o stratum+tcp://vnl.suprnova.cc:1111 -u vanilla.1 -p x -w 64 -g 2 -X 4096 --no-submit-stale --gpu-powertune 20 --gpu-engine 1150 --gpu-memclock 1500 --lookup-gap 2 --expiry 1 --scan-time 1 --queue 0

first run stabil at 264 Mhs
hw: 0 R: 0 temp max: 80 c 3000 rpm

after a day

speed unstable 261-263
hw:0 R: to much max: 90 c 2500 rpm

something wrong with my gpu or this a bad network

[traumschiff]

News 03/27

0.2.5 wallet released. Changelog:

• GUI now shows all receiving addresses and account names.
• Support for RPC "listreceivedbyaddress" and "listreceivedbyaccount"
• Lock file support to prevent multiple instances on *nix.
• General Bug Fixes

Original post by john-connor: http://vanillacoin.net/forums/viewtopic.php?id=608

[z0n0]

2 R280x

setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1

sgminer.exe -k whirlpoolx -o stratum+tcp://vnl.suprnova.cc:1111 -u vanilla.1 -p x -w 64 -g 2 -X 4096 --no-submit-stale --gpu-powertune 20 --gpu-engine 1150 --gpu-memclock 1500 --lookup-gap 2 --expiry 1 --scan-time 1 --queue 0

first run stabil at 264 Mhs
hw: 0 R: 0 temp max: 80 c 3000 rpm

after a day

speed unstable 261-263
hw:0 R: to much max: 90 c 2500 rpm

something wrong with my gpu or this a bad network

As I undersood wolf0, you should remove "--no-submit-stale"

[z0n0]

Is VNL still one of the most profitable coins to mine?
Or in other words, what is more profitable: x11 with 6,6 mh/s or VNL with 260MH/s (R9 280x) ?

http://www.coinwarz.com/cryptocurrency nor http://whatmine.com/ doesn't show profitability for WhirlpoolX. Is there any other site which does show?