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

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!

Your numbers for the last 4 days look OK. Before that something was clearly wrong, though, as a stale rate of 1% is already abnormal.

Total newbie to cryptomining, can you advise if these stale and invalid shares look normal?
I am using three L3+ miners, obvious form the data I have added them over the last month.  Not overclocked.  Thanks!

Date (UTC)   Average speed   Valid shares   Stale shares   Invalid shares   Rewards
2019-01-08   1,501,243 kH/s   1,475,854,336   4,866,048 (0.33%)   1 (0.00%)   0.0951577745096704 LTC
2019-01-07   1,505,799 kH/s   1,979,219,968   5,963,776 (0.30%)   1 (0.00%)   0.1276129783447552 LTC
2019-01-06   1,505,811 kH/s   1,979,269,120   5,931,008 (0.30%)   4 (0.00%)   0.1276161474887680 LTC
2019-01-05   1,514,262 kH/s   1,990,328,320   6,012,928 (0.30%)   5 (0.00%)   0.1319126392963072 LTC
2019-01-04   1,436,857 kH/s   1,762,910,208   131,383,296 (6.94%)   160 (0.00%)   0.1169387702452224 LTC
2019-01-03   1,503,127 kH/s   1,818,951,680   162,709,504 (8.21%)   153 (0.00%)   0.1206561579991040 LTC
2019-01-02   1,156,932 kH/s   1,497,186,304   28,065,792 (1.84%)   68 (0.00%)   0.1005728575029248 LTC
2019-01-01   1,006,235 kH/s   1,322,221,568   4,358,144 (0.33%)   0 (0.00%)   0.0899599888220160 LTC
2018-12-31   1,008,261 kH/s   1,325,236,224   4,014,080 (0.30%)   1 (0.00%)   0.0901650969722880 LTC
2018-12-30   1,011,877 kH/s   1,331,363,840   2,654,208 (0.20%)   0 (0.00%)   0.0903121466179584 LTC
2018-12-29   317,114 kH/s   416,727,040   1,343,488 (0.32%)   0 (0.00%)   0.0278011526922240 LTC
2018-12-28   0 kH/s   0   0 (0.00%)   0 (0.00%)   0.0000000000000000 LTC
2018-12-27   787,001 kH/s   974,757,888   62,791,680 (6.05%)   135 (0.00%)   0.0650291204579328 LTC
2018-12-26   1,008,360 kH/s   1,244,495,872   84,885,504 (6.39%)   86 (0.00%)   0.0826720201670656 LTC
2018-12-25   988,874 kH/s   1,220,313,088   83,378,176 (6.40%)   87 (0.00%)   0.0808151122214912 LTC
2018-12-24   995,100 kH/s   1,223,245,824   88,653,824 (6.76%)   88 (0.00%)   0.0810093323698176 LTC
2018-12-23   494,344 kH/s   562,331,648   89,391,104 (13.72%)   112 (0.00%)   0.0375641704890368 LTC
2018-12-22   499,942 kH/s   604,962,816   54,140,928 (8.21%)   50 (0.00%)   0.0457194598563840 LTC
2018-12-21   510,326 kH/s   627,523,584   45,268,992 (6.73%)   37 (0.00%)   0.0474244673372160 LTC
2018-12-20   500,241 kH/s   615,079,936   44,417,024 (6.73%)   22 (0.00%)   0.0464840510832640 LTC
2018-12-19   501,676 kH/s   583,974,912   77,414,400 (11.70%)   81 (0.00%)   0.0413218660073472 LTC
2018-12-18   506,374 kH/s   595,099,648   72,482,816 (10.86%)   69 (0.00%)   0.0420745567830016 LTC
2018-12-17   496,643 kH/s   580,239,360   74,514,432 (11.38%)   89 (0.00%)   0.0410239091589120 LTC
2018-12-16   496,456 kH/s   576,831,488   77,676,544 (11.87%)   77 (0.00%)   0.0409224015036416 LTC
2018-12-15   500,328 kH/s   655,998,976   3,612,672 (0.55%)   10 (0.00%)   0.0470132162134016 LTC
2018-12-14   499,849 kH/s   657,915,904   1,064,960 (0.16%)   0 (0.00%)   0.0471505959256064 LTC
2018-12-13   492,331 kH/s   647,954,432   1,114,112 (0.17%)   0 (0.00%)   0.0464366910963712 LTC
2018-12-12   487,944 kH/s   641,843,200   1,441,792 (0.22%)   0 (0.00%)   0.0435527324303360 LTC
2018-12-11   502,745 kH/s   661,618,688   1,179,648 (0.18%)   0 (0.00%)   0.0442286799978496 LTC

saludos soy nuevo aca

quiero ayuda si esta en sus manos
tengo 12 computadras y quiero ponerlas a minar ltc de donde descargo el programa y que me recomiendan hacer

Greetings!

A major new release for Myriadcoin:

https://www.reddit.com/r/myriadcoin/comments/a1u0yc/myriadcoin_01630/

Mining pool feedback is most welcome. In the event that you wish to remain on v0.14, a optional but recommended update is available:

https://www.reddit.com/r/myriadcoin/comments/9x0xxb/myriadcoin_01441/

Thanks for your support!

Not that I know of. Besides, these could very well be solo miners.

I noticed that there are some pools that are not small, but are not labeled in the hashrate distribution chart. Is there any way to discover what these pools are?

Greetings!

A major new release is planned for Myriadcoin:

https://www.reddit.com/r/myriadcoin/comments/9xasno/myriadcoin_01630rc0/

Mining pool feedback is most welcome. In the event that you wish to remain on v0.14, a optional but recommended update is available:

https://www.reddit.com/r/myriadcoin/comments/9x0xxb/myriadcoin_01441/

Thanks for your support!