Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Kaspa prices transactions by how much permanent storage they create A dust attack once flooded #Kaspa with tiny coin fragments that every full node must store forever. Unlike old blocks, which nodes can discard, these coin records never expire. KIP-9, a protocol rule co-authored by Kaspa's Michael Sutton, was...

17,459 Aufrufe • vor 2 Monaten •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

Stateless History Node is almost like a regular Ethereum node, but it doesn't store state and it doesn't have EVM execution. It's used only for syncing events and thus - is faster and gives you FREE INDEXING. You don't have to pay 6 figures for RPC anymore! Just spin up a Stateless History Node, plug rindexer or Ponder there, and enjoy free (AND FAST!!) indexing! This node is syncing >1000 blocks per second at my local pc (less than 6hrs for the whole Ethereum), and it should use less than 200GB - which means you can host it on a MacMini, Hetzner or whatever. You can futhermore filter that by using block ranges or bloom filters, etc - I haven't developed this yet. What you see is a proof of concept. It works via native devp2p 'eth' protocol, but with EIP4444 and The Prune we would have to also support era1 archives and Portal Network. But so far it works - there are plenty of peers serving historical receipts, and they serve them FAST! If you run Stateless History Node you can also serve the blocks and receipts - so that could help to preserve archival data too. For now there is no data validation yet (and even no data storage - that's a very early PoC), but we can verify validity of chain by simultaneously running a lightweight CL node (or not lightweight if you're extremely paranoid). And then support verifying the hashes of receipts and blocks with their parents, maintaining full integrity and zero trust. It's also written in rust, btw. So, I guess, at least for Ethereum Mainnet the era of RPC's pumping moneybags is over - there's finally a local, trustless and free indexing alternative available. Too sad this won't work for Optimism / Base , cause despite introducing P2P after Bedrock - they haven't enabled receipts transfer in the protocol (or at least I couldn't find one). Arbitrum is even sadder - I don't believe there is a P2P layer at all - you just have to run your own node, hold state and execute blocks to get events. There is hope - Paradigm recently released Ress - stateless execution, but it requires nodes to support Witness preparation & exchange - but this could work for L2s - cause the main blocker for local RPCs rn is huge state (VPS with TB storage cost a lot), and the second blocker is EVM forks makes it hard to hold a node - it needs to be maintained, upgraded, etc. Ress at least solves the state part. But anyways, I will try to continue working on this and release some MVP version with RPC endpoint and data storage soon - follow the updates!

Convergence Boy

29,823 Aufrufe • vor 10 Monaten

Destra Network| True decentralized Storage solution How Destra Decentralized File Storage solves the centralization issues in Filecoin & IPFS Filecoin and IPFS have become synonymous with decentralized file storage, highly hyped alternatives to traditional centralized data storage systems. However, a deep dive into their architecture reveals a crucially centralized component: both networks rely on a set of centralized bootstrap nodes. Whenever a new node wants to join the Filecoin or IPFS network, it must first communicate with these bootstrap nodes to obtain information about other peers, placing complete trust in the provided information. The Filecoin team operates these bootstrap nodes on centralized cloud servers. These nodes serve as the initial points of contact for new nodes entering the network, acting as directories to facilitate the network's mesh topology, and thus are critical components of the architecture. Major Centralization Concerns: 1. Surveillance: Centralized nodes offer a concentrated point for surveillance. Authorities or malicious actors could target these nodes to gather data on user activities, node interactions, and network dynamics, posing significant privacy risks. 2. Central Control and Censorship: The operators of bootstrap nodes potentially wield significant control over the network. They can influence which parts of the network are more discoverable or enforce certain network rules, leading to a form of gatekeeping. This centralized control contrasts with the decentralization ethos of blockchain and peer-to-peer technologies. 3. Single Points of Failure: Bootstrap nodes act as central hubs through which traffic and connections are often routed, especially during the initial connection phase. This setup can create single points of failure. If these nodes are compromised, go offline, or experience technical issues, new nodes may struggle to integrate into the network, potentially taking down the whole network. At Destra, we are building the Destra Decentralized File Storage to ensure that such centralization or pseudo-decentralization has no place in our architecture. As always, we are committed to our vision of 100% decentralization, delivering an unprecedented level of decentralization to our users and the broader ecosystem. As we continue developing the Destra Decentralized File Storage, we will keep on publishing regular updates to our community.

Destra Network

10,988 Aufrufe • vor 2 Jahren