Flow — Sleeping Giant

Flow Introduction

One of the most significant hurdles in blockchain architecture is how to process the most amount of transactions in the least amount of time, a metric referred to as throughput. When you look at other blockchain networks like BTC, ETH, SOL, etc. you notice that they improve by increasing efficiency of their single node types that are used to run the network. FLOW on the other hand, developed a unique approach to split up the work traditionally assigned to cryptocurrency miners into different roles, where selection and ordering of the consensus are performed independently from execution.

Why so many different nodes?

  1. Access Node: Access nodes provide external clients with access to recent blocks and submit transactions from clients to the collection node cluster.
  2. Collection Node: Collection nodes are organized into collection clusters →A collection nodes cluster decides which collection will be sent to the network in a form of Collection Guarantee →The Collection Guarantee can be used to get the full content of the collection and its transaction.
  3. Consensus Node: Form and propose blocks based on collection information sent from collection nodes.
  4. Execution Node: Execute the transactions and send the receipts to the network.
  5. Verification Node: Evaluate the correctness of the work done by execution nodes and submits a result approval to the network.

Cadence: The first high-level resource-oriented programming language

This is the most exciting part about the FLOW ecosystem. Cadence is the smart contract language developed by FLOW and it brings an entirely new element to the network. By including a native representation of the digital assets in the programming language, FLOW not only serves as a better digital ownership model, but also has its own built-in protections against value-destroying bugs.

  1. Comfortability and ergonomic syntax, making is easy to learn and read
  2. Uses strong, static type system to minimize runtime errors
  3. Must easier to learn, audit, and ultimately more productive
  1. Each resource exists in exactly one place at any given time
  2. Ownership of a resource is defined by where it is stored
  3. Access to methods on a resource is limited to the owner



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store



Ivey 22' (MBA) | UBC 18' (Accounting) | UBC 15' (Bsc) | ex-EY | Learning Web3 & finance