Καλά εδώ δεν καταφέρνει αυτό το κράτος να πιάσει όσους φοροδιαφεύγουν με πειραγμένες ταμιακές, θα hackαρει μήπως το blockchain του monero για να βρει τους Έλληνες με αδήλωτα νομίσματα ή θα ελέγξει τις καταναλώσεις ρεύματος για να πιάσει τους miners;
Ακόμα και αν το 2025 εντάξουν τα κρυπτονομίσματα στη φορολογική δήλωση, αμφιβάλλω αν θα μπορέσει να ελεγχθεί από το κράτος... ότι θα δηλώνουμε αυτό θα ισχύει. Αρκεί να αυξηθούν τα καταστήματα (ηλεκτρονικά και μη) που δέχονται κρυπτονομίσματα για πληρωμές και έτσι δεν θα υπάρχει κάποια ανάγκη για μετατροπή σε ευρώ.

Thanks you. Hope for the best I am all in in this project. I have doubts about the gpu mining. I mining with cpu about 60 80 coins per day. Someone with gpu will mining 200 300 per day. So my coins will be useless because someone else will will be making much more coins in less days than mine that spend many days for the coins i have. I don't think a gpu mining is a good choice hope to stay cpu mining only coin.

As i stated earlier so i state it again you can count me in for anything in this regard let me know what to do and i'll make sure things follow in line

Since I use assembler it will take a lot of time to implement all these changes and I don't have enough time currently. I implemented pow7 but for other forks you should use other miners.

it is enough that we do not let the project die, we can join as the strong people we are, take over the project and launch a new version with decentralized seed nodes maintained by the community, we can create a new site and play the project forward, list on sites like Coinlib and etc, I came here to see if Crepcoin would change the Algorithm of difficulty to LMWA, we can do that guys, we set up a community on the telegram and maybe raise funds, digital coins are decentralized and do not depend on Devs.

1. No, and won't do it. Why ? As soon as i release it, people will remove devfee, and upload that version to the forum and everywhere else. If that happens, i won't work on the miner anymore. Why ? Look at SRBPolaris, it's free, you know how much donation i got for it ? About 150$ maybe 200$. But of course lot of people use it.

2. Claymore is a magician, he probably worked at AMD and knows all the good insider stuff

Yeah I did notice he took out the fee's at least for 3GB or under cards i think..

But how much memory do you have exactly in total when it's correct? Then I might be able to finally dig into it and see if i can get something going.
Since mines actually doing the opposite for some reason.. on 14.4 it's showing 1024 iirc, and 2047 for 15.7.1...not sure why it isn't 2048 though..

1.) Nope, and don't think he's going to, but never know later on.

Far as claymore 9.7 goes.. probably some shady coding he doesn't want anyone to know, or just wants to keep it away from everyone for fee's possibly, never know.

2.) I did notice on 14.4 drivers that my vram was more around 1GB and switching over to 15.7.1 it has 2047MB for some reason detected on all the other miners, but claymore did find 2047 on both drivers..
     so determining how it gets the m1 and m2 should be an easy fix, I know for a fact I only have 512MB dedicated, which is also shown in m2.. I'll have a look at which way xmrig/stak is polling the memory.  iirc this has been an issue with those for quite awhile.. I've never been able to get any miner to work without dying except for claymore on 15.7.1, and believe me I am trying to find a workaround that doesn't involve switching and mangling drivers around to make something work.

How much memory does 14.4 show you compared to 15.7.1?

wow , long post
To tell you the truth, at the moment i have more important things to improve on the miner. Yes, surely lagging is a problem, but since mining is 98% happening on rigs, where you don't need a responsive ui, it really isn't a problem

If you come up with something , surely i can integrate it, so that 2% of users can get a responsive desktop, with minimal hash drop

Nothing really can help that without the kernels that are executed. This also happens on any other gpu miner as well right?

For everyone:

     I'll explain a bit about OpenCL and how the "kernels" work a bit..
