András Novoszáth

@nocibambi

12 Following

3 Followers

András Novoszáth pfp

András Novoszáth

https://farcaster.xyz/shawmakesmagic/0x7ad1e59a

0 reply

0 recast

0 reaction

András Novoszáth pfp

András Novoszáth

◼️42/100: Block-by-Block One thing I learned about: Web3 Data Engineering Guides Two further great data engineering guides I missed before: - "Getting Started as a Data Engineer with a Blockchain Scenario — Part I" (2025): https://medium.com/towards-data-engineering/getting-started-as-a-data-engineer-with-a-blockchain-scenario-part-i-ce7c3aea3433 - "[2025 Annual Guide] Crypto Data Engineering Guide" (2025): https://read.cryptodatabytes.com/p/2025-annual-guide-crypto-data-engineering

0 reply

0 recast

0 reaction

András Novoszáth pfp

András Novoszáth

◼️41/100: Block-by-Block One thing I learned about: The steps of the blockchain verification flow The three main stages: 1. Transaction lifecycle 2. Block creation 3. Block propagation 🔽📝Breakdown🔽

1 reply

0 recast

0 reaction

András Novoszáth pfp

András Novoszáth

◼️40/100: Block-by-Block One thing I learned about: Alternatives to using blockchain nodes Blockchains do not need always to use full-nodes for every task in the network. They can use alternatives suited to their goals, circumstances, and constraints. Examples: - Light clients: performs trust-minimized verification by requesting proofs from ful nodes. - Data availability layers: store and serve block data apart from execution nodes. - Layer2 and sidechains: process data off-chain and rely on proofs or state roots. - Blockchain indexers: store data and allow queries nodes do not support. - Remote or federated apis: third-party on-chain data providers 🔽🛠️Resources🔽

1 reply

0 recast

0 reaction

András Novoszáth pfp

András Novoszáth

◼️38/100: Block-by-Block One thing I learned about: Blockchain node components Nodes work differently depending on the blockchain and their role within the blockchain. Some general components & functions across the stack: - P2P Networking - Mempool Management - Consensus Execution - State & Ledger storage - RPC/API Layer - Synch mechanisms

0 reply

0 recast

0 reaction

András Novoszáth pfp

András Novoszáth

https://farcaster.xyz/nocibambi/0x07589ff0

0 reply

0 recast

0 reaction

András Novoszáth pfp

András Novoszáth

◼️38/100: Block-by-Block One thing I learned about: The fastest way to set up a blockchain node (II) (Perhaps) the fastest way to set up a blockchain node is to start a light Celestia node in your browser: https://lumina.rs/ 🔽🛠️Resources🔽 - @celestia: https://celestia.org/

0 reply

0 recast

0 reaction

András Novoszáth pfp

András Novoszáth

◼️37/100: Block-by-Block One thing I learned about: Providers of indexed on-chain data. Blockchain data is hard to search and query. Indexed data providers restructure on-chain data and serve them in a queriable format. Main players: - The Graph: @graphprotocol - Covalent: @covalent-hq - SubQuery: @subquerynetwork - SQD: @hellosqd 🔽🛠️Resources🔽 - The Evolution of Data Access in Web3 (2024) by @DFG__Official: https://dfg-official.medium.com/the-evolution-of-data-access-in-web3-5d09e837150b - The Graph (2025): https://thegraph.com/ - SQD.ai (2025): https://www.sqd.ai/ - Covalent (2025): https://www.covalenthq.com/ - SubQuery (2025): https://subquery.network/

0 reply

0 recast

0 reaction

András Novoszáth pfp

András Novoszáth

https://farcaster.xyz/nocibambi/0x21a09333

0 reply

0 recast

0 reaction

András Novoszáth pfp

András Novoszáth

◼️36/100: Block-by-Block One thing I learned about: The fastest way to set up a blockchain node. The fastest way to set up a blockchain node is to set up a blockchain client. The fastest way to set up a blockchain client is to set up a light client. The fastest way to set up a light client is (perhaps) to use Avail... 🔽🛠️Resources🔽 - Run an Avail light client (2025) by @availproject: https://docs.availproject.org/docs/operate-a-node/run-a-light-client/

0 reply

0 recast

0 reaction

András Novoszáth pfp

András Novoszáth

