nico54
Newbie
Offline
Activity: 7
Merit: 0
|
|
March 22, 2014, 07:56:53 PM |
|
Could you write to me what is your rig scrypt setup ? I have r9 280x and I'm getting about 300 kh/s per one card. I have read that the optimal hashrate estimates about 350 kh/s. Do you know the optimal rig setup ? Here is my scrypt :
setx GPU_MAX_ALLOC_PERCENT 100 setx GPU_USE_SYNC_OBJECTS 1
cgminer --scrypt -o stratum+tcp://east1.us.stratum.dedicatedpool.com:3379 -u user -p password -g 1 -w 256 -I 13 --lookup-gap 2 --thread-concurrency 8193 --gpu-engine 1080
Any suggestion what I can change/add (i'm using verminer) ?
set gpu engine in 1000 or 1020 Did not help Download Vertminer ou exeminer exeminer.exe --nscrypt -o stratum+tcp://east1.us.stratum.dedicatedpool.com:3379 -u ..... -p ..... -I 13 -g 2 -w 256 --lookup-gap 2 --thread-concurrency 8192 --gpu-fan 95 --gpu-engine 1048 --gpu-memclock 1500
|
|
|
|
|
jwinterm
Legendary
Offline
Activity: 3164
Merit: 1117
|
|
March 22, 2014, 08:08:15 PM |
|
can confirm, dedicated is a super solid pool
|
|
|
|
HeadsOrTails
|
|
March 22, 2014, 08:14:40 PM |
|
Sorry for the delay. We wanted to improve the code, making merkle hash from 22:00, and cutting block maturity.
Explain what this means and why you thought it'd take 5 minutes.
Then we started genesis block, we found it. Doing the compilation something failed.
What failed exactly? Because coins were mined up to block 75 or so.
We wanted to fix it, because the other wallets looks better and have more features. Time was up, and we wanted to solve it.
So was it because of something failing or the other wallet looking better? Also, was delaying everyone worth it when you had a fallback plan? How does the wallet effect the nodes, released so slowly?
At the end END OF WHAT? we decided to release the version from yesterday.
At that moment we were on a hurry and github got screwed.
Please elaborate on this - Github broke?
Then we had to upload the source to mega and release it from there. Again we are sorry for the big delay.
How did getting yesday's prepared file and uploading it to Mega take so long? Why the password?
...as miners we feel ashamed for the big delay and for not being able to release all the stuff that we had ready to release....
As miners, why did you slowly release nodes over time, with the initial node not showing a ping, thje 2nd node being the IP of the first node etc? Also, as miners, why would you think we'd support such a coin?
...We'll keep working the whole night to release the real wallets. ..
Don't bother. We don't care about the features of a team which is incompetent.
Again let me explain myself. Yesterday we did a test with the wallet that right now it's released. Block maturity was set to 120 blocks. With a block time of 288s while doing the test we realized that base maturity was so high and we wanted to change the value to 90. At the same time, we wanted to adjust merkle hash because at block 13 (aprox 1h) DGW kicks in. If you put a merkle hash from let's say a week then you find a whole bunch of blocks until dif retargets properly. Then we compiled the daemon, found the genesis block and while compiling the linux wallet we got an issue. We tried to find the issue, but we couldn't fine it. Time went up. We thought it was a matter of ten minutes to solve the problem with the wallet. At the end we did not want to abort the launch because pretty much the code was the same and we decided to release our older wallet. Bitcointalk was down, so we decided to release a wallet with password to IRC, Twitter and wait to Bitcointalk. We didn't want a ninja launch for that reason we were saying constantly at twitter that the wallet was with password to prevent that. Once Bitcointalk went up again we released everything. We had to change everything for that reason we had no more nodes at that time. Maybe you don't care but our community cares. We are sorry because we weren't expecting this to happen. What community? Look I'll give it to you, you're good with words and stay calm - a good PR man. Let me ask you directly, b/c you keep skirting around the question: DURING THE LAUNCH DELAYS GOING ON ... WHO WAS MINING AND HOW WERE THEY DOING SO? I don't buy it because every other launch has the following ready: * nodes * RPC port * P2P port * conf file example Also the fact we've seen it a million times before and there is no community. You're not dogecoin. You have no Shibes to fall back on. It's some guy from 4chan. Who comes up when wallet launches. That guy... he's your community. That's it man. Get a grip. This greedy pre-mine shit is infuriating because you're so, so, so sorry but the fact remains people had working wallets from genesis block, no? Maybe I am wrong - but if so that is actually worse... because you're not sneaky, you're incompetent and don't know it's the case.
|
|
|
|
lagharto
|
|
March 22, 2014, 08:25:34 PM |
|
I don't buy it because every other launch has the following ready:
Ok dont mine, dont waste time, dont waste money....
|
|
|
|
Rotocoin (OP)
|
|
March 22, 2014, 08:28:36 PM |
|
Sorry for the delay. We wanted to improve the code, making merkle hash from 22:00, and cutting block maturity.
Explain what this means and why you thought it'd take 5 minutes.
Then we started genesis block, we found it. Doing the compilation something failed.
What failed exactly? Because coins were mined up to block 75 or so.
We wanted to fix it, because the other wallets looks better and have more features. Time was up, and we wanted to solve it.
So was it because of something failing or the other wallet looking better? Also, was delaying everyone worth it when you had a fallback plan? How does the wallet effect the nodes, released so slowly?
At the end END OF WHAT? we decided to release the version from yesterday.
At that moment we were on a hurry and github got screwed.
Please elaborate on this - Github broke?
Then we had to upload the source to mega and release it from there. Again we are sorry for the big delay.
How did getting yesday's prepared file and uploading it to Mega take so long? Why the password?
...as miners we feel ashamed for the big delay and for not being able to release all the stuff that we had ready to release....
As miners, why did you slowly release nodes over time, with the initial node not showing a ping, thje 2nd node being the IP of the first node etc? Also, as miners, why would you think we'd support such a coin?
...We'll keep working the whole night to release the real wallets. ..
Don't bother. We don't care about the features of a team which is incompetent.
Again let me explain myself. Yesterday we did a test with the wallet that right now it's released. Block maturity was set to 120 blocks. With a block time of 288s while doing the test we realized that base maturity was so high and we wanted to change the value to 90. At the same time, we wanted to adjust merkle hash because at block 13 (aprox 1h) DGW kicks in. If you put a merkle hash from let's say a week then you find a whole bunch of blocks until dif retargets properly. Then we compiled the daemon, found the genesis block and while compiling the linux wallet we got an issue. We tried to find the issue, but we couldn't fine it. Time went up. We thought it was a matter of ten minutes to solve the problem with the wallet. At the end we did not want to abort the launch because pretty much the code was the same and we decided to release our older wallet. Bitcointalk was down, so we decided to release a wallet with password to IRC, Twitter and wait to Bitcointalk. We didn't want a ninja launch for that reason we were saying constantly at twitter that the wallet was with password to prevent that. Once Bitcointalk went up again we released everything. We had to change everything for that reason we had no more nodes at that time. Maybe you don't care but our community cares. We are sorry because we weren't expecting this to happen. What community? Look I'll give it to you, you're good with words and stay calm - a good PR man. Let me ask you directly, b/c you keep skirting around the question: DURING THE LAUNCH DELAYS GOING ON ... WHO WAS MINING AND HOW WERE THEY DOING SO? I don't buy it because every other launch has the following ready: * nodes * RPC port * P2P port * conf file example Also the fact we've seen it a million times before and there is no community. You're not dogecoin. You have no Shibes to fall back on. It's some guy from 4chan. Who comes up when wallet launches. That guy... he's your community. That's it man. Get a grip. This greedy pre-mine shit is infuriating because you're so, so, so sorry but the fact remains people had working wallets from genesis block, no? Maybe I am wrong - but if so that is actually worse... because you're not sneaky, you're incompetent and don't know it's the case. Okay let me explain it again. We had rpc port, p2p port and 1 node ready. We were setting more nodes when we had to stop that to fix our issue. Now we know it came from the 47 languages that we added to the wallet. When we fixed the whole thing Bitcointalk was down. Then we didn't want to do a ninja launch so we uploaded a wallet with password, we post it here, at twitter and also at IRC. After some minutes, so everyone could have their wallet downloaded we released the password in all the sites at the same time. You can check the blockchain and you'll see that before the password was released only 8 blocks were mined. 4 in one adress and another 4 in another address. 1 block was premine block, the other 7 blocks we are goin to give them away. People did not have wallets from genesis block. Because the tesnet from Thursday was from a different source. We changed merkle hash, block maturity, added the languages (the issue), and a couple more stuff. So when time was up, and we couldn't fix the issue we had to release the older wallet because we couldn't fix the new one. In one thing you are wrong, we have our community, and we made the coin for our comunity. If you don't want to mine it it's fine, we'll keep working to improve the coin. Besides what's the point of having more than 40 BTC from IPO + the remaining coins and screwing everything for how much 50 blocks=100 coins? Again You are wrong there. Cheers
|
|
|
|
grandMasterHash
Newbie
Offline
Activity: 38
Merit: 0
|
|
March 22, 2014, 08:29:00 PM |
|
|
|
|
|
xfear
Newbie
Offline
Activity: 55
Merit: 0
|
|
March 22, 2014, 08:34:56 PM |
|
The Spanish comunity can become like a mafia !, and yes, I'm from spain too, and I've seen many of the people posting here in some spanish forums xD, although i dont know them take care !!!!! yeah, got page 100
|
|
|
|
virtualdn
Legendary
Offline
Activity: 1372
Merit: 1093
|
|
March 22, 2014, 08:57:25 PM |
|
|
1 BTC = 1 BTC
|
|
|
luiggybit
Member
Offline
Activity: 66
Merit: 10
|
|
March 22, 2014, 09:04:13 PM |
|
sent to the faucet a few coins!
|
|
|
|
franckuestein
Legendary
Offline
Activity: 1960
Merit: 1130
Truth will out!
|
|
March 22, 2014, 09:07:47 PM |
|
Let's try It when coins arrive! Thanks a lot!
|
[ AVAILABLE SIGNATURE SPACE ]
|
|
|
virtualdn
Legendary
Offline
Activity: 1372
Merit: 1093
|
|
March 22, 2014, 09:08:39 PM |
|
|
1 BTC = 1 BTC
|
|
|
lagharto
|
|
March 22, 2014, 09:16:47 PM |
|
Wait coins!
|
|
|
|
virtualdn
Legendary
Offline
Activity: 1372
Merit: 1093
|
|
March 22, 2014, 09:17:25 PM |
|
Wait coins! working!
|
1 BTC = 1 BTC
|
|
|
|
lagharto
|
|
March 22, 2014, 09:27:17 PM |
|
Still mining, 2.1 ghs its good!
|
|
|
|
NickPortland
Member
Offline
Activity: 98
Merit: 10
|
|
March 22, 2014, 09:27:59 PM |
|
Wait coins! working! Faucet balance: 0.00074 lol!
|
Official Ambassador for UTC-PND relations *donations here* UTC: Ujff1xrc8brmHkRaFG3BcG5nVScXdh5Wu1 BTC: 159uuxJCfUsG44N52NUsydi2bCNeFSYyTi
|
|
|
niki25
Legendary
Offline
Activity: 1036
Merit: 1000
|
|
March 22, 2014, 09:34:51 PM |
|
Still mining, 2.1 ghs its good!
+1, great support behind
|
|
|
|
cherominerito
|
|
March 22, 2014, 09:47:57 PM |
|
Still mining, 2.1 ghs its good!
+1, great support behind 2.1 N-Factor = 4 normal Scrypt Nice,
|
FootballCoin: FXFCWvewynp8feR4ZQ1BJbYxeWzByvqgN8
|
|
|
Trinibits
|
|
March 22, 2014, 09:50:01 PM |
|
Guys please can you help me. My wallet has no active connections and it wont sync. Please can someone help me.
Many Thanks
|
|
|
|
|