Topic: [ANN] The First Litecoin PPS Pool (litecoinpool.org) - page 13. (Read 227557 times)

If the speed reported by the pool is consistently lower than what it should be, it means that the miners are submitting fewer shares than they should be. Since the speed reported locally is as expected, my guess would be that the miners are running into HW errors, i.e., some hashes are computed incorrectly and result in invalid shares. You may not see them reported by the pool because most ASIC controllers check for bad hashes before submitting to the server, and discard them. The most common causes of HW errors are an insufficient power supply, overclocking, firmware bugs triggered by special network conditions, and of course actual hardware defects in the hashing circuitry. Did the 4 hash rates drop all at the same time? Does resetting the miners help? Maybe write an email to support including your username, so that we can have a look at the account.

Hi,

We've recently started testing some mining equipment and have 1 x AntMiner L3+ and 3 x BW L21 setup.

Initially they performed as specified but around March 21st we noticed a drop in hashrate as reported by the pool. The L3+ dropped to around 350mh/s and the L21's to somewhere between 450mh/s and 210mh/s.

Temperature is fine and the units themselves are reporting running at full speed - so around 500mh/s for the L3+ and 550mh/s for L21's (give and take a little).

Does anybody have any hints or clues as to what could cause this ?

Thx

/K

Dear my Friends,

many Thanks for your best idea !

Regards

Hello Group !

What are the best Asic LTC miner 2019?

Thanks for your help
[/quote]

From what I understand IF you have real low (less than probably 8c kWh electric data hall rates) ...unsure how much lower...my friend with a data hall is making 40c a day on

L3+'s..that go for (or so I've seen) $80 without PSU now IF you pick them up (not counting shipping)

so that is like $12.00 a month after electric costs he says  or a 6.67 month ROI at FLAT difficulty (which does not exist)

So unless you already have one and need an electric space heater, or have free electric in a dorm or something,  you are SHOL.

Sorry to say. (I have some shut off)

So at this point in time you are better off just buying LTC and go into HODL mode, and hope for a pump. Because it is the same plan with equipment you need

price pump in order to mine LTC these days...and all things being the same, safer bet is to just HODL your LTC and get more and just eliminate the whole miner

risk at this point in time.

IMHO anyway

brad


[/quote]

From what I understand IF you have real low (less than probably 8c kWh electric data hall rates) ...unsure how much lower...my friend with a data hall is making 40c a day on

L3+'s..that go for (or so I've seen) $80 without PSU now IF you pick them up (not counting shipping)

so that is like $12.00 a month after electric costs he says  or a 6.67 month ROI at FLAT difficulty (which does not exist)

So unless you already have one and need an electric space heater, or have free electric in a dorm or something,  you are SHOL.

Sorry to say. (I have some shut off)

So at this point in time you are better off just buying LTC and go into HODL mode, and hope for a pump. Because it is the same plan with equipment you need

price pump in order to mine LTC these days...and all things being the same, safer bet is to just HODL your LTC and get more and just eliminate the whole miner

risk at this point in time.

IMHO anyway

brad

Hello Group !

What are the best Asic LTC miner 2019?

Thanks for your help

Working with this information
https://en.bitcoin.it/wiki/Stratum_mining_protocol

Ok, I made another subscribe call to the server with the extraNonceOne that the subscribe result gave me and now new things started happening. looks like I'm getting 'mining.notify' socket messages now but the messages are coming in super fast, not sure if this is normal or if my configuration is bad

I'm developing a stratum client for litecoin research purposes but I can't seem to get jobs from the server. the only response that my client gets is the subscribe result and occasionally the set difficutly response, no job "mining.notify". Wondering if I messed up or am configuring something wrong, I seem to be authenticating correctly but  I'm not sure if I'm handling the subscription correctly.

I cannot find these transactions anywhere in the mempool or on block explorers, so if you want help you will probably need to provide the full transactions, not just the IDs. Feel free to send an email to support.

