HackMD
  • New!
    New!  “Bookmark” and save your note
    Find a note that's worth keeping or want reading it later? “Bookmark” it to your personal reading list.
    Got it
      • Create new note
      • Create a note from template
    • New!  “Bookmark” and save your note
      New!  “Bookmark” and save your note
      Find a note that's worth keeping or want reading it later? “Bookmark” it to your personal reading list.
      Got it
      • Options
      • Versions and GitHub Sync
      • Transfer ownership
      • Delete this note
      • Template
      • Save as template
      • Insert from template
      • Export
      • Dropbox
      • Google Drive
      • Gist
      • Import
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
      • Download
      • Markdown
      • HTML
      • Raw HTML
      • ODF (Beta)
      • Sharing Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Note Permission
      • Read
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • More (Comment, Invitee)
      • Publishing
        Everyone on the web can find and read all notes of this public team.
        After the note is published, everyone on the web can find and read this note.
        See all published notes on profile page.
      • Commenting Enable
        Disabled Forbidden Owners Signed-in users Everyone
      • Permission
        • Forbidden
        • Owners
        • Signed-in users
        • Everyone
      • Invitee
      • No invitee
    Menu Sharing Create Help
    Create Create new note Create a note from template
    Menu
    Options
    Versions and GitHub Sync Transfer ownership Delete this note
    Export
    Dropbox Google Drive Gist
    Import
    Dropbox Google Drive Gist Clipboard
    Download
    Markdown HTML Raw HTML ODF (Beta)
    Back
    Sharing
    Sharing Link copied
    /edit
    View mode
    • Edit mode
    • View mode
    • Book mode
    • Slide mode
    Edit mode View mode Book mode Slide mode
    Note Permission
    Read
    Owners
    • Owners
    • Signed-in users
    • Everyone
    Owners Signed-in users Everyone
    Write
    Owners
    • Owners
    • Signed-in users
    • Everyone
    Owners Signed-in users Everyone
    More (Comment, Invitee)
    Publishing
    Everyone on the web can find and read all notes of this public team.
    After the note is published, everyone on the web can find and read this note.
    See all published notes on profile page.
    More (Comment, Invitee)
    Commenting Enable
    Disabled Forbidden Owners Signed-in users Everyone
    Permission
    Owners
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Invitee
    No invitee
       owned this note    owned this note    
    Published Linked with
    Like BookmarkBookmarked
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    # Five Minute Crypto – The Bitcoin Hodler Rabbit Hole: Risk ![](https://i.imgur.com/IVIt0GC.jpg) Please [click the link to listen to the 84th episode](https://anchor.fm/5-minute-crypto-podcast/episodes/Five-Minute-Crypto--The-Bitcoin-Hodler-Rabbit-Hole-Risk-eg7624) of my weekly crypto podcast ‘Five Minute Crypto.’ These are intended to be short, single-topic ramblings on some aspect of the cryptosphere. Consider dropping a like and or a review on [iTunes](https://anchor.fm/5-minute-crypto-podcast) or [Podbean](https://cryptosdecrypted.podbean.com/) if you enjoy the podcast. Comments and critiques welcome. --- ## Podcast Links ### https://anchor.fm/5-minute-crypto-podcast/episodes/Five-Minute-Crypto--The-Bitcoin-Hodler-Rabbit-Hole-Risk-eg7624 or ### https://open.spotify.com/episode/0MN18TQlFMTFSZGe42BM6I --- # Transcript ## Five Minute Crypto – The Bitcoin Hodler Rabbit Hole: Risk Welcome to Five Minute Crypto – today marks part one of a two-part series exploring the vital importance of assessing and planning for the known risk factors that may affect Bitcoin in the coming years. A simple caveat before we begin – when outlining future risk events I’m drawing on my own understanding of Bitcoin, and the broader economic, financial and political systems within which it exists. I’ve highlighted many of these in previous episodes, a justification for each perspective expressed lies beyond the scope of this particular instalment. For example, my view on the probability of a China BTC ban has already been outlined in a five-part series which I will link in the transcript. *A statement of hodling intent does not a hodler make.* Simply buying BTC and waiting for number go up is a recipe for dashed hopes and eventual capitulation. The journey to BTC financial relevance is certain to be a rocky one. If you fail to reflect on what you will do should certain negative events occur you are simply setting yourself up to fail as a kneejerk emotional response to a situation you haven’t considered is much more likely to occur when you haven’t already thought it through. As [Benjamin Franklin](https://www.goodreads.com/author/quotes/289513.Benjamin_Franklin) put it – ‘By failing to prepare, you are preparing to fail.’ First and foremost – you absolutely must take on board the reality that the current financial system and those that benefit from it are not simply going to roll over and fade quietly into the night. This is an entirely naïve perspective that flies against the whole of human history. Roll up your hodler sleeves – because you are going to have to fight for it. By calmly assessing risk factors before they occur you are laying the groundwork for a more rational reaction if and when they do play out. Planning empowers you in your assessment of whether to sell, buy or sit it out. Can you precisely anticipate the challenges ahead – of course not - but you can forearm yourself to some extent as certain negative outcomes are much more probable than others. Broadly speaking BTC risk can be broken down into five areas – two which are addressed here: ### **Bans** With almost absolute certainty bans await BTC. While it is relatively easy to shrug off such actions by developing or marginalized nations; have you considered the impact of a total Chinese or USD ban on Bitcoin? Doubting that China will ban Bitcoin – completely misses the key driver of the Chinese Communist Party – control and ever more of it. Money is a fundamental pillar of state control. The CCP is simply not going to allow a competitor to their remit over money. The only question is timing and extent. When and to what degree will they seek to ban BTC. Additionally, the CCP will likely target mining too. Any move will be coordinated and intended to have maximum effect. A sharp selloff seems eminently likely in this scenario. BTC could plunge 50% or more and stay there for a prolonged period of time. The doomsayers would emerge in droves. Is this a scenario where you too would lose faith in BTC? Probably best to think on it now. In a similar but less predictable vein, the US may adopt a draconian approach. Do you really view Donald Trump and Mnuchin as crypto friendly? The odds of a ban on BTC over the short to medium term are in my opinion roughly 50-50. Once again, the market would plunge on even the rumour of such an event. What would you do? Any US ban would likely be partial and temporary but would you know that in the moment? ### **Restrictions / Taxes / Access** In tandem with outright bans – restrictions are a near inevitability in the coming years. From punitive taxation to limitations on banking relationships, governments the world over are more likely to seek to harness BTC than simply embrace its quiet revolution. Of course, your mileage will vary. Aside from international financial regulatory bodies such as the Financial Stability Board (FSB) and the Basil Committee on Banking Supervision (BCBS) each jurisdiction will approach regulation and control within the context of their own regulatory environment. The Swedes for example – already enjoy freedoms beyond that of most other nations albeit with a high tax burden. In that context, Tax then might an area worth considering. In contrast, the UK, has long demonstrated a mild antipathy towards Bitcoin particularly the BOE – further anti-money laundering measures, etc. can and should be expected or at the very least planned for. In the US a host of regulatory bodies have the ability to restrict access to and the use of BTC – the SEC, FinCEN, and the CFTC are just three examples. Given the tendency to play political football with almost any issue -COVID-19 included it would be incredibly naïve to expect Bitcoin to escape such treatment. Once again when it comes to Bitcoin – verify don’t trust. In this context, don’t trust that all will be well – it will not. Bans, restrictions and limitations will punctuate your hodling journey. If you hope to weather them – plan, note your thoughts, and from time to time revisit that plan. Indeed, you may decide that certain events would cause you to sell a portion or all of your position – that’s of course, entirely up to yourself. Next week we’ll turn our attention to other areas worthy of reflection – protocol issues, bearish momentum, general FUD, and most pernicious of all - unrealistic expectations. Thanks for listening. --- Also published on [TIMM](https://mentormarket.io/category/cryptocurrencies/). ![](https://i.imgur.com/kQG71zt.png) --- # Related Resources https://mentormarket.io/cryptocurrencies/cryptos-decrypted/two-minute-crypto-deciphering-chinas-blockchain-play-part-1-of-5/ https://mentormarket.io/cryptocurrencies/cryptos-decrypted/two-minute-crypto-how-to-hodl-bitcoin/ https://mentormarket.io/cryptocurrencies/cryptos-decrypted/five-minute-crypto-the-bitcoin-hodler-rabbit-hole-saving/

    Import from clipboard

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lost their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template is not available.
    All
    • All
    • Team
    No template found.

    Create a template

    Delete template

    Do you really want to delete this template?

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in via Google

    New to HackMD? Sign up

    Help

    Documents

    Tutorials
    YAML Metadata
    Slide Example
    Book Example

    Contacts

    Talk to us
    Report an issue
    Send us email

    Cheatsheet

    Example Syntax
    Header # Header
    • Unordered List
    - Unordered List
    1. Ordered List
    1. Ordered List
    • Todo List
    - [ ] Todo List
    Blockquote
    > Blockquote
    Bold font **Bold font**
    Italics font *Italics font*
    Strikethrough ~~Strikethrough~~
    19th 19^th^
    H2O H~2~O
    Inserted text ++Inserted text++
    Marked text ==Marked text==
    Link [link text](https:// "title")
    Image ![image alt](https:// "title")
    Code `Code`
    var i = 0;
    ```javascript
    var i = 0;
    ```
    :smile: :smile:
    Externals {%youtube youtube_id %}
    LaTeX $L^aT_eX$

    This is a alert area.

    :::info
    This is a alert area.
    :::

    Versions

    Versions and GitHub Sync

    Sign in to link this note to GitHub Learn more
    This note is not linked with GitHub Learn more
     
    Add badge Pull Push GitHub Link Settings

    Version named by    

    More Less
    • Edit
    • Delete

    Note content is identical to the latest version.
    Compare with
      Choose a version
      No search result
      Version not found

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub

        Please sign in to GitHub and install the HackMD app on your GitHub repo. Learn more

         Sign in to GitHub

        HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully