Topic: SEGWIT LTC.TBDICE.ORG 0.5% fee SOLO MM LTC/DGE POOL 3K+ LTC/7K+ DGE blks solved - page 24. (Read 42899 times)

Guy's,

A quick note about MutliSig addresses pool support
MutliSig addresses starting with 3 are properly supported.
Addresses beginning with “M” are not supported

So as a rule of thumb the best option is to use L-addresses - Legacy Litecoin accounts for user name.
Best
Loshia

There is a planned maintainance in server collocation  datacenter. It may interrupt pool operation during this period up to 35 mins. Make sure you have backup pools ready to take over
  
Planned Date: 04.09.2017
Maintenance window: 22:30 – 04:00 - UTC
Reason: Switching infrastructure upgrade
Task: Upgrading N7K-SUP1 to N7K-SUP2E
Expected Traffic interruption duration: up to 35 min.
Best
Loshia

We are back. Short network outage (20 mins) is resolved and block was found immediately  

Hello,
There are some routing issues in our datacenter. When i get more info i will let you know.
I hope they are going to fix them asap
Best
Loshia

Update:
I want to share some info about couple stale LTC Blocks found lately

[2017-07-30 12:00:04.852] Possible LTC block solve diff 25823388459.596317 > 25805017447.881905(25830848296.178082)!
[2017-07-30 12:00:04.854] SUBMIT LTC BLOCK RETURNED: high-hash

and

[2017-08-01 15:40:41.565] Possible LTC block solve diff 28688071358.062317 > 28666450307.025860(28695145452.478336)!
[2017-08-01 15:40:41.567] SUBMIT LTC BLOCK RETURNED: high-hash


By design, to avoid rounding errors pool submits a share as block solve when this share diff > 0.99% of Network diff just in case to avoid loosing a block due to possible math rounding errors.
That is what actually happened - Our last couple of STALE LTC blocks were not meeting actual network difficulty because of 0.99% safety rule. They were so close though.
When they were submitted, LTC deamon returned high hash as expected and they showed in pool stats as stale.

All is good and our LTC demons are well connected. And our luck rocks lately
Pool stats has it all and speaks instead of me.

Best
Loshia


  

Info about LTC Price index. As you know BTC-E has been having hard times recently. So Price index died also. I will wait i week or two to see if it will recover. That will not happen  most probably. So i am gonna implement other LTC price source.
Best
Loshia

A note for our fastest miner 300+GH at time of writing
When you increased you speed recently from 100 Gh/s to 300+Gh/s, your reject rate increased dramatically. I do not know if you are using rented hash or own equipment.
The 99% of rejects are due to share above target errors. In my opinion this is because of  rented hash dropping and reestablishing connections too frequently. Some rejects  are normal though.
When mining solo the only thing that matters is a share solving a block which will be accepted for sure  
The above rejects are not DECREASING your chance of finding a block and are HARMLESS
Pool stats are looking ugly, but it does not matter for me as long as i know the reason. Please contact me via PM if you want to discuss it.
Thanks
Best
Loshia

 

The downtime was about two hours i am really sorry...
Two things happend simultaniously
1. There were some network issues in datacenter. Pool was not restarted for months.... I checked everything and decided to update and reboot  the machine while datacentre network recovers...

2. The real issue popped up after reboot because poll starting diff was too low. Even though pool adjusts diff per worker due to the nature how stratum works because of too many rejects while fast ASIC miners start to submit work at higher diff they are dropped (forced to reconnect) by ckpoll because of potential flood which was not the case. That is the the way it must work. Unfortunately this situation was looping. It took me a while to realise what is really going on. So I INCREASED POOL START DIFF and all is back to normal
Once again sorry guys for downtime

After last restart we found a lucky  block (LTC+DOGE) almost immediately
MINE ON:)
Best
UP:
Last restart a minute ago to apply some fixes - all miners reconnected immediately without issues. No further restarts planned.

Guys,
There were some issues with datacenter. The outage was for about 20 mins. When i get more info about issues i will post back. Now pool hash is recovering ..
Best

R1-LTC (OWRT - probably many others having similar issue) - DOGE MM address + mail notifications fix


A big thanks to m1n3m1n3m1n3 providing his way for fixing the issue:

Easy route: downloaded Winscp > login as root > browse to /etc/inid.d/ > right click on cgminer and select edit

Example:

Original    POOL1="-o $_pool1url -O $_pool1user:$_pool1pw"

Changed to   POOL1="-o $_pool1url -u $_pool1user -p $_pool1pw"

Full changed pool section below from the cgminer file

if [ "$_pool1url" != "" -a "$_pool1user" != "" -a "$_pool1pw" != "" ]; then
       POOL1="-o $_pool1url -u $_pool1user -p $_pool1pw"
   fi
   if [ "$_pool2url" != "" -a "$_pool2user" != "" -a "$_pool2pw" != "" ]; then
       POOL2="-o $_pool2url -u $_pool2user -p $_pool2pw"
   fi
   if [ "$_pool3url" != "" -a "$_pool3user" != "" -a "$_pool3pw" != "" ]; then
       POOL3="-o $_pool3url -u $_pool3user -p $_pool3pw"
   fi

Hard route use putty to login into your miner and edit config file with vi(m)

Restart Miner - Hit save and apply on cgminer config page

Happy mining

R1-LTC - DOGE MM address issues and mail notification issues
Folks,

There are some issues with R1-LTC  miners and you are not able to provide proper password string so that pool can parse your MM address
The short term solution is you to watch pool doge blocks page. If you happen to hit Doge block, just let me know by PM or posting here. I will process your payout manually.
However i would appreciate if someone provides me Teamviewer  access to a PC so i can ssh to R1-LTC miner (meanwhile you are going to watch what i will do) and provide proper fix for all of you
Thank you very much
Best
Loshia - Pool OP

