Ismael-KG
    • 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
    • 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
    • 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
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
# Pre-publication Peer review! ###### tags: `The Timeline` :::info Hi there! Thanks for dropping by! If you would be so kind as to review the below possible chapter(s) for [*An Incomplete History of Research Ethics*](https://www.tiki-toki.com/timeline/entry/1753034/A-History-of-Research-Ethics/), please make sure you have the "split view" of this site (click **[here](https://hackmd.io/VW6SvaOYTemXnOd4SMcC4Q?both)** if you can't see two panes; note this is best viewed on tablets or larger screens), and either: * Log into HackMD to type straight into the text on the left pane, which contains text in "**[markdown](https://github.com/adam-p/markdown-here/wiki/Markdown-Here-Cheatsheet)**," or * Without needing to log in, you can highlight sections on the right pane (with rendered text on a white background) to add comments anonymously. Afterwards, if you share your name when signing up to HackMD, you will appear as a contributor in the story! Contributions are acknowledged following [**Protocol 3**](https://github.com/Ismael-KG/A-History-of-Research-Ethics/blob/main/Protocols.md#Protocol-3-Contribution-Types). ::: # Texts for Review | Title | Issue # | Begin pre-review | End pre-review | | --- | --- | --- | --- | | CE 1991 How To Time-Stamp a Digital Document by Haber & Stornetta | [95](https://github.com/Ismael-KG/An_Incomplete_History_of_Research_Ethics/issues/95) | 04-Apr 2022 | 16-Apr 2022 | ## CE 1991 How To Time-Stamp a Digital Document by Haber & Stornetta ### Intro Haber & Stornetta introduce the idea of "distributed trust" in the context of blockchain technology, the foundation of cryptocurrencies. ### The story On 14 February 1876, Elisha Gray's lawyer paid the US Patent Office a visit. The lawyer was to apply for a "caveat," a sort of patent, for Gray's invention of a device that could transmit voice for people to communicate with one another. On the same day, Alexander Graham Bell's lawyer applied for a patent for Bell's device, which was rather similar. On that day, Bell got the patent and crowned himself as the inventor of the telephone. However, it is debateable that this was done fairly (Science Reference Section, Library of Congress, [2019](https://www.loc.gov/everyday-mysteries/item/who-is-credited-with-inventing-the-telephone/)). Ideally, the patent - or "caveat" - would have gone to whomever applied first. Whilst historians continue to discuss who really invented the telephone, Haber and Stornetta ([1991](https://doi.org/10.1007/BF00196791)) suggest a technological solution for cases like these. In 1991, Haber and Stornetta proposed a computational approach to time-stamping documents. The aim was to ensure the validity of claims about documents' time-stamps. In other words, they wanted a system whereby activities concerning documents (creation, editing, sending, receiving...) could not have their time-stamps falsified. Haber and Stornetta speak of a time-stamping service (TSS), which would work much like Gray and Bell's Patent Office. However, the TSS might be corrupt or make mistakes. They suggest "hashing" as an approach to ensuring that claims are valid. A hash function is a function or method for converting data into a value of "fixed size." For example, hashing would convert the words "hello world" into a fixed size of 64 bits (of 1s and 0s) whilst "world hello" could result in another combination of 64 bits. The "collision-free hash function" (101) is one that converts a string of bits to another string of seemingly random bits. The key is that it is computationally infeasible to reconstruct the former string - which could be a text, an image or any digital document - with the latter. With this function, validating a timestamp is as simple as comparing it to its hash-function. Haber and Stornetta then suggest that the TSS use "digital signatures" to confirm they have received a hash value and appended a time-stamp. This minimises the likelihood of error on their part. However, perhaps the most important feature of Haber and Stornetta's system is their idea of "distributed trust" (§5.2.). The question they respond to is no longer "how do we verify claims about time-stamps?" but "who verifies those verifications?" They do argue for a second method for verifying validations, but it is distributed trust what has come to underlie the technology and philosophy of today's cryptocurrencies. In short, distributed trust amounts to having the majority of a network of surveyors confirm that a hash is correct. We might want to think about Gray and Bell's lawyers at the US Patent Office again. Rather than have a unique Patent Office - like the TSS -, we can picture everybody in the US who has an interest in patents needing to agree on who came in first. To make it more feasible, we need at least fifty percent of those individuals to confirm that Gray or Bell applied for the patent first. This way, for the information to be false, it would require an enormous conspiracy amongst at least fifty percent of the network. This is, at its simplest, the mechanism underpinning blockchain technology. Haber & Stornetta's "distributed trust" for time-stamping needs just two more ingredients to become today's blokchain: money and blocks. Recall that "hashing" cannot be effectively undone. This hash, in turn, is confirmed by a majority of a network - let's call them "peers." Where does the network keep their confirmed hashes? The pseudonymous Satoshi Nakamoto ([2009](https://www.ussc.gov/sites/default/files/pdf/training/annual-national-training-seminar/2018/Emerging_Tech_Bitcoin_Crypto.pdf)) suggests a public ledger. This ledger, in turn, operates as a sequence of blocks of hashes; it maintains all past, network-confirmed hashes. This way, the difficulty of "reversing a hash" is compounded by its being in a chain of blocks - a blockchain. The use of the term "ledger" already gives away what Nakamoto argued for: blockchain for cryptocurrencies substitutes bankers and accountants. We are no longer disagreeing with a possibly corrupt Patent Office, but a dubious financial system. What cryptocurrency does away with is the need for trust in a system that has failed time and time again. Reading Nakamoto's paper in light of recent discussions about cryptocurrencies (e.g.: BBC, [2021](https://www.bbc.co.uk/news/business-57096305); Crypto Climate Accord, [2021](https://www.southpole.com/news/crypto-climate-accord-launches-to-decarbonize-cryptocurrency-industry); Francis, [2021](https://finance.yahoo.com/news/15-environmentally-sustainable-cryptocurrencies-invest-224849569.html); Volpicelli, [2021](https://www.wired.co.uk/article/china-ban-bitcoin-cryptocurrencies) gives way to a slight face-palm moment. In the abstract, we read: "The network timestamps transactions by hashing them into an ongoing chain of hash-based proof-of-work, forming a record that cannot be changed without redoing the proof-of-work. The longest chain not only serves as proof of the sequence of events witnessed, but proof that it came from the largest pool of CPU power" (ibid.: 1). Translating this to a language I can try to understand: we can hold full trust in the blockchain if we use vast amounts of energy to maintain it. This is particularly true of Bitcoin, the energy for which we can track with the [Bitcoin Energy Consumption Index](https://digiconomist.net/bitcoin-energy-consumption). However, it wasn't until 2017 when "proof-of work" - i.e.: proof that a peer has spent energy on confirming a hash - began to be seriously questioned (European Environment Agency, [2020](https://www.eea.europa.eu/publications/blockchain-and-the-environment)). This seems to be slowly changing. Whatever we think of cryptocurrencies, it is positive to see a move towards more environmentally-friendly There are at least three perspectives when analysing the ethics of cryptocurrencies: the underlying technology of blockchain, the environmental impact of Bitcoin mining, and the values upheld by some of those who partake in the use of cryptocurrencies, namely: automation for trust and transparency. On the technological underpinning of blockchain, we discussed Haber and Stornetta's desire for a way to ensure that documents were accurately time-stamped. They had considered this as something of use in the context of intellectual property, using photographs as evidence, and large organisations with many official documents to keep track of. The applications they imagined were, to be frank, a little boring. They do not hint at the possibility of their ideas being applied to some "digital currency." And yet, just under two decades after their paper was published, a revolutionary form of banking emerged. The financial system that hinges on Haber and Stornetta's approach to digital time-stamping seems completely unrelated to what the authors had in mind. What's more, the world of cryptocurrencies raises new ethical challenges, which could not have been foreseen by Haber and Stornetta. One important ethical challenge relates with the environmental impact of Bitcoin, as we have mentioned. We will see more ethical questions pertaining to cryptocurrencies below. But with the infeasibility of Haber and Stornetta predicting where their technology would end up, we have a troubling realisation: researchers cannot fully account for the ethical implications of their work. With the above realisation, it seems that we can either gasp in terror at the prospect of having to conduct endless analyses to describe every possible future event, or simply shrug away any link between the self and "unintended consequences." Rather than either one of those extremes, I suggest researchers be creative when considering the ethical consequences of their work. This would not be to haphazardly guess at what the future holds, but to use scenario analysis to better understand the potential of their own work. Regarding the moral values of those engaged in the world of cryptocurrencies, well, it is hard to say. It is not feasible to map the ethics of entire populations (although some have tried, like Awad et al., [2018](https://doi.org/10.1038/s41586-018-0637-6)), but it might be possible to point to the politics of a certain technology (Winner, [1980](https://www.jstor.org/stable/20024652)). Recall, once again, Haber and Stornetta's move from the TSS, to a TSS with hashes, to a TSS with hashes and digital signatures, to hashes and digital signatures for a network of distributed trust. It should be no secret to users of cryptocurrencies - and related products and services - that they aim to do away with a need for trust in any one individual or organisation. Rather, they seek to distribute trust amongst a network of machines; they seek to automate trust. This automation of trust is the first important value of a digital currency that quashes the need for a centralised banking system. The second is transparency. Recall that Nakamoto presented the idea of a ledger. This ledger, which underpins Bitcoin, is public. After all, at least fifty percent of the network's energy must be spent on confirming transactions. With this, Nakamoto notes that transparency might complicate the assurance of privacy. This is because transactions in the ledger could be linked to the individuals behind them. But Nakamoto claims - rest assured - that the blockchain has two mechanisms to break the link between individuals and their transactions (Nakamoto, [2009](https://www.ussc.gov/sites/default/files/pdf/training/annual-national-training-seminar/2018/Emerging_Tech_Bitcoin_Crypto.pdf): 18). Over the years, transparency has reigned supreme by virtue of the openness of blockchain technology. Indeed, privacy only later emerged as a concern that has required new applications (Kshetri, [2018](https://libres.uncg.edu/ir/uncg/f/N_Kshetri_Cryptocurrencies_2018.pdf); see also Frankenfield, [2020](https://www.investopedia.com/terms/z/zcash.asp)). In sum, blockchain technologies seem to clearly uphold certain moral values above others. It provides a clear example of a technology that has its "own" politics. For the sceptics of such a claim, we can trace "the technology's politics" to its founders. People who have developed modern blockchain - amongst others, the people behind Nakamoto's name - have reproduced and amplified these values, which have been challenged; in part by the need for privacy, in part by the increasing understanding of its detrimental impact on the environment. Furthermore, due to its technical nature, it has become a technology for computer scientists and mathematicians - not to say cryptographers - to research and improve. Whether the values of the technology are held by its researchers is something for each of them to decide and, perhaps, communicate. --- :::warning Check out [this list of stories](https://github.com/Ismael-KG/A-History-of-Research-Ethics/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22+label%3A%22Help+wanted%22+label%3AWIP) if you are looking for more stories to comment on! :::

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