Looks like we just dropped to 102% PPS.... Ouch!

I made a rookie mistake with sending litecoin to an exchange with low fees. Can a litecoin miner please help me out? Trx IDs:

1.d30b57cfef7b31ccc78a67c456dde987afefa2b681e05aed70de1011d49809dd

2.428963a144d15ac5c85cfa72937cc95e87d01559a3d872c0bd5194227253e6c2

Transactions have been stuck for weeks now, willing to pay to get them confirmed.

Thanks!!

Greetings!

A Required Update for Myriadcoin has been released:

https://www.reddit.com/r/myriadcoin/comments/asv1ph/myriadcoin_01640/

Please note, this release plans a BIP9 consensus fork that will disallow skein blocks and allow argon2d4096 blocks.

Noted that litecoinpool.org has already updated, thanks for your prompt attention.

Thanks for your support!

BFGMiner Version 5.5.0 - January 3, 2019

  "( silly question, Need help setting up a .bat file to run...) ty"

- Update official Win32/64 build compiler and libraries:
- - Win64 compiler (GCC) from 5.3.0 to 7.2.0 (Win32 remains at 4.7.4)
- - c-ares from 1.10.0-r1 to 1.11.0
- - libjansson from 2.7 to 2.10
- - libcurl from 7.47.1 to 7.57.0
- - libevent from 2.1.5-r4 to 2.1.8
- - libusb from 1.0.20 to 1.0.21
- - libmicrohttpd from 0.9.48 to 0.9.58
- - zlib from 1.2.8-r1 to 1.2.11-r1
- Update copyrights
- AUTHORS: Update
- README.ASIC: Update Alcheminer
- alchemist: Reset using DTR as well
- alchemist: Experimental USB->UART Dongle Support on RPi
- make-release: Add crypt32.dll to OS-provided library list
- README: Expand on --set-device documentation
- Update libblkmaker to 0.6.0
- openwrt: Update for LEDE 17.01
- ccan: Update to latest version (which fixes musl libc support)
- Bugfix: probe_device_thread: Fix threadname buffer size
- Bugfix: appdata_file_call: Fix buffer size and loop
- Bugfix: SSM: Clear desired_default_share_pdiff when initialising
desired_share_pdiff before authentication
- cpu: Avoid relocations for x86_64 assembly that interfere with building
BFGMiner as a PIE
- Bugfix: SSM: We already hold the pool lock when we need to call stale_work,
so avoid trying to lock it a second time inside the function
- Bugfix: Hold the control lock when updating the generate-to script
- Bugfix: Hold the pool lock when updating lp_id
- Bugfix: icarus: Explicitly specify type wide enough for bitshift in
icarus_proc_for_nonce
- configure: BFG_FIND_INCLUDE_PATH: Handle more unusual syntax correctly
- Bugfix: SSM: Handle network problems safely, and use thread-safe libevent


BFGMiner Version 5.4.2 - March 26, 2016

- Update official Win32/64 build compiler and libraries:
- - Win64 compiler (GCC) from 4.7.4 to 5.3.0 (Win32 remains at 4.7.4)
- - libcurl from 7.39.0 to 7.47.1
- - libevent from 2.0.21 to 2.1.5-r4
- - libusb from 1.0.18 (Win32) and 1.0.19 (Win64) to 1.0.20
- - libmicrohttpd from 0.9.38_pre33603 to 0.9.48
- Update libblkmaker to 0.5.3
- Bugfix: Sanitise lock situation for work2d
- Bugfix: SSM: Never issue the same work2d twice in a row
- Bugfix: SSM: Never send mining.notify for stale work2d
- SSM: Refactor work2d check and job pruning from _stratumsrv_update_notify
into stratumsrv_update_notify_str
- Updates for OpenWrt 15.05
- Bugfix: Correct work2d handling for GBT servers