The kernel or "payload/work" is sent to the video card and is kind of like a singular pipe, okay that analogy sucked, but imagine
with all the "CU" Compute Units available.. the work from these kernels are sort of like threads on a miniature scale and they all
work according to the OpenCL standard (Hopefully) But it's like a faucet.. turn it on or off.. also you may need to turn down intensity
even more until you have a freeze free desktop which costs all the extra hashing power you would have had.  Remember on SRBMiner you can
use decimals so don't forget that ex: "intensity 20.3" or what have you.

     I've left an earlier comment on a "low intensity" mode that is about splitting
up one big time job to do work into much smaller timed jobs and if done right, it really shouldn't have any negative impact on hashing speed,
or at least any notable impacts on it so that could be maybe be a modulation of 100ms or 1/10th a second per command queue or even smoother
by doing it roughly ~16.67ms for 1/60th a second, but I'm getting a bit to technical trying to explain it.. Anywho, a good way to perhaps implement
this would be to take an argument for say --desktop_mode <time in milliseconds> ex. --desktop_mode 25 and plug that in which would do 40 pulses_per_second.

     I'm not the most intelligible on OpenCL and gpu kernel work, but to the best of my knowledge this is the only way that claymore/phoenix miners are doing this,
please correct me if I'm wrong (Which I probably am on a few things ).  Since I have no source code to these miners, I've been doing a bit of work on XMRig-amd
and testing my findings out on that.. So far I haven't got into splitting up kernel execution times, but i did turn an almost static 32H/s into 35H/s by redoing a bit
of the way the kernel maps memory.. Not sure how big of an improvement it would be on a real card, but it probably would give a good bit more hashes on other cards..
I'm only able to test with an amd radeon HD6530D APU setup and the maximum i've ever got it to do was 42H/s at a slight bit of OC on claymore and around 50H/s if i jacked
timing up to almost 700Mhz from stock 444Mhz for this cards core..(Probably wondering to yourself how that is even achieved with these old APU's?? I call it part of the good
silicon lottery.) If you have an A6-series or A4's or whatnot, I might be able to also help with clocks and suggestions...

     Also if anybody would like to try and help coding for and helping SRBMiner be the serious go to for cryptonight mining with this low intensity thing and kernel work.. I'd gladly
