Search content
Sort by
Showing 20 of 63 results by onecryptoguy
It seems that the XCore (the storage node software) is abandoned. No updates, no bug fixes, for over 6 months. So the system that is supouse to keep your files safe, is abandoned by devs, and soon by node operators. On the other hand, Storge project is updated regularly, with a new release almost every week. So, stop buying Internxt’s stupid plans, and move to a serious storage service. Devs even said on Telegram that their final intent is to move to a few big data centers, so bye bye decentralisation. The Internxt token is another scam… they pay the node operators with this useless token, and they (the devs) hold the biggest percent of coins, just for pump and dump. So the node operators are screwed over and over. I was a node operator, but after realising that it’s worthless, I deleted the node and bye bye Internxt.
Also, their storage service is so slow (I wonder why…;)) I tryed the mobile and desktop versions. Bleah… Good only for very small files.
So, don’t jump and buy their plans. First try the free plan on all platforms and see if it’s what you’re looking for.
And wait one more year or two. They still need to figure things out.
Also, their storage service is so slow (I wonder why…;)) I tryed the mobile and desktop versions. Bleah… Good only for very small files.
So, don’t jump and buy their plans. First try the free plan on all platforms and see if it’s what you’re looking for.
And wait one more year or two. They still need to figure things out.
The project is moving forward, Drive is working great on all platforms, even the Token rocketed.
The only problem I have with it is that the X Core GUI on Windows, which is the storage node that stores all the data from the clients of this project, is not maintained properly, and needs stability improvements and cosmetisation. They should focus their resources on nodes first, because without nodes, there is no Drive, Photos, Send etc., and no decentralisation.
The only problem I have with it is that the X Core GUI on Windows, which is the storage node that stores all the data from the clients of this project, is not maintained properly, and needs stability improvements and cosmetisation. They should focus their resources on nodes first, because without nodes, there is no Drive, Photos, Send etc., and no decentralisation.
Why did you removed my post How to set BTC MINING DIFFICULTY - fix diff / custom diff without any explanation?
I spent over 3 hours writing that guide and you just deleted because...?!?!?
If something bothered you, you should tell me to edit it, not piss on my work just because you can?
I tought this forum promotes the free of speach and people sharing info.
I spent over 3 hours writing that guide and you just deleted because...?!?!?
If something bothered you, you should tell me to edit it, not piss on my work just because you can?
I tought this forum promotes the free of speach and people sharing info.
How to set BTC MINING DIFFICULTY - fix diff / custom diff
I hope this guide will answer many or all of your questions about mining difficulty.
I was a miner for more than 2 years, doing a lot of mining with CPU, GPU and ASICs, did a lot of tests, trying to set my rigs as optimum as possible. I started from zero, with no programing skills, and no knowledge of cryptocoins. I learned a lot, but many times I felt the need for proper begginer guides. There is so much info about mining crypto, and very few usefull complete guides for beginners. Many miners don't understand essential notions and do a less than optimum mining with their equipament and the money they spent. I just try to be helpfull, because I was one of them. Let's begin with a simple but too many times ignored notion.
BTC MINING DIFFICULTY.
These notions can be applied to any PoW algo.
A miner is the owner of an account on a mining pool, to which he points his workers to mine a coin and get rewarded for the work he does.
An worker is an individual mining machine, an ASIC for BTC and many coins, a rig or a PC for many other coins. If the miner uses a proxy (a software runnig on a PC, on the same local network as the workers), than the pool sees the proxy as one single powerfull worker, and dosen't sees the actual individual machines. In this case, "worker" means the proxy, that has the combined HR of the machines pointed to it. The proxy is like a middleman between the local ASICs and the pool; it gathers all the small shares (work) from the ASICs, combines them into one big share and sends this big share to the pool. This, I mean using a proxy, is better for the pool and for the miners. The reason for this is that each pool is a server with CPUs and stuff, and like any machine, it has a limited compute power, limited compute cycles. The small shares are sent more often to the pool. The big shares are sent rarer. So it's easier for it to verify fewer bigger shares, than more small ones that can choke it up.
This is what many attacks do on small pools, with small coins; the attacker chokes the pool with many small fake shares, like a DOS attack, and the pool can't process the good ones.
The "same thing" as the proxy, the difficulty adjustement does. It forces the worker to send fewer big shares, than more small ones. The reward for the miner is the same (approximately
), but the pool's server is working less. The pool can also drop incoming shares if there are too many and can't be processed in time. These are the rejected shares.
The mining difficulty for a worker (ASIC, individual machine, proxy) mining on a BTC pool (or any other SHA-256 coin) is calculated as a power of 2, and usualy is adjusted near the value of the worker's hashrate (HR) in GH/s, or the double of that value, by the pool's algorithm. This is the autodiff function of the pool.
The autodiff process: the pool makes guesses using lower and higher diffs, in order to establish the best diff for the worker. It checks the number of shares received from the worker in a period, and makes adjustments to difficulty untill reaches a target, like 1 share at 10 seconds. All this process costs you. You can find this target yourself for a specific pool, as an exercise: let the ASIC mine on the pool for 24h or more, with autodiff; enter the web interface of the ASIC, take the Acceped shares and the Elapsed time (in seconds, or minutes), divide them and you get the "number of shares/minute" or "one share at x seconds". This is the pool's target for diff.
Also, many pools supports custom diff - that is a fixed difficulty the miner can set for each worker. The pool also has some rules for this custom diff, to limit the number of small shares that it receives, and to make an attack less possible.
With autodiff the problem is solved, but there are advantages for the custom diff too, especialy for the miners. So many pools allow custom diff in order to attract miners.
A proper set diff can give a miner 0-2% more rewards than a wrong set one, from my tests. Maybe more. This applys to every minable PoW coin. The custom diff is very usefull for rentals or when you switch pools often; when you rent a rig/ASIC to mine for you, you do this for a limited time, usualy 3 to 24 hours. Than switch to another, and another... These means pool conection-disconection-conection-.... If you don't use a custom diff to tell the pool the best difficulty at start, it will start the autodiff process, that will cost you shares.
From my research, for coins with 2 minutes block time, like many cryptonight coins, the best target is 1 share for 15 seconds; for CN we calculate diff = HR x target_time; ex. diff=950h/s x 15s=14250.
For BTC mining, the target is around 1 share in 3-10 seconds, for the majority of pools. In this case (SHA-256 coins), diff is a power of 2, and usualy it's around the value of the hashrate in GH/s or the double of this value. For a 28TH machine (28000GH/s), you have d=2^15=32768 or 2^16=65536.
The spikes and drops in HR you will see on pool are bigger with bigger diff, and closer to a line with smaller diff. They represent the aproximation of your HR made by the pool, according to the shares that it gets. So the smaller shares (shares with small diff) are sent faster, the pools gets more info in a period of time and the graph has more dots on it; the curve is more linear...
)
WOW, that's a long explanation Thank you for reading all of this, and I hope it was usefull to you and you learned somethig from it.
If you want to show me your appreciation and to motivate me to write more usefull stuff, please consider a donation. Thanks!
BTC: 1PQHFKx4iFSJzB5CWAEVSd4bJAKwF38fLj
==========
This is a list with some BTC pools and their rules for setting the difficulty; the custom diff can be set by entering in the password field the formula below, like d=65536
f2pool.com - fd=2^n (n=19-25)
poolin.com - autodiff (target 2^n, aprox. double of HR)
pool.btc.com - d=2^n
viabtc.com - d=HR*1000 (wrong)
slushpool.com - d=2^n (>128)
kano.is - autodiff (min. 442, starting at 4098, target 18 shares per minute)
Here are some usefull links, if you want to investigate more:
https://bitcointalk.org/index.php?topic=274023.0
Here are some of my old tests in CN algo:
Test fix diff RIG LOKI miner.rocks:
diff 50.000 - start at 23:00-11:00 / 8307903092 - 8450153092 = 142250000 shares > 3292,8 H/s +1,97%
diff 100.001 - start at 11:15-23:15 / 8450153092 - 8589654487 = 139501395 shares > 3229,2 H/s
Test vardiff-fix diff AMD LOKI miner.rocks:
505486003-486059580 vardiff = 19426423 in 10h > 539,6
485975580-466424580 21000 = 19551000 in 10h > 543,1 +0,65%
I was a miner for more than 2 years, doing a lot of mining with CPU, GPU and ASICs, did a lot of tests, trying to set my rigs as optimum as possible. I started from zero, with no programing skills, and no knowledge of cryptocoins. I learned a lot, but many times I felt the need for proper begginer guides. There is so much info about mining crypto, and very few usefull complete guides for beginners. Many miners don't understand essential notions and do a less than optimum mining with their equipament and the money they spent. I just try to be helpfull, because I was one of them. Let's begin with a simple but too many times ignored notion.
BTC MINING DIFFICULTY.
These notions can be applied to any PoW algo.
A miner is the owner of an account on a mining pool, to which he points his workers to mine a coin and get rewarded for the work he does.
An worker is an individual mining machine, an ASIC for BTC and many coins, a rig or a PC for many other coins. If the miner uses a proxy (a software runnig on a PC, on the same local network as the workers), than the pool sees the proxy as one single powerfull worker, and dosen't sees the actual individual machines. In this case, "worker" means the proxy, that has the combined HR of the machines pointed to it. The proxy is like a middleman between the local ASICs and the pool; it gathers all the small shares (work) from the ASICs, combines them into one big share and sends this big share to the pool. This, I mean using a proxy, is better for the pool and for the miners. The reason for this is that each pool is a server with CPUs and stuff, and like any machine, it has a limited compute power, limited compute cycles. The small shares are sent more often to the pool. The big shares are sent rarer. So it's easier for it to verify fewer bigger shares, than more small ones that can choke it up.
This is what many attacks do on small pools, with small coins; the attacker chokes the pool with many small fake shares, like a DOS attack, and the pool can't process the good ones.
The "same thing" as the proxy, the difficulty adjustement does. It forces the worker to send fewer big shares, than more small ones. The reward for the miner is the same (approximately
), but the pool's server is working less. The pool can also drop incoming shares if there are too many and can't be processed in time. These are the rejected shares.The mining difficulty for a worker (ASIC, individual machine, proxy) mining on a BTC pool (or any other SHA-256 coin) is calculated as a power of 2, and usualy is adjusted near the value of the worker's hashrate (HR) in GH/s, or the double of that value, by the pool's algorithm. This is the autodiff function of the pool.
The autodiff process: the pool makes guesses using lower and higher diffs, in order to establish the best diff for the worker. It checks the number of shares received from the worker in a period, and makes adjustments to difficulty untill reaches a target, like 1 share at 10 seconds. All this process costs you. You can find this target yourself for a specific pool, as an exercise: let the ASIC mine on the pool for 24h or more, with autodiff; enter the web interface of the ASIC, take the Acceped shares and the Elapsed time (in seconds, or minutes), divide them and you get the "number of shares/minute" or "one share at x seconds". This is the pool's target for diff.
Also, many pools supports custom diff - that is a fixed difficulty the miner can set for each worker. The pool also has some rules for this custom diff, to limit the number of small shares that it receives, and to make an attack less possible.
With autodiff the problem is solved, but there are advantages for the custom diff too, especialy for the miners. So many pools allow custom diff in order to attract miners.
A proper set diff can give a miner 0-2% more rewards than a wrong set one, from my tests. Maybe more. This applys to every minable PoW coin. The custom diff is very usefull for rentals or when you switch pools often; when you rent a rig/ASIC to mine for you, you do this for a limited time, usualy 3 to 24 hours. Than switch to another, and another... These means pool conection-disconection-conection-.... If you don't use a custom diff to tell the pool the best difficulty at start, it will start the autodiff process, that will cost you shares.
From my research, for coins with 2 minutes block time, like many cryptonight coins, the best target is 1 share for 15 seconds; for CN we calculate diff = HR x target_time; ex. diff=950h/s x 15s=14250.
For BTC mining, the target is around 1 share in 3-10 seconds, for the majority of pools. In this case (SHA-256 coins), diff is a power of 2, and usualy it's around the value of the hashrate in GH/s or the double of this value. For a 28TH machine (28000GH/s), you have d=2^15=32768 or 2^16=65536.
The spikes and drops in HR you will see on pool are bigger with bigger diff, and closer to a line with smaller diff. They represent the aproximation of your HR made by the pool, according to the shares that it gets. So the smaller shares (shares with small diff) are sent faster, the pools gets more info in a period of time and the graph has more dots on it; the curve is more linear...
)WOW, that's a long explanation
Thank you for reading all of this, and I hope it was usefull to you and you learned somethig from it.If you want to show me your appreciation and to motivate me to write more usefull stuff, please consider a donation. Thanks!
BTC: 1PQHFKx4iFSJzB5CWAEVSd4bJAKwF38fLj
==========
This is a list with some BTC pools and their rules for setting the difficulty; the custom diff can be set by entering in the password field the formula below, like d=65536
f2pool.com - fd=2^n (n=19-25)
poolin.com - autodiff (target 2^n, aprox. double of HR)
pool.btc.com - d=2^n
viabtc.com - d=HR*1000 (wrong)
slushpool.com - d=2^n (>128)
kano.is - autodiff (min. 442, starting at 4098, target 18 shares per minute)
Here are some usefull links, if you want to investigate more:
https://bitcointalk.org/index.php?topic=274023.0
Here are some of my old tests in CN algo:
Test fix diff RIG LOKI miner.rocks:
diff 50.000 - start at 23:00-11:00 / 8307903092 - 8450153092 = 142250000 shares > 3292,8 H/s +1,97%
diff 100.001 - start at 11:15-23:15 / 8450153092 - 8589654487 = 139501395 shares > 3229,2 H/s
Test vardiff-fix diff AMD LOKI miner.rocks:
505486003-486059580 vardiff = 19426423 in 10h > 539,6
485975580-466424580 21000 = 19551000 in 10h > 543,1 +0,65%
Re: [ANN] | SINOVATE(SIN) | X25X GPU Algo | INFINITY NODES | I.D.S | R.S.V |
@pallas
It worked finnaly... I tryed the Tree view in Coin control and it grouped the 2 lines in one line. I selected that line, I chouse the recomended fee, and it worked.
Prevoiously, I used List view, and selected only one line from the two, and used a custom fee. That didn't worked.
So... Coin control > tree view > select one box > transfer all available with fee substracted from amount > recomended fee - 2 blocks > working!
It worked finnaly... I tryed the Tree view in Coin control and it grouped the 2 lines in one line. I selected that line, I chouse the recomended fee, and it worked.
Prevoiously, I used List view, and selected only one line from the two, and used a custom fee. That didn't worked.
So... Coin control > tree view > select one box > transfer all available with fee substracted from amount > recomended fee - 2 blocks > working!
Re: [ANN] | SINOVATE(SIN) | X25X GPU Algo | INFINITY NODES | I.D.S | R.S.V |
the transtactions with conflict disappeared from the list, but I couldn't send anything, becouse of the same conflict error. Coincontrol shows only 2 rows... 7xxx.xx sinovate and 1.xxx sinovate. I tryed to send the entire 7xxx.xx from the first row, as the guide said. Conflict...
Re: [ANN] | SINOVATE(SIN) | X25X GPU Algo | INFINITY NODES | I.D.S | R.S.V |
I try to send some Sinovate from the GUI Windows wallet, last version available, and I keep getting this for any amount that I try: "Status: conflicted with a transaction with 1 confirmations".
What's the problem? How can I get my transactions to work?
I used the wallet.dat file from the old SUQA project.
What's the problem? How can I get my transactions to work?
I used the wallet.dat file from the old SUQA project.
Re: ⭐️⭐️⭐️[ANN][PRE]NORD - New Age Gaming Platform⭐️⭐️⭐️
It's been 1 month and still didn't got my money back. They told me to wait 2 weeks. I've waited. After 2 weeks, they ask for an "invoice". Wtf? What crap is that? I proved to them that I own that account, I sent them my address from witch I made the payment, they know exactly how much I payed for ICO. 1 week and now answers.
Wtf is so hard? You know the amount, you know the ETH address; just press send! It's not rocket sience!
Why the hack do you say you give our money back, if you don't intend to?
Anyone wants to buy my NORD coins, pm me. I have 900.
Wtf is so hard? You know the amount, you know the ETH address; just press send! It's not rocket sience!
Why the hack do you say you give our money back, if you don't intend to?
Anyone wants to buy my NORD coins, pm me. I have 900.
You speak in the name of your friend and in the name of the people... personaly, I can't recall hiring you as my advocate. I want other coins. I want Zano. I don't give a rats a... if useses the name of 10.000 other stuff. 😜
"The first known currency was created by King Alyattes in Lydia, now part of Turkey, in 600BC."
So why the hack do we have $, , £,¥, and the other thousand different coins invented by the humankind?
Why the hack did we created ETH, LTC and the other thousand crypto projects if we already had the almighty Bitcoin? Isn't something that you missed? Or all people are so dumb and create repetitive stuff?
"The first known currency was created by King Alyattes in Lydia, now part of Turkey, in 600BC."
So why the hack do we have $, , £,¥, and the other thousand different coins invented by the humankind?
Why the hack did we created ETH, LTC and the other thousand crypto projects if we already had the almighty Bitcoin? Isn't something that you missed? Or all people are so dumb and create repetitive stuff?
Re: [Started][AirDrop#3 - 25th March] - Electronic Dollar(eDollar)
I have a lot of the original EDL coins. Is this the same project? Do I need to swap the old coins for the new ones? Can my old wallet keys be used in the new wallet?
Re: 🇨🇭🚀[ANN] [ICO] LAPO - DECENTRALIZED FINANCE REINVENTED. Whitelist Bonus!
Wow! I'm shocked. People are actualy paying 0.035 $ /1 LAX?! You can buy hashpower on miningrigrentals and pay lower than 0.0005 $ / 1 LAX. LOOOL
Re: ⭐️⭐️⭐️[ANN][PRE]NORD - New Age Gaming Platform⭐️⭐️⭐️
Well, I can't find the open tickets in my account, I see only "Write to support" option. Yes, I used 0.6576146700 ETH to buy 6xx NORD, I don't know how I received the rest. Please, give my ETH back. I don't know how to respond to tickets. Thanks!
For a non-technical reader, what are the practical differences between Mimblewimble projects (Grin, Beam) and what Zano brings to the table, especially regarding the main 2 aspects: privacy and blockchain size?
I mean from a users point of view...
I mean from a users point of view...
1.where can I find a list of all parameters and what they mean?
2.what is the best starting .bat for 7x GTX 1060 3GB, Windows 10, mining Boolberry?
3.how to OC the cards? More core? More mem? Thx!
2.what is the best starting .bat for 7x GTX 1060 3GB, Windows 10, mining Boolberry?
3.how to OC the cards? More core? More mem? Thx!