Topic: [Ultracoin] [Est. Feb 2014] ~ ASIC Resistant & Ultrafast 6 Second Transactions! - page 77. (Read 381018 times)

I am very happy to report that PressTab has made a breakthrough in the UltraCoin wallet development.

It requires some more work and further testing - but all things are coming together now rather nicely.

Again - sorry for delays but we really want to get this job done properly - and we only want to fork once.


Cheers - usukan

Wallet testing update

Basically we are still waiting.  Rapture333 has taken the wallet to some 3rd parties for further testing, analysis and review.

Nothing to do but wait unfortunately - we do not want any issues with the fork.

We don't want anything like Ethereum/The DAO to happen.


I'm a strong Ethereum supporter but for light relief - this video is worth watching.


https://www.youtube.com/watch?v=_O5fdMFKEC0

If you want to try mining UTC (I tried for a long time with no joy) - this really works rather well

Thanks @thirtybird

There is a version here to suit any WINDOWS system


https://github.com/thirtybird/cpuminer/releases/

eg for .bat file

minerd-x64-avx2.exe --nfmin=14 --nfmax=14 -a scrypt-chacha -o stratum+tcp://yacoin.club:3413 -O USER.WORKER NAME:PASSWORD

i.e.
minerd-x64-avx2.exe --nfmin=14 --nfmax=14 -a scrypt-chacha -o stratum+tcp://yacoin.club:3413 -O usukan.w6:x


when you unzip and open up the folder

Which version do I use??? ‘avx’ works on most - if you are new system use ‘avx2’. If old I7 use ‘corei7’

If you do not know which CPU you have, try each one starting from the top and work your way down.

Intel Processors
‘avx2’      Intel Core CPU with 64-bit extensions, MOVBE, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, AVX, AVX2, AES, PCLMUL, FSGSBASE, RDRND, FMA, BMI, BMI2 and F16C instruction set support.
‘avx-i’      Intel Core CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, AVX, AES, PCLMUL, FSGSBASE, RDRND and F16C instruction set support.
‘avx’      Intel Core i7 CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, AVX, AES and PCLMUL instruction set support.
‘corei7’   Intel Core i7 CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2 and POPCNT instruction set support.
‘core2’      Intel Core 2 CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3 and SSSE3 instruction set support.
‘nocona’   Improved version of Intel Pentium 4 CPU with 64-bit extensions, MMX, SSE, SSE2 and SSE3 instruction set support.

AMD Processors
‘avx’      Intel Core i7 CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, AVX, AES and PCLMUL instruction set support.
‘athlonfx’   Processors based on the AMD K8 core with x86-64 instruction set support, including the AMD Opteron, Athlon 64, and Athlon 64 FX processors. (This supersets MMX, SSE, SSE2, 3DNow!, enhanced 3DNow! and 64-bit instruction set extensions.)
‘nocona’   Improved version of Intel Pentium 4 CPU with 64-bit extensions, MMX, SSE, SSE2 and SSE3 instruction set support.


For more information, read it from the source : http://gcc.gnu.org/onlinedocs/gcc/i386-and-x86-64-Options.html#i386-and-x86-64-Options



Sorry about progress on release of new wallet - still some issues we are working through with PressTab and Rapture333 - we have not abandon - just getting everything 100% correct for release.


Cheers - usukan

Wallet testing update

Please be patient everyone

PressTab is still hard at work between his other commitments getting the new wallet, retargetting and staking working to perfection.

Some unexpected pool connectivity issues also need solving - but its coming along.

I will advise when the wallet update is close at hand.

Cheers - usukan

Hi Marnie1976

Its no problem.  Basically its because of the retargetting issue with the current UTC wallet - the old one (the one we are fixing up at present).

We have periods where its a very long time between blocks - maybe an hour or two or longer - then the blocks rush through in a matter of seconds when the diff drops.  I have been mining a bit to study this lately.

If you choose to send during a slow block time (high diff) be prepared to wait for a while to get your 6 confirmations. If someone is staking it may help too.

At the end of the day - if you are patient - they will get all confirmed.  Dont be alarmed if it takes a few hours for 6 confs - but if you time it right (about 8-12 hrs time) they will go through in a few seconds.

When we get this new wallet all fixed up we should be back to 60 sec blocks again.

Cheers - usukan

Hello UTC Team,

I have a question.
I want to send some coins to Bitrex exchange.
The Bitrex deposit wallet adress give the following warning :  The last block update occurred 489 minutes ago.
What does it means ?

