Evernode host export
A host's transactions as CSV for your tax tool - rewards, lease income, refunds and reputation wallet transfers labelled.
- Your host account and, if you have one, its reputation wallet
- The days, the labels, what to leave out - change them after fetching, the table follows
- Download the CSV: one for the host, one for the reputation wallet
In most cases a minimum XAH amount is all you need: it cuts the hourly 1-drop payments. The files import into your tax program as they are; the columns - which, and what each is called in the file - are yours to set below.
What a row is. One transaction of the account's: one it sent (OUT) or one it received (IN) - a tenant's lease purchase counts as received, the host being the token's seller. Amounts have 8 decimals, negative when sent; Fee Amount is on the transactions the account sent. A failed transaction, and an offer, moved nothing: its amount is 0, and its fee is still there.
Labels. The first that fits: a transaction with your reputation wallet is a Transfer (between your own accounts); a memo with evnRefund, the refunds' label; with evnAcquireLease, the lease income's; EVR from the rewards account rHktfGUbjqzU4GsYCMc1pDjdHXb5CJamto, the rewards'. Anything else is left unlabelled for you or your tax tool to decide.
TxHash is the transaction's CTID, which identifies it as uniquely as a hash: open it at https://xahauwin.com/tx/CTID, or ask any node for it.
Fees. Every row the account sent carries its fee (Fee Amount). A transaction the filters leave out - a 1-drop heartbeat under the minimum, say - still cost one: with Keep the fees of left-out transactions those fees come as rows of their own - one per transaction, or with Group by day one a day - written as a fee paid on its own: Sent Amount the fees, labelled Cost (or Other fee), Fee Amount empty; the optional is_fee column says YES. The transactions themselves are not in the file, so no fee is counted twice.
Group by day sums a day's transactions of the same kind into one row - the same direction, currency, label, transaction type and outcome (failed ones apart) - dated the day, 00:00 UTC. A year of a host is then a few rows a day instead of dozens, for tax tools that charge by the row. Labelled transactions are grouped whoever the other account (all a day's lease income is one row); unlabelled ones only with the same account's, since only the account says what they are. A grouped row has no TxHash, ledger or memo - Aggregated Count says how many it holds - and Source or Destination only where all of them had the same. A transaction alone in its group is left as it is.
Where it comes from. WinDB, this site's index of the ledger, which follows it by a few minutes - a month at a time, and a month that has ended is kept, so asking again is quick. Rows, labels and files are made in your browser; nothing is sent anywhere.
Provided as is, for your own use and at your own responsibility; not tax advice - see the Terms & Conditions. Check the labels against your jurisdiction's rules.