Installed new wallet and it is not synchronized. Someone tell me a working node?
please read post above
https://bitcointalksearch.org/topic/m.16577937
Topic: [Ultracoin] [Est. Feb 2014] ~ ASIC Resistant & Ultrafast 6 Second Transactions! - page 69. (Read 381063 times)
October 16, 2016, 06:35:10 PM
please read post above
https://bitcointalksearch.org/topic/m.16577937
October 16, 2016, 06:28:31 PM
Installed new wallet and it is not synchronized. Someone tell me a working node?
October 15, 2016, 10:57:54 PM
Ultracoin has a network error at present.
We currently do not know the exact cause but both old and new wallets are affected. The wallets can sometimes connect - but they are not "talking" and not transferring/sharing data.
Mining, syncing wallets or attempting transactions is not recommended (futile) until we fix the network issue.
The issue arose a couple of days ago when the mining diff went up. Time between blocks became very long and lots of transactions bloated the blocks. Bathrobehero came in and cracked the diff and got mining working again. Unfortunately the issue arose again - with some correlation to a flood of 1,000's of small transactions. Both the pool and PressTabs node were overwhelmed by the transaction processing load - and went down. Alenevaa applied a temporary fix but that also eventually did not hold up with the load and another flood of transactions. PressTab has restarted his node several times remotely but it just keeps crashing.
Alenevaa will be working on the pool Mon-Wed next week to hopefully arrange a fix to get us to the fork. Please note that after the fork when we run with the new diff retargeting the problem will likely disappear.
PressTab is travelling at present but is also aware of the issue. As soon as he is back he will try and get a fix for the his seed node - which is key to the new wallets finding reliable peers.
I have been working on coordinating tests and fixes while travelling - its unfortunate that I am not tech in this area - so we must wait for the tech guys to get on deck next week.
So for now you should do nothing - shut down your wallets and miners. We will let you know when the network is up again.
I think the main strategy will be to apply fixes until the fork - and after that the new wallet will take over and things should be back to BETTER than normal.
(I can't help but think that this is shades of Ethereum at present!)
Don't worry - your coins are safe.
Apologies for the inconveniences - its a cruel joke that we were hit with this issue just before the fork.
I can tell you that I am not happy.
Cheers - usukan
We currently do not know the exact cause but both old and new wallets are affected. The wallets can sometimes connect - but they are not "talking" and not transferring/sharing data.
Mining, syncing wallets or attempting transactions is not recommended (futile) until we fix the network issue.
The issue arose a couple of days ago when the mining diff went up. Time between blocks became very long and lots of transactions bloated the blocks. Bathrobehero came in and cracked the diff and got mining working again. Unfortunately the issue arose again - with some correlation to a flood of 1,000's of small transactions. Both the pool and PressTabs node were overwhelmed by the transaction processing load - and went down. Alenevaa applied a temporary fix but that also eventually did not hold up with the load and another flood of transactions. PressTab has restarted his node several times remotely but it just keeps crashing.
Alenevaa will be working on the pool Mon-Wed next week to hopefully arrange a fix to get us to the fork. Please note that after the fork when we run with the new diff retargeting the problem will likely disappear.
PressTab is travelling at present but is also aware of the issue. As soon as he is back he will try and get a fix for the his seed node - which is key to the new wallets finding reliable peers.
I have been working on coordinating tests and fixes while travelling - its unfortunate that I am not tech in this area - so we must wait for the tech guys to get on deck next week.
So for now you should do nothing - shut down your wallets and miners. We will let you know when the network is up again.
I think the main strategy will be to apply fixes until the fork - and after that the new wallet will take over and things should be back to BETTER than normal.
(I can't help but think that this is shades of Ethereum at present!)
Don't worry - your coins are safe.
Apologies for the inconveniences - its a cruel joke that we were hit with this issue just before the fork.
I can tell you that I am not happy.
Cheers - usukan
October 15, 2016, 10:44:30 AM
Hello,
Can someone tell my if I am doing something wrong, I installed the new wallet , and am syncing it. But in the last 12 hours I have only managed Sync 5% of the blocks.
I have 19 active connections but it is still going so slow.
thx
Can someone tell my if I am doing something wrong, I installed the new wallet , and am syncing it. But in the last 12 hours I have only managed Sync 5% of the blocks.
I have 19 active connections but it is still going so slow.
thx
October 15, 2016, 10:40:27 AM
There must be something wrong at the moment.. loading very slow.
Could someone check it?
Valpe
The ping time must be 600,000ms
Could someone check it?
Valpe
Volume is more than 4.2 btc, so UTC should stay. 
Valpe
I gave up on http://utc14.yacoin.club/ pool...it would take me 2 more hours to set workers.Valpe
Can you confirm UTC will not be delisted from bittrex?
The ping time must be 600,000ms
October 15, 2016, 08:50:28 AM
Volume is more than 4.2 btc, so UTC should stay.
Valpe
I gave up on http://utc14.yacoin.club/ pool...it would take me 2 more hours to set workers.Valpe
Can you confirm UTC will not be delisted from bittrex?
The ping time must be 600,000ms
October 13, 2016, 11:27:25 PM
Volume is more than 4.2 btc, so UTC should stay.
Valpe
Valpe
Can you confirm UTC will not be delisted from bittrex?
October 13, 2016, 11:26:02 PM
Can you confirm UTC will not be delisted from bittrex?
Nothing in life is certain - I cannot "confirm" - but its highly unlikely since our vol is up and they have been informed of our current upgrade plans and seem onboard.
This has happened many times before - and we have not been delisted. Although - they have raised thresholds now and seem keen to weed a few minor coins out.
Ultracoin is far from bottom of their board at present.
Cheers - usukan.
October 13, 2016, 10:39:51 PM
Can you confirm UTC will not be delisted from bittrex?
October 13, 2016, 10:36:31 PM
Now everything seems fine, both my wallets synced perfectly. Not sure why they didn't sync yesterday with the same nodes.
Edit: Scratch that. Solomined blocks won't show on other wallets again (I essentially fork off if I find a block) and the pool also seems to have some issues.
Edit: Scratch that. Solomined blocks won't show on other wallets again (I essentially fork off if I find a block) and the pool also seems to have some issues.
Yes - its fair to say there are some signif network issues at present. For some reason all wallets - both old and new are connecting but not passing information between themselves.
Alenevaa managed to get the pool working yesterday - but its gone again. We need to wait for PressTab and Alenevaa to swap notes and ideas.
PressTab and Alenevaa will look into the problem - I let them know the issue early this morning.
Cheers - usukan
October 13, 2016, 03:25:27 AM
Now everything seems fine, both my wallets synced perfectly. Not sure why they didn't sync yesterday with the same nodes.
Edit: Scratch that. Solomined blocks won't show on other wallets again (I essentially fork off if I find a block) and the pool also seems to have some issues.
Edit: Scratch that. Solomined blocks won't show on other wallets again (I essentially fork off if I find a block) and the pool also seems to have some issues.
October 12, 2016, 09:02:29 PM
Hey, it's nice to see the new wallet is here and thanks to everyone who made it happen!
Though there are some issues. It seems that some blocks were found on the pool but some parts of the pools still say the pool is still on block 1809901.
I solomined a block on the new wallet but a local wallet on another machine with the same nodes is still stuck on 1809901. It seems blocks are not transferring between nodes.
Though there are some issues. It seems that some blocks were found on the pool but some parts of the pools still say the pool is still on block 1809901.
I solomined a block on the new wallet but a local wallet on another machine with the same nodes is still stuck on 1809901. It seems blocks are not transferring between nodes.
Hi bathrobehero
Thanks for stepping in and crunching past those high diff blocks we got stuck on.
I'm just working from a hotel room on a mobile tether so I'm having trouble checking things out in terms of wallets and mining.
It seems that mining on the pool is progressing now and the diff has dropped down to an acceptable level. I can connect to the pool with CPU miner and get shares OK. The pool just got another block while I'm typing.
I note that as you say - the current block reported on the pool is behind the actual block we are mining.
I can get a wallet to connect to 2 peers with a .conf file - UPDATE - and yes the wallet has started to sync now with new blocks coming in fine.
I will ask if Alenevaa and PressTab can check things out asap.
I will check back when later.
Cheers - usukan
From a proper connection I have checked everything out and all seems OK.
Pool has correct stats - mining is going well.
My wallet synced fast to correct block.
All good - Thanks bathrobehero and Alenevaa
PressTab's Ultracoin block explorer seems to be offline - but I'm sure that will be fixed shortly.
Cheers - usukan
October 12, 2016, 04:04:26 PM
Hey, it's nice to see the new wallet is here and thanks to everyone who made it happen!
Though there are some issues. It seems that some blocks were found on the pool but some parts of the pools still say the pool is still on block 1809901.
I solomined a block on the new wallet but a local wallet on another machine with the same nodes is still stuck on 1809901. It seems blocks are not transferring between nodes.
Though there are some issues. It seems that some blocks were found on the pool but some parts of the pools still say the pool is still on block 1809901.
I solomined a block on the new wallet but a local wallet on another machine with the same nodes is still stuck on 1809901. It seems blocks are not transferring between nodes.
Hi bathrobehero
Thanks for stepping in and crunching past those high diff blocks we got stuck on.
I'm just working from a hotel room on a mobile tether so I'm having trouble checking things out in terms of wallets and mining.
It seems that mining on the pool is progressing now and the diff has dropped down to an acceptable level. I can connect to the pool with CPU miner and get shares OK. The pool just got another block while I'm typing.
I note that as you say - the current block reported on the pool is behind the actual block we are mining.
I can get a wallet to connect to 2 peers with a .conf file - UPDATE - and yes the wallet has started to sync now with new blocks coming in fine.
I will ask if Alenevaa and PressTab can check things out asap.
I will check back when later.
Cheers - usukan
October 12, 2016, 07:59:37 AM
Hey, it's nice to see the new wallet is here and thanks to everyone who made it happen!
Though there are some issues. It seems that some blocks were found on the pool but some parts of the pools still say the pool is still on block 1809901.
I solomined a block on the new wallet but a local wallet on another machine with the same nodes is still stuck on 1809901. It seems blocks are not transferring between nodes.
Though there are some issues. It seems that some blocks were found on the pool but some parts of the pools still say the pool is still on block 1809901.
I solomined a block on the new wallet but a local wallet on another machine with the same nodes is still stuck on 1809901. It seems blocks are not transferring between nodes.
October 11, 2016, 05:54:58 PM
Code:
___ _ ___ _ _
/ __\___ (_)_ __ / __\ |__ ___ ___| | _____ _ __
/ / / _ \| | '_ \ / / | '_ \ / _ \/ __| |/ / _ \ '__|
/ /__| (_) | | | | / /___| | | | __/ (__| < __/ |
\____/\___/|_|_| |_\____/|_| |_|\___|\___|_|\_\___|_|
v0.0.4 October 2016 | http://www.fuzzbawls.pw
Checking Host OS... WIN
Creating temp folder to clone remote repository...
Cloning https://github.com/presstab/ultracoin-2.git...
-= Repository Information =-
============================================================
Number of commits: 229
Last commit date: Thu, Sep 29, 2016 9:46:36 AM
Days since last commit: 9.71 Days
-= Build System Information =-
============================================================
Build Type: QMAKE/Makefile
Build Version: 0.4.3.0
Qt Bin: ultracoin-qt
Daemon Bin: ultracoind
-= Coin Specifications =-
============================================================
Coin Name: ultracoin
Client Version: 1.0.0.0
Client Name: /Ultracoin:1.0.0.0/
Default P2P Port: 44100
Default PRC Port: 44101
Message Start String: 0xd9 0xe6 0xe7 0xf5
-= Coin Information Checks =-
============================================================
Matching P2PPORT in init documentation: [OK]
Matching RPCPORT in init documentation: [OK]
Build & Client Version Match: [!!]
-= Library Version Compliance Checks =-
============================================================
Miniupnpc v1.9 (API 14): [OK]
OpenSSL v1.0.1k+ (Strict DER Signatures): [OK]
Boost v1.58+ (boost::get): [OK]
-= Security Standards Checks =-
============================================================
Free of IRC related files: [OK]
IRC based peer fetching: [--]
Contains signature malleability patch (PPCoin): [OK]
-= Connectivity Checks =-
============================================================
Contains unique ClientName: [OK]
Contains DNS seeder addresses: [OK]
Contains Hex-Encoded seeder addresses: [!!]
Has at least ONE default connection method: [OK]
Number of DNS Seeds: 1
Listing DNS Seed addresses...
* utcseed.presstab.pw
212.180.171.44 [!!]
198.27.82.163 [!!]
74.118.192.18 [OK]
-= OS Specific Checks =-
============================================================
Mac OS X Native Notification Support: [OK]
Mac OS X Deployment Script: [OK]
Mac OS X Application Icon: [OK]
Mac OS X Dock Icon Menu (Qt5): [OK]
Windows Installer Script: [**]
Windows Installer Header Image: [!!]
Windows Installer Logo Image: [!!]
Windows Installer Icon: [!!]
============================================================
* Windows installer script is using an incorrect name!
* Deployment build won't have the correct metadata!
* Windows installer sript is using an incorrect version!
* Deployment build won't have the correct metadata!
Results should be manually verified and you should NOT rely
on any automated scripts (including this one) before running
or compiling any crypto wallet.
============================================================
/ __\___ (_)_ __ / __\ |__ ___ ___| | _____ _ __
/ / / _ \| | '_ \ / / | '_ \ / _ \/ __| |/ / _ \ '__|
/ /__| (_) | | | | / /___| | | | __/ (__| < __/ |
\____/\___/|_|_| |_\____/|_| |_|\___|\___|_|\_\___|_|
v0.0.4 October 2016 | http://www.fuzzbawls.pw
Checking Host OS... WIN
Creating temp folder to clone remote repository...
Cloning https://github.com/presstab/ultracoin-2.git...
-= Repository Information =-
============================================================
Number of commits: 229
Last commit date: Thu, Sep 29, 2016 9:46:36 AM
Days since last commit: 9.71 Days
-= Build System Information =-
============================================================
Build Type: QMAKE/Makefile
Build Version: 0.4.3.0
Qt Bin: ultracoin-qt
Daemon Bin: ultracoind
-= Coin Specifications =-
============================================================
Coin Name: ultracoin
Client Version: 1.0.0.0
Client Name: /Ultracoin:1.0.0.0/
Default P2P Port: 44100
Default PRC Port: 44101
Message Start String: 0xd9 0xe6 0xe7 0xf5
-= Coin Information Checks =-
============================================================
Matching P2PPORT in init documentation: [OK]
Matching RPCPORT in init documentation: [OK]
Build & Client Version Match: [!!]
-= Library Version Compliance Checks =-
============================================================
Miniupnpc v1.9 (API 14): [OK]
OpenSSL v1.0.1k+ (Strict DER Signatures): [OK]
Boost v1.58+ (boost::get): [OK]
-= Security Standards Checks =-
============================================================
Free of IRC related files: [OK]
IRC based peer fetching: [--]
Contains signature malleability patch (PPCoin): [OK]
-= Connectivity Checks =-
============================================================
Contains unique ClientName: [OK]
Contains DNS seeder addresses: [OK]
Contains Hex-Encoded seeder addresses: [!!]
Has at least ONE default connection method: [OK]
Number of DNS Seeds: 1
Listing DNS Seed addresses...
* utcseed.presstab.pw
212.180.171.44 [!!]
198.27.82.163 [!!]
74.118.192.18 [OK]
-= OS Specific Checks =-
============================================================
Mac OS X Native Notification Support: [OK]
Mac OS X Deployment Script: [OK]
Mac OS X Application Icon: [OK]
Mac OS X Dock Icon Menu (Qt5): [OK]
Windows Installer Script: [**]
Windows Installer Header Image: [!!]
Windows Installer Logo Image: [!!]
Windows Installer Icon: [!!]
============================================================
* Windows installer script is using an incorrect name!
* Deployment build won't have the correct metadata!
* Windows installer sript is using an incorrect version!
* Deployment build won't have the correct metadata!
Results should be manually verified and you should NOT rely
on any automated scripts (including this one) before running
or compiling any crypto wallet.
============================================================
The UTC network could benefit from more active dedicated nodes. Presstab has done a good job at making sure the most relevant security updates have been applied (namely the OpenSSL and Signature Malleability issues). Though, without dedicated nodes to support incoming connections there is still a risk factor involved.
Thanks for this checkup Fuzzbawls.
I've reviewed a lot of your other coin checks and the new Ultracoin wallet compares very favourably. There are some shocking wallets out there.
The issues you note in CoinChecker are minor - PressTab may wish to comment further.
As for the nodes - yes we absolutely agree. More dedicated nodes will come online shortly.
Cheers - usukan
No problem,
The build/client version mismatch is a consistency issue, not a functional issue
The lack of any hex-encoded seed addresses would only present a problem if the nodes returned from presstab's DNS seeder all fail
And the windows installer issues obviously only matter if such a binary is being built
All the critical tests passed, which is the important thing to take away from this
I am not a giant fan of pnseeds. They are hardcoded ip addresses into the source code. I much prefer user a dns seed, where you can add/remove hard coded seeds on the dns side of things instead of the wallet source.
But pnseeds do have some benefits too. Connect a few seconds quick on your first try?
having a couple pnseed addresses available is (in my mind) useful as a failsafe or a fallback option. Back when coins were using IRC based peer fetching, many used pnseeds as a fallback if/when there was an issue with fetching addresses from IRC. Upstream, Bitcoin now primarily uses them as fallbacks for DNS resolution issues as there could be instances where DNS name resolution on a client machine is unsuccessful for whatever reason.
Indeed, DNS seeding is (and should continue to be) the primary and first method of fetching valid node addresses.
October 11, 2016, 09:02:53 AM
Code:
___ _ ___ _ _
/ __\___ (_)_ __ / __\ |__ ___ ___| | _____ _ __
/ / / _ \| | '_ \ / / | '_ \ / _ \/ __| |/ / _ \ '__|
/ /__| (_) | | | | / /___| | | | __/ (__| < __/ |
\____/\___/|_|_| |_\____/|_| |_|\___|\___|_|\_\___|_|
v0.0.4 October 2016 | http://www.fuzzbawls.pw
Checking Host OS... WIN
Creating temp folder to clone remote repository...
Cloning https://github.com/presstab/ultracoin-2.git...
-= Repository Information =-
============================================================
Number of commits: 229
Last commit date: Thu, Sep 29, 2016 9:46:36 AM
Days since last commit: 9.71 Days
-= Build System Information =-
============================================================
Build Type: QMAKE/Makefile
Build Version: 0.4.3.0
Qt Bin: ultracoin-qt
Daemon Bin: ultracoind
-= Coin Specifications =-
============================================================
Coin Name: ultracoin
Client Version: 1.0.0.0
Client Name: /Ultracoin:1.0.0.0/
Default P2P Port: 44100
Default PRC Port: 44101
Message Start String: 0xd9 0xe6 0xe7 0xf5
-= Coin Information Checks =-
============================================================
Matching P2PPORT in init documentation: [OK]
Matching RPCPORT in init documentation: [OK]
Build & Client Version Match: [!!]
-= Library Version Compliance Checks =-
============================================================
Miniupnpc v1.9 (API 14): [OK]
OpenSSL v1.0.1k+ (Strict DER Signatures): [OK]
Boost v1.58+ (boost::get): [OK]
-= Security Standards Checks =-
============================================================
Free of IRC related files: [OK]
IRC based peer fetching: [--]
Contains signature malleability patch (PPCoin): [OK]
-= Connectivity Checks =-
============================================================
Contains unique ClientName: [OK]
Contains DNS seeder addresses: [OK]
Contains Hex-Encoded seeder addresses: [!!]
Has at least ONE default connection method: [OK]
Number of DNS Seeds: 1
Listing DNS Seed addresses...
* utcseed.presstab.pw
212.180.171.44 [!!]
198.27.82.163 [!!]
74.118.192.18 [OK]
-= OS Specific Checks =-
============================================================
Mac OS X Native Notification Support: [OK]
Mac OS X Deployment Script: [OK]
Mac OS X Application Icon: [OK]
Mac OS X Dock Icon Menu (Qt5): [OK]
Windows Installer Script: [**]
Windows Installer Header Image: [!!]
Windows Installer Logo Image: [!!]
Windows Installer Icon: [!!]
============================================================
* Windows installer script is using an incorrect name!
* Deployment build won't have the correct metadata!
* Windows installer sript is using an incorrect version!
* Deployment build won't have the correct metadata!
Results should be manually verified and you should NOT rely
on any automated scripts (including this one) before running
or compiling any crypto wallet.
============================================================
/ __\___ (_)_ __ / __\ |__ ___ ___| | _____ _ __
/ / / _ \| | '_ \ / / | '_ \ / _ \/ __| |/ / _ \ '__|
/ /__| (_) | | | | / /___| | | | __/ (__| < __/ |
\____/\___/|_|_| |_\____/|_| |_|\___|\___|_|\_\___|_|
v0.0.4 October 2016 | http://www.fuzzbawls.pw
Checking Host OS... WIN
Creating temp folder to clone remote repository...
Cloning https://github.com/presstab/ultracoin-2.git...
-= Repository Information =-
============================================================
Number of commits: 229
Last commit date: Thu, Sep 29, 2016 9:46:36 AM
Days since last commit: 9.71 Days
-= Build System Information =-
============================================================
Build Type: QMAKE/Makefile
Build Version: 0.4.3.0
Qt Bin: ultracoin-qt
Daemon Bin: ultracoind
-= Coin Specifications =-
============================================================
Coin Name: ultracoin
Client Version: 1.0.0.0
Client Name: /Ultracoin:1.0.0.0/
Default P2P Port: 44100
Default PRC Port: 44101
Message Start String: 0xd9 0xe6 0xe7 0xf5
-= Coin Information Checks =-
============================================================
Matching P2PPORT in init documentation: [OK]
Matching RPCPORT in init documentation: [OK]
Build & Client Version Match: [!!]
-= Library Version Compliance Checks =-
============================================================
Miniupnpc v1.9 (API 14): [OK]
OpenSSL v1.0.1k+ (Strict DER Signatures): [OK]
Boost v1.58+ (boost::get): [OK]
-= Security Standards Checks =-
============================================================
Free of IRC related files: [OK]
IRC based peer fetching: [--]
Contains signature malleability patch (PPCoin): [OK]
-= Connectivity Checks =-
============================================================
Contains unique ClientName: [OK]
Contains DNS seeder addresses: [OK]
Contains Hex-Encoded seeder addresses: [!!]
Has at least ONE default connection method: [OK]
Number of DNS Seeds: 1
Listing DNS Seed addresses...
* utcseed.presstab.pw
212.180.171.44 [!!]
198.27.82.163 [!!]
74.118.192.18 [OK]
-= OS Specific Checks =-
============================================================
Mac OS X Native Notification Support: [OK]
Mac OS X Deployment Script: [OK]
Mac OS X Application Icon: [OK]
Mac OS X Dock Icon Menu (Qt5): [OK]
Windows Installer Script: [**]
Windows Installer Header Image: [!!]
Windows Installer Logo Image: [!!]
Windows Installer Icon: [!!]
============================================================
* Windows installer script is using an incorrect name!
* Deployment build won't have the correct metadata!
* Windows installer sript is using an incorrect version!
* Deployment build won't have the correct metadata!
Results should be manually verified and you should NOT rely
on any automated scripts (including this one) before running
or compiling any crypto wallet.
============================================================
The UTC network could benefit from more active dedicated nodes. Presstab has done a good job at making sure the most relevant security updates have been applied (namely the OpenSSL and Signature Malleability issues). Though, without dedicated nodes to support incoming connections there is still a risk factor involved.
Thanks for this checkup Fuzzbawls.
I've reviewed a lot of your other coin checks and the new Ultracoin wallet compares very favourably. There are some shocking wallets out there.
The issues you note in CoinChecker are minor - PressTab may wish to comment further.
As for the nodes - yes we absolutely agree. More dedicated nodes will come online shortly.
Cheers - usukan
No problem,
The build/client version mismatch is a consistency issue, not a functional issue
The lack of any hex-encoded seed addresses would only present a problem if the nodes returned from presstab's DNS seeder all fail
And the windows installer issues obviously only matter if such a binary is being built
All the critical tests passed, which is the important thing to take away from this
I am not a giant fan of pnseeds. They are hardcoded ip addresses into the source code. I much prefer user a dns seed, where you can add/remove hard coded seeds on the dns side of things instead of the wallet source.
But pnseeds do have some benefits too. Connect a few seconds quick on your first try?
October 11, 2016, 12:19:28 AM
anyone else stuck at block 1809901?? generated 6hrs ago
you are not stuck - you are actually synced all fine.
Seems the old wallet shot up the diff - and the miners are having a hard time gettings blocks cos so many shares required. It will improve since diff is dropping now - but it will take a while to churn out some number of new blocks and get diff back to normal.
Once we are past the fork block - the new wallet will not suffer this issue which has been plaguing UTC since Nov last year.
Its a pain because this slows down the fork (it will take longer to reach the fork block).
Sorry I'm travelling and will check back tomorrow.
Cheers - usukan
October 10, 2016, 09:06:23 PM
anyone else stuck at block 1809901?? generated 6hrs ago
October 10, 2016, 04:35:21 PM
Bittrex will delist on october 14 if UTC isnt averaging atleast 0.3 btc in volume daily until that time! Lets get some volume going guys 
October 10, 2016, 08:16:33 AM
Hi tbearhere,
Mine here: http://utc14.yacoin.club/
Valpe
Thx Valpe Mine here: http://utc14.yacoin.club/
Valpe
Are there any pools?.. or people just wallet mining until the fork? thx
Jump to: