Search content
Sort by

Showing 3 of 3 results by skyluis2000
Post
Topic
Board Announcements (Altcoins)
Topic OP
[ANN] [STRS] STRONGS Coin - kHeavyHash | PoW
by
skyluis2000
on 08/05/2025, 14:27:05 UTC
STRONGS


STRONGS [STRS] is a new cryptocurrency with a great future!
Also, an experienced marketer and trader will join our team after the launch of the project. Our cryptocurrency is based on kHeavyHash algorithm


Main Features

Name: STRONG$
Abbreviation: STR$
PoW algorithm: kHeavyHash
Maximum Coins: 180M
Premine: 100000 STR$ (To be used for rewards, adding to exchanges and promotions)
Block reward: 25 STR$ (50% to miners / 50% to masternodes)
Masternode Pledge: 7000 STR$
Average time to find a block: 50 seconds
Number of blocks to mature: 20
Calculation of difficulty: every 3 blocks

Mining will begin on May 8, 2025

For the first 100 blocks, the reward will be set at 1 STR$ to prevent instamining.

Wallet:

Windows: https://github.com/STRONG-chain/STRONG/releases/download/1.0.1/STRONGS.-v.1.0.1-Release-Win64.zip
Linux: https://github.com/STRONG-chain/STRONG/releases/download/1.0.1/STRONGS.-v.1.0.1-Release-Linux.tar.gz


Roadmap

May 8, 2025 - Start of mining
May 10, 2025 - Launch official pool with 1.5% commission and DDOS protection
May 10,  2025 - Launch of a website
June, 2025 - Exchanges (First Xeggex, Second NOKYC)



PUBLIC RELATIONS

Website: May 9, 2025





AWARDS.

Transfer: 200 STR$
Pools: 200 STR$ (For the first three pools).
Post
Topic
Board Mining (Altcoins)
Re: [ANN] lolMiner-mnx, Mining MinexCoin(MNX) New version: v0.31 (Mar 15)
by
skyluis2000
on 15/03/2018, 12:24:50 UTC
Time is running fast and coding never stops.

Although its only a small update, I would like to share lolMiner-mnx 0.31 with you

For those who do not want all the info whats new, here are just the download links:

Linux 64: Click me (v0.31)
Windows 64:   Click me (v0.31)

But why to download that without need? Well, this is new:

Fixed a bug in the Stratum Interface causing segfaults when receiving new jobs
This did not occur very often and most likely when the miner connected, but well - it happens from time to time and after some searching I found out why. But it seems I will have to do a new json interface for 0.4 - what fixes the segfault is rather a dirty fix and it only covers approx 80% of the possible reasons. Will try to come back with something better.

Introduced a new parameter "--optim"
This takes the two values OFF and STD (default). Setting the parameter to OFF will turn back some optimizations done for 0.3 that cause some lower end or older GPUs to run slower. So this kind of brings back the optimization level of 0.22 if you liked that more. Mid and high end cards will mine faster with this parameter not set (or the default STD), but also consume more energy. So the value OFF is also an option for those running into thermal problems.

If will extent the parameter in future for vendor specific optimizations. Lets see.

Introduced a new parameter "--use-compact-accept-msg"
This will replace the "Submitting Share / Share Accepted" message pair by * symbols attached to the 5 seconds statistics. This automatically activates --use-compact-short-stat, so we now have the following options for lolMiner-mnx to look like:

