Where is Windows wallet?
Not ready yet. Soon will be.I'm very close to making it work...
Topic: Vertcoin - First Scrypt N | First Stealth Address - Privacy without mixer - page 41. (Read 1232701 times)
December 07, 2014, 06:58:42 PM
I'm very close to making it work...
December 07, 2014, 06:53:46 PM
Where is Windows wallet?
Not ready yet. Soon will be. 
December 07, 2014, 05:33:19 PM
Where is Windows wallet?
December 07, 2014, 04:06:44 PM
I just flashed up the new v.0.9.0.1 64 bit linux wallet. Everything appears as it should and is syncing up nicely.
You guys compiled a linux ccminer for me! You rock!
You guys compiled a linux ccminer for me! You rock!
If you use KopiemTu in your rigs, this compiled ccminer supports also KopiemTu web statistics ("syslog" option in configuration file)
December 07, 2014, 03:34:23 PM
Not sure if this is tripping any of you guys up but xintensity 64 for a 290x is not the same as xintensity 64 for a 280x or even a 290. xintensity is a multiple of shaders your card has.
For example a 290x at xintensity 64 is 2816*64 = 180224 raw intensity which is close to an intensity of 17.45 (2^17.45 = 179049)
a 290 at xintensity 64 is 2560*64 = 163840 raw intensity which is close to an intensity of 17.32 (2^17.32 = 163621)
Not much of a difference between a 290x and a 290 but with a 7950 having 1792 shaders would be something like an intensity of 16.8
Again not a huge deal but something to consider.
For example a 290x at xintensity 64 is 2816*64 = 180224 raw intensity which is close to an intensity of 17.45 (2^17.45 = 179049)
a 290 at xintensity 64 is 2560*64 = 163840 raw intensity which is close to an intensity of 17.32 (2^17.32 = 163621)
Not much of a difference between a 290x and a 290 but with a 7950 having 1792 shaders would be something like an intensity of 16.8
Again not a huge deal but something to consider.
No shit. That's the entire point of xintensity.
Awww shame...why sooo mean Wolf?
Not my intention to be mean; I can be rather blunt when I've been awake for more than 60 hours or so.
Understandable, it happens. All is forgiven. See jch9678, Wolf was just tired from all the tinkering and reporting back to us, that he has been doing. Thaaaank you Woooolf.
December 07, 2014, 03:21:44 PM
Not sure if this is tripping any of you guys up but xintensity 64 for a 290x is not the same as xintensity 64 for a 280x or even a 290. xintensity is a multiple of shaders your card has.
For example a 290x at xintensity 64 is 2816*64 = 180224 raw intensity which is close to an intensity of 17.45 (2^17.45 = 179049)
a 290 at xintensity 64 is 2560*64 = 163840 raw intensity which is close to an intensity of 17.32 (2^17.32 = 163621)
Not much of a difference between a 290x and a 290 but with a 7950 having 1792 shaders would be something like an intensity of 16.8
Again not a huge deal but something to consider.
For example a 290x at xintensity 64 is 2816*64 = 180224 raw intensity which is close to an intensity of 17.45 (2^17.45 = 179049)
a 290 at xintensity 64 is 2560*64 = 163840 raw intensity which is close to an intensity of 17.32 (2^17.32 = 163621)
Not much of a difference between a 290x and a 290 but with a 7950 having 1792 shaders would be something like an intensity of 16.8
Again not a huge deal but something to consider.
No shit. That's the entire point of xintensity.
Awww shame...why sooo mean Wolf?
December 07, 2014, 03:06:46 PM
Not sure if this is tripping any of you guys up but xintensity 64 for a 290x is not the same as xintensity 64 for a 280x or even a 290. xintensity is a multiple of shaders your card has.
For example a 290x at xintensity 64 is 2816*64 = 180224 raw intensity which is close to an intensity of 17.45 (2^17.45 = 179049)
a 290 at xintensity 64 is 2560*64 = 163840 raw intensity which is close to an intensity of 17.32 (2^17.32 = 163621)
Not much of a difference between a 290x and a 290 but with a 7950 having 1792 shaders would be something like an intensity of 16.8
Again not a huge deal but something to consider.
For example a 290x at xintensity 64 is 2816*64 = 180224 raw intensity which is close to an intensity of 17.45 (2^17.45 = 179049)
a 290 at xintensity 64 is 2560*64 = 163840 raw intensity which is close to an intensity of 17.32 (2^17.32 = 163621)
Not much of a difference between a 290x and a 290 but with a 7950 having 1792 shaders would be something like an intensity of 16.8
Again not a huge deal but something to consider.
No shit. That's the entire point of xintensity.
Just trying to help. I guarantee that someone out there thinks they are pushing their 7950 with an xintensity of 64 as hard as you are pushing your 290x. Maybe I have a misunderstanding, is the thinking supposed to be that a 7950 can't handle the same intensity as a 290? I try to keep my 290s and 290Xs around the same raw intensity. I always took it that intensity was just how hard you want to push your card, so if you wanted to push your 290x to intensity of 17, for an older card you would have to add more to xintensity to reach intensity of 17. Oh well I've never mined with different types of cards so I never had to consider it.
December 07, 2014, 02:40:48 PM
Is the testnet pre-forked with new wallet ?
Yes, it forked at block 100. Block explorer for testnet is here: http://test.vtc.sovereignshare.com/exp/#/vtctest
December 07, 2014, 02:40:10 PM
Not sure if this is tripping any of you guys up but xintensity 64 for a 290x is not the same as xintensity 64 for a 280x or even a 290. xintensity is a multiple of shaders your card has.
For example a 290x at xintensity 64 is 2816*64 = 180224 raw intensity which is close to an intensity of 17.45 (2^17.45 = 179049)
a 290 at xintensity 64 is 2560*64 = 163840 raw intensity which is close to an intensity of 17.32 (2^17.32 = 163621)
Not much of a difference between a 290x and a 290 but with a 7950 having 1792 shaders would be something like an intensity of 16.8
Again not a huge deal but something to consider.
For example a 290x at xintensity 64 is 2816*64 = 180224 raw intensity which is close to an intensity of 17.45 (2^17.45 = 179049)
a 290 at xintensity 64 is 2560*64 = 163840 raw intensity which is close to an intensity of 17.32 (2^17.32 = 163621)
Not much of a difference between a 290x and a 290 but with a 7950 having 1792 shaders would be something like an intensity of 16.8
Again not a huge deal but something to consider.
December 07, 2014, 02:30:26 PM
Is the testnet pre-forked with new wallet ?
December 07, 2014, 02:22:57 PM
I just flashed up the new v.0.9.0.1 64 bit linux wallet. Everything appears as it should and is syncing up nicely.
You guys compiled a linux ccminer for me! You rock!
You guys compiled a linux ccminer for me! You rock!
December 07, 2014, 02:03:44 PM
December 07, 2014, 02:00:32 PM
is this vertacoin?
first hear about this coin "vertacoin" , maybe you do not understand properly .... this is VERTCOIN - Bitcoin Upgraded
December 07, 2014, 02:00:03 PM
Thanks James122 for clearing up the version number.
I understand the algorithm change is not for a while yet. I assume there will be another wallet upgrade then?
I understand the algorithm change is not for a while yet. I assume there will be another wallet upgrade then?
Yup! As a matter of fact its here: https://github.com/vertcoin/vertcoin/releases/tag/v0.9.0.1
December 07, 2014, 01:57:08 PM
Thanks James122 for clearing up the version number.
I understand the algorithm change is not for a while yet. I assume there will be another wallet upgrade then?
I understand the algorithm change is not for a while yet. I assume there will be another wallet upgrade then?
December 07, 2014, 01:54:49 PM
is this vertacoin?
December 07, 2014, 01:33:31 PM
[Official] Testnet Forked | 0.9.0.1
from http://www.reddit.com/r/vertcoin/comments/2okgan/official_testnet_forked_0901/
Quote
All,
Github now has version 0.9.0.1 which includes the correct code for testnet to function properly. You do not need to update unless you want to use testnet. We are working on pushing new builds for this, but if you want to grab the source, just visit https://github.com/vertcoin/vertcoin
We restarted testnet from the first block on scrypt-n and watched it fork at block 100. You can use the following as a testnet block explorer: http://test.vtc.sovereignshare.com/exp
Also, please harass your favorite pool operators and ensure they are up to date! :-D
More to come soon!
Cheers,
Adam
Github now has version 0.9.0.1 which includes the correct code for testnet to function properly. You do not need to update unless you want to use testnet. We are working on pushing new builds for this, but if you want to grab the source, just visit https://github.com/vertcoin/vertcoin
We restarted testnet from the first block on scrypt-n and watched it fork at block 100. You can use the following as a testnet block explorer: http://test.vtc.sovereignshare.com/exp
Also, please harass your favorite pool operators and ensure they are up to date! :-D
More to come soon!
Cheers,
Adam
from http://www.reddit.com/r/vertcoin/comments/2okgan/official_testnet_forked_0901/
December 07, 2014, 01:28:21 PM
@Wolf0 I used like this, nothing changed:
I don't know what is the problem. I cannot see the error message because it dissappears so fast. Maybe because I use 64 bit Win7?
add "pause" at the end of your bat file Code:
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
sgminer.exe --algorithm Lyra2RE -o stratum+tcp://92.27.201.170:9174 --worksize 256 --gpu-engine 1050 --gpu-memclock 1500 --intensity 13
setx GPU_USE_SYNC_OBJECTS 1
sgminer.exe --algorithm Lyra2RE -o stratum+tcp://92.27.201.170:9174 --worksize 256 --gpu-engine 1050 --gpu-memclock 1500 --intensity 13
I don't know what is the problem. I cannot see the error message because it dissappears so fast. Maybe because I use 64 bit Win7?
December 07, 2014, 01:25:56 PM
someone reloads little by little
December 07, 2014, 01:06:48 PM
Cannot start the program with this config. Where do I wrong?
Code:
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
sgminer.exe --kernel Lyra2RE -o stratum+tcp://92.27.201.170:9174 -u blabla.1 -p 1234 --worksize 256 --thread-concurrency 8192 --lookup-gap 2 --gpu-engine 1050 --gpu-memclock 1500 --intensity 13 -g 2
setx GPU_USE_SYNC_OBJECTS 1
sgminer.exe --kernel Lyra2RE -o stratum+tcp://92.27.201.170:9174 -u blabla.1 -p 1234 --worksize 256 --thread-concurrency 8192 --lookup-gap 2 --gpu-engine 1050 --gpu-memclock 1500 --intensity 13 -g 2
use --algorithm Lyra2RE, and get rid of thread concurrency and lookup gap - they don't even make sense for this algo.
Cannot start the program with this config. Where do I wrong?
Code:
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
sgminer.exe --kernel Lyra2RE -o stratum+tcp://92.27.201.170:9174 -u blabla.1 -p 1234 --worksize 256 --thread-concurrency 8192 --lookup-gap 2 --gpu-engine 1050 --gpu-memclock 1500 --intensity 13 -g 2
setx GPU_USE_SYNC_OBJECTS 1
sgminer.exe --kernel Lyra2RE -o stratum+tcp://92.27.201.170:9174 -u blabla.1 -p 1234 --worksize 256 --thread-concurrency 8192 --lookup-gap 2 --gpu-engine 1050 --gpu-memclock 1500 --intensity 13 -g 2
use --algorithm Lyra2RE, and get rid of thread concurrency and lookup gap - they don't even make sense for this algo.
anyhow, it needs some adjustment, right now the buffer is a bit too large
Jump to: