Technical flashcards

Question 1

Explain Solana Proof of History

Answer 1

cryptographic timestamp is placed on transaction which is used to then organize which transactions should be confirmed first based on their submission times

Question 2

Solana Tower Byzantine Fault Tolerance

Answer 2

even if 1/3 of nodes get faulty, blockchain will still operate

Question 3

Solana Turbine

Answer 3

splits 128MB block into small packages of 64kb and sends them to closest validators to get processed. once these smaller packages are claimed by validators they can then recreate the original block.

erasure codes - when validator changes and retransmits data in small package

Question 4

Solana Gulf Stream + Mempool

Answer 4

Mempool = waiting queue
*valid transactions that have been submitted, but have not yet been processed by the network

while transactions are waiting for confirmation in mempool “in line”, transactions can be aligned to validators to be processed for when their time comes up

ex. you are at ticket booth and there are 5 to choose from. as soon as one opens up and it’s your turn in line you redirect to that line immediately.

Question 5

Solana Sealevel

Answer 5

EVM has limitation to single-thread processing, only allowing execution of one smart contract at a time.

Solana Sealevel allows smart-contract to be execued in parallel.

how? smart contracts which run transactions that are read only run in parallel to mitigate manipulation

Question 6

Solana Pipelining

Answer 6

stream of input data that needs to be processed by a sequence of steps and there’s different hardware responsible for each step

Question 7

Solana Archivers

Answer 7

as blockchain grows in usage, the ledger gets heavier and nodes need to be able to store this effectively

Question 8

Hubble & Hubble Space telescope analogy

Answer 8

“Hubble can be thought of similarly to the hubble space telescope. Similar to how the hubble space telescope is has revolutionized how we explore outer space, hubble by figment fundamentally changes the way we explore blockchains & validators.”

The idea was born when we saw a common thread of developers wasting too much time on node management. From that point forward we declared “No more node management for developers.” Our goal is to enable web 3 developers to focus on building creative apps on web 3, not managing the underlying infrastructure.