András Novoszáth

@nocibambi

10 Following

3 Followers

András Novoszáth pfp

András Novoszáth

◼️47/100: Block-by-Block One thing I learned about: Cryptographic guarantees - Confidentiality: Only we can access it. - Authenticity: They were the ones who sent it. - Integrity: This is what they have sent. - Non-repudiation: They really have sent it. + Data availability: We can access the data. + Data verifiability: We can tell this about the data without reading the data. 🔽🛠️Resources🔽 - 'Polkadot Blockchain Academy' @AcademyPolkadot: https://pbax.polkadot.academy/

0 reply

0 recast

0 reaction

András Novoszáth pfp

András Novoszáth

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

0 reply

0 recast

0 reaction

András Novoszáth pfp

András Novoszáth

The State of EVM Indexing guide from @dune.eth https://dune.com/blog/the-state-of-evm-indexing

0 reply

0 recast

0 reaction

András Novoszáth pfp

András Novoszáth

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

0 reply

0 recast

0 reaction

András Novoszáth pfp

András Novoszáth

◼️46/100: Block-by-Block One thing I learned about: How Ponder optimized its data indexing workflow Ponder indexes EVM smart contracts for mobile & web developers. It works as an ETL pipeline from RPC nodes to a Postgres database. It aims to process 100,000 events per second. Three speed optimizations it took: - Cache events in-memory with periodical flushes in batch - Move primary key checks to the cache flush step - Pre-fetch queries based on database access patterns + Also tried: static code parser with concurrent indexing 🔽🛠️Resources🔽 - Why Ponder via @typedarray.eth: https://ponder.sh/docs/why-ponder - Ponder’s (ongoing) journey to 100,000 events per second (2025) via @typedarray.eth: https://ponder.sh/blog/performance

0 reply

0 recast

0 reaction

András Novoszáth pfp

András Novoszáth

◼️45/100: Block-by-Block One thing I learned about: Types of Token Design projects Token design helps token issuers find a token-network fit. However, token design is different before and after the token launch. - Pre-launch: systematic, theory-driven - Post-launch: iterative, data-driven 🔽🛠️Resources🔽 - Unpacking Token Design (2023) by @VM_TokenDesign: <https://medium.com/@VendingMachine/unpacking-token-design-3a44d1eef6b5> - A Token Design Thesis (2023) by @VM_TokenDesign: <https://medium.com/@VendingMachine/a-token-design-thesis-1d1b400461d9>

0 reply

0 recast

0 reaction

András Novoszáth pfp

András Novoszáth

Flipside closing down its dashboards and focusing on AI

1 reply

0 recast

3 reactions

András Novoszáth pfp

András Novoszáth

Got my Base Batch Europe SBT 😤 https://opensea.io/assets/base/0x98D9D7B9556ebc8be8F10Cd5B7148E9C8aDF744e/373 @base @devfolio @opensea

0 reply

0 recast

0 reaction

András Novoszáth pfp

András Novoszáth

◼️44/100: Block-by-Block One thing I learned about: Bloom filters. On-chain data indexers often try to avoid refetching the same transactions. A bloom filter can help to test if they already have a record. - It is a probabilistic data structure consisting of a binary array - Maps record hash values to values of the array - Maps record keys to the corresponding indexes of the array - Membership check consists of checking the array values Caveat: Can produce false positives. 🔽🛠️Resources🔽 - Real-time Blockchain Data Indexing: Challenges and Solutions (2025): https://medium.com/@aannkkiittaa/real-time-blockchain-data-indexing-challenges-and-solutions-fcb1f8aa3911 - Bloom Filters (2022): https://www.youtube.com/watch?v=V3pzxngeLqw&t=208

0 reply

0 recast

0 reaction

András Novoszáth pfp

András Novoszáth

https://media.tenor.com/Dd8lVFGweNMAAAAM/always-has-been-among-us.gif

0 reply

0 recast

0 reaction

András Novoszáth pfp

András Novoszáth

◼️43/100: Block-by-Block One thing I learned about: Blockchain nodes - my current understanding I discovered a writing contest on blockchain nodes by @hackernoon and @Getblock. I decided to enter. I wanted to write a 'comprehensive' overview. But the time was short, and I realized some knowledge gaps. So, it became an 'essential' overview instead. :'-) Anyway, here is the article: https://hackernoon.com/what-is-a-blockchain-node-and-how-does-it-work-essential-overview I hope you find it useful. It was for me. And, a shoutout to @NeoSoft for the image! Was a lifesaver in the last moment. :) P.S.: I learned a lot writing it. Will try to share them in the upcoming days...

0 reply

0 recast

0 reaction

András Novoszáth pfp

András Novoszáth

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

0 reply

0 recast

0 reaction

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