Bibliographic record
Abstract
Current Canada Revenue Agency (CRA) guidance suggests that cryptoassets (such as bitcoin) should generally be taxed as commodities for the purposes of the Income Tax Act. However, recent changes in the regulation of entities that facilitate the purchase and sale of cryptoassets (crypto trading platforms) under securities law have introduced new ways of understanding transactions involving cryptoassets. Many crypto trading platforms hold cryptoassets on behalf of users rather than delivering the cryptoassets directly to them, and the Canadian Securities Administrators has taken the position that this relationship among crypto trading platforms and their users itself constitutes a security. To date, there has been no guidance from the CRA relating to the taxation of these securities, which are known as "crypto contracts." This article considers potential income tax implications arising from the existence of crypto contracts by exploring how income taxation would differ for users of crypto trading platforms if they were taxed on crypto contracts rather than cryptoassets. Specifically, the article considers the treatment of transactions as being on income or capital account, the availability of elections to treat transactions on capital account, the applicability of section 49.1 of the Income Tax Act, and the income taxation of staking rewards earned through crypto trading platforms. Rather than offering conclusions on these topics, this article aims to provide a framework for thinking about crypto contracts from a Canadian income tax perspective and to provoke further thought from Canadian tax professionals.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.002 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.000 | 0.001 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one teacher head, not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".