SShortSingh.
Back to feed

How Thousands of Independent Nodes Keep Blockchain Networks Decentralized

0
·4 views

Blockchain networks achieve decentralization by having thousands of independent computers, called nodes, each maintain a full copy of the ledger and verify every transaction themselves without relying on a central authority. Bitcoin currently operates with over 15,000 such nodes worldwide, each independently validating blocks against protocol rules. Different node types exist for different purposes, including full nodes for maximum security, lightweight nodes for mobile wallets, and archive nodes used by analytics platforms. Unlike traditional client-server systems, blockchains use peer-to-peer architecture where each node connects to 8–20 peers, spreading transaction data exponentially across the network within seconds. This design makes the network resistant to censorship, regional outages, and single points of failure, as even a fraction of active nodes can keep the system running.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Zero-Budget Framework for Benchmarking AI Coding Models on Side Projects

A developer has published a structured, repeatable workflow for evaluating AI coding assistants without spending money, using free-tier APIs and a disposable git repository. The method replaces the common "vibes-based" approach — testing a model with one prompt and judging it on that alone — with a reusable benchmark suite of five to eight task types. A minimal Python harness captures raw model responses, timestamps, and errors for offline comparison across multiple models and runs. The workflow is designed to be provider-agnostic, removing barriers like API costs and the need for local hardware capable of running large models. By versioning prompts and never tuning them to favour a specific model, the approach aims to surface genuine strengths and weaknesses before any real-world deployment.

0
ProgrammingDEV Community ·

Velero Backup Bug: Kubernetes Tool Silently Omitted PVC Data for Weeks

A homelab operator discovered on June 19, 2026, that Velero had been reporting successful daily backups while never actually capturing any PersistentVolumeClaim data. The tool defaulted to snapshot-based backups, which require a CSI snapshot provider — something NFS and local-path storage classes do not support. Without a snapshot provider, Velero silently backed up only Kubernetes manifests, omitting all application data including Postgres databases, Vaultwarden passwords, and Nextcloud files. The issue was fixed by adding a single line — defaultVolumesToFsBackup: true — to the backup schedule, switching Velero to filesystem-based backup via Kopia, after which backup size jumped from roughly 2 MB to 4 GB. The operator noted that running 'velero backup describe --details' and checking the 'Pod Volume Backups' field is the only reliable way to confirm actual PVC data was captured.

0
ProgrammingDEV Community ·

New Tool Converts Dynamics 365 Task Recordings into Structured Markdown Guides

A developer tool called axtr-to-markdown automates the conversion of Microsoft Dynamics 365 Task Recorder exports into editable Markdown documents. The skill processes recorded user steps, form names, field controls, and action types to produce structured Level 3 or Level 4 process documentation. Output includes sections for purpose, scope, prerequisites, troubleshooting, and a SIPOC analysis draft, reducing manual transcription work for teams. Functional consultants and process owners can then review and enrich the generated draft rather than building documentation from scratch. The tool is designed to support use cases such as end-user training, onboarding guides, UAT test scripts, and SharePoint knowledge articles.