Bitcoin Forum
January 16, 2019, 11:15:19 AM *
News: Latest Bitcoin Core release: 0.17.1 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1] 2 »
1  Other / Serious discussion / YIIMP Support on: November 12, 2018, 03:18:47 PM
Is there anyplace one can get support for YIIMP?

I'm seeing exception: CDbCommand failed to execute the SQL statement: SQLSTATE[22003]: Numeric value out of range: 1690 BIGINT value is out of range in '((count(`Yiimp`.`shares`.`id`) * 2097152) * 4398046511104)'

and wondering what to do about it.
2  Alternate cryptocurrencies / Announcements (Altcoins) / [ANN][BOOT] Bitcoin-Rebooted on: November 10, 2018, 11:19:12 PM
Announcing the new Bitcoin Rebooted coin



Coin Details

Ticker: BOOT
Algorithm: SHA256
Block Reward: 50 BOOT
Block Time: 150 Seconds
Block Maturity: 100 Blocks
PoW Reward: 50 BOOT
Difficulty Retargeting: New Fuzzy Effect Wave DAA
Premine: 200K BOOT (about a weeks worth)
Total Supply: 268,234,500 BOOT (50 years of mining)
Website: https//www.bitcoin-rebooted.xyz
Hashtag: #GettheBOOT

This is a "soft launch".  We have been internally developing and testing since July of 2018.  The coins tests out.  The DAA has been extensively tested (over a 1000 hours).  We have had the website publicly available for close to a month.  An explorer went online two weeks ago.  We have an experimental yiimp pool that appears to be up and running, but no promises there - pool operation is not our forte, others are coming online to do that job right.

So what is Bitcoin Rebooted?  Well, you can read an overview (or everything you would ever want to know about it in the coin details tab) at:  https://www.bitcoin-rebooted.xyz

Here is a bit more detail:

This is NOT a fork of the Bitcoin blockchain, this is a fork of the Bitcoin sourcecode and utilizes the SHA256 hash algorithm so can be ASIC mined

The blockchain has been restarted with a new genesis key, magic numbers, etc.  

Block reward is 50 coins per block, which decreases by 1 coin per year per block.  So 50 years of mining, and no major penalty if your late to the game (at least for the next dozen or two years)

Block time target is 2.5 minutes, just like Litecoin.  Minimum blocktime is 2 seconds, 20 seconds if the block is empty (to discourage mining of such)

Block maximum size is 16mb

The DAA is all new code, dubbed "Fuzzy Effect Wave" and has a few special features, like "cliff" detection to prevent super long blocks that impact many alt-coins when profit-switching pools leave

Segwit support has been removed from the original source tree - we don't believe in it and feel it punishes miners via reduced transaction fees

There has been no ICO, there will be no airdrops, there have been no special partners that benefited early

The blockchain was mined by the developers for the first week in order to establish some checkpoint records to help reduce the chance of early forking.  Announcements then went out via another popular forum and shortly thereafter a pool came online:

https://cryptocurrencytalk.com/topic/113782-ann-bitcoin-rebooted/
https://twitter.com/BRebooted/status/1059168270597718016
http://pool.bitcoin-rebooted.xyz

What do we consider a "soft launch"?  Announcing there first to get a few folks to help confirm everything was stable for a broader audience.  Now announcing here for a wider audience.   Once a broader infrastructure is in place (bigger network, more pools, hopefully an exchange or two) we will publicize the coin more via other outlets.   Of course, the source code is available and a Windows wallet installation program is available - just hop over to the coin website for those.   e..g.  Not a lot of fan-fare, just public awareness.  We are not in this as a "get rich quick" scheme, but rather for the long haul.  If this takes a year or three, so be it.

Source code at:  https://bitbucket.org/ccgllc/Bitcoin-Rebooted
Direct Windows installed download via bitbucket:  https://bitbucket.org/ccgllc/bitcoin-rebooted/downloads/Bit-Reboot-Self-Installation-64bit.exe

Project download folder (logos, Windows self-install storage location, etc.) at:  https://bitbucket.org/ccgllc/bitcoin-rebooted/downloads/