Default look--enable-time-print
Code:
[Device 0] Average speed (5s): 22714.3 sol/s
[Device 1] Average speed (5s): 22586.9 sol/s
Submitting share
Share accepted
[Device 0] Average speed (5s): 22544.1 sol/s
[Device 1] Average speed (5s): 22776.2 sol/s
Submitting share
Share accepted
Submitting share
Share accepted
Submitting share
Share accepted
[Device 0] Average speed (5s): 22045.2 sol/s
[Device 1] Average speed (5s): 22045 sol/s
Code:
12:15:12 [Device 0] Average speed (5s): 22660.5 sol/s
12:15:12 [Device 1] Average speed (5s): 22526.5 sol/s
Submitting share
Share accepted
12:15:17 [Device 0] Average speed (5s): 22494 sol/s
12:15:17 [Device 1] Average speed (5s): 22618.8 sol/s
Submitting share
Share accepted
12:15:22 [Device 0] Average speed (5s): 22020.2 sol/s
12:15:22 [Device 1] Average speed (5s): 22010.2 sol/s
Submitting share
Share accepted
12:15:27 [Device 0] Average speed (5s): 23222 sol/s
12:15:27 [Device 1] Average speed (5s): 23155.6 sol/s
--use-compact-short-stat--use-compact-short-stat --enable-time-print
Code:
Average speed (5s): 22643.7 sol/s | 22736.9 sol/s Total: 45380.5 sol/s
Submitting share
Share accepted
Average speed (5s): 22485.7 sol/s | 22536.9 sol/s Total: 45022.6 sol/s
Average speed (5s): 22606.5 sol/s | 22537.9 sol/s Total: 45144.4 sol/s
Submitting share
Share accepted
Submitting share
Share accepted
Average speed (5s): 22599.5 sol/s | 22529.1 sol/s Total: 45128.6 sol/s
Code:
12:21:43 Average speed (5s): 22705.1 sol/s | 22755 sol/s Total: 45460.1 sol/s
12:21:48 Average speed (5s): 22546.3 sol/s | 22667.3 sol/s Total: 45213.6 sol/s
Submitting share
Share accepted
12:21:53 Average speed (5s): 22578.1 sol/s | 22612.7 sol/s Total: 45190.8 sol/s
Submitting share
Share accepted
12:21:58 Average speed (5s): 22595.9 sol/s | 22635.1 sol/s Total: 45231 sol/s
Submitting share
Share accepted
--use-compact-accept-msg--use-compact-accept-msg --enable-time-print
Code:
Average speed (5s): 23167.9 sol/s | 23124 sol/s Total: 46291.9 sol/s **
Average speed (5s): 20888.2 sol/s | 22592.3 sol/s Total: 43480.5 sol/s
Average speed (5s): 20381.9 sol/s | 22738.9 sol/s Total: 43120.8 sol/s
Average speed (5s): 20863 sol/s | 22592.1 sol/s Total: 43455.1 sol/s
Average speed (5s): 20359.9 sol/s | 22602.3 sol/s Total: 42962.2 sol/s *
Code:
12:23:52 Average speed (5s): 21990.8 sol/s | 22753.8 sol/s Total: 44744.7 sol/s
12:23:57 Average speed (5s): 21497 sol/s | 22487.4 sol/s Total: 43984.4 sol/s *
12:24:02 Average speed (5s): 20862.4 sol/s | 23229.8 sol/s Total: 44092.2 sol/s
12:24:07 Average speed (5s): 20294.7 sol/s | 22661.5 sol/s Total: 42956.2 sol/s **
12:24:12 Average speed (5s): 20326.9 sol/s | 22620.1 sol/s Total: 42947 sol/s *

So, pick what you like most Cheesy
(Edit: you may see some speed differences between cards ... well the card 0 in this example running into heat problems rather soon and throttles - just that you know)



Hi, everybody!
The last days new version 0.3 works minutes 20-40 and speed falls on 0 sol and so indefinitely there is 0 sol 0sol......
How to fight against it also what to do?
The mine from 5 pieces 1060 3

Did you try the new --exit-on-zero parameter of 0.3? That should close the miner after at most two minutes after the first 0 sols was detected and the scripts provided with the miner (.bat file in Windows, .sh in Linux) should be able to restart it. Does this work for you? If you want a quicker restart you can set the long stats interval shorter.

Hello. I really liked this version 0.3 and I just tested this version 0.31 but just like version 0.3 the older video card is not timed and still slow. in version 0.22 it makes 1700 soles. in this new version is making 900 sol / s even with the new parameter --optim OFF / STD. continues reading for gtx560 2GB. thank you
Post
Topic
Board Mining (Altcoins)
Re: [ANN] lolMiner-mnx, Mining MinexCoin(MNX) New version: v0.3 (Mar 12)
by
skyluis2000
on 12/03/2018, 18:37:12 UTC
Hi folks,

well it took some time for me, but finally it is there: lolMiner-mnx 0.3 Cheesy
And its the first month birthday of the miner as well - time to party  Grin

As usual here are the download links:

Linux 64: Click me (v0.3)
Windows 64:  Click me (v0.3)

It will take a bit to describe what is new, so lets start.

Introduced a complete new Stratum Interface

As you may know the stratum interface of 0.22 was very buggy and caused serious problems on connection losses as well to the user as to the dev fee pool. Therefore 0.3 now has a complete new Stratum interface that should handle the situation much more gracefully and stable.

That said the new interface also comes with a new feature: fail-over support. You now can pass comma separated lists  to --server, --port, --user and --pass. The miner will try to connect to the first server in the list with the first credentials. Once there are too many reconnection attempts for this first connection the miner will go to the next pool in list with the 2nd user name and so on.
With --max-connection-attempts you can define how many connection attempts to be used before the miner switches over to the next pool & credentials in list. The default is 5.

This new stuff also applies for the dev fee connection. To bring this down the current three biggest pools have to be down simultaneously. Moreover the dev fee connection will try to use the same pool as the user for the fee, so the miner does no longer damage the balance of the pools by sending all shares to one pool. If this is not possible, it will do a round robin through all pools in the integrated list.