My wallet is up to date and is syncd and has version v0.7.4.1-g-9-g23ef1a4-beta.
But still my send coins to Bitrex have in the wallet the 0/Uncunfirmed status for more then 1 hour.

Can the team members tell me what is happening ?

Thanks.

Will do - thanks bathrobehero

Sounds good. Feel free to pm me if you or anyone on the team needs help with testing (with mining or otherwise) as I don't always check this thread but I react to pm's if I can.

Testing Update

So far we have progressed well with re-target and staking tests.  Both functions appear to work but we need some more detailed tests.

We have some issues with nodes/wallets connecting with the pool - but peers connect just fine to each other. PressTab and Alenevaa will be working on this next week.

PressTab is away for the weekend - testing will resume in earnest next week.


Cheers - usukan

Thanks bathrobehero - I noted all your exploits with great interest (and eel chipping in to save my ass) - damn fine extreme set of tests - your time and hash very much appreciated.


The retargetting looks pretty good to me.  Not an expert but massive improvement and as good as I have seen on some other coins that I have mined that get hit by multipool swings.  After such a huge set of swings I was expecting to be left on the ledge for longer after you left (although I got one very soon by extreme luck).  I think the retargetting is pretty much fixed here by PressTab but he will ponder and comment on that.

While hash was relatively stable (2-15 KH/s) the av block time was pretty much dead on target for 1 min (56-65mins) if I rely on dashboard stats.  It went crazy - (but not bizarre like now) -  when you came on and returned nicely after we got over the hump from removing your several 100 KH/s hash.

I'm not convinced the stats on the pool are representing the reality yet - in fact on the dashboard they are completely crazy at present but Alenevaa can handle that.

I agree that even when stable at present we are not getting 60 blocks per hour - and that may need attention (if its not averaged out for a longer period than I am considering). Additionally - I don'y have enough hash (only 2-3 KH/s) to probably put the retargetting in the range its properly designed to work. SHA256 just don't work here unfortunately. At 15KH/s it looked much better - but still a bit short on 60 blocks per hour. At a normal load it may be much better.

Looking good and we will test out staking tomorrow.

Cheers - usukan.

I threw my rigs at the test pool a few hours ago to see how the difficulty behaves and it seems great. The maximum difficulty I've seen was 0.0063 (instead of ~0.1) and more importantly it's much more reactive and can jump up und a down a lot (eg. 0.0026 > 0.0004) between blocks if needed instead of slowly climbing like the previous retarget did.

But the block times seem to be quite high.
From block 1733140 to 1733188 the average was 1 minute and 26 seconds with 110% average actual shares needed. It's a small period I know but still.

Then I stopped my miners abruptly to see how the difficulty adapts. There was no blocks found for about 92 minutes but it was due to really bad luck (I think) so eventually I put one rig back on the test pool.
I mean the pool's dashboard said we were at ~1400% shares when the block was found but on the blocks page it seems to be divided by 10 and shows 143% shares required (block 1733192).
1400% seems more reasonable compared to the time between blocks.

Thanks to "eel" for joining me on the testpool.

 

bathrobehero - Thanks for bumping it over the forkpoint today so the testpool can explore the post fork world.
EDIT - and blasting the TestPool to check the retarget at extremes.  Nice work indeed.

Testpool is hashing away now and I'll let the experts dissect the results.



Cheers - usukan

Yep, was just about to say it. Unfortunately we had some poor luck finding the two most difficult blocks but now we're speeding up.

cheers

Update - and lots of nice blocks by your good self - diff diving

No problem. I'd have kept mining but now the difficulty is so high that it would take me 40 minutes to find a single block and the difficulty is still increasing so I stopped. You can understand why I don't want to mine air for days.

But I'll mine some more later today in the hopes of pushing through the difficulty climb and seeing it turning back and start decreasing. We might just be able to reach the fork block without another difficulty climb period.

Thanks for your tests there bathrobehero.

We have a few low level (compared to your rigs) miners on the test pool now.

We'll just let it run and monitor things.

Cheers - usukan

The fork on the testpool is a bit far out (~580 blocks), especially now that the difficulty is swinging up.

Hi bathrobehero

Thanks for that hash

Yes we could do with more hash on the test pool - when you are ready.

Thanks usukan

I threw some hash at it for a short while but for now I have to go, I will mine tomorrow if needed.