BFGMiner Version 5.4.1 - November 21, 2015

- bitmain: Use more portable PRIu64 rather than %llu (which fails on Windows)
- icarus: Use more portable PRIu64 rather than %llu (which fails on Windows)
- Bugfix: openwrt: Fix bitmain option
- Bugfix: antminer: Avoid strstr(NULL, ...) when device has no [available]
product string
- Update libblkmaker to 0.5.2
- openwrt: Add option to enable bitmain driver
- openwrt: Update libusb device list


BFGMiner Version 5.4.0 - October 23, 2015

- AUTHORS: Move jstefanop to current maintainers
- Disable alchemist by default, add Travis build, and document configure option
in README
- alchemist: New scrypt ASIC driver
- hashfast: Support setting clock speed from TUI Manage
- avalon: Support setting clock speed from TUI Manage
- antminer: Support setting clock speed from TUI Manage (hidden for non-BM1382/4
devices)
- jingtian: Allow changing clock speed from TUI
- Debuglog for retrodiff being disabled
- Disable retrodiff when it was not explicitly enabled, and the pool doesn't
seem to like it
- Bugfix: Only adjust work_difficulty on retrodiff submissions, so we can still
detect them on rejection
- (Re-)enable retrodiff by default for stratum pools, since some servers
implement mining.set_difficulty wrong in this way
- New pool option "retrodiff"
- If a share passes difficulty check for the updated pool target,   record that
target for correct accounting of diff_stale.
- DevAPI: Remove unused temporary variable from driver iteration
- README.ASIC: Expand Antminer S5 section to S1-S5 for completeness, since in
theory they should work
- bitmain: Make reg_data optional for S4 and S5, calculating it from clock
- Document Bitmain Antminer S5 support
- bitmain: Remove poll_prio_threshold and just ensure we poll at a regular
interval to avoid nonce buffer overruns
- bitmain: Remove dead per-device constants
- bitmain: Only have one set of actual maximums
- bitmain: Migrate BITMAIN_MAX_NONCE_NUM to runtime packet_max_nonce
- bitmain: Migrate BITMAIN_MAX_WORK_QUEUE_NUM/bitmain_work_poll_prio to runtime
poll_prio_threshold
- bitmain: Migrate BITMAIN_MAX_WORK_NUM to runtime packet_max_work
- bitmain: Dummy model parameter
- bitmain: Remove baud/flush, as the fake VCOM kernel driver ignores (and
complains about) both
- bitmain: Poll after queuing work, once enough is queued
- bitmain: Sleep a little between polling
- bitmain: Flush queues for work restarts
- bitmain: Queue multiple works at a time
- bitmain: Remove more dead code
- bitmain: Prune old work eventually
- Bugfix: bitmain: Properly count work-search failures as HW errors
- bitmain: Refactor to work with minerloop_queue (leaks work memory)
- bitmain: Avoid busy-looping on network devices
- bitmain: Support for talking to a device over the network
- bitmain: Use the hottest reading for device temperature
- Bugfix: bitmain: Actually use baud setting
- bitmain: Remove more dead code
- bitmain: Handle stale results normally
- bitmain: Simplify num2bit
- bitmain: Initial set-device based configuration
- bitmain: Use lowl-vcom abstractions
- Update copyrights
- Bugfix: bitmain: Type-safe printf-format usage
- Travis: Test bitmain-only build
- Build bitmain driver
- bitmain: Hardcode configuration for now
- bitmain: Rework nonce_diff handling
- bitmain: Update headers
- bitmain: Deal with unused variable warnings sanely
- bitmain: Explicitly de-const device_path for freeing
- Bugfix: bitmain: Correct type of cgpu->temp reference
- Bugfix: bitmain: Use uint8_t consistently for binary data
- Bugfix: bitmain: Clear opt_bitmain_dev string properly
- bitmain: Remove non-existent bitmain_detect parameter
- bitmain: Cleanup unnecessary code
- bitmain: Use uthash to find queued work
- bitmain: Implement inc_dev_status within record_temp_fan
- bitmain: Remove non-applicable limits
- bitmain: Remove obsolete get_statline_before function
- bitmain: Move g_miner_version to bitmain_info struct
- bitmain: Remove direct USB code
- bitmain: Update driver registration
- bitmain: Update symbol names
- bitmain: Remove dead code
- bitmain: Replace custom hexdump with normal bin2hex
- bitmain: Get network difficulty from first work task
- bitmain: No-op htole8
- bitmain: Simulate cgminer work_block somewhat
- bitmain: Update bin2hex usage for malloc-free version
- bitmain: Copy low-level code from Bitmain cgminer usbutils
- Copy working driver-bitmain.c from Bitmain's cgminer at commit
4ecf89341657ea7efecdf588586ca3f068ab17ab
- Add api_add_percent to miner.h
- Bugfix: DevAPI: Update includes from uthash to utlist and support older
versions of uthash
- Bugfix: RPC: Need to include utlist.h for config file list
- Bugfix: antminer: Avoid NULL dereference for non-BM1382/4 devices
- README.ASIC: Update documentation for BM1382/4 clock calculation support
- antminer: Support for setting BM1382/4 clock by frequency MHz
- Bugfix: Keep JSON from getaccountaddress around long enough for debug messages
- Bugfix: Run gen-version.sh from source directory
- Fix to enable building into directory out of source tree
- Bugfix: Clean up JSON from getaccountaddress
- Bugfix: Do not use hash tables for driver lists, since they require unique
keys
- Pool option #cksuggest to use CKPool-compatible mining.suggest_difficulty
- RPC: Add "Rotate Period" to config
- RPC: Extend setconfig to change strategy
- Allow setting strategy by name
- bitforce: Enable changing voltage from the Manage TUI
- avalonmm: Use proc_set_device_tui_wrapper instead of avalonmm_tui_wrapper
- DevAPI: Add generic proc_set_device_tui_wrapper
- bitforce: Add "voltage" setting to send V?X commands
- Bugfix: compac: Set dname so assignments match
- README.RPC: Add missing setconfig|stratum-port documentation
- README.RPC: Add missing setconfig|http-port documentation
- Bugfix: lowl-vcom: Check for tcgetattr/tcsetattr/tcflush failure
- configure: List compac driver in output
- Travis: Workaround Travis bug
- configure: Use AC_PROG_SED to find sed


