Kracko
|
|
December 08, 2014, 04:09:59 PM |
|
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.
|
|
|
|
Uggle
|
|
December 08, 2014, 05:04:42 PM |
|
I am amazed over that the price is so stable and relatively high even after this chain of events.
|
UTC UTC UTC
|
|
|
Thiago1
|
|
December 08, 2014, 05:15:44 PM |
|
Hey steve the guide is good for windows but how about the people with MAC or UBUNTU Would be nice if you make the guide for all
|
|
|
|
mirny
Legendary
Offline
Activity: 1108
Merit: 1005
|
|
December 08, 2014, 06:38:13 PM |
|
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.
is it necessary to add listen=0, with "connect" ?
|
This is my signature...
|
|
|
Valpe
|
|
December 08, 2014, 06:46:58 PM |
|
I am amazed over that the price is so stable and relatively high even after this chain of events. why not? This all only show how strong UTC community is and dev team are ready to do hard work. If someone wants dump UTC I will buy..Ihave nice amout of BTC ready to move to crypsty.
|
|
|
|
Kracko
|
|
December 08, 2014, 07:00:53 PM |
|
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.
is it necessary to add listen=0, with "connect" ? Only if you have inbound connections because your wallet isn't behind a firewall or has NAT to its p2p port from a netrouter. If that is the case it will help in keeping other nodes from connecting to you.
|
|
|
|
wtfc360
|
|
December 08, 2014, 07:12:20 PM |
|
Updated two wallets from ver. 733 to 733.1, no problems!
|
|
|
|
usukan
Legendary
Offline
Activity: 1590
Merit: 1002
|
|
December 09, 2014, 08:09:47 AM |
|
this is very useful advise from Kracko
"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"
its a pain in the ass restarting blockchain download otherwise
|
--
--
|
|
|
usukan
Legendary
Offline
Activity: 1590
Merit: 1002
|
|
December 09, 2014, 08:19:13 AM Last edit: December 09, 2014, 08:43:44 AM by usukan |
|
is anyone mining? http://www.coinwarz.com/network-hashrate-charts/ultracoin-network-hashrate-chartseems like POS is sustaining the network at present - I would hesitantly say - lucky we have POS also - why when staking - UTC can be sent without encryption password? This feels a little bit vulnerable as it suggests wallet is fully open?
|
--
--
|
|
|
opper
Newbie
Offline
Activity: 57
Merit: 0
|
|
December 09, 2014, 09:29:50 AM |
|
861588 12 left opper 12/09/2014 11:12:57 0.0002 30.00
Why blocks before the target block for the hard for have a block reward of 30? As you see the example here is for block 861588 that is around 100 blocks before the fork.
|
|
|
|
Rabinovitch
Legendary
Offline
Activity: 2030
Merit: 1076
A humble Siberian miner
|
|
December 09, 2014, 11:00:04 AM |
|
Que pasa! I mine in solo with my R9 290. Why there are so many rejects? And when I mine in solo DRK for example, each "accepted" means found block - in this case it's differs or what? Why I see 16 "accepted" in cgminer but only one transaction in the wallet? Btw, is that hashing speed OK for R9 290? I can't find adequate hardware comparison chart or something like that... That incoming transaction remains unconfirmed about 6 hours already - is that OK?.. Wallet is updated to the latest update if any. )
|
|
|
|
BorisWCR
Member
Offline
Activity: 554
Merit: 10
|
|
December 09, 2014, 11:11:31 AM |
|
@Kracko
Is it correct that wallet v.733 can not sync anymore since this morning ? So it stays out of sync.
Does it sync again only after downloading v.733.1 ?
|
|
|
|
Kracko
|
|
December 09, 2014, 11:25:28 AM |
|
@Kracko
Is it correct that wallet v.733 can not sync anymore since this morning ? So it stays out of sync.
Does it sync again only after downloading v.733.1 ?
Install the latest and you will get a sync.
|
|
|
|
Kracko
|
|
December 09, 2014, 11:32:27 AM |
|
How many confirmations does it have? If it is stuck at 0 after 6 hours it's probably an orphan. Open the transaction and take a look at it the "Status" column. Use the "Clear orphans" option on the pop-up/context menu in the transactions window. You can pull it up by right clicking your mouse on any of your transactions in the window. You would probably fare better mining at a pool. Que pasa! I mine in solo with my R9 290. Why there are so many rejects? And when I mine in solo DRK for example, each "accepted" means found block - in this case it's differs or what? Why I see 16 "accepted" in cgminer but only one transaction in the wallet? Btw, is that hashing speed OK for R9 290? I can't find adequate hardware comparison chart or something like that... That incoming transaction remains unconfirmed about 6 hours already - is that OK?.. Wallet is updated to the latest update if any. )
|
|
|
|
Kracko
|
|
December 09, 2014, 11:38:33 AM |
|
It appears Santa came early this year. Ho ho ho. 861588 12 left opper 12/09/2014 11:12:57 0.0002 30.00
Why blocks before the target block for the hard for have a block reward of 30? As you see the example here is for block 861588 that is around 100 blocks before the fork.
|
|
|
|
Namsbreh
|
|
December 09, 2014, 11:39:29 AM |
|
An R9 290 should get more that 3.5kh/s Rabinivitch, a 280x gets over 4kh/s.
There are loads of orphans when the diff drops, probably why your blocks are not confirming
|
|
|
|
|
opper
Newbie
Offline
Activity: 57
Merit: 0
|
|
December 09, 2014, 12:18:15 PM |
|
An R9 290 should get more that 3.5kh/s Rabinivitch, a 280x gets over 4kh/s.
There are loads of orphans when the diff drops, probably why your blocks are not confirming
Around 5.3 - 5.4 with 1100 core.
|
|
|
|
opper
Newbie
Offline
Activity: 57
Merit: 0
|
|
December 09, 2014, 12:34:33 PM |
|
Everything is running smooth now. 34 found blocks in last hour, 0 orphans.
|
|
|
|
Valpe
|
|
December 09, 2014, 12:47:30 PM |
|
Everything is running smooth now. 34 found blocks in last hour, 0 orphans. Seems to working Thanks Kracko
|
|
|
|
|