BrianSutioso
    • 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
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • 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
    • Note Insights
    • 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 Versions and GitHub Sync Note Insights Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
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
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    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
    --- tags: Writtens --- # White Paper :::info **Released:** May 4th, 11:59pm EST **Due:** May 16th, 11:59pm EST ::: :::danger There are **NO LATE DAYS** allowed for this assignment. You must submit your whitepaper by 11:59pm on May 16th. Anything later than that will receive a 0. ::: ## Introduction Like other technical domains, cryptocurrencies and blockchains tend to have underlying [white papers](https://en.wikipedia.org/wiki/White_paper)---documents designed to outline a project's goals, purpose, and underlying technologies (consensus algorithm, structure, etc...). You have two options for how you can complete this assignment, both requiring an understanding of whitepapers as well as their outlined components that you should have learned throughout this course. First, you should read a few famous white papers for reference. ## References Most of the following whitepapers won't delve too deep into the technicalities and specifics of their underlying technologies. Instead, they're meant to give a sense of how their creators dealt with issues such as **scaliblity, security, and consensus.** What seems to be the driving principles and philosophy behind the project; what problem are they trying to solve? --- #### [Bitcoin Whitepaper](https://bitcoin.org/bitcoin.pdf) The Bitcoin Whitepaper is most well known for its brevity. As you read, it may be helpful to consider how the preceding **2008 Financial Crisis** may have affected the principles, language, and design choices reflected in this whitepaper (so much so that Satoshi included a reference to it on the [Bitcoin Genesis Block](https://miro.medium.com/max/663/0*yXKX_m5U2m9UTWMM)). Additionally, consider the most sensationalized element of Bitcoin's whitepaper: the anonymity of [Satoshi Nakamota](https://en.wikipedia.org/wiki/Satoshi_Nakamoto). #### [Ethereum Whitepaper](https://ethereum.org/en/whitepaper/) A notable stylistic departure from Bitcoin's Whitepaper, Ethereum's Whitepaper is more rigorous. Arriving later to the party, Ethereum was influenced by Bitcoin's shortcomings, as can be seen in the [History](https://ethereum.org/en/whitepaper/#history), [Mining Centralization](https://ethereum.org/en/whitepaper/#mining-centralization), and [Scalability](https://ethereum.org/en/whitepaper/#scalability) sections in particular. #### [Monero Whitepaper](https://github.com/monero-project/research-lab/blob/master/whitepaper/whitepaper.pdf) CryptoNote (which would later become the basis for [Monero](https://en.wikipedia.org/wiki/Monero)) approached its whitepaper as a way to "study and propose solutions to the main deficiencies of Bitcoin", going so far as to have an entire section titled **"Bitcoin drawbacks and some possible solutions."** As such, it can be insightful to see what the developers saw as the primary shortcomings of Bitcoin. Additionally, Monero expands beyond the traditional cryptocurrency realms of scalability and consensus to challenge an issue not discussed as much in the previous whitepapers: **privacy**. --- Students are allowed (and encouraged) to study/select other whitepapers, such as [Solana's](https://solana.com/solana-whitepaper.pdf), [Binance's](https://www.exodus.com/assets/docs/binance-coin-whitepaper.pdf), and so on. Additionally you may use/look at blockchain technologies that don't have whitepapers and rather just bodies of research, such as [Cardano](https://whitepaper.io/document/581/cardano-whitepaper). A few recent samples of application based papers are also provided for your reference. [Coss.io](https://medium.com/@coss.io/coss-io-whitepaper-50ae43af2864), [Ailink](https://www.allcryptowhitepapers.com/ailink-token-whitepaper/), [Shikoku Inu](https://www.allcryptowhitepapers.com/whitepaper-of-the-week/), and [Alchemist](https://www.allcryptowhitepapers.com/alchemint-standards-whitepaper/). ## Assignment ### OPTION 1 - "CREATE" --- For this option, you are tasked with using everything you have learned about blockchain technology thus far to create your very own whitepaper. While this option is designed to be as freeform as possible, there are certain specifications your whitepaper must meet, such as containing a discussion about a consensus algorithm, previous whitepapers' shortcomings, and the issues you are trying to address. Consult the **grading section at the bottom of this page** for a full list of requirements. Feel free to be as creative, logical, or scientific as you want with your whitepaper. Some additional discussion points may be whether your whitepaper's creator decides to remain anonymous, how your whitepaper is acting as a response to the world's current circumstances, choosing a relevant/significant cryptocurrency name, etc... ### OPTION 2 - "CRITIQUE" --- For this option, you may pick 2 or more existing blockchain technologies and discuss their similarities and differences. There are certain characteristics you must mention, such as their purpose, their consensus algorithms, token issuance, etc... For a total list of the characteristics you must address, consult the **grading section at the bottom of the page**. After covering the required areas, we encourage you to explore more deeply the nuances between your selected blockchains, such as differences between how they came about and are/were developed (are they backed by a foundation, team, etc...), their popularity, and so on. ___ Your assignment must be **greater than 1000 words**, but **no more than 2000**. If you're worried you'll go over and have tons of great ideas, just let us know (privately) on Ed and we'll work something out. :::warning **When using sources, cite them!** Failing to do so constitutes plagiarism and will be dealt with as such. Pick your favorite citation method, and be sure to give credit where it's due. ::: ## Handin 1. Log into [Gradescope](https://www.gradescope.com/). 2. Submit your whitepaper as a PDF ## Grading This assignment is out of **100 points**. Your grade will be determined by whether or not your whitepaper contains sufficient discussion of the following topics: | Criteria (OPTION 1) | Points | |:-------------------------------------------------------- |:-------:| | *Consensus Algorithm* | 10 | | *Scalability, Security, and Resource-Efficiency* | 10 | | *Previous Whitepaper Shortcomings* | 20 | | *Goals and How Your Cryptocurrency Achieves Them* | 20 | | *Basic Cryptocurrency Structure (blocks, hashs, etc...)* | 20 | | *Method of Issuing Tokens* | 20 | | **Total** | **100** | | Criteria (OPTION 2) | Points | |:-------------------------------------------------------- |:-------:| | *Consensus Algorithm* | 20 | | *Scalability, Security, and Resource-Efficiency* | 20 | | | *Goals / Purpose / Philosophy* | 20 | | *Discussion of Basic Cryptocurrency Structure (blocks, hashs, etc...)* | 20 | | *Method of Issuing Tokens* | 20 | | **Total** | **100** |

    Import from clipboard

    Paste your markdown or webpage here...

    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 has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a 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

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    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
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    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

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

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

        Syncing

        Push failed

        Push successfully