https://farcaster.xyz/nocibambi/0x7c0111ac

0 reply

0 recast

0 reaction

András Novoszáth pfp

András Novoszáth

◼️35/100: Block-by-Block One thing I learned about: Data location in Solidity. - EVM stack: value types (e.g. `uint`, `bool`, `address`) and opcode executions - Storage: reference types, not as function arguments/returns - Calldata: reference types excluding mappings, and not as constructor parameters - Memory: reference types, excluding mappings - Transient: state variable value types 🔽🛠️Resources🔽 - Types – Solidity 0.8.31 documentation (2025) by @solidity_lang:  https://docs.soliditylang.org/en/latest/types.html#data-location

0 reply

0 recast

0 reaction

András Novoszáth pfp

András Novoszáth

◼️34/100: Block-by-Block One thing I learned about: Web3 domain services Blockchain addresses are not intuitive for everyday users. Web3 domain services provide memorable names tied to on-chain accounts. This is similar to how DNS resolves domain names into IP addresses. This should help Web3 users own a domain and send/receive transactions. But, there are adoption challenges. 🔽📝Details🔽

1 reply

0 recast

1 reaction

András Novoszáth pfp

András Novoszáth

◼️33/100: Block-by-Block One thing I learned about: Reasons to run your blockchain node. There are reasons to run a node as a user and there are reasons to run a node as a developer.

1 reply

0 recast

1 reaction

András Novoszáth pfp

András Novoszáth

◼️32/100: Block-by-Block One thing I learned about: What is an RPC API? RPC is a way to design APIS. - Focuses on processes: calls a function - It calls remote functions as if a local service - Both client and server keep a proxy representation of each other (stub and skeleton) - Fixed data format - Client needs to know server functions and parameters - Can be stateful 🔽🛠️Resources🔽

1 reply

0 recast

1 reaction

András Novoszáth pfp

András Novoszáth

◼️31/100: Block-by-Block One thing I learned about: Applications of mechanism design in Web3 - Consensus: How to agree... - Markets: How to allocate... - Incentives: How to behave... - Governance: How to decide... - Public goods: How to fund... ...among strangers on the internet 🔽🛠️Resources🔽

1 reply

0 recast

0 reaction

András Novoszáth pfp

András Novoszáth

◼️30/100: Block-by-Block One thing I learned about: How does Farcaster store data? It follows a mixed, on-chain/off-chain logic: - On-chain registry: creates accounts and keeps track of identities, permissions, and pointers. - Off-chain hubs: verifies, stores, syncs, and shares data (e.g. posts, follows). - User-facing clients: signs messages on behalf of the user and sends them to hubs. NOTE: Farcaster has just moved its data layer from hubs to Snapchain. 🔽🛠️Resources🔽

1 reply

0 recast

0 reaction

András Novoszáth pfp

András Novoszáth

◼️29/100: Block-by-Block One thing I learned about: Onchain data indexing methods. - Event-based: Listen to specific events. Simple but selective. - RPC polling: Regularly query the node. Straightforward but slow and can miss reorgs. - Trace-based: Fetch internal transaction trace. Deep but resource-intensive. - Push streaming: Push-based data streams. Fast but complex. +1. Archive node querying: Query historical states. Can assist indexing with replaying the blockchain. 🔽🛠️Resources🔽

1 reply

0 recast

0 reaction

András Novoszáth pfp

András Novoszáth

◼️28/100: Block-by-Block One thing I learned about: Why there are no floats in Solidity. - Nodes must agree on transaction results. - Transaction results must be deterministic. - Different systems calculate floats in different ways. (e.g. 2/3 can be 0.66666 or 0.66667) "In Solidity, division rounds towards zero." 🔽🛠️Resources🔽

1 reply

0 recast

0 reaction

András Novoszáth pfp

András Novoszáth

◼️27/100: Block-by-Block One thing I learned about: Types of consensus mechanisms in Web3 There are many ways to agree in a network. Examples: - Proof of Work: First miner who solves the puzzle creates the block. - Proof of Stake: Random validator creates the block. - Delegated Proof of Stake: The next top delegate creates the block. - Byzantine Fault Tolerant (BFT) Consensus: Supermajority creates the block. - Proof of Authority: Known authorities create the block. 🔽🛠️Resources🔽

1 reply

0 recast

0 reaction