惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

T
Tenable Blog
K
Kaspersky official blog
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
T
The Exploit Database - CXSecurity.com
Cisco Talos Blog
Cisco Talos Blog
P
Palo Alto Networks Blog
Latest news
Latest news
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
C
CXSECURITY Database RSS Feed - CXSecurity.com
P
Privacy International News Feed
The Hacker News
The Hacker News
T
Tor Project blog
www.infosecurity-magazine.com
www.infosecurity-magazine.com
C
Cisco Blogs
阮一峰的网络日志
阮一峰的网络日志
Recent Commits to openclaw:main
Recent Commits to openclaw:main
博客园_首页
N
News and Events Feed by Topic
W
WeLiveSecurity
罗磊的独立博客
GbyAI
GbyAI
T
Troy Hunt's Blog
Y
Y Combinator Blog
Recorded Future
Recorded Future
The Cloudflare Blog
TaoSecurity Blog
TaoSecurity Blog
爱范儿
爱范儿
美团技术团队
Attack and Defense Labs
Attack and Defense Labs
C
Check Point Blog
Engineering at Meta
Engineering at Meta
Cyberwarzone
Cyberwarzone
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
F
Fortinet All Blogs
The GitHub Blog
The GitHub Blog
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Apple Machine Learning Research
Apple Machine Learning Research
Know Your Adversary
Know Your Adversary
AWS News Blog
AWS News Blog
D
DataBreaches.Net
Recent Announcements
Recent Announcements
K
KPMG report finds enterprise disconnect between AI and its ROI | CIO
M
MIT News - Artificial intelligence
Webroot Blog
Webroot Blog
Security Latest
Security Latest
T
Tailwind CSS Blog
V2EX - 技术
V2EX - 技术
aimingoo的专栏
aimingoo的专栏
S
Security @ Cisco Blogs
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant Common SOC 2 Failures (Real World) Stop Vibe-Checking Your AI App: A Practical Guide to Evals How to Use SonarQube and SonarScanner Locally to Level Up Your Code Quality Your Next To-Do App Is Dead — I Replaced Mine with an OpenClaw AI Sign a Nostr event in 60 lines of Python using coincurve — no nostr-sdk, no nbxplorer, no rust toolchain ITGC Audit Explained Like You’re in Big 4 Patch Tuesday abril 2026: Microsoft parcha 163 vulnerabilidades y un zero-day en SharePoint Stop scraping everything: a better way to track competitor price changes Listing on MCPize + the Official MCP Registry while routing payments OUTSIDE the marketplace — how I kept 100% of my x402 revenue Building an AI-Powered Risk Intelligence System Using Serverless Architecture Why We Ripped Function Overloading Out of Our AI Toolchain Testing AI-Generated Code: How to Actually Know If It Works SaaS Churn Is Killing Your Business. Here Is What to Do About It (Without a Support Team) The Speed of AI Is No Longer Linear - And Self-Improving Models Are Why How to Implement RBAC for MCP Tools: A Practical Guide for Engineering Teams From Standard Quote to Persuasive Proposal: AI Automation for Arborists I built a CLI that scaffolds complete multi-tenant SaaS apps Axios CVE-2025–62718: The Silent SSRF Bug That Could Be Hiding in Your Node.js App Right Now The dashboard that ended our friendship Data Pipelines Explained Simply (and How to Build Them with Python) The Hidden Cost of AI Systems Nobody Talks About. undefined vs undeclared, and how typeof behaves Switching from file-based jobs to NATS/Kafka in Rust without changing code io_uring Adventures: Rust Servers That Love Syscalls Why Agentic AI is Killing the Traditional Database The POUR principles of web accessibility for developers and designers Quantum Neural Network 3D — A Deep Dive into Interactive WebGL Visualization How To Install Caveman In Codex On macOS And Windows Automation Pipeline Reliability: Why Your Workflow Breaks When Nobody Is Watching I Built an 'Open World' AI Coding Agent — It Works From ANY Folder From Freelancing to Product: A Tech Service Company's SaaS Transformation China's AI Giants: Adding Tencent Hunyuan & ByteDance Doubao to AI University (74 Providers) On the Vibe Coders and Their Lies clerk: Auto-Summarize Your Claude Code Sessions AI Weekly — 2026/04/10–04/17 | The Model Lockdown Is Here, but the Toolchain Is the Real Battleground AI 週報 — 2026/04/10–2026/04/17 模型封鎖潮來了,但工具鏈才是真戰場 Maybe this is how Open-Source apps are born... 🚀 Fine-Tune LLMs with LoRA and QLoRA: 2026 Guide tRPC v11 + Next.js App Router: End-to-End Type Safety Without the Boilerplate ShadCN UI in 2026: Why I Stopped Installing Component Libraries and Started Owning My Components SaaS Billing in React Server Components: Stripe + Supabase Without a Single `useEffect` Join our DEV Weekend Challenge — $1,000 in Prizes Across TEN winners! Submissions Due April 20 at 6:59 AM UTC. Implementing FSRS Spaced Repetition in Flutter + Supabase — Adding Memory Science to an AI Learning App "I Texted My Localhost From the Train — Claude Code Fixed the Bug Before I Got Home" I Built a Sales Prep AI and It Went Deeper Than Expected Design to Code #2: One JSON, Eleven Outputs Solving the 100M-Row Problem: A Summary Table Pattern for High-Volume Push Notification Logs Flutter Web With Wasm: What Actually Changes For Developers I Built 50 Royalty-Free Soundtracks for My Side Project in a Weekend Using AI Music Generation The Vibe Coding Security Checklist: 7 Things to Check Before You Ship Stop Letting Googlebot Guess Fix Your React App's SEO Right Desconstruindo o Streaming do LinkedIn: Como Criar um Engine de Extração de Vídeo de Alta Performance com HLS e FFmpeg (EDA Part-1) EDA (Exploratory Data Analysis) Explained With Real Life — Why Looking at Your Data Is the Most Important Step in Machine Learning Brand Relationship Management at Scale: Our 4-Touch Outreach System for 200+ Brands Why String.fromEnvironment() Might Return an Empty String in Dart JGuardrails 1.0.0 — Hardening Java LLM Apps Against Jailbreaks, Toxicity, and Prompt Injection Plan and Schedule a Full Week of Threads Content From One Claude Conversation Coding Cat Oran Ep3, Five Tables Changed Everything Updated: BFF Pattern I'm done watching freelancers get buried by 200 proposals. So I'm building the alternative. This is my first post BFS Algorithm in Java Step by Step Tutorial with Examples Tracking LLM Pricing Monthly: An Open Dataset for 22 AI Models How We Measure Content ROI on a Comparison Site: Revenue Attribution Without Perfect Data Introducing Nova AI Ops: The AI-Native Operating System for SRE Teams I built a free desktop video downloader for Windows — Grabbit How Talkie OCR Helps Vision-Impaired & Dyslexic Users Read the World Around Them VRCFaceTracking安装和iPhone面捕配置教程,有bug Even CrowdStrike Can't See Your Agents The Automation Gold Rush: What n8n Workflows and Claude Are Opening Up for Developers Right Now
Blockchain afterparty
Basstardd · 2026-06-21 · via DEV Community

