A nonprofit organization receives a donation of 50 Solana tokens from a supporter. The donor needs documentation for a tax deduction. The nonprofit must record the asset’s fair market value on the donation date, track the receipt, and ensure compliance with IRS requirements for noncash charitable contributions. A self-custodial cryptocurrency wallet like Phantom introduces a new layer of operational complexity to this process because the organization controls its own private keys, maintains full responsibility for asset security, and must produce verifiable transaction records from a decentralized ledger rather than from a custodian’s statement.
The practical challenge for nonprofits is that cryptocurrency donation workflows were not designed with tax compliance in mind. Traditional charity accounting assumes a donation receipt from the receiving organization, often paired with a statement from a financial institution. Blockchain transactions are permanent and transparent, but the link between a wallet address and a donor’s identity is not automatic. A nonprofit using Phantom for digital asset management must bridge this gap: connecting transaction data on the blockchain to donor records, fair market value documentation, and the audit trail that satisfies both IRS requirements and donor expectations for tax deduction substantiation.
Understanding self-custodial responsibility in nonprofit governance
When a nonprofit adopts Phantom or any self-custodial wallet, it assumes direct custody of private keys and full responsibility for asset security. This is fundamentally different from a custodial arrangement with a bank or traditional exchange, where an institution holds the keys and maintains insurance, regulatory oversight, and recovery procedures. With a self-custodial wallet, there is no intermediary to restore a lost Secret Recovery Phrase, reverse an incorrectly sent transaction, or recover assets sent to the wrong address. The organization becomes its own custodian, which has significant implications for governance, internal controls, and tax documentation.
The IRS does not yet have specific guidance tailored to nonprofit custody of cryptocurrency, but the agency has made clear that noncash charitable contributions require substantiation from the receiving organization. For a donation of digital assets, the nonprofit must provide written acknowledgment that includes the date of receipt, a description of the property, and whether any goods or services were provided in return. When the organization controls a Phantom wallet, that acknowledgment must be backed by transaction data that the organization can retrieve and verify. A transaction hash from the Solana blockchain, for example, is permanently recorded and can serve as part of the audit trail, but only if the organization knows which wallet address belongs to which donor and has documented that connection at the time of receipt.
Governance frameworks should address who holds the Secret Recovery Phrase, how it is stored, and how multiple staff members can authorize transactions without exposing the recovery phrase to unnecessary risk. A common approach is to distribute the recovery phrase across multiple secure locations, require two staff members to authorize high-value transactions, and maintain a log of all wallet access and transfers. This adds procedural complexity, but it also creates the documented chain of custody that auditors expect and that the IRS may examine if a donation is later questioned.
Insurance presents another practical gap. Standard organizational insurance policies do not typically cover self-custodied cryptocurrency. A nonprofit considering Phantom adoption should consult its insurance broker to determine whether coverage exists and what conditions apply. Some policies may exclude cryptocurrency entirely, while others may require specific security controls such as multi-signature wallets or hardware device integration. Understanding this boundary before accepting large donations can prevent disputes when a loss occurs.
Fair market value documentation and the donation date
The IRS requires that noncash charitable contributions be valued at fair market value on the date of donation. For publicly traded cryptocurrencies like Solana or Ethereum, fair market value is typically established using exchange prices from a reliable source. If a donor transfers 50 SOL to a nonprofit’s Phantom wallet address on December 15, and SOL is trading at $130 per token on that date, the donation is valued at $6,500 for tax purposes. The nonprofit’s tax deduction is $6,500, and the donor can claim a $6,500 charitable deduction on their individual tax return if the organization is a qualified charity.
The critical step is establishing which price source is authoritative. Major cryptocurrency exchanges such as Coinbase, Kraken, and Binance publish prices that are widely used for tax purposes. A nonprofit should adopt a written policy specifying which data source it will use—for example, “the Coinbase price at 11:59 PM UTC on the donation date” or “the CoinGecko historical price at market close.” This consistency matters if an IRS examination occurs. Using different price sources for similar donations, or using prices from illiquid exchanges, can raise questions about whether the valuation was genuinely representative of fair market value.
Price volatility is significant. If a donor indicates intent to donate on one date but the transaction settles on a different date due to network confirmation delays, blockchain fees, or donor error, the fair market value is based on the settlement date, not the intent date. A nonprofit should clarify this with donors in advance and confirm the transaction date once the blockchain confirms the transfer. With Phantom’s transaction preview feature, donors can verify the transaction details before signing, reducing the likelihood of sending to the wrong address, but the organization still bears responsibility for recording the correct valuation date based on when the blockchain actually recorded the receipt.
For NFTs or less liquid tokens, valuation becomes more subjective. If a nonprofit receives a donation of an NFT with no recent sales history, or a token trading on a low-volume exchange, determining fair market value requires either a qualified appraisal or a documented method that reasonably reflects market conditions. The IRS may challenge donations of illiquid or unique assets valued at high amounts without supporting documentation. A nonprofit accepting such donations should budget for an independent appraisal and retain that appraisal as part of the donation file.
Connecting blockchain addresses to donor identity
A blockchain address is pseudonymous. The address “EPjFWaJrnUguAPiFz5nXqkRPC5THc5ZBYdqeKvTekBXM” (Solana’s USDC token) tells observers that a transaction occurred, but it does not inherently reveal who the donor is. For a nonprofit to issue a valid tax deduction letter, it must know who made the donation. This requires a separate process outside the wallet itself: the donor must communicate their identity to the nonprofit, and the nonprofit must correlate that identity with the wallet address used for the donation.
Best practice is to establish a documented chain of communication. When a donor expresses interest in contributing cryptocurrency, the nonprofit should request the donor’s legal name, address, tax ID, and the blockchain address from which they will send the donation. Once the transaction is confirmed on the blockchain, the nonprofit compares the sending address to the address provided, confirming the match. This creates a documented connection between identity and address. If the donor uses a shared wallet, a hardware wallet custodied by a third party, or multiple addresses, that complexity should be resolved before the donation is accepted.
Phantom’s interface allows a nonprofit to see the receiving address in the wallet app, and donors can share their sending address once they initiate a transaction or obtain it from the wallet details. The organization should record this information in its donor management system or accounting software, alongside the transaction hash and the fair market value as of the donation date. Some nonprofits use a simple spreadsheet; others integrate blockchain monitoring tools that automatically detect transfers to specific wallet addresses and flag them for manual review and matching to donor records.
Privacy considerations arise here as well. A nonprofit that makes donations public—for example, by publishing blockchain addresses or transaction hashes—may inadvertently reveal donor identity if a donor’s sending address is linked elsewhere online to their legal name. A nonprofit should consult its privacy and donor communication policies before publishing donation transaction data. Blockchain data is permanent and public, but the nonprofit’s own disclosure practices can affect donor privacy expectations.
Maintaining audit-ready documentation within organizational systems
The blockchain creates an immutable record of when a transaction occurred and how much was transferred, but the blockchain is not the nonprofit’s accounting system. A nonprofit must record the donation in its own systems—grant management software, accounting platforms, or donor databases—with supporting documentation that connects the blockchain data to the organization’s financial records. This dual documentation requirement is essential for audits, because an external auditor will examine the nonprofit’s books, not the blockchain directly.
A well-structured donation file should include: the donor’s name and contact information; the date of donation (blockchain settlement date); the blockchain address that received the donation; the transaction hash; the quantity of asset transferred; the fair market value per unit on the donation date; the total donation value; the data source used to establish fair market value; the nonprofit’s tax identification number and the donor’s tax identification number if provided; and a copy of the written acknowledgment sent to the donor. For NFT donations, add the NFT’s contract address, token ID, and (if applicable) a link to the NFT or a screenshot showing the asset. This documentation should be retained for at least seven years in case of IRS examination.
Integration with accounting software can reduce manual entry errors. Many nonprofit accounting platforms support cryptocurrency receipt workflows or can be customized through integrations. The goal is to ensure that a donation recorded in Phantom’s transaction history can be traced through the organization’s general ledger, matched to the donor record, and supported by the underlying blockchain evidence. If an auditor or the IRS requests documentation of a donation, the nonprofit should be able to produce the full chain: donor identification, blockchain transaction, fair market value documentation, nonprofit acknowledgment letter, and ledger entry.
The nonprofit should also document its procedures for valuing cryptocurrency, securing the wallet, and authorizing transactions. Written policies demonstrate that the organization is following reasonable governance practices and makes it easier to train new staff members who may handle donations. If two people are required to approve transactions above a certain threshold, that policy should be documented and followed consistently. This operational discipline, while it may seem burdensome, is precisely what separates legitimate nonprofit practice from casual handling of donations.
Tax deduction substantiation and donor communication
The IRS requires that a charitable organization provide a written acknowledgment to donors for noncash contributions of property. For cryptocurrency donations, this acknowledgment should state the date of receipt, describe the property (for example, “50 Solana tokens” or “one NFT identified as [contract address, token ID]”), and confirm whether any goods or services were provided in return. If the nonprofit provides nothing of value in return, the letter should state that explicitly. The letter should include the nonprofit’s legal name, tax ID, and a statement that the organization is a qualified charity for tax purposes.
Critically, the letter should not include a value. The IRS prohibits the receiving organization from valuing noncash contributions in the acknowledgment letter. The donor is responsible for determining fair market value, and if the donation exceeds $5,000, the donor must obtain a qualified appraisal from an independent appraiser and file Form 8283 with their tax return. The nonprofit’s letter should acknowledge receipt and describe the property, but the valuation decision belongs to the donor and their tax professional. This distinction protects the nonprofit from liability if the IRS later challenges the valuation.
Timing is important. The IRS generally requires that the written acknowledgment be provided no later than the date the donor files their tax return, but best practice is to send it within 30 days of receipt. A nonprofit using Phantom for digital asset management should establish a process that confirms the blockchain receipt, verifies donor identity, and generates the acknowledgment letter with minimal delay. Delays in issuing acknowledgments can frustrate donors and complicate their tax filing.
Donors often have questions about tax treatment. A nonprofit staff member should be prepared to explain that the organization cannot provide tax advice, but can confirm what was received and when. A nonprofit may benefit from creating a simple guide for donors explaining how cryptocurrency donations work, what documentation will be provided, and recommending that donors consult a tax professional. Directing donors to resources like IRS Publication 561 (Determining the Value of Donated Property) or Publication 526 (Charitable Contributions) can help them understand their own filing obligations.
Multi-blockchain considerations and bridge transactions
Phantom supports digital asset management across multiple blockchain networks including Solana, Ethereum, Base, Polygon, Bitcoin, Sui, HyperEVM, and Robinhood Chain. A nonprofit that accepts donations on multiple networks must apply the same fair market value and documentation procedures to each network. A donation of 10 Ethereum on the Ethereum network, and a donation of 10 Ethereum through Wrapped Ethereum on the Polygon network, are technically different assets. Both have value based on market price, but the nonprofit must document which network the donation was received on and ensure that the donor understands the distinction.
Phantom’s asset bridging feature allows users to move assets between networks, but bridging introduces additional transaction fees and technical complexity. From a tax and documentation standpoint, a bridging transaction is a separate transaction from the donation itself. If a donor intends to donate USDC on Polygon but bridges the funds from Ethereum, the donation date is the date the USDC arrives on Polygon, not the date the bridge transaction was initiated. The fair market value is based on the date of Polygon receipt. A nonprofit should clarify with donors whether they will donate directly on a specific network or whether they plan to bridge first, to avoid confusion about the donation date.
Network transaction fees are paid to blockchain validators, not to the nonprofit, but they affect the amount actually received. If a donor intends to donate 1 Ethereum but pays $20 in gas fees, the nonprofit receives 1 Ethereum minus the gas cost of the receiving transaction. The fair market value of the donation is the full 1 Ethereum (assuming that is what was sent), but the nonprofit may wish to clarify with donors that network fees are their responsibility and may reduce the net amount after the transaction settles. This is a reasonable donor expectation-setting conversation and reduces disputes about the donation amount.
If a nonprofit offers donors the ability to donate across multiple networks, it should maintain consistent procedures for recording, valuing, and acknowledging donations on each network. The blockchain network, the sending and receiving addresses, the transaction hash, and the date of receipt should all be documented. A spreadsheet or software integration that captures this information consistently reduces the likelihood of errors and creates a clear audit trail across all networks on which the organization accepts donations.
Security, insurance, and loss prevention in nonprofit custody
Because Phantom is a self-custodial wallet, the nonprofit bears full responsibility for securing the Secret Recovery Phrase and preventing loss or theft of assets. The wallet cannot reverse transactions, reset a lost recovery phrase, or restore assets sent to an incorrect address. These limitations mean that a nonprofit must implement robust security controls and operational procedures to protect donated assets. Network transaction fees are paid to validators once a transaction is confirmed; they cannot be recovered, so careful review of transaction details before signing is critical.
Multi-signature wallets or hardware integration with devices like Ledger can increase security by requiring multiple approvals for withdrawals or key access. A nonprofit might implement a policy requiring that the Secret Recovery Phrase be stored in two secure locations, that two staff members be required to authorize transactions over a certain threshold, and that all transactions be logged for review. These controls add procedural overhead, but they align with nonprofit governance standards and reduce the risk of accidental or fraudulent loss.
Insurance is a gap that many nonprofits overlook. Standard organizational insurance policies do not typically cover self-custodied cryptocurrency losses. A nonprofit considering Phantom adoption should discuss this with its insurance broker and consider whether specialized cybersecurity or digital asset insurance is available and economically justified. For organizations with limited cryptocurrency donation volumes, the cost of insurance may exceed the value of donations received, in which case the organization might decide that the risk is acceptable. For organizations with larger holdings or aspirations to raise significant cryptocurrency donations, insurance should be part of the financial planning.
Regulatory changes also merit monitoring. While current IRS guidance does not specifically address nonprofit self-custody of cryptocurrency, future regulations could require custodial arrangements, reporting requirements, or specific security standards. A nonprofit should stay informed of IRS updates, state registration requirements if applicable, and any guidance from nonprofit associations or sector peers. Having a clear written policy on cryptocurrency acceptance, custody, and valuation creates a foundation for adapting to regulatory changes when they occur.
Building a scalable donation workflow and technical integration
Small nonprofits may handle cryptocurrency donations manually: a donor provides their wallet address before sending, the organization monitors its Phantom wallet for the receipt, and staff members confirm the transaction on the blockchain explorer and match it to the donor record. This process works for occasional donations but becomes unwieldy as volume increases. Larger nonprofits should consider technical integrations that automate parts of the workflow. You can read more about Phantom’s capabilities and consider how they might integrate with your organization’s systems.
Blockchain monitoring services can watch specific wallet addresses and alert staff when transfers are detected. Donor management systems can be configured to flag cryptocurrency donations for review and matching to donor records. Accounting software can import blockchain data or accept manual entry linked to transaction hashes. The goal is to create a workflow where donations are recorded promptly, linked to donors, valued correctly, and documented sufficiently for audit purposes without requiring manual intervention at every step.
Standardizing on particular currencies or networks can also simplify operations. Rather than accepting donations on every blockchain Phantom supports, a nonprofit might decide to accept Solana, Ethereum, and Bitcoin, and direct donors to those networks. This reduces the complexity of fair market value documentation, fee structures, and wallet management. As the organization gains experience, it can expand to additional networks if there is clear donor demand.
Training for staff members who handle cryptocurrency donations is essential. A nonprofit should document its procedures, ensure that at least two people understand the process, and create a runbook or checklist that covers donation receipt, identity verification, blockchain confirmation, fair market value lookup, acknowledgment letter generation, and accounting entry. Staff turnover is a normal reality in nonprofits; clear documented procedures ensure continuity and reduce the risk that cryptocurrency donations are handled inconsistently or incompletely.
Frequently asked questions
What documentation does a nonprofit need to provide to donors for a cryptocurrency donation?
The IRS requires a written acknowledgment that includes the date of receipt, a description of the property (for example, “50 Solana tokens”), and whether any goods or services were provided in return. The acknowledgment should not include a valuation; the nonprofit should confirm receipt and let the donor determine fair market value and obtain a qualified appraisal if the donation exceeds $5,000. The acknowledgment must include the nonprofit’s legal name and tax ID.
How is fair market value determined for a cryptocurrency donation?
Fair market value is established using exchange prices from a reliable source such as Coinbase, Kraken, or CoinGecko, based on the date the donation was received (the blockchain settlement date). A nonprofit should adopt a written policy specifying which data source it will use, to ensure consistency across donations. For illiquid tokens or NFTs without recent sales history, the organization may need to obtain a qualified independent appraisal.
Can a nonprofit reverse a transaction or recover assets sent to the wrong address in Phantom?
No. Phantom is a self-custodial wallet, and the blockchain transactions it executes are permanent and irreversible. The nonprofit cannot reverse transactions, reset a lost Secret Recovery Phrase, or restore assets sent to an incorrect address. This is why careful transaction review before signing and secure storage of the recovery phrase are critical. A nonprofit using Phantom must implement strong internal controls and governance procedures to prevent errors and unauthorized transactions.
