Topic: [UFO] CORE 0.18.0 RELEASED! - page 20. (Read 115206 times)

v0.9.0 and 0.10.0 connects to the world but i cannot do solo mining anymore with v0.10.0

UFO Core 0.10 is working fine. Will update all links tomorow, folks.

is there even working wallet lol ? non of wallets i downloaded seems to connect to server

mm weird i got this:

http://users.skynet.be/xixou/ufo_10.png


edit: I had to remove this line from my config file:

rpcallowip=localhost

re edit:
I'm not sure how to solo mine now that i removed the localhost.

Is there a fix local ip address i can use instead?

C:\mining\miners\ccminer>ccminer-x64.exe -a neoscrypt -o http://localhost:30200/  -u ufocoinrpc -p ..
ccminer 8.14-KlausT (64bit) for nVidia GPUs
Compiled with Visual Studio 2015 using Nvidia CUDA Toolkit 8.0

Based on pooler cpuminer 2.3.2 and the tpruvot@github fork
CUDA support by Christian Buchner, Christian H. and DJM34
Includes optimizations implemented by sp-hash, klaust, tpruvot and tsiv.

[2017-11-29 19:15:00] NVML GPU monitoring enabled.
[2017-11-29 19:15:00] 5 miner threads started, using 'neoscrypt' algorithm.
[2017-11-29 19:15:00] JSON-RPC call failed: Method not found
[2017-11-29 19:15:00] json_rpc_call failed, retry after 10 seconds
[2017-11-29 19:15:10] JSON-RPC call failed: Method not found
[2017-11-29 19:15:10] json_rpc_call failed, retry after 10 seconds

re re edit:

rpcallowip=192.168.1.1
rpcport=30200

Not working either:
C:\mining\miners\ccminer>ccminer-x64.exe -a neoscrypt -o http://192.168.1.1:30200/  -u ufocoinrpc -p ..
ccminer 8.14-KlausT (64bit) for nVidia GPUs
Compiled with Visual Studio 2015 using Nvidia CUDA Toolkit 8.0

Based on pooler cpuminer 2.3.2 and the tpruvot@github fork
CUDA support by Christian Buchner, Christian H. and DJM34
Includes optimizations implemented by sp-hash, klaust, tpruvot and tsiv.

[2017-11-29 19:18:41] NVML GPU monitoring enabled.
[2017-11-29 19:18:41] 5 miner threads started, using 'neoscrypt' algorithm.
[2017-11-29 19:19:02] HTTP request failed: Failed to connect to 192.168.1.1 port 30200: Timed out
[2017-11-29 19:19:02] json_rpc_call failed, retry after 10 seconds
[2017-11-29 19:19:33] HTTP request failed: Failed to connect to 192.168.1.1 port 30200: Timed out
[2017-11-29 19:19:33] json_rpc_call failed, retry after 10 seconds

UFO coin wallet 0.10.0 version released
Please check: https://github.com/Bushstar/UFO-Project/releases/tag/v0.10.0.0

?

Sub-version   Protocol   Count   Network Share
/Satoshi:0.9.0/   node list   70000   42   87.5 %   87.5 %
/Satoshi:0.8.8.1/   node list   60005   3   6.3 %   93.8 %
/Satoshi:0.10.0/   node list   70005   2   4.2 %   97.9 %
/Satoshi:0.8.8.3/   node list   60006   1   2.1 %   100.0 %

/Satoshi:0.10.0/exist

Almost December, no miner/wallet update yet?

what about hashrate? Neoscrypt likes to take my 4343 Mб VRAM but gtx1060 could get at 900 kH/s and 918 is you overclock memory to hell. Gygabite have put me Samsung one so I can do 9400 MHz (+695)

I have also been using altminer with pretty consistent payouts on my little old 750 ti

  seems the 200+ diff issue still going on as yesterday altminer.net haven't paid me any shares for the whole 6 hrs while I was away. Now it's diff 0.978 and it finds new blocks relatively fast

If by 'attacks' you mean someone has used some 10 GH/s Nicehash order on it that happens a lot with Neoscrypt coins... but maybe it's a good part in it as the price would go back to 4 sat like a week ago

Hy,

i use the stratum from yiimp and the frontend is based on yiimp with modifications.

UFO is a small coin and there is not a massive amount of mining power, we will change that but these things take time, updating to the latest Bitcoin and commissioning additional services are what we can do to get UFO noticed.

About the stalling blockchain, what's classic is the miners leaving when the difficulty is high, what's not classic is the unusual and broken difficulty adjust in UFO which allows the difficulty to jump too quickly too soon, miners leave and the chain gets stuck. There's another situation where you end up with low difficulty and the chain gets stuck, I'll explain with some background, there are numerous 51% attacks on smaller coins, even devastating for some like HTMLCOIN which is launching a new coin to compensate exchanges as the loss has been so great (I've built the replacement coin for them which is based on Qtum), to prevent this we employ automatic checkpointing to prevent the chain being rolled back, with low difficulty you can end up with lots of long competing chains and sometimes it is not the longest one that gets checkpointed, those clients latched on to the longer uncheckpointed chain have to wait for the shorter chain to become the longer chain.

Both these issues are understood and will be solved with the hard fork in 0.10 to change the difficulty adjust. We would have had 0.10 out a month ago as planned but the NeoScrypt miner had to be updated which it now has been, we only need to now wait on new binaries. We can expect 0.10 out next week and the fork four weeks later, we need to wait that long to ensure that the majority of people have updated so as few people as possible are left on the old chain.


Pools can be a lot of hard work to get running. My only experience with pools is MPOS + stratum-mining. What pool software are you using and are you using a NeoScrypt module for hashing?

classic situation? really.. dont think so.. last generation was 14 hours ago.. network hash is down... there is no "strong" mining on this coin...

Hy,

my pool have problem to make new blocks. all REJECTED:


In Logfiles if found this :

i use: UFO Client 0.9.0.

Do i miss some options in the conf file?