BFGMiner Version 5.3.0 - September 5, 2015

- README.ASIC: Compac docs
- antminer: Explicit support for GekkoScience's Compac BM1384 Bitcoin Miner
- icarus: Use all null padding when probing work division (BM1384 reacts
strangely - using part as start nonce?)
- antminer: Match Product strings including "Antminer"
- Bugfix: icarus: Never set timeout to 0, since it disables the timeout
altogether


BFGMiner Version 5.2.0 - June 5, 2015

- Upgraded Windows hidapi library from 0.8.0_pre20130121 to 0.8.0_rc1_p20140719
- Update bundled libbase58 to 0.1.4
- README.ASIC: Document usage with AntMiner U3
- icarus: Include ns/hash estimates for each nonce result, in debug logging
- icarus: Cleanup dev vs proc repr in logging
- Bugfix: update_block_display: Ensure we have console lock, and avoid rare
relock when resizing windows inside curses_print_status
- gitmodules: Change libblkmaker URI to use GitHub since Gitorious is defunct
- Bugfix: DevAPI: Avoid infinite hang in set_device help
- bitforce: Wait until pre-initialisation jobs all flush completely before
starting to avoid sanity check issues
- bitforce: Wait to clear job queue (at init) until we have actually opened the
device
- bitforce: Remove unnecessary delay
- Bugfix: vcom: Avoid overflowing cc_t before division to deciseconds
- Bugfix: bitforce: Ensure hashes_done is called for every completed job
- antminer: Adapt default configuration to work with U3 as well as U1/U2
- antminer: Add U3 voltage setting (x??? format only for now)
- antminer: getstatus needs to read a result for every chip, but we don't use
the output anyway, so just skip it
- icarus: Modify work division detection packet to be compatible with Antminer
U3
- icarus: Replace decisecond-precision read_count with read_timeout_ms
(millisecond precision) to handle faster devices like the Antminer U3 that
complete works in under 1ds
- lowl-vcom: vcom_set_timeout_ms function (increases precision to ms on Windows
only)
- util: timer_remaining_us function
- configure: Improve path finding macro to work with more possible CPP output
- configure: Macroify header path search
- Reduce HTTP request failure log level to DEBUG since it often occurs probing
stratum pools
- Bugfix: DevAPI: Guarantee set_device functions never get passed a NULL pointer
for newvalue
- Always update block display after pool display in case of username wrapping
around
- icarus: Pass device representation to icarus_{gets,write} so logging can use
it rather than fd numbers
- Bugfix: icarus: Check for impossibly fast hw errors (and don't report Eh/s
when they occur)
- Bugfix: icarus: Avoid a race with watchdog applying settings by setting
device_data before add_cgpu
- RPC: Clean up api_add_* somewhat
- Bugfix: util: Fix is_power_of_two
- Port antminer driver to use set_device_funcs


