IRC §6001 / Treas. Reg. §1.6001-1
Built to comply with — audit-defensible record-keeping
The federal record-keeping statute requiring taxpayers to maintain books and records sufficient to establish gross income, deductions, and other items — the legal foundation for audit-defensible staking records.
What the statute requires
IRC §6001 requires every person liable for any tax imposed by the Internal Revenue Code to keep such permanent books of account or records, including inventories, as are sufficient to establish the amount of gross income, deductions, credits, and other matters required to be shown on a return. Treasury Regulation §1.6001-1(a) implements this mandate and requires that records be retained as long as their contents may be material in the administration of any internal revenue law.
For ETH staking rewards, this means maintaining records that establish: the validator pubkeys and withdrawal addresses linking on-chain activity to the taxpayer; on-chain transaction hashes and block heights for every staking-reward withdrawal or payout event; the fair-market-value source and USD value used at the time of income recognition; and the recognition methodology chosen with its documented rationale.
IRS Publication 583 translates the §6001 obligation into practical retention guidance, recommending that records be kept for at least three years from the filing date — the baseline statute of limitations under IRC §6501(a). The six-year extended period under §6501(e)(1) applies when a taxpayer omits from gross income an amount exceeding 25% of stated gross income, making thorough records especially important for stakers with significant reward income.
IRS Notice 2014-21 anchors the FMV record-keeping requirement for digital assets: the record must capture the fair market value in U.S. dollars as of the date of receipt, from an exchange-rate source established by market supply and demand.
How TrueStake applies it
TrueStake's architecture is designed from the ground up around §6001 compliance.
Append-only event history. All reward receipts are recorded as immutable facts. No mutation or deletion of recognized reward data is permitted. The full chain of evidence from beacon-node API response to parsed event to income row is preserved.
Complete citation chain. Each income record carries references to the specific on-chain event that generated it and the specific price observation used to value it. An IRS examiner or the taxpayer's counsel can trace each income dollar back to its source in the raw chain data.
Raw payload retention. The original API response from the beacon and execution nodes is stored alongside every reward event. This means the source data underlying every FMV determination is auditable independently of TrueStake's derived output.
Audit-ready export. The tax report export includes a Provenance sheet linking each income row to the underlying event ID and price observation, and a Citations sheet listing the primary legal authorities relied upon. This format is designed to satisfy the practical record-production requirements that IRS examiners apply to digital-asset accounts.
Not tax advice. Consult a qualified tax professional regarding your specific circumstances.
Citations
- [1]IRC §6001 — Requirement to keep records· Statutory authority — books and records requirement
- [2]Treas. Reg. §1.6001-1(a) — Records to be kept· Regulatory implementation — permanent books of account
- [3]IRS Publication 583, Starting a Business and Keeping Records (Rev. Jan. 2021)· IRS practical record-retention guidance
- [4]IRC §6501(a) — Three-year limitations period· Statute of limitations — minimum retention floor
- [5]IRS Notice 2014-21, 2014-16 I.R.B. 938 (Apr. 14, 2014)· Anchors what records must be retained — FMV source, date, amount