Blockchain & Layers

A blockchain records transactions into blocks that are linked by a cryptographic hash of the previous block, timestamp and transaction data. See hashes as a red line to connects all blocks in a blockchain. This line ensure the data integrity and immutability of each blocks in a blockchains. A cryptographic hash is a mathematical reduction of a string, so that one hash of a string will always be the same. ...

November 26, 2023 · 3 min · 507 words · cleminso

Message & Transaction & Signature

We know a blockchain records transactions into blocks that are linked by a cryptographic hash of the previous block. Let’s focus on the transaction word and see how it’s work. Why are message, transaction and signature in blockchain, and what are their relations? Imagine asking for or ordering a bank transfer for a friend: You need to provide your intent and the necessary data, such as ‘amount requested’ => message You need to send your intent in understandable words and provide the sender and receiver of the order => transaction the institution who execute, it needs to understand and ensure the transaction is legitimate => signature Let’s compare it with what happens when users initiate an interaction with a blockchain. ...

November 29, 2023 · 3 min · 590 words · cleminso

TL;DR #012 - Stateless Infra, Social networks and third-parties

Stateless Infrastructure Source Stateless Infra from Polynya What is Stateless Infrastructure For this blog: stick with blockchain = any chain achieving real-time strict global consensus (including rollups); stateless infra = not a chain, no consensus (or loose consensus), but decentralized complements that interact with the above mentioned blockchains. Current statement: in blockchain world, we have been attuned to honest-majority assumptions, trust running as many nodes as possible is import outside of blockchains, things operate with an honest-minority assumption, as long as there’s one honest party Servers - This one’s obvious and a well-known quantity. Servers with redundancy - Add redundancy and the ability for anyone to spin up a server, and you get some decentralization but also retain the max efficiency of traditional servers. These are maximally decentralized constructions, running peer-to-peer, but there’s no consensus (or loose consensus) run with an honest-minority assumption, and even a network with 10-100 nodes is perfectly decentralized can be certain types there’s one node, thx validity proofs don’t need more (storage proof) Stateless infra can enable a lot of features incorrectly attributed to blockchains, but without the burden of consensus can have a state but not a real-time strict consensus state with strict state transitions associated with blockchains Why do we need stateless infra Current statement: ...

February 16, 2024 · 4 min · 717 words · Cleminso