BFGMiner Version 5.1.0 - February 19, 2015

- Fix broken driver options in configure script
- Bugfix: extract_domain: Correctly handle query/fragment in URI without path
- kncasic: Do flush!
- kncasic: avoid duplicate nonces to be reported
- kncasic: Fix logging levels
- kncasic: Neptune-compatible API interface for enabling/disabling dies
- kncasic: Use one bfgminer processor per die (not per core)
- Update libblkmaker to 0.5.1
- Titan: Lower log level when reconfiguring dies
- Titan: does not need SHA256d algo
- Titan: lower log level for flush messages
- Titan: adjust log levels in knc_titan_get_info
- get_master_rolling_hashrate -> get_proc_rolling_hashrate
- Update webconfig code to latest BFGMiner
- allow url based config files
- kncasic: Fix "double free" error
- kncasic: We need to free queued work to avoid memory leaks
- Bugfix: minion: Don't try to add 0-chip devices
- configure: Avoid BASHisms for better portability

This works, thanks!

You probably want to create a new worker (at the top of your "My Account" page), and connect your second miner using this new worker's username and password. That way the website will show separate statistics for the two miners.

I started my Litecoinpool account with a futurebit moonlander miner and have since added the Apollo miner to the mix.  I can see the Moonlander in my litecoinpool account page, but I can't see the Apollo there.  How do I set this up to combine the two into one view?

On the Apollo itself, I set it to share with my litecoinpool user name and password.  So, it seems like it should be working, but I can't see how the apollo is generating new litecoin anywhere.  What do I do?

Looks like we just dropped to 103% PPS

That does seem to be the likely scenario, were they producing the normal heat you would expect? Assuming you are running L3+'s, BM released a FW a couple of months ago to address "vulnerabilities" across all kinds of L3's. Are you running this updated FW? If not, its possible whatever vulnerability that got patched was exploited to change the credentials of your machines.

I lost access to my machines via ip. When I try to get with root/root login and pass, I cant get into the web UI. Also, the green light as they're mining is turned on. I don't see any hash rate on any of my workers on the pool? I had to get into it pressing the reset button and setting up every machine again....

Just to see your opinion, what could happen there? somebody hacked my machines?

Thank you!

Sending an email to support was enough, but of course I understand you're worried about the situation.

Thanks for the reply.  When you say 'something was clearly wrong' - what do you mean and how do I o about troubleshooting?  Thanks!