@Andreas_CoinTracking 

Trading 5 eth + 5 schmocoin for liquidity  in the eth/schmocoin pool: Should I have 3 tx: spend 5 eth; spend 5 schmocoin; and what is the third?  How do I show a purchase of the LP tokens (with appropriate cost basis, and making sure that the incoming coin is not treated as income)?

@Andreas_CoinTracking
Oh thanks, I made a mess of some of those tx, but am repairing it.  

1. For my first "Swap" tx of Weth for Eth, I am getting 2 separate (duplicated) warnings for the exact same, single tx:
"Sell of xxx WETH
There is no suitable purchase to this swap trade (all purchasing pools consumed). Assuming purchase on the same day for 0 USD."
The previous purchases are 2 tx from several days prior, and clearly add up to enough weth and eth to make the tx.  It is the first warning when sorted by date, and I'm not sure how to get rid of this one.  Anything I'm overlooking?  I've tried manually set a Weth price for the prior purchases, but that doesn't seem to be the problem.  


2. I'm also running into problems when withdrawing more than one coin from a pool.  e.g. I deposited eth into curve pool and later remove (in same tx) eth + seth.  This seth, when later sold, has no cost basis even when I manually input it.  

@Andreas_CoinTracking
ty.  

When reviewing issues, I'm having trouble visualizing eg how much eth I have at a certain moment in time (and perhaps on what exchange).  This would be helpful when trying to find out what inputs I've messed up when I get a "short" error on taxes.  Is there any native asset 'viewer' that makes reviewing discrepancies easier than checking things out line by line?  

Also, any way to input trades with more than 1 input 1 output?  

---

When dealing with fees, is there a difference if they are inputted as stand-alone items vs. withdrawals vs deposits vs staking fees etc.?  Specifically in how they are used to do tax calculations for the USA, Germany.  

And are there "Undo" and "Redo" functions?  

@Andreas_CoinTracking

Great to know.  The extra deposit/withdraw seems redundant then.  Is it done to properly keep the record of the current value of my tokens?  (As the xxx-Gauge token is valued at 0 in the same transaction)? 
If so, I'm not sure why we couldn't just use the "trade" and "swap" trick as used above, or something similar.   Just thinking out loud.   


Also, I've imported as you might have guessed, the eth address using your import, and have put the eth address as the exchange name.  Do you recommend that or something else?

Thanks for the swap tip.  A great help.  


Staking e.g. ECRV on curve (the actual "Staking" tx):
1. normal tx fee   √
2. Non-taxable income on newly acquired ECRV-GAU  √
3. Withdrawal ECRV
4. Deposit ECRV

3, 4-- Is this updating my cost-basis?  If I want to keep original cost basis, can I simply combine 3,4, and group them as a swap?  

Question on WETH (swap unswap). 

I receive 1 WETH on Jan 1.  unwrap on Feb 1 for ETH.  wrap unwrap etc between two logically equivalent things. 

How do I correctly log the wrapping and unwrapping if I want to keep the original basis price and date for tax purposes on subsequent sale for a different non-equivalent token? 

Is there any canonical way I should be editing Opensea offer acceptances (for WETH)?   
Cointracking is currently showing "income" of 10 Weth for the offer.  In a separate line, it shows Coinbases take as a withdrawal (1 Weth).  Later, when I get my secondary sales income, the income is again added in (+0.1 Eth). 

I need to pay taxes on 10-1 Weth at time of sale and another 0.1 eth at time of secondary sale payment.  Is there a neat way to do this?

800mhz?  Remind me how to export mine for me?  I think the tables that everyone is using are lc tables, though.  Definitely check this thread.  My 3 Sapphire vega64 lc are pulling 545W from the wall, so probably 150W each.  I've got the fans on pretty low (low minimum and high max temp of 60 i think), but the rig seems to be fine (goes at least a week, no errors at least).  Also, max temp on the lc is 70.  Anything higher will cause you an error in overdriventool. 

I don't have that rig anymore, sorry. 
But if I remember correctly, I was using screen on the rig, and using a root user for screen (and thus sgminer), I sstopped the annoying errors, and it would reboot.  It probably wasn't the kosher way, but it got the job done. 

