Crypto portfolio setup checker
Use these questions to prepare a safer review. This checker does not connect to accounts, calculate performance, or recommend an asset.
Prepared by Token Metrics Research Team. Source review date: July 14, 2026. Product terms can change; check the official sources below.
Important: never enter a seed phrase or private key into a tracker or tax tool. Use read-only permissions where available and keep independent records.
Disclosure: Token Metrics may earn compensation when readers use certain partner links. Compensation does not determine editorial coverage. This is general educational information, not investment, tax, legal, or custody advice.
Related guides in this research cluster
Sources checked
What this checker does: It turns three setup questions into a short next-step list. It does not connect to any account. It does not read a wallet, save an answer, calculate performance, or recommend an asset.
How to use it
Choose the answer that matches your setup today. Select the button once. Read the next step in the live output box. A “complete” result means only that you answered yes to the three checks. It does not prove that the records are right.
Use the result as a start for a manual review. Keep the account list and permission log outside this page. Never paste a seed phrase, private key, API key, balance, or tax record into the checker.
How to read the output
An account-list prompt means you may be missing a wallet, exchange, or old account. A record-review prompt means the import may have gaps, duplicates, or unmatched transfers. A privacy prompt means you have not yet checked rights and terms.
If all three answers are yes, the tool tells you to reconfirm the setup. It does not award a score. It does not say the tracker is safe, complete, or ready for tax work.
Method
The checker uses a simple rule. Each “no or unsure” answer adds one matching task. The order follows a dependency: list sources, review records, then review access and privacy. If there are no missing answers, it returns a reminder to check again before relying on the output.
There are no weights, hidden inputs, or numeric scores. The result is reproducible from the three visible answers.
Worked example
A reader has two exchanges and three wallets. The account list is complete, but one transfer appears twice. The reader also has not checked the exchange API rights. The answers are yes, no, and no.
The output calls for a record review and a permission review. The reader checks the transfer on both source accounts, fixes the duplicate if the product allows it, records the change, and narrows or revokes access.
Limits and safety
The checker cannot see whether an answer is true. It cannot test a connection, detect a leak, review a privacy policy, or find a missing account. It has no tax logic. It gives no custody or investment advice.
Treat a tracker as a copy of selected data. Keep direct records. The IRS digital-asset page is a starting point for federal reporting information. CISA guidance can help with phishing awareness, but your provider and account may need more controls.
Next steps
Open the product help center for the exact connection you plan to use. Check permission scope and revocation. Test a small source. Compare one known transfer and one ending balance. Export a sample.
If a required record is still wrong, stop before adding more sources. Ask the provider how the item is mapped. Keep a note of the date and answer.
Frequently asked questions
Does this checker store my answers?
The preserved module runs in the page and does not submit a form. Do not enter private data.
Does a complete result mean my portfolio is correct?
No. It only means all three visible answers were yes.
Can I use the result for taxes?
No. Keep source records and get qualified help for your facts.
Why is there no score?
The tool has three visible checks. A score would add false precision without evidence that one check should weigh more.
A safe way to repeat the check
Run the selector once with your current answers. Save the words in the output, not private data. Change one answer and run it again. Only the matching part of the next step should change.
If the result does not match the visible choices, stop and reload the page. Do not use the output as proof that an account, provider, or record is safe. The tool is a prompt for a human review.
Repeat the check when you add a source, change a permission, move from research to production, or find a missing record. The value is the next action, not a permanent badge.
What would change this decision
The next-step text should change only when the visible decision tree or a safety rule changes. A provider launch alone does not require a new result.
A change is not accepted from a headline alone. Open the primary page, note the date, and repeat the hard case. Keep the old finding until the new result can be checked. If the change affects only one region, plan, chain, or platform, say so rather than rewriting the whole verdict.
Readers should also revisit the choice when their own job changes. A tool selected for a quick view may be wrong for an audit trail. A tool selected for one public address may be wrong for a team API. Fit belongs to the task, so the update record must name the task.
