HackMD
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
      • Invitee
      • No invitee
    • Publish Note

      Publish Note

      Everyone on the web can find and read all notes of this public team.
      Once published, notes can be searched and viewed by anyone online.
      See published notes
      Please check the box to agree to the Community Guidelines.
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Versions and GitHub Sync Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
Invitee
No invitee
Publish Note

Publish Note

Everyone on the web can find and read all notes of this public team.
Once published, notes can be searched and viewed by anyone online.
See published notes
Please check the box to agree to the Community Guidelines.
Engagement control
Commenting
Permission
Disabled Forbidden Owners Signed-in users Everyone
Enable
Permission
  • Forbidden
  • Owners
  • Signed-in users
  • Everyone
Suggest edit
Permission
Disabled Forbidden Owners Signed-in users Everyone
Enable
Permission
  • Forbidden
  • Owners
  • Signed-in users
Emoji Reply
Enable
Import from Dropbox Google Drive Gist Clipboard
   owned this note    owned this note      
Published Linked with GitHub
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 (Part 2) ![](https://i.imgur.com/DYu8uB3.jpg) Please [click the link to listen to the 85th episode](https://anchor.fm/5-minute-crypto-podcast/episodes/Five-Minute-Crypto--The-Bitcoin-Hodler-Rabbit-Hole-Risk-Part-2-egqlkb) 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-Part-2-egqlkb or ### https://open.spotify.com/episode/73M7CGrzOpSoWGcBHmNUHq?si=qbc0jW0GSWmBoj5Lw4YevA --- ## Transcript ## Five Minute Crypto–The Bitcoin Hodler Rabbit Hole: Risk (Part 2) > Some risks that are thought to be unknown, are not unknown. With some foresight and critical thought, some risks that at first glance may seem unforeseen, can in fact be foreseen. Armed with the right set of tools, procedures, knowledge and insight, light can be shed on variables that lead to risk, allowing us to manage them. > ― [Daniel Wagner](https://www.goodreads.com/quotes/tag/risk-management) --- Welcome to Five Minute Crypto - this week’s episode marks part two of our examination of the need to be risk aware and proactive if you intend to hold Bitcoin over the long term. As previously highlighted:A statement of hodling intent does not a hodler make. Part 1 focused on 2 broad areas of known risk – state bans and government or regulatory body restrictions and limitations. This week we turn our attention to protocol issues, bearish momentum, general fear, uncertainty, and doubt (FUD), and most pernicious of all - unrealistic expectations. **Protocol Issues** Despite its elegant design, BTC is not perfect – it is the product of human efforts, ongoing development, and implementation. As such, it is subject to error. In the past Bitcoin has indeed been found to contain bugs - some of them critical in nature. Notoriously – in 2010 a Bitcoin block contained an integer overflow bug that led to an exploit that created 184 billion BTC out of thin air. The exploit was noticed and hotfixed within a couple of hours but other serious bugs have been discovered before and since. In fact, dozens of code issues have been uncovered in the 11 years since Bitcoin first went live. These days the network and all of its transactions are heavily monitored – the dev community is not asleep at the wheel. The fact remains, however, that at some point another critical error or exploit may emerge. If the bug allows a double-spend or some other material impact on the network to occur – BTCs market value could and very likely would be hit hard. Understanding that BTC is not perfect is important to contextualizing any issues that do emerge in the coming years. **Bearish Momentum** Asset prices move in cycles – Bitcoin is no different in this regard. Where it does differ from other assets is to the degree with which it moves within a cycle and the volatility with which it does so. It a wild ride from new all-time highs to 90% retracements. With BTC – the highs and lows are very pronounced. While it’s relatively easy to hodl Bitcoin as it prints ever higher highs that is certainly not the case once the worm turns and turn it does and will again. How you choose to cope with these inevitable cycles is entirely up to yourself but you absolutely must anticipate and plan for them. It also worth being aware that Bitcoin is an entirely new asset class - its history is being written as we speak. All previous trends are drawn from thin previous price action. BTC is a mere 3 halvings into its issuance cycle so predictions based on previous performance should be viewed with substantial skepticism. For example, just because the last two halvings led to a steep price rise does not, in and of itself, prove that the current halving will have the same outcome or that BTC would be doomed if that were not to happen. Speaking of Doom. **Fear, Uncertainty, and Doubt** A broader category but one simply enough distilled to – think for yourself and always reflect before you act. Bitcoin’s community adopted motto – ‘verify don’t trust’ is particularly apt here. The cryptosphere and beyond is always going to be full of Bitcoin to zero narratives – some blatantly obvious – others seductively structured and argued. Somewhat perversely, the more you engage with crypto the more exposed you are to the doom and gloom that awaits BTC hodlers. Over time it can simply wear you down. Just as COVID-19 was the catalyst to a global market meltdown so too can a diet of FUD set you up to panic sell your holdings. **Unrealistic Expectations** Face it – you are probably lying to yourself right now. I’m in it for the long-run you glibly state. So, what exactly does that journey look like because for BTC – long should most likely be counted in decades or at the very least 3 or 4 full cycles. Three cycles – would take you to 2032 - are you really thinking at that kind of scale and if not -why not? We are surrounded by lofty price predictions -BTC to 50 thousand dollars by the end of 2021, no 100 thousand, no more, and on and on it goes. While it would be great for Bitcoin to hit such targets, you really are just setting yourself up to fail by placing to much credence in them. Be honest with yourself – do a little more research -see Bitcoin’s potential but remember you are going to most likely have to wait for it and longer than you would like! In summary, acknowledging, assessing, and preparing for Bitcoin risk events increases the likelihood of successfully navigating through them if and when they arise. As always, thanks for listening. --- Also published on [TIMM](https://mentormarket.io/category/cryptocurrencies/). ![](https://i.imgur.com/IwVSz4y.png)

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 lose their connection.

Create a note from template

Create a note from template

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

Create custom template

Upgrade

Delete template

Do you really want to delete this template?
Turn this template into a regular note and keep its content, versions, and comments.

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 with Wallet
Wallet ( )
Connect another wallet

New to HackMD? Sign up

Help

  • English
  • 中文
  • Français
  • Deutsch
  • 日本語
  • Español
  • Català
  • Ελληνικά
  • Português
  • italiano
  • Türkçe
  • Русский
  • Nederlands
  • hrvatski jezik
  • język polski
  • Українська
  • हिन्दी
  • svenska
  • Esperanto
  • dansk

Documents

Help & Tutorial

How to use Book mode

How to use Slide mode

API Docs

Edit in VSCode

Install browser extension

Get in Touch

Feedback

Discord

Send us email

Resources

Releases

Pricing

Blog

Policy

Terms

Privacy

Cheatsheet

Syntax Example Reference
# 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
19^th^ 19th
H~2~O H2O
++Inserted text++ Inserted text
==Marked text== Marked text
[link text](https:// "title") Link
![image alt](https:// "title") Image
`Code` Code 在筆記中貼入程式碼
```javascript
var i = 0;
```
var i = 0;
:smile: :smile: Emoji list
{%youtube youtube_id %} Externals
$L^aT_eX$ LaTeX
:::info
This is a alert area.
:::

This is a alert area.

Versions and GitHub Sync
Upgrade to Prime Plan

  • Edit version name
  • Delete

revision author avatar     named on  

More Less

No updates to save
Compare
    Choose a version
    No search result
    Version not found
Sign in to link this note to GitHub
Learn more
This note is not linked with GitHub
 

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.
      • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
      Learn more  Sign in to GitHub

      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
      Include title and tags
      Available push count

      Upgrade

      Pull from GitHub

       
      File from GitHub
      File from HackMD

      GitHub Link Settings

      File linked

      Linked by
      File path
      Last synced branch
      Available push count

      Upgrade

      Danger Zone

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

      Syncing

      Push failed

      Push successfully