Upon every reboot, I have to try several times before my cards are recognized.  Does anyone else have that?  ie If I cut power (via 'restart' or physically with a switch), upon reboot, attempting to disable gpu's only results in one or two disabling (and conversely one or two are recognized)..  It varies which gpu's won't be recognized, but if they're unrecognized, disabling does not help me, so I attempt rebooting again.  I've changed out risers, but since it's a different gpu giving me problems every time, I'm stumped.  Sometimes I have to wait several minutes w/o power or plug in a physical monitor, but nothing seems to work 100%. 
When running, the rig will go for days at a time w/o a hitch, but if there's any day (like this morning) when I wake to find the power's been cut for a second, the miner will be idling because my script failed at startup.  Any ideas?

Please at least attempt to contribute to the conversation. 


Thanks for the real-world experience.  I don't know if I'm down to start diy'ing my own wires, but I'll at least keep an eye on them.  I did a little further combing and found an old post on tomshardware, which may or may not be true?  Either way, it's interesting.  I would love it if someone threw a mythbuster up on youtube for this one. 

""
Johnny & the group,

Have learned several interesting facts about the PCI-E plugs and power after researching it this past week, that is worth sharing

The PCI-E connecter has 6 pins. They are not all used for power. For the 6 pin connector, Pins 1 & 3 are 12V & each can carry 8 Amps. Pin 2 by spec is not connected, although some PSU manufacturers do add a 12V line there. Pins 4 & 6 are Com return lines. Pin5 is Com for sensing. Using 2 lines, you get 12V*8A*2= 192Watts, much over the required 75Watts. With an 8 pin PCI-E connector, 2 Com lines are added (4& not a 12V & Com. There, Pins 1,2,3 are 12V, Pin 4 is a Com for the 8 pin connector sensing, Pin 5,7,8 are Com return lines, & pin 6 is for the 6 pin connector sensing. Using that config, 12V*8Amp*3=288 Watts, much over the required 150Watts.

Since Mar 2005, the molex pins are required to be "HCS" rather than "Std", which each carry a max of 11Amps. So properly made, an 8 pin PCI-e can supply 12V*11Amps*3lines=396Watts of power for the graphic cards.

Ther aren't 4 12V pins on the 8 pin connector, only 3, and 2 leads are used for sensing the connector type.

The other limiting factor of course is the width of the PCB lines on the graphics card, each typically carrying 1-2 Amps. That would also determine how much power it could carry to the graphics electronics.
Also worth noting Scott Meuller in his latest 19th Ed of "Upgrading and Repairing PCs" has this information incorrectly listed.
""

Dual I understand.  Certified, I do not.  The whole world of cabling is new to me, however.  Is there a trusted certification authority or something?   Also, I haven't been able to find any 8-pin to 2x8-pin that seem to be from reputable vendors.  Everyone seems to make 6-pin ones, but the 8-pin ones seem harder to find.  Am I missing something or are larger vendors doing this intentionally? 

Per my little research..
Credit to stackexchange question.. "Is there any limit on how many SATA power connectors i can extend" (superuser). 
Helpful link was wire gauge to current rating..  Seems 18 gauge for short runs can max out at 16A, 16 gauge at 22A, which translates to roughly 12*16 and (or) 12*22. 
As per their nifty chart, they're saying (as conservative figures) for max load for  the different wires:

Gauge	Max Load
18	192
16	264

 
I could definitely be wrong.  So eat with salt.  But since everyone's undervolting, if they're using the 18 gauge, they're probably somewhere near the top end of the allowable range.  If the cards or software fault, however, and they start pulling 250+ from the psu (does anyone know what it pulls w/o the undervolt--has anyone measured the wire?), I guess it's anyone's chance if a fire starts/they begin to melt?  For posterity and the curious, I've got vega64 lc's running on these cords. 
If anyone's got wiring like this, but is NOT undervolting, I would be curious as to how long they've been running, how many watts they've been pulling, etc.  It's hard to find solid information out there. 

Please beat this dead horse for me.. 
I bought a Y-Splitter, 8-Pin pcie to 2x 8-pin pcie. 

https://www.amazon.de/adaptare-35118-Grafikkarte-Stromkabel-8-pin-PCIe-Stecker-Stecker/dp/B01N5JJ7DD
If that link gets taken down, search B01N5JJ7DD on amazon.de

No, I'm not advertising, I just want to be clear about my cables, because the whole . 

Is it the PSU that will be causing problems or the connections on the cable that I've got?  (or am I fine?)

I imagine that the problem would lie with the connection at the PSU end (where there is up to 250W going through those small wires), am I wrong?  What's wrong with my thinking that a more quality Y-Splitter would be able to handle the wattage? 

PS I've been mining about a week with two of these cables for 2 cards, and the other 2 cards using 2 separate cables each which came with the PSU (2x 8-pin to 8-pin).  Am I playing with fire?

I'm also 4x vega 64's, 1990 or so (though i am on lc if that matters).  You can definitely get that wattage down if you care.  I had zero problems with the reg mod (from hella).  Definitely worth a shot if you have an hour or two to spare. 
I've yet to test the new stak, but want to get that cpu up and running as well soon.  Hopefully push out another hundred h/s and check if it's worth it. 

Silly me, here I was thinking you were going to show us a beautiful marijuana garden living amongst your vegas. 

A single rx vega 56/64 can pull about 2000 hashes/second at about 150W if that's what you mean.

apropos eli5 shit, does anyone know some good introductory videos explaining on a more granular level how gpu's function, especially if they're in relation to mining? 
I think everyone gets that the name of the game is the most hashes for the least amount of energy spent.

I've been reading through the threads trying to glean a little knowledge and it's things like this that light me up. 

I've got the latest stable hwinfo64 5.60-3280.  When simply disabling GPU I2C support (that single check-box), my hash-rate drops.  Any other options I should be adding/dropping?  ... I think that it might be working now if I keep hwinfo64 open, reset my vegas, and then check temps.  Is that what you mean? 

Also, since talking temps, you said you set target to 50.  Is that via Wattman in Radeon Settings?  For some reason I was under the impression that the temp targets in wattman weren't effective and that it all had to be done manually.  Yes, I'm talking LC here.  I'm also interested in keeping fans down if possible. You said hbm temp 65-67 C.  Would you say over 70 is dangerous? 

You can flash the 64 bios onto the 56, so that's why people are getting the 56.  I've personally got a 64, because it just seemed easier and I don't have as much time as I used to.  If you find it fun and you're not doing this because you have free electricity, you should go with whatever you've got time for.  My vega rig wasn't very hard to get set up to mine at 150 or so watts.  at over 10 hashes per watt (xmr), that's a lot better than my rx480 rig is doing.  And it has been easier to set up so far. 

Hoping some linux or screen guru can help here with rebooting when a GPU is sick/dead. 

I've got the options configured correctly for sgminer-gm to attempt the reboot after gpu-failure, but since I'm not running sgminer as sudo, the program spits out a permissions error. 
I'm using screen to create a new session, start the miner at every boot.  I only run into a problem when a GPU flunks out on me, and I'm new to linux, so still learning systemd.  Does anyone know the proper way to let sgminer reboot when it attempts to? 

I'm on Ubuntu 16.04 kernel 4.8.3-040803-generic amdgpu-pro-16.50

Here's the error (from within the miner)..

Thread 0 still exists, killing it off
Failed to set wall message, ignoring: Interactive authentication required.
Failed to reboot system via logind: Interactive authentication required.
Failed to start reboot.target: Interactive authentication required.
See system logs and 'systemctl status reboot.target' for details.
Failed to open /dev/initctl: Permission denied
Failed to talk to init daemon.

GPU0: Not responded for more than 10 minutes, declaring DEAD!
running shutdown -r now
Failed to set wall message, ignoring: Interactive authentication required.
Failed to reboot system via logind: Interactive authentication required.
Failed to start reboot.target: Interactive authentication required.
See system logs and 'systemctl status reboot.target' for details.
Failed to open /dev/initctl: Permission denied
Failed to talk to init daemon.

"systemctl status reboot.target" shows..

My systemd service to start up the miner (which works fine afaik) is the following:

I'm thinking I should be able to elevate priveleges for certain screen sessions or maybe make an alias for the reboot command within that session (so that I am only changing the priveleges within that single command w/in that single session) but am having a hard time figuring out how.