Come join us on Discord:  https://discord.gg/srXW6fJ

Known pools (in order of creation):

http://pool.bitcoin-rebooted.xyz (Mid-West USA)
http://youcrazy.me (Australia)
http://1pool.pw (Europe)
http://usa.thecryptominerpool.com (Texas, USA)

Exchanges:

[urlhttps://micromm.online/][/url]
3  Bitcoin / Mining software (miners) / Avalon Management System on: September 28, 2018, 10:24:58 PM
Has anybody gotten this software up and running?

I'm to the point that the web page pops up, but trying to login doesn't do anything.

I tried to use the "amscli controller" command to add my controllers (although I expected to be able to do that via the web page) and it tells me it can't parse what I put in.

Also unclear about the [farm] and [JWT] sections in /etc/ams.conf.

Sure would appreciate some sample file formats with explainations.  The github issues area for the product seems pretty dead.
4  Bitcoin / Mining support / One Avalon 841 lost on a chain on: September 26, 2018, 11:16:12 PM
Hi all - I'm currently running 31 Avalon 841s and a whole bunch of S9s.

While doing a daily check I noticed one of the 841s, in a 3 deep chain, is missing.  The controller has 13 machines on it (now 12 showing up).  I went out to the data center to visually inspect and all 13 on that controller have blue indicator lights.

I have not come across this before.

Any suggestions?   Of course, I tried rebooting the controller, but that didn't help.

Figured it out:  I just turned all the LEDs on to find the odd-man-out.  It was actually dead after rebooting the controller, so would have been obvious had I gone back into the data center.  In any case, power cycled the box and it came right back up.
5  Alternate cryptocurrencies / Mining (Altcoins) / (2) of (6) TI 1070s just slowed dow on: August 23, 2018, 05:53:08 PM
I have a GPU rig that has been running for close to a year now.  Today, (2) of the (6) TI 1070s took a major plunge in effectiveness, dropping from ~500 sols/s to ~300 sols/s.  The other GPUs continue as before:

Code:
   GPU0  50C  85% |  504.3 Sol/s   508.8 Avg   272.7 I/s | 3.92 S/W  131 W |  2.56  100  124
   GPU1  48C  85% |  514.9 Sol/s   506.6 Avg   271.9 I/s | 3.91 S/W  128 W |  2.46  100  135
   GPU2  48C  85% |  339.1 Sol/s   339.4 Avg   176.7 I/s | 2.70 S/W  126 W |  2.25  100  126 +
   GPU3  50C  85% |  502.1 Sol/s   498.9 Avg   267.3 I/s | 3.85 S/W  133 W |  2.26  100  125 ++
   GPU4  49C  85% |  321.1 Sol/s   336.0 Avg   176.0 I/s | 2.72 S/W  119 W |  1.77  100  127
   GPU5  53C  85% |  489.9 Sol/s   490.5 Avg   265.6 I/s | 3.78 S/W  132 W |  3.19  100  131 +
   ============== | 2671.3 Sol/s  2680.2 Avg  1430.2 I/s | 3.48 S/W  771 W | 14.50  100  128

Note GPUs 2 and 4 in the above screenshot.  This represents about a 10% loss in mining efficiency for me.

Any suggestions on how to recover?
6  Bitcoin / Mining support / S9s running warm? on: July 24, 2018, 08:50:16 PM
Spent some time today checking temps on my miners (easily done with Awesome Miner by just sorting on the Status tab).  Anyhow, out of ~120 S9s I found 5 that were running hotter than the others.  Most had reported chip temps in the 60s-70s.  These 5 were 80+.

My first step was to do what I thought was the obvious thing:  tear them down and blow them out.  That actually helped 3 of them.  The other 2 continued to run warmer than expected.

Opened up the web gui on each and discovered both had one fan only running around 2000-2600 RPM.  Swapped the fans out (with spares I had previously purchased from Bitmain), and goodness returned.

Learning for today:  Just because it boots and passes the BIOS fan test, doesn't mean those fans are running correctly!

Oh, for the record: I started down this journey today because Awesome Miner alerted me that one of the miners hit 96C.  Nice to be notified.  Not good that a miner was running at that temp.  I should also note the intake air temp is 90F (32C) right now.
7  Bitcoin / Mining support / Avalon 821 & 841 Socket connect failed => Connection refused on: June 06, 2018, 04:36:28 PM
Woke up this morning to discover ALL my Avalons, both 821s and 841s, offline.  S9s on the same switch to the same pool are working fine.  These Avalons are spread between 3 controllers and 6 AUCs.  All have yellow lights on them.  I've tried rebooting the Pis several times - both by power cycling and soft reboots.

The cgminer API log is showing (with trivial variations):

[Firmware Version] => Avalon Firmware - 20180305
    luci: 62d814c
    cgminer: b5b497e
    cgminer-packages: 960e108
Socket connect failed => Connection refused


These machines have been working well for quite some time.

Any ideas?
8  Bitcoin / Hardware / Canaan vs. Bitmain PSUs test on: May 06, 2018, 09:47:09 PM
Hi all.  My data center is getting warm (air temp at the entrance to the miners is around 85F) and I was curious if one brand of miner PSU vs. the other was dealing with it any better.

Awhile back I ordered a https://www.amazon.com/DROK-Digital-Multimeter-Voltmeter-Ammeter/dp/B01MRZAFAF/ref=pd_sbs_469_1 thinking I could use it on one of my power panels, but it was way too light duty.  Instead I spiced it into a spare power cord and put the whole thing in a plastic wall box.  A few wire nuts and a bit of electrical tape later I had a fully functional "watt meter" for my power connections.

Originally I planned on using existing power supplies, one APW3++ and one Sorcerer.  For each test I allowed an Avalon 841 miner to fully spin up, measured by watching the power usage slowly climb until it was bouncing +/- a few watts.

Test 1:  APW3++ 1439.4 Watts, 6.29 Amps at 232.1 volts.
Test 2:  Sorcerer  1451.3 Watts, 6.33 Amps at 232.6 volts.

Then decided to unbox a new APW3++ and test it on the Test 2 miner, since the results were close, and we know individual miners vary a bit:

Test 3:  APW3++  1448.4 Watts, 6.32 Amps at 232.4 volts.

Good news... its appears the power supplies are, for all intents and purposes, equally efficient. 

The APW3++ has a higher rated temperature range, but past experience (especially at the low end), educated me to ignore those ratings by a wide margin.

I know this isn't exciting news, but figured others might be curious as well.
9  Bitcoin / Mining support / Avalon 841 PG 3 on: May 03, 2018, 03:55:58 PM
Most of my Avalon 841`s have a "15" under the PG column to the far right (hovering shows that as "Power Good").  One has a "3" and is underperforming.

Should I just swap the power supply?

Update:  I have spare PSUs, so went ahead and swapped it out.  Problem appears to be solved.  This is also the unit that was running about 4C higher in temp prior to the PG number changing.

Of course, will continue to monitor it.
10  Bitcoin / Mining support / Massive Antminer failure on: April 29, 2018, 06:29:19 PM
Around 9am CST6CDT the vast majority of my antminer farm went offline.  At the moment I have about 150 S9s and a few L3s offline.

The miners physically look fine, with flashing green lights, no red lights (mostly), network activity, etc.  However the majority can not be pinged, and a few that can be are not starting up.

Current network topology:   PFSense firewall -> right side Netgear GS316 -> <fans out to 7> Netgear GS316 -> Antminer S9s
                                                          ->  left side Netgear 10-100 switch on right side -> Netgear 7 port gigabit switch on left side -> <fans out to 3> Netgear GS316 -> Antminer S9s & L3s
                                                                                                                                                                                                 -> Avalon 821s & 841s

My normal topology is to have the right side Netgear GS316 also support the left side, but I split the network using a redundant feed I had back to the PFSense firewall with morning in an attempt to isolate the problem.

Of my (76) 14TH S9s, (24) are active, the rest can not be pinged.  Likewise (9) of my (25) 13.5TH S9s are reachable - mostly on the right side.

The left side has (11) of (13) 13TH S9s working, (2) T9s, and (2) of (Cool "problem children" S9s.  All of the Avalons are fine, but of course, they are clustered behind a few PIs, so have a lower network port count.  (22) of my (26) L3s cannot be pinged.

So both the left side and right side is having problems, and they are independent of each other network wise back to PFSense firewall box.  Occasionally I'm seeing Antminers go blinking Red, but a quick power cycle clears that. 

I'm at wits end without a clue.  I'd be fine if I lost a switch.  But my problem children appear to be spread across several switch, and in fact, several physical networks.  The LAN side IP addressing is shared at the firewall, but I can't see how that would be a problem.

Although growing (with the latest batch of 34 mixed Antminers being added early this week), the network has been otherwise stable until this morning.

Somebody please!  Give me some ideas of what I am overlooking...

11  Alternate cryptocurrencies / Mining (Altcoins) / Best place to point 12GH/s of Scrypt hash? on: April 27, 2018, 02:50:05 PM
I decided to diversify my SHA256 farm and start mining some Scrypt, mostly because of coupons from Bitmain and then $505 list prices of L3s, combined with some empty shelf space in my data center.

Spent some time on Google, but unlike BTC pool information, not finding as many pool comparisons for LTC and its friends or specific fee structures.
Update:  Finally found https://litecoin.info/index.php/Mining_pool_comparison

Recommendations I found so far:

Solo hash - Pro:  no fees.  Cons:  LTC only unless I was to setup merged mining and manage multiple wallets.  Doable.

Litecoinpool - Pro:  Claims 0 fee compliments of merged mining.  Cons:  Cost money to run a pool, guessing they shave some off the merged mining and keep (currently trivial) transaction fees.  Concerns:  PPS pools TEND to have higher fees to cover themselves.  Reported in the Pool Comparison to charge 4%

Give-Me-Coins - Pro:  Smaller pool, merged mining, payout directly to each wallet.  PPLNS - so SHOULD have lower fees. Cons: (Minor) Need to maintain multiple wallets (already setup).  Concerns:  Pool Comparison claims 0% fee, but a pool must charge something to survive.

ProHashing - Pro:  Profit Switching, rumored to pay out substantially more than merged mining sites.  Ability to pay out in any coin, including BTC.  Cons:  Somebody is paying for all the transaction fees associated with mining multiple coins and converting them to payout coins.  Concerns:  Unknown fee structure.  Also, if they are so great, and pay a lot more, why isn't everyone mining there?

FYI: Out of principle, I refuse to mine on any Chinese owned or controlled pool.  Also trend towards smaller pools for the health of the network - so long as blocks are found on a weekly basis I consider them big enough (which is why Litecoinpool is just a backup for me now).

Basically, this boils down to trying to maximize my return, which usually means minimizing expenses.

Can anyone please help educate me on this branch of mining?
12  Alternate cryptocurrencies / Mining (Altcoins) / L3+ startup issue on: April 03, 2018, 11:33:42 PM
Hi all.

I run over a 100 S9s so am somewhat familiar with Bitmains front ends.

Just received my first (4) L3+s.  Hooked them up, powered them up (with APW3++s running on 220V), and waited.  And waited.  And waited some more (now 53 minutes), and all I get is the basic web screen.

S9s can take over 20 minutes during their first boot to scan the cards.  Figured the L3+ has 4 cards vs. the S9s 3, so it might take a half hour or so.  Now its been substantially longer than that.

Also find it odd that the kernel log is blank on all 4.  I can web into them, but otherwise zip.

Any suggestions?  Zero experience with these things.  Bought them because I had room in my data center, $400 coupons to burn, and a strong curiosity.

Correction:  Kernel log was just VERY slow to respond.  Looking for errors I found the following repeating in the logs:

Code:
Apr  3 23:38:37 (none) local0.err cgminer[8003]: Get [1]Temp Data Failed!
Apr  3 23:38:37 (none) local0.notice cgminer[8003]: Dump IIC Data:[1][98][1][12]@ChainID:[0], Chip[C]
Apr  3 23:38:37 (none) local0.notice cgminer[8003]: Dump IIC Data:[1][98][1][10]@ChainID:[1], Chip[C]
Apr  3 23:38:37 (none) local0.notice cgminer[8003]: Dump IIC Data:[1][98][1][11]@ChainID:[2], Chip[C]
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[1][98][1][10]@ChainID:[3], Chip[C]
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[1][98][1][12]@ChainID:[0], Chip[C]
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[1][98][1][10]@ChainID:[1], Chip[C]
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[1][98][1][11]@ChainID:[2], Chip[C]
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[1][98][1][10]@ChainID:[3], Chip[C]
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[1][98][1][12]@ChainID:[0], Chip[C]
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[1][98][1][10]@ChainID:[1], Chip[C]
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[1][98][1][11]@ChainID:[2], Chip[C]
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[1][98][1][10]@ChainID:[3], Chip[C]
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: Chain 0 chip 0 RemoteTemp 0x12
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: Chain 1 chip 0 RemoteTemp 0x10
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: Chain 2 chip 0 RemoteTemp 0x11
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: Chain 3 chip 0 RemoteTemp 0x10
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[41][98][1][0]@ChainID:[0], Chip[C9]
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[41][98][1][0]@ChainID:[1], Chip[C9]
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[41][98][1][0]@ChainID:[2], Chip[C9]
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[41][98][1][0]@ChainID:[3], Chip[C9]
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[41][98][1][0]@ChainID:[0], Chip[C9]
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[41][98][1][0]@ChainID:[1], Chip[C9]
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[41][98][1][0]@ChainID:[2], Chip[C9]
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[41][98][1][0]@ChainID:[3], Chip[C9]
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[41][98][1][0]@ChainID:[0], Chip[C9]
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[41][98][1][0]@ChainID:[1], Chip[C9]
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[41][98][1][0]@ChainID:[2], Chip[C9]
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[41][98][1][0]@ChainID:[3], Chip[C9]
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[41][98][1][0]@ChainID:[0], Chip[C9]
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[41][98][1][0]@ChainID:[1], Chip[C9]
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[41][98][1][0]@ChainID:[2], Chip[C9]
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[41][98][1][0]@ChainID:[3], Chip[C9]
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: OK Chain 0 chip 0 local 0x12 remote 0x12 offset 0xfffffffa
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: Remote = 0 Chain 0 chip 1 local 0x0 remote 0x0 offset 0x14
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: OK Chain 1 chip 0 local 0x12 remote 0x10 offset 0xfffffff6
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: Remote = 0 Chain 1 chip 1 local 0x0 remote 0x0 offset 0x14
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: OK Chain 2 chip 0 local 0x10 remote 0x11 offset 0xfffffff9
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: Remote = 0 Chain 2 chip 1 local 0x0 remote 0x0 offset 0x14
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: OK Chain 3 chip 0 local 0x10 remote 0x10 offset 0xfffffff9
Apr  3 23:38:38 (none) local0.notice cgminer[8003]: Remote = 0 Chain 3 chip 1 local 0x0 remote 0x0 offset 0x14
Apr  3 23:38:39 (none) local0.notice cgminer[8003]: Dump IIC Data:[1][98][11][FA]@ChainID:[0], Chip[C]
Apr  3 23:38:39 (none) local0.notice cgminer[8003]: Dump IIC Data:[1][98][11][F6]@ChainID:[1], Chip[C]
Apr  3 23:38:39 (none) local0.notice cgminer[8003]: Dump IIC Data:[1][98][11][F9]@ChainID:[2], Chip[C]
Apr  3 23:38:39 (none) local0.notice cgminer[8003]: Dump IIC Data:[1][98][11][F9]@ChainID:[3], Chip[C]
13  Bitcoin / Mining support / Rapsberry Pi 1 controlling an Avalon AUC3 on: April 03, 2018, 01:45:19 AM
Hi all.  Received my first batch of Avalons today.  I went to set up (3) strings:  String 1 was headed by a pi 1 with a single 821 on it.  String 2 was headed by another pi 1 with (5) 841s on it.  String 3 was headed by a Pi 3 with (5) 841s on it.  Once I found real data cables to use with the AUC3s (and found out just how many charging only cables I have!), the Pi 3 unit came up just fine.

The (2) Pi 1 units had AUC3's that were mostly blue but slow blinking green.  e.g.  They were more-or-less always in setup mode and resetting as soon as they came ready.  The Avalons behind those two Pis remained idle (yellow light).

I moved the AUC3s from those Pis over to the Pi 3 and confirmed the AUC3s were fine, the cables were fine, and that the miners were fine.  Currently running all (11) Avalons off that single Pi 3.

Curious if anyone knows what the problem was driving the AUC3s from the Pi 1s?  I thought perhaps insufficient power supplies to drive both the Pi 1 and the AUC3, so tried a 2.4 amp one - but had no change.

Any other ideas?
14  Bitcoin / Mining support / Avalon heat rejection management question on: March 30, 2018, 04:47:24 PM
Hi all.  Running a farm of 100+ S9s.  Heat rejection for them is easy:  Stick the rear fan through your cold/hot aisle wall and the issue is solved (cold air in from the cold aisle, hot air out to the hot aisle).  Only downside is the power supply waste heat (7% of what is used, more or less) ends up in the cold aisle.

I have (11) Avalons coming on Monday and I've been trying to figure out an equally elegant cooling solution for them.  Alas their power connections are on the back of the machine, so if I played a similar game as I do with the S9s, I'd either need holes in the cold/hot aisle wall for power cables, or would need to put the power supplies in the hot aisle - which just doesn't sound like a good idea (and would involve some other minor redesign issues like moving power from the cold aisle to the hot aisle to avoid having the power cords going through the wall).

FWIW - I'll be using Bitmain APW3++ power supplies for the Avalons, mostly because I have an excessive quantity of them.  So many in fact that I've considered splitting them, with each power supply driving half of an 841.  e.g.   P - A - P - A - P...  That would at least prevent power cables from crossing the back of the exhaust area of the Avalons.

Any thoughts or suggestions?
15  Other / Meta / Is it possible to merge login stats? on: March 20, 2018, 03:46:48 PM
Wondering if its possible to merge profiles?

For personal reasons, I've abandoned my old Sr. Member account (although I still have access) and started using this one.

I would like to have that account disabled and the Activity points merged with this account.

Is that possible?
16  Bitcoin / Pools / Best pool rules on: March 18, 2018, 08:17:15 PM
In my opinion, more or less in order:

1)  Lowest fees - currently believe that is Kano.is at 0.9% with transaction sharing
1a)  Shares transaction fees - back in December, fees represented close to 40% of the per-block earnings at one point
1b)  Any pool that does NOT share transaction fees should be rejected from consideration (which, unfortunately, is most, if not all, Chinese based pools)

2)  Reasonable variance - you need to get paid often enough to be happy.  This is a tough one.  Comparing two pools that pass rule #1:

Slushpool - finds a dozen or so coins a day
Kano - finds a coin every few days
.
.
.
solo - only an option if you have several thousand miners or are good with getting a paycheck once a year or so or maybe never.

Variance is the close cousin to "luck".  The luckier a pool is, the more blocks it finds relative to its hashing speed, and the less variance it will have.  But its not a real thing!  "luck" could change any microsecond.
 "luck" is just mathematical statistics - over a long enough time period, all pools will average out to 100% luck.

You need to understand variance:  A big pool finds more blocks, but distributes the earnings out to more miners.  A small pool is just the reverse:  it finds fewer blocks, but pays those earnings to fewer people.  Over the long run, rule #1, well, rules.

3)  Wind-up/Wind-down time - most pools use some leveling algorithm.  Using the two above examples:

Slushpool - about 4 hours
Kano - about 12 days

4)  User Interface.  Slushpool wins hands down over Kano - but you pay over 2X in fees to have that privilege.  That doesn't matter much if you have a few miners.  If you have hundreds, the difference can be thousands of dollars a year.

Notes:

A) In the long run #2 & #3 really don't matter much.  Both pools show your hashing rate in minutes, payouts just lag on Kano compared to Slushpool, but would continue longer if you changed in the future
B) Bigger is not better.  Sure Antpool is #1 in size, in no small part to Bitmain using their own pool (no fees for them!).   Your profit will be determined mostly by rule #1 - lower fees mean more profit.
C) More, smaller, pools is healthier for the blockchain.  If you can live with the variance, support the pool with the longest average payout you are happy with.
D) For pools with long ramp up times that are relatively small, like Kano, you MIGHT suffer due to difficulty changes while you ramp up.  For smaller pools, make sure you understand what happens to your efforts (based on their scoring system) when a difficulty change occurs.

Personally, as I thought this over, I decided to switch my 1.3PH from Slushpool to Kano.
17  Other / Beginners & Help / With Bitcoin Core 16.0 wallet new receiving addresses are starting with a 3? on: March 17, 2018, 08:34:22 PM
Upgraded my wallet to 16.0 recently and generated a new receiving address.  Noticed it starts with a 3 now?  I thought that indicated a multi-sig address???  
18  Bitcoin / Mining speculation / S9 or 841 or... on: March 16, 2018, 07:53:20 PM
I run a farm of about 100 S9s currently.  I'm looking to do a purchase of a dozen or so more miners and am really torn on what to do.

Price/TH wise, especially with the coupons Bitmain has been providing, the S9 is still the winner.

However... the Avalon 841 has a lower power consumption/TH, worth about $100/year/miner to me in electrical savings/miner.  But they are more expensive, even with 2 years of running factored in.

However... adding more S9s now to add to the S9s I have been accumulating since June of 16 (yeah, I have a few Batch 1 S9s...)... well... they are feeling a bit old, architecturally.  Top that off with paying anywhere between $1296/S9 last April to $2725/S9 last December, and remembering them for around $1145 back in October, I have to believe that Bitmain will substantially drop their prices when they come out with their anticipated 14nm S11.  That would, of course, reduce the resale price for whatever I bought at todays relatively high $1915 (Even with $450 off coupons they are still more expensive than most in my farm).  Just looks what they did with T9s recently:  dropping from ~$2000 to $1400.

But... if I order S9s soon, I'll probably get about 20 more days of computing time.  At todays price & difficulty, thats about $6/day/miner after power cost.

And...  The next Canaan product, the 861, is close - but its just an 841 with an internal power supply - so no tech change.

Of course, if Bitcoin jumps to $25000 this December, anything bought now will appear to be a brilliant move.  But we are living in an $8500 bitcoin world today.

So.  Speculators:  Is anything coming in the next couple of months that will shatter the current price/performance/consumption curves?

What SHOULD I be worried about, given that I tend to buy about a dozen miners at a time as I fill my data center?  (e.g.  I re-invest as I go, so won't take a loan to buy 60-80 841's directly from China, although I keep thinking about that.)  FWIW:  The advantage of growing incrementally is that even mistakes get moderated out over time.  Of course, no quick riches either.

Your thoughts?

Oh, just to share on speculation:  Most of my Bitmain coupons expire in June.  Therefore I expect a major announcement and price drop on S9s shortly after expiration.
19  Bitcoin / Mining support / Burnt pin on: March 08, 2018, 07:22:08 PM
Hi all -

One of my S9s keeps dropping one card.  When I examine it, I see that one pin on the power connector is off-colored compared to everything else.  Often just resetting that connector will get the card up and running... for awhile.

Is there any way to clean that pin?  What would I use?
20  Bitcoin / Mining support / Will I brick a fixed frequency card by loading autofreq firmware? on: March 01, 2018, 08:30:34 PM
I have a couple of older fixed frequency S9s in my farm, including on 14TH one that is running at 13.6.

I'm just wondering what would happen I loaded one of the auto-freq firmwares?

My guess is that it would boot (controllers likely being compatible), but not find the cards?

Just thought I'd get some opinions before jumping...
Pages: [1] 2 »
Bitcointalk.org is not available or authorized for sale. Do not believe any fake listings.
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!