[Ultracoin] [Est. Feb 2014] ~ ASIC Resistant & Ultrafast 6 Second Transactions!

[king_pin]

I think the TestPool is telling me its on N-factor 16
So any new miners that I try to connect get rejected (yacminer)

And a friend of mine all ways tells me there is no such thing as "Bad publicity" so maybe the price will go UP after this fuckUP

[Levole11]

I think the TestPool is telling me its on N-factor 16
So any new miners that I try to connect get rejected (yacminer)

And a friend of mine all ways tells me there is no such thing as "Bad publicity" so maybe the price will go UP after this fuckUP

I have difficulty to believe that, judging by the way you do 'business', you really care about someones life, king Pin  ..

( don't get me wrong, its fun to have you around )

[Valpe]

I think the TestPool is telling me its on N-factor 16
So any new miners that I try to connect get rejected (yacminer)

And a friend of mine all ways tells me there is no such thing as "Bad publicity" so maybe the price will go UP after this fuckUP

its still nf 14. Workers difficult seems to be under 1 so yacminer wont work. Sure I can be wrong.

[wtfc360]

I think the TestPool is telling me its on N-factor 16
So any new miners that I try to connect get rejected (yacminer)

And a friend of mine all ways tells me there is no such thing as "Bad publicity" so maybe the price will go UP after this fuckUP

From "getting started" page on the Test pool I read this:
Yacminer GPU Miner [example config for 7790. Use static diff port 5555]
yacminer --scrypt -w 128 --lookup-gap 2 -I 17 --thread-concurrency 8000 -g 1 -o stratum+tcp://stratum2.tumblingblock.com:5555 -u Weblogin.WorkerName -p WorkerPassword

Got NF 14 (yacminer) and low hashrate, tried to change the batfile with the above settings and got NF 16 but no connection to the pool, changed back to the original settings and still can't connect with this miner to the test pool. The other miners have 0,1 difficulty and very low hashrate with the original settings...

[tsjaar]

With all this mining stuff... Don't forget to buy some now the are still cheap.

Thank you all for your great support.

[Official Ultracoin Team]

@Thiago
The testnet isn't a real pool, all that hash is just for testing purposes, it is not going to become the real version of the coin.

I am trying to put some hash on the testnet as well. I'll ask Kracko about the issues with connectivity once he wakes up, I know he was working LATE into the night last night trying to get things ironed out. We are seeing a lot of light at the end of the tunnel and things have been progressing nicely. Thank you all for your contributions towards the testnet, I am happy to see that the community can come together during this time of need!

Sincerely,

Steven "Rapture"
Management Director
Ultracoin
Steven@Ultracoin.net

[Kracko]

I think the TestPool is telling me its on N-factor 16
So any new miners that I try to connect get rejected (yacminer)

And a friend of mine all ways tells me there is no such thing as "Bad publicity" so maybe the price will go UP after this fuckUP

From "getting started" page on the Test pool I read this:
Yacminer GPU Miner [example config for 7790. Use static diff port 5555]
yacminer --scrypt -w 128 --lookup-gap 2 -I 17 --thread-concurrency 8000 -g 1 -o stratum+tcp://stratum2.tumblingblock.com:5555 -u Weblogin.WorkerName -p WorkerPassword

Got NF 14 (yacminer) and low hashrate, tried to change the batfile with the above settings and got NF 16 but no connection to the pool, changed back to the original settings and still can't connect with this miner to the test pool. The other miners have 0,1 difficulty and very low hashrate with the original settings...

The test pool is at NF14 just like the live chain.  Have you tried the static diff port I just added?  Try port 64445 with your yacminers. 

[wtfc360]

I think the TestPool is telling me its on N-factor 16
So any new miners that I try to connect get rejected (yacminer)

And a friend of mine all ways tells me there is no such thing as "Bad publicity" so maybe the price will go UP after this fuckUP

From "getting started" page on the Test pool I read this:
Yacminer GPU Miner [example config for 7790. Use static diff port 5555]
yacminer --scrypt -w 128 --lookup-gap 2 -I 17 --thread-concurrency 8000 -g 1 -o stratum+tcp://stratum2.tumblingblock.com:5555 -u Weblogin.WorkerName -p WorkerPassword

Got NF 14 (yacminer) and low hashrate, tried to change the batfile with the above settings and got NF 16 but no connection to the pool, changed back to the original settings and still can't connect with this miner to the test pool. The other miners have 0,1 difficulty and very low hashrate with the original settings...

The test pool is at NF14 just like the live chain.  Have you tried the static diff port I just added?  Try port 64445 with your yacminers. 

Strange, now  when I looked at the testpool, all my original rigs with yacminer pointed at stratum+tcp://stratum2.tumblingblock.com:64444 had high variable difficulties (1-5) and normal hashrate. Tried my first rig which got rejected before and pointed it towards port 64444 and got low difficulty (0,1), switched to port 64445 and it seem to be hashing at normal speed and difficulty around 1.
So it seem to be working on both ports with yacminer, the original ones with port 64444 and the first one that got rejected now works on port 64445, if you can make something out of that...

[king_pin]

One yacminer connected from yesterday that hasn't restarted yet, is still hashing normally!
All other yacminers that I try to connect even if pointed to port 64445 give me NF16

I have no such problems at the old pools, static or variable difficulty.

[Kracko]

@Thiago
The testnet isn't a real pool, all that hash is just for testing purposes, it is not going to become the real version of the coin.

I am trying to put some hash on the testnet as well. I'll ask Kracko about the issues with connectivity once he wakes up, I know he was working LATE into the night last night trying to get things ironed out. We are seeing a lot of light at the end of the tunnel and things have been progressing nicely. Thank you all for your contributions towards the testnet, I am happy to see that the community can come together during this time of need!

Sincerely,

Steven "Rapture"
Management Director
Ultracoin
Steven@Ultracoin.net

Yes, thanks tons for the hash guys.   You've been awesome.  This has been very helpful.

So far Digishield - 10 block average looks like the best candidate.  It is set up to retarget every block, adjustments will be no more than in increments of 8% up and 16% down.  It averages out over the last 10 blocks, allowing it to be fairly flexible with inconsistent hash rates.  If there's a hit and run on us, we'll recover at a decent rate.   I've also implemented the same retarget on the staking, but with its original 20 second spacing.

I'll be resetting the testchain and test database back again soon, so we can test transition to the new retarget starting from a higher diff block.  If you leave your miners aimed at the pool, I'll have everything restored, including your pool workers, within 5 minutes or so after it goes down.

[Kracko]

One yacminer connected from yesterday that hasn't restarted yet, is still hashing normally!
All other that I try to connect yacminers even if pointed to port 64445 give me NF16

I have no such problems at the old pools, static or variable difficulty.

That is weird.  I've noticed some strange http errors in the stratum output from yacminer as well.  Can you set the nfactor manually?

[wtfc360]

Looks like the test pool is up and running again. All my miners are connected and mining at normal hashrate. Changed one rig from port 64444 to port 64445, so now two rigs are running on the static port and the rest on variable diff, all yacminer NF 14.

[Valpe]

  Its good to see all working together with this problem.

UTC will be stronger than ever after this. Thanks to you all.

[Kracko]

Looks like the test pool is up and running again. All my miners are connected and mining at normal hashrate. Changed one rig from port 64444 to port 64445, so now two rigs are running on the static port and the rest on variable diff, all yacminer NF 14.

Good to hear. Anyone else have their Yacminers running successfully on the test pool? It really shouldn't be any different than the other pools as I'm using the same plain NOMP setup for the stratum.

[tuankiet716]

Kracko you finish the test yet.
https://www.upsieutoc.com/images/2014/12/07/Utlc.png

[barbados-fs]

Kracko, I have a pool or I'm not there? I have to be there yesterday.

[Thiago1]

Hi friends
after all the trouble we have with the pools My buddy KING_PING,Terminator and my self decided open back http://ultracoins.info for anyone who decides to have an extra option For as many miners like me the pool will work with 0% fee,the Pool is brand new everything, the e-mail SERVICE working if You forget the password is easy to recovery
Include the database.and have the new version of Ultracoin wallet
Cheers

Thiago

[Valpe]

Hi friends
after all the trouble we have with the pools My buddy KING_PING,Terminator and my self decided open back http://ultracoins.info for anyone who decides to have an extra option For as many miners like me the pool will work with 0% fee,the Pool is brand new everything, the e-mail SERVICE working if You forget the password is easy to recovery
Include the database.and have the new version of Ultracoin wallet
Cheers

Thiago

Nice new pools are welcome.
I must ask you Thiago where is your support for Testnet UTC pool?

[dan_and_shan]

Hey im trying to get a miner up on the test pool, what looks wrong with my bat. it just closes on startup?
  del *.bin
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1 
cgminer --scrypt-jane -o stratum+tcp://stratum2.tumblingblock.com:64444 -u dan_and_shan.worker -p snake --thread-concurrency 8192 -I 13 --worksize 256 -g 2

any ideas?

I didn't take the averaging out that far when I gave my number- I stand corrected.  I messed up.  I apologize.  I'm fixing it and I need your help- everyone's help.

If you want to help make things better please throw some hash at the test server that is running the new retarget algorithm at http://utctest.tumblingblock.com.  If you already have an account at utc2 you can use that to login.  It's an isolated fork of the production chain with a different retarget.  I need as much hash as we can throw at it to test it as my two rigs aren't enough to budge it about minimum.   The retarget is set to 10 minutes.  At end state the retarget will be from 1-3 days.  I am testing to make sure that the retarget keeps things close to a 30 second block time.

@Kracko
We have mined less than 2000 blocks, which makes less than 0.69 blocks a minute!
Which makes this a total lie:

If you look at the overall average we are still putting out a block every 30 seconds.

Lets not forget the  one million ORPHANS!  

How do you want me to be happy, I can bet that I have mined more than you have developed crypto, and Steven marketed restaurants,... I meant to say crypto.



@BorisWCR
As a noob yoy should listen to your older sisters say:
Delete everything in your old Ultracoin app data folder except wallet.dat
Just type  %Appdata%\Ultracoin in the addressbar and you will be redirected there.
You can do it before or after you install the new version, the Deamon (the program itself) and the wallet are on separate locations.

[Namsbreh]

I tried to sign up for the test pool.  I am not receiving the verification email though so unable to login to create workers etc.