Understanding Blockchain

This notes will cover below questions...
  1. Introduction to Blockchain
  2. What is the difference between Blockchain and Bitcoin?
  3. What are some other uses of blockchain that go beyond bitcoin?
  4. History of blockchain
  5. Could you explain the blockchain process in laymen terms?
  6. If all data is available to the public. Can anyone know my bank balance (in Bitcoin)?

Introduction to Blockchain
The Blockchain is a decentralized and distributed public (digital) ledger where transactions are recorded and confirmed anonymously. It’s a record of events that is shared between many parties. More importantly, once information is entered, it cannot be altered without altering subsequent blocks.
WTF is the blockchain? A guide for total beginners

What is the difference between Blockchain and Bitcoin?
The blockchain is a technology behind bitcoin. Blockchain is to Bitcoin, what the internet is to email.
Simplest Explanation | The Difference Between BLOCKCHAIN and BITCOIN

What are some other uses of blockchain that go beyond bitcoin?
Apart from bitcoin, many application use cases are being developed and coming to lime light using blockchain technologies like Smart Contract, e-voting, digital identity, music track record licensing, medical records etc.
17 Blockchain Applications That Are Transforming Society

History of blockchain
In 2008, Satoshi Nakamoto (the pseudonym for an as-of-yet unidentified individual) published a white-paper called Bitcoin: A Peer to Peer Electronic Cash System. In this paper, he argued that he had solved the issue of double-spend for digital currency via a distributed database that combined cryptography, game theory, and computer science.

Around 2014, technologists and investors shifted their focus from Bitcoin to blockchain, bitcoin’s underlying technology. Though Bitcoin and blockchain are often referred to interchangeably, that’s incorrect. Bitcoin is built on a version of a blockchain. A blockchain is an open, decentralized ledger that can record transactions between two parties efficiently and in a verifiable and permanent way without the need for a central authority.

An initial contributor to the Bitcoin codebase, Vitalik became frustrated in 2013 by Bitcoin’s programming limitations. Vitalik decided that Bitcoin’s protocol was designed too prescriptive so he decided to build public blockchain 2.0, which he called Ethereum.
A Brief History of Blockchain: An Investor’s Perspective

Could you explain the process of how does it work in laymen term?
The simplest explaination I can get so far...
Become a blockchain expert in 1,384 words

If all data is available to public. Can anyone know my bank balance?
Yes and hence it is recommended to use different address for different transactions. But, still it seems it is hard to hide your identity. This article lists seven ways where yours identity can be leaked.
Top Seven Ways Your Identity Can Be Linked To Your Bitcoin Address



Comments

Post a Comment

Popular posts from this blog

Performance Test Run Report Template

You have gathered requirements from clients, identified key critical business scenarios, analyzed the workload distributions, found out performance goals and requirements, identified  tool for generating load, setup the test environment, designed the scripts, executed the performance run, collected the raw data, analyzed it, what next?  Send information to stakeholders? No!!  Wait!! It needs to formatted, customized for different stakeholder(s) and reported accordingly. This article suggests one of the ways to report performance run results to client especially if the performance testing activity has been outsourced to yours company.  It discusses the performance report template and importantly the reasons for including the items in the report. The performance report template contains information by data collected from client side only and doesn’t discuss / talk about data from server side like processor utilization etc. Broadly the performance report has been divided in three major
Read more

Bugs Management in Agile Project

Agile has a refreshing approach to bugs, especially when contrasted with traditional waterfall practices. Historically, teams would postpone bugs to a stabilization phase. This stabilization phase was long and tedious, typically with high stress and long hours. Agile, on the other hand, promotes the following thought processes: Carrying bug debt is unhealthy and sometimes, even destructive. We should fix bugs, not track them. A feature isn't done until the bugs are fixed. Quality is part of the overall cost. Bugs are prioritized against new features. A bug needs to be more important than the next new feature. Notes All new features have a "bug tail." The bug tail is the diminishing number of open bugs on the new functionality. When a feature is added, bugs are introduced. Most are discovered and fixed immediately by the team as a part of feature development: some a few days later, others not until long after a story is considered &quo
Read more