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

The orphans have been brutal with the low difficulty surges.  I just checked and UTC and UTC2 are on the same chain.  Things will improve once we switch over to the new retarget at the hard fork block.

The exchanges have been notified of the update. Here is a guide on how-to upgrade your wallet software: http://ultracointalk.org/b3/how-installupdate-your-wallet/170/

Sincerely,

Steven "Rapture"
Management Director
Ultracoin
[email protected]

We need to get the network populated with the latest version as the latest release will only accept blocks from the latest version- hence the random stopping.  The problem is that the new wallet will still connect up with previous versions to exchange peer nodes and will send blocks.  And the wallet tends to jump around to random clients rather than sticking to just the few that it has successfully started downloading blocks from.   Try restarting your wallet or, alternatively, you can edit your ultracoin.conf file to use "connect" rather than "addnode" to synch up- this way it won't try to connect to others.  If you do change them to connect, be sure to change them back to addnode after you've managed a full sync.  As we get more protocol version 70065 wallets out there the connectivity will improve.

I'm stuck at 860732
Last block time: Mon 8. Dec 14:24:29 2014

Is UTC down? Last received block was generated over 2h ago. All mined blocks are taged with "orphan". My last block was 860664.

I have the latest Version of the wallet v0.7.3.3-g15-g0bcf258-beta (http://www.tumblingblock.com/ultracoin_733.1_win32.zip)

Nice work Kracko - thanks

just a heads up - it will hang while converting - for maybe several hours - don't despair - thats what it has to do to set things up first time.

Wallet Update

The new sources are up.  Exchanges and pools, please update your wallets as soon as possible.   The fork to correct the issues we are having will happen at block 861677, which should be sometime around 12/9/14 12pm UTC.  Note: this version will not accept incoming blocks from previous versions, but it will still be capable of connecting to them and also send blocks to them.

The wallet sources can be found here https://github.com/Kracko/ultracoin-2.git

To verify the version, the version and protocolversion lines should show as so with the getinfo RPC command to the wallet:


I recommend using these addnodes as at first they'll be the only wallets the new version will be able to communicate with.



To confirm that you are on the correct chain please use the block explorer here http://ultrabex.tumblingblock.com as it's source wallet is using the latest version.

The new version of the Windows wallet can be found here:  http://www.tumblingblock.com/ultracoin_733.1_win32.zip




If you have already installed v733 and downloaded the chain you will not have to go through that again.

* Back up your existing wallet.  This should be happening anyway.  If you're like me you have it encrypted and in 10 different places, including offsite locations.
* Extract the downloaded zip file
* Stop the current version Ultracoin wallet if you have it running.
* Start the MSI file and go through the installation.  If you picked the install for All Users last time, do that again.   It will install over the top of your existing installation if you have already installed the v733 wallet that was put out.
* If you have a pre-v733 wallet, delete the UltraCoin-qt.exe executable.  Starting it up won't do you much good

I have included an ultracoin.conf file in the install with the addnodes above.  This should help get us over the initial hump.  You can confirm your version in the about menu of the wallet.  It show up on the first line as v0.7.3.3-g15-g0bcf258-beta.  The last part (0bcf258) will match the first 7 characters of the current master branch guid of the repository.

Coins on the exchanges should be safe (well - as safe as any coin on any exchange ever is)

Cryptsy UTC wallets are locked (under maintenance) - so you can not transfer IN or OUT anyway.  Not sure about other exchanges - but suspect thats the case for all - and if its not, I would be worried about those exchanges that are not locked until everything is sorted.

Are coins on exchanges going to be safe after fork? Should we transfer them to our local wallets?

absolutely 100% agree on this - do it once.........do it right

Just take your time - and make sure its working properly before you release

I DONT CARE IF IT TAKES A WEEK

I think that its better to be sure the fork is working right. So dont hurry things and be sure all will be right and ok after the fork.
Even if needs to delay the fork couple days it will be better.

Well I was certain that they will find a way to benefit the Stake holders, after all the devs hold huge amounts of UTC, I hope its for the best.

Slowing down the blocks should have been done long time ago, the N-factor was changing too fast, but I guess better late then never.

Why release the fork on Tuesday. Set an earlier time - why not Monday 00:00 UTC
(24 hours is 24 hours, we have accumulated huge Losses this past week)

New Wallet Update

What you see in the test pool is what you are going to get.   Thanks again to those who have helped in testing.    I am very grateful for your donation of time and energy.  You've done a great service to Ultracoin.  We will be releasing the source tonight and schedule the fork on Tuesday.  The exact block is yet to be determined.  We want this update in fast, but we want to give everyone at least some time to update.  This new update will not require a complete conversion or redownload of the chain if you have already done so.  

Here is the what you'll be getting.  We are going to be increasing the block time at 60 seconds and will be upping the reward by the same factor to maintain the same rate of payouts- the amount will be 30UTC per generated block.  The staking and proof of work difficulties will be completely separated, with the proof of stake time being set to 1 minute too.  In the past, before the latest update, we were producing one staking block for every ten, giving an average of 5 minutes per stake and have pretty much rested on the staking minimum difficulty of 0.25.  

This action will not change the payout amounts for stakes.  The stake payout is not tied to a flat reward rate like PoW blocks, instead it is directly tied to a coin age calculation which varies according to the amount of coin group size and how long it has been held since its last stake or first transaction time.  Staking attempts will still continue at 1 every 30 seconds.  The coin age will be remaining the same as well, ranging from a minimum of 7 days to a max coin age of 35 days.  With these changes, staking and proof of work blocks will have more of a chance of doing something useful for the network other than increasing the block chain as they will be containing more transactions.  Transactions will still be fairly fast.

The biggest things we are trying to achieve here is fixing the current difficulty retarget and also slowing the growth of the block chain.  Already some of our slowest devices are feeling the effects of a long chain in combination with our intensive ChaCha/Keccak512 hashing algo.  Even my I7 Intel the download goes from 200+ blocks per second at the start of the chain down to 6-10/sec once it gets to NFactor-14.   This will slow the annual growth of the chain from 1 million blocks to around half a million.  This will help out enormously for the long run as we climb into the higher NFactors.

Edit:  I left out an important part, the retarget method.  The retargeting algorithm we'll be using is Digishield, with a 10 block averaging time, that retargets every block based on the last ten blocks. It takes slightly longer to adjust to higher hash rates (8% max up per block), but it corrects more quickly after the hash drops (16% per block).  It has also been applied to the staking calculation.  On the PoW side all only proof of work blocks are counted in the difficulty calculation, skipping over the PoS blocks until the last 10 PoW blocks are found and the PoS calculation is based solely on PoS blocks, skipping over the PoW blocks.

IDK if it is my imagination but since I.ve installed the wallet on 30+ machines all staking with a few hundred UTC the network seems to be getting more stable...
To everybody:
Install the wallet on as many machines as u can, since there isn't a new fork for now!!!

They definitely need to do something my wallet stuck couples times plus the difficulty in the pool is crazy

http://ultracoins.info

Steven or Kracko

are we soon to have another fork and a new wallet?

We await an update on progress at your earliest possible convenience.

Thanks

Staking does not really help very much right now as it seems there are many more pow than pos blocks.   If you look in the block explorer the blocks with a .25 difficulty are generally stake blocks.  The miners have much more an effect on the chain. This will change once we get the newer retarget out and we absolutely will need people staking to stabilize the difficulty for pos.

For the curious, here is an example of a PoS block.  http://ultrabex.tumblingblock.com/block/3b382c65aa2470bb286f05a9f1fac8aa86d79ac204ab74a2a6f889fa83c287c5

You can see the from and too addresses are the same.

Who can tell how to get solo UTC?
I set up a file ultracoin.conf

rpcuser=login
rpcpassword=pass
rpcallowip=localhost
rpcport=44101
port=44100
addnode=31.220.0.203
addnode=192.99.8.7
addnode=198.27.82.163



and miner

SET GPU_MAX_ALLOC_PERCENT=100
yacminer.exe --scrypt-chacha -o 127.0.0.1:44101 -u login -p pass --nfmin 4 --nfmax 30 --starttime 1388361600 -R 4576 -g 1 -w 256 --buffer-size 2656 --lookup-gap 7 --auto-fan --temp-cutoff 86 --temp-overheat 80 --gpu-fan 40-95 2>logfile.txt


Purse running, but production does not occur. Yakmayner writes an error URL. What am I doing wrong?

Dude, you waited until full synchronization purse? I, too, when you install a new wallet balance several times less, but I waited until the full upgrade (about 36-40 hours) and the balance returned so as it should have been.