The speculation has burned off. Most of what got built is gone or forgotten - the party's over. What's left with us is after-party landscape, sticky floor and the broken bottles. But these sobering moments, once the hangover sets in, are exactly when the questions bite sharp. So it's a good moment to ask: what was blockchain technology for in the first place?

The answer most people reach for is "removing middlemen." But that's an answer to a smaller question. To see what blockchain is really aimed at, you have to go one level deeper - past the intermediaries, past the technical machinery - to the thing underneath both.

The problem

Human nature is unreliable, and it fails us in a specific, repeating way. Give a person power over something shared, and sooner or later they bend it toward their own interest. Not always, not everyone - but reliably enough, across enough people, that you can treat it as a constant.

Let me give you the smallest possible version of it. Years ago, as a student, I was queuing at the post office on our campus to pay a fee for an exam application - exam season, crowded, a bit chaotic. At the door stood a middle-aged security guard whose entire job was to regulate who went in and who goes out. But you could watch it happen in real time. The tiny scrap of authority went to his head. Instead of just doing the procedural thing, he got rude, made people wait, made sure everyone understood he was above them. And my conclusion was that this wasn't his personal problem. It was human nature problem talking through him. Flawed human nature talking through a thousand historical faces, across cultures, historical periods and position of power we've ever invented. It was just same old human nature doing it's thing, nothing more.

And it really is a constant. It doesn't matter what the culture is, how rich the society is, how good its anti-corruption laws are, or how transparent its institutions claim to be. These things change the rate. They don't change the direction. Sooner or later, someone with power over a shared resource, or post office entry door, will find a way to put themselves first and to missus.

This is the very old problem that plagued our societies for the centuries. Just look at how much of civilization is actually a response to it. Law. The separation of powers. Audits and oversight. Transparency requirements. A free press. Term limits. Cultural norms, honor and shame. Strip away the specifics and they're all the same kind of move: attempts to temper human nature from the outside. Every one of them is a railing built around the same cliff. Attempted behavioral modifiers with more or less historical success.