accept the help and can set up a private git branch that we could work on that through xmrig source, if the Doktor gives an ok on doing, he could throw it into SRB with perhaps
minimal changes and nothing else will have it.  My goal as a mining hobbyist is to make these miners work on pretty much all driver versions (Except the ones like the crimson beta
which doesn't include anything to use far as i can tell...)

Drivers tested with using DDU (Without Format):
  14.4 - Confirmed as working and stable for pre-GCN cards.
  15.7 - Can only confirm that it does not work with A6-series Apu's without driver crash.
  15.11 - Also same as 15.7.
  16.2.1 - Forget about it... for pre-GCN computing.

     Perhaps I should just ask Doktor if he in any way, shape, or form would like to collaborate even?  I tend to use bitbucket for it's private git repositories with things such as these.
And by the way, here is something to talk about.. not sure if there is a rant section, but people that totally pack their miners and put in disassembly code that shuts off a miner for
having any debug software going, or show's faked hashrates to ppl who use nofee or cheats as they worded it, or are those numbers not just higher in the code.. SRB i'm 99.9999% sure
there isn't any of that since we're all getting just about the same hashes on all the open sourced ones, but this seems a good bit more optimized already with more share turn in's
compared to hashes, perhaps Dok already found those memory speedups Okay, enough of my novella.. Thanks.

Διαφήμιση κάνεις; Το εχεις γράψει 3-4 φορές, γι αυτο λεω.

Srbminer is helping you to use these old cards, so be patient.

easy, lower the intensity and problem solved

Ok well I used DDU and found the correct 14.4 drivers.. seems the last one wasn't actually installing for some reason.. anyways now all other miners work as well.
Only one issue really is the intensity setting, I can only go up to 2.0. 2.1 or higher kills display driver or gives the CL invalid buffer.. tried all 4 kernels and worksizes, kernel 2 seems to be the best
at 14H/s compared to 12-13H/s on 3 & 4 kernels.  I was wondering if the gpu kernels having "256" in them as being the hash size? and if so, is there a way to lower or give a CLI option to change them or
maybe a 128 version? If that isn't the case, oh well.
(126 intensity seemed to be the optimal number for xmr-stak for some odd reason, also with a 35.9H/s which isn't to far off of the original claymore 9.7's 42H/s with low intensity mode on before v7.)

Does anyone know how to keep windows and everything from being totally unusable on all these miners?
(like clay's -li low intensity mode, which doesn't seem to be related at all to actual intensity.)

Best of luck to everyone.

Crypto-Bridge = Καινούργιο αλλά με ανοδική πορεία. Είναι Decentralized Exchange, δηλαδή δεν υπάρχει μια οντότητα που το ελέγχει αλλά οι σερβερ τρέχουν από άτομα που κερδίζουν μέρος των fees. Απλά είναι λίγο δύσκολο στη χρήση, πρόσεξε ότι κωδικό σου δώσει να τον σημειώσεις γιατί αν χάσεις κάτι συμαντικό δεν μπορούν να σου επαναφέρουν το account. Φυσικά δεν υπάρχει verification εδώ. Α και μια ιδιετερότητα που έχει... τα fees νομίζω είναι γενικά χαμηλά αλλά για κάθε κίνηση που κάνεις στο σύστημα υπάρχει μια απειροελάχιστη χρέωση καθώς το όλο exchange είναι πάνω σε blockchain από όσο έχω καταλάβει. Είτε αλλάξεις κωδικό, είτε βάλεις εντολή συναλλαγής σε χρεώνουν, αλλά μπορεί να είναι και λιγότερο από 0,01€, ανάλογα τι κάνεις. Απλά δεν συμφέρει να σπαμάρεις εντολές αγοράς/πώλησης και να τις ακυρώνεις.
UPDATE: Eπίσης ξέχασα να αναφέρω την εμπειρία μου με το support του Crypto-Bridge. Μέσω του Discord μίλησα άμεσα με 2 άτομα (από το community support team νομίζω) οι οποίοι με καθοδήγησαν και καταφέραμε να λύσουμε το πρόβλημα που μάλιστα ήταν ιδιαίτερο. Είχα καταλάθος βάλει 2 κωδικούς, ένα private key για withdraw και ένα custom password για login & trade, με αποτέλεσμα να μη μπορώ να κάνω withdraw με τον κωδικό μου! Ευτυχώς είχα φυλάξει το private key και μου έδειξαν πως να κάνω σωστά την αλλαγή κωδικού.

Also claymore is pretty much dead now.. would be nice if they released the code to it, would help out about all branches of miners

Hi there, I've had a problem with every miner around since the monero pow change, since the only miner I was able to use was Claymore 9.7beta without it crashing my display drivers.
I've tried xmr-stak, xmrig-amd, newer claymore's (No ASM bin found for my old card.) and about anything else that is supposed to work, I've compiled all the ones available and tried
with stock binaries on windows..

Display drivers crash no matter which version I try.. 14.4 15.7, 15.11-beta (for some reason this one is tricky to find.) Even tried the crimson edition beta which I've found out doesn't
actually include any assembler/disassembly tools for openCL.. Anywho..

Display card: AMD Ati Radeon 6530D (Evergeen or BeaverCreek as it picks it up everywhere.)
Cpu: AMD A6-3620 APU w/ the onboard 6530D

I've tried all 4 kernels out, all kill display, and of course can't get ADL to work, but I'd be highly surprised if that could even work at all anyways on this gpu.

All in all I really don't know what to do, or even try anymore.. I'd lend a hand if I could for getting what is needed to make these A-Series APUs to work.  I haven't really seen anything in
the code for the other miners like xmrig/xmr-stak that would be a problem.. But I noted for some reason Claymore is posting exact driver versions for all of their releases, and wondering
how they are able to compile against them specifically, or if that just happens to be what they were using when compiling...

Any help is appreciated, and I'd love to get back to mining on my gpu, had a ton more shares and efficiency even at 42H/s and that's better than 0 since it's on 24/7 anyways.

Here are a couple screenshots for how it's acting and what it catches, and second is showing when display was killed and came back.
https://imgur.com/a/mBtohkv

Thanks, you really are saving miner's lives with this miner and I hope you keep at it.. So I tip my hat to you Doc.