Hi,
Which one is red User or MM Addr? If it is MM Addr that means that you are not providing DOGE address to Merge mine DOGE coins. In order to do so and get DOGE also you will need to provide DOGE address inside your password as explained in pool home page. Otherwise you are going to mine LTC only. As long as you see your LTC address (some chars in the middle skipped to keep your privacy as long as possible) in users/workers page all is GOOD
Please post here or send me a PM with your config. Screen shot of web interface or ssh config whatever your L3+ has
Best
PS:
---------------
Also on average how many litecoin blocks will an L3+ solve a month?
--------------
Assuming 520 MH/s
Expected Time per Block   29 days 08 hours
Big Fat notes:
1. We are talking about PROBABILITY and  there is no guarantee. In other words at CURRENT networking diff you are expected to solve one block per month. You can solve 10 blocks (GOOD LUCK) per month or you can solve 0 blocks per month (even year BAD LUCK) also. No Guarantees. That is what PROBABILITY is.

https://www.litecoinpool.org/calc?hashrate=520&speedunit=MH%2Fs&difficulty=306983.06700834&price=41.7145¤cy=USD&power=1000&energycost=0.10
-------------------
 Is it worth trying?
-------------------
You are the one to decide....Math is Math (1=1 always) Luck is Luck. Imagine that you are buying ONE of two (The lottery has two tickets in total) lottery tickets available for a lottery. You have 50% chance winning the lotary right? Will it happen today, tomorrow or the day after tomorow ? Each time you have 50% chance it must happen someday for sure but when? Or you can win 10 times in a row That is LUCK
Good luck

I want to solo mine but it says pool in red when I connect my L3+ using my coinbase litecoin address as my worker. If not coinbase address what litecoin wallet address will work? Also on average how many litecoin blocks will an L3+ solve a month? Is it worth trying?

HI,
First of all it is not possible to find 7 LTC blocks for 48 hours with just 138Mhs .....
Now answering your question
1. The big misunderstanding is that many solo pools do exist. For me personally, solo pool means that NEW coins (when block is found) are generated directly to your address inside CB transaction.
2. Having in mind 1. there are only three REAL SOLO pools as far as i know:
   a) CK BTC pool - the original
   b) My pool TBDice
   c) Nice hash LTC (and probably other coins also - NiceHash only). I have just checked NiceHash CB LTC transactions for new blocks and all seems good
3. Assuming you are mining on niche hash LTC SOLO pool (OR ANY OTHER TRUE SOLO POOL) you can do:
https://chain.so/address/LTC/YOUR_LTC_ADRESS

For instance:
https://chain.so/address/LTC/LUNyycVonDH9aQMZn1fxyUeu8N3yS8w7ud - That is my pool address and you can see how page looks like.

The important part you are looking for is: Newly Generated Coins and it should say 24.xxx-25.xxx
That is the only relaialble way to check out what you have found. Again this is up to pool to include your LTC dress in CB genaration transaction

In your case some or both happened. !!Note these are presumptions only!!!
1. You miner software has buggy network diff implementation
2. You are mining some other script coin with lower network difficulty...Or your miner is connecting to other none LTC pool also for backup or balance or whatever...

All TBDice miners have the option to use mail notification for all miner events - New blocks, connects or disconnects for free

Good luck to you!
Best
Loshia

Hi,

It's possible to find out if an address (bitcoin or litecoin) has ever found a block? I have this curious issue where my 138mhs Innosilicon A4 claims to have found 7 blocks within 48 hours, but i was mining on nicehash regular pool, so cannot verify if it's true.

Hi,
Try x:DOGE_ADDRESS - put x: infort of your doge address. if it is not working again, please PM me both LTC and doge address. i will process all doge payouts manually.
Best
Loshia

Hi, I'm having the exact same problem. LTC address seems fine, DOGE address doesn't register, it says Pool. I tried the : at the start but it didn't help. I am using a AntRouter, R1-LTC

Please help!

Thanks

Maintainance completed as planned. Pool graph shows it took 10 to 15 minutes.
Best
Loshia

Hello,

There is a Planned  maintenance scheduled in server hosting data center

Planned Date: 16.05.2017
Maintenance window: 00:30 – 06:00 (UTC+2)
Reason: Switcing infrastructure upgrade
Affected Customers/Partners: All
Affected Services:  Internet and L2 services.
Expected Traffic interruption duration: up to 15 min.

Best
Loshia

Hello,

In short try setting your mining difficulty manually as explained in pool home page  
----------------------------
The pool supports difficulty setting inside your password. The format is: diff_xxxxxxx:(DOGE address), where xxxxxxx can be any positive integer value. For example s(bf)gminer -o stratum+tcp://tbdice.org:13333 -u LUNyycVonDH9aQMZn1fxyUeu8N3yS8w7ud.0 -p diff_2048:(your DOGE address) will start you mining at 2048.
--------------
In your case you MUST use 16 as diff setting or:
-p diff_16

What happens is that you are mining ok. But pool starting difficulty is a bit higher and you are not submitting shares because cpu mining is slow. And because you are not submitting anything pool is not able to adjust your difficulty and your miner (user) is not showing in pool stats page.

I do not want to discourage you but today LTC diff is making your chance almost 0 to find a block and get a reward for it. Same applies for other pools also. Unfortunately CPU mining these days can be used for educational perposes or as a lottery  But that is what is tbdice is all about. You can always try your luck  
Best
Loshia
Pool Admin
PS. You can always PM me your starting cpuminer line along with your LTC+DOGE address if you are not able to sort it out