And basically every one of them shares the same flaw. The railing is also built and maintained by humans. The auditor can be bought. The judge has interests. The transparency report is written by the people it's meant to expose. We've been patching problem for millennia with tools that are made of the very material that causes it. That's why the patches are partial - they slow the failure, they never stop it.

What Was That Blockchain Actually For?

Blockchain is the first technological attempt to address this problem from a different angel - not by tempering human nature, but by removing the human from the loop entirely. Where possible. Lowering the space where misuse can happen. That's all.

Where every previous tool said "let's constrain the person in power," blockchain says "let's build a protocol that remove humans from risky loops!" The code should executes the same way every time, for everyone, regardless of who's asking. There's no official to lobby, no clerk to bribe, no authority whose discretion you have to trust, because there's no discretion left to misuse.

That's the real claim, and it's worth stating precisely: blockchain doesn't make people honest. It makes their honesty unnecessary. It's the first time we've tried to address subjective distortion of shared power not with a better human check on humans, but by taking the human out of the decision altogether lowering surface where misuse can happen (not entirely eradicating, we will come back to this later).

How?

That's the why, and it has to come first - once you see the real target, everything else falls into place as means to that end. But "remove the human from the loop" is an ambition, not a system. Three more questions turn it into something you can actually reason about, and each is only answerable once the one before it is settled. What does the protocol promise? How is it really built? And what can you honestly do with it?

The protocol: what it promises, and on what condition

If the point is a system that runs without a trusted human at its center, the protocol is what makes that possible - and its promises are the famous words: immutability, censorship-resistance, one canonical chain. The trap is treating them as unconditional. They aren't. Three things to keep apart: the mechanism (proof-of-work, proof-of-stake) is the how; the guarantee (immutability) is the what; and the assumptions (honest majority, bounded network delay, rational actors) are the fine print.

We recite the what and never say the under what conditions out loud - which is exactly where every famous failure lives. A 51% attack isn't a bug in the mechanism; the mechanism works as designed. What broke is the assumption underneath it. Immutability was always immutability-given-honest-majority. We just dropped the second half. A guarantee whose preconditions you don't state isn't a guarantee. It's a marketing claim.

The machinery: the spec versus the thing that actually runs

The protocol is a clean mathematical object with theorems. The thing actually running is a client - written by specific people, carrying properties the protocol never promised: consensus bugs, MEV, governance, the social layer that decides which fork is "real" when the chain splits.

The protocol is mathematical; the running blockchain is: social, cyrptograpical, economical and technical system. All this mixed together. The map is not the territory, and most of the real engineering - and the real drama - happens in the gap between those dimensions. Notice what surfaces here: the human we removed in the "why" creeps back in. Not as the official with discretion over your case, but as the person who writes the client, who governs the upgrade, who decides which fork to keep building on. Blockchain doesn't abolish human judgment. It relocates it - from the inside of every transaction to the edges of the system, where it's rarer, more visible, and harder to exercise quietly. That's a real improvement. It is not the same thing as the human disappearing.

And there's a deepest edge, the one that should worry you most: layer zero - the core developers, the community, the culture that produces a neutral protocol in the first place. That neutrality was itself an assumption. It held only as long as the people building the thing didn't want to bend it. But teams change. Culture drifts. A core team gets infiltrated, or simply captured, by people with different intentions, and now a totally different set of values is being projected onto the canvas of the technology - from the one position no consensus mechanism can defend. Call it the revenge of human nature: it doesn't break the cryptography, it walks in through the only door cryptography was never able to lock. This is the long-lasting problem of the field. Governance, and the human ability to capture the position from which the nature of the technology itself is decided.

So what is it good for?

One question settles it, and it points straight back at the beginning: does this remove a human point of failure that no law or audit could ever reliably fix? If yes, it's a real candidate. If the honest answer is "a trustworthy person already handles this fine," you're not solving the human-nature problem - you're just bolting a chain onto something that didn't need one.

Most of the hype fails that test. "Supply chain on the blockchain" is the textbook miss: the hard part was never storing the record, it was whether the human typing "ethically sourced" told the truth. The chain faithfully records the lie - you didn't remove the human failure, you notarized it. What passes points straight at the original target: money under an issuer who can debase or freeze it (remove the issuer, nothing left to debase), or value transfer an intermediary can be compelled to block - capital controls, a hostile border, a dissident (remove the intermediary, no one left to compel). Same shape every time: not "we trust the system more than the person," but "there is no longer a person whose honesty we're forced to depend on."

That problem is ancient. Blockchain is just the first tool we've built that doesn't try to make us better, and instead tries to make our weakness irrelevant until we really become better. To create better society without necessary having to create better people.