Even if the fee is completely blocked the miner will now continue to work, but slower then usual, because it will pause in between for reconnection attempts. The performance loss is approximately 5-10% depending on card and settings, but it will continue to work.

Improvement of the OpenCL code

As for the OpenCL code I did some performance improvements, that help hiding the memory latency (by almost 40%). This results the following performance table. I only listed the devices available for testing.

Nvidia

lolMiner-mnx 0.22 lolMiner-mnx 0.3
GTX 970 unknown 10.2k sol/s
GTX 1060 9.9 - 10.1k sol/s 10.8-11.1k sol/s
GTX 1070ti 15.2k sol/s 17.5k sol/s
GTX 1080 FE 13.4k sol/s 17.1k sol/s
GTX1080 Ti 19.5k sol/s 22.5k sol/s

AMD

lolMiner-mnx 0.22 lolMiner-mnx 0.3
RX 570 8GB 6.9k sol/s 8.9k sol/s
RX 580 4GB 7.4k sol/s 9.1k sol/s
RX 580 8GB 7.6k sol/s 9.8k sol/s
RX 580 4GB 9.9k sol/s 10.3k sol/s
with Mining BIOS 
Vega 64 16k sol/s ~19k sol/s (to be confirmed)

All of the above numbers were generated with the Linux version of the miner with current amdgpu-pro or cuda drivers.

Note that the performance of AMD cards may be limited in Windows, see the commends to –set-work-batch below.

Beside this I added some new comfort features & changes:

--platform and –device
The platform parameter now understand the keyword AUTO, which is also default. This one will select the platform with the most graphic cards automatically. If there are two with the same number, e.g. and Intel integrated GPU and one AMD / Nvidia graphic card it will prefer the non-Intel platform.

Device now detects two special values ALL and ALLGPU (default), that will select all devices or all graphic cards in the selected platform. Note then when using --device ALL on a processor with integrated graphics the miner will mine as well on the integrated graphics and on the CPU part. For most configurations this is not recommended.

--set-work-batch
There are now three special values 2G, AUTO and HIGH. When the work batch is set to 2G the miner is allowed to use 2 gigabytes of graphic memory at most. At level AUTO it will use at most 60% of the graphic cards memory and at level HIGH 90%. Note that AUTO and HIGH operate on per-GPU level, so mixing graphic cards with different memory sizes is no problem.

For Windows and AMD graphic cards there currently is a problem with lolMiner-mnx and the driver preventing that the miner works with more then 2 gigabytes of memory. Therefore the default for the Windows version is 2G, while the default for the Linux version is AUTO. This causes lolMiner-mnx 0.3 to be slightly faster on Linux compared to Windows when using AMD graphic cards.

The restriction does not apply for Nvidia graphic cards. For this GPU it should be save to use AUTO on any operation system.

New parameter: --use-compact-short-stat

This parameter will make lolMiner-mnx to print the short statistics in a similar style as the long statistics but without the surrounding dashed lines. Therefore one single line will be used for all devices instead of one line per device.

New parameter:  --exit-on-zero

This parameter will cause lolMiner-mnx to check the speed of each device when printing out the long statistics. If an device is detected with 0 sol/s (thus it was idle on the long statistics intervall) the miner will quit, so it can be restarted from a watchdog script.

With all those changes I still may announce that working configuration files from 0.22 can be used with 0.3 and should work as before. But to use the new features you may like to modify it  Wink

Beside the new comfort work I also tried to hunt down the memory access crashed and the reasons for reported 0 sol/s. This said it is natural that I may have overseen a problem, but it should be better now. If not please report.

That said there are two more smaller changes:
1. The dev fee is now reduced to 1.5%  Smiley
2. There is a new readme in .pdf file format shipped with the miner. This is now much closer to a real manual and should help to configure the miner Wink


Bugs is a good keyword.
The fee collector collected slightly over 72 MNX for my early testers. That said I decided to round it up to 75 to make is a smooth number - or just because I have a good day  Grin
But still I do not have all addresses yet, so here a remember to the following people still missing - Remember you have time until this Friday, 12:00 UTC  to claim your part (!)

From bitcointalk forum:
Code:
AAile
Anon11073
Atomsprengkopf
BtcBlack
ExEric3
gaissa
goedi
HarleyQuinn2011
Inves
Kompik
mikebzh44
Monayman
NameTaken
ol92
salshicha
Sebahl
Syth
TheG
Wa4A
YoloMolo
yurez83

From telegram:
Code:
crodair
Racquemis
Reagan
Valery

Beside this I will do one more announcement. Unfortunately I am not good enough in doing batch programming for a cool Watchdog, so I will put up an contest for that during next week. More details will follow.




GTX970 4GB  6.8>7 KSOL/ V0.3  10KSOL