Category:Crypto Technology

From P2P Foundation Wiki
Jump to navigation Jump to search

New section, part of a collection of related sections on


Quotes

Blockchain as Substrate for Regeneration‎

"AI alone is insufficient. AI can build tools, but tools need infrastructure. The affordances of blockchain technology provide the substrate on which regenerative systems can run, not out of blind allegiance to blockchain as an ideology, but because its specific technical properties align with what re/acc requires.

Privacy through zero-knowledge proofs. When everything on centralized platforms can be faked, when synthetic content becomes indistinguishable from human creation, we need cryptographic verification of provenance and identity. Zero-knowledge proofs enable verification without surveillance. You can prove you’re a member of a community, that you’ve completed a commitment, that you hold a credential, without revealing the underlying data. This is the technical foundation for coordination without control.

Auditability without centralization. Blockchain creates transparent, tamper-resistant records of commitments and transactions. This enables what traditional institutions promised but couldn’t deliver: accountability and trust. When a community currency’s issuance rules are encoded in a smart contract, no one can secretly inflate the supply. When a cooperative’s governance is on-chain, no faction can quietly change the rules.

Programmability of economic relations. This is perhaps the most profound affordance. Values can be encoded directly into the infrastructure of exchange. A token can be programmed to circulate only within a bioregion. Revenue can automatically flow to ecological restoration with every transaction. Governance rights can be distributed according to contribution rather than capital. The relationships that capitalism strips away can be programmed back into the medium of coordination itself.

Credible neutrality. Open protocols don’t privilege particular actors. Unlike platforms owned by corporations optimizing for extraction, protocols can be designed so that no party has special access or control. This is the technical basis for infrastructure that serves users rather than harvesting them."

- Benjamin Life [1]


The decentralisation lives in a layer almost nobody touches

1.

"The problem is not the vibes. It’s the architecture.

For example, Uniswap’s smart contracts run on Ethereum and are genuinely permissionless. But almost nobody interacts with them directly — 99% of users go through a single web interface, built and run by a single company, which can change it, restrict what it shows, or switch it off.19 This isn’t a criticism of Uniswap Labs for following the law; it’s the structural observation that the decentralisation never reached the layer people actually use. Whatever the protocol permits, the access point has a centre — and a system with a centre can be captured there, whether the lever is regulation, capital, or commercial incentive. The decentralisation lives in a layer almost nobody touches. The product is centralised. This pattern repeats across the ecosystem — decentralised in the architecture, centralised in the access layer, extractive at the economic layer, and gradually captured at the governance layer as capital concentrates.

In other words, many “decentralised” projects are most centralised where it matters most for them not to be."


2.

"This pattern is older than crypto, and bigger than it. Every distributed system humans have built drifts, over time, back toward a centre. Blockchain governance concentrates into plutocracy as capital concentrates. Mastodon develops admin hierarchies. Wikipedia evolves an entrenched editor class. Open source defaults to benevolent dictators. The internet’s protocols are decentralised at the wire level; the application layer that sits on top is owned by five companies. Distributed systems hold their distributed form only while their design actively resists re-centralisation — at every layer, all the time.

The counter-pressure is real, and it has several sources at once. Centralisation is what humans default to when coordination gets hard, because we each experience ourselves as the centre of our own world — all of our experience lands in the self, and the self builds the way each of us think. We build dependencies on ourselves. We make ourselves the point things flow through. And centralisation is the easiest way to make a system legible — to deliver clarity about who’s responsible, where the bottleneck is, who to ask. At scale, it’s also the fastest. The design problem is not whether to centralise. It’s what you have to build to deliver legibility, accountability, and speed without a centre.

Crypto’s failure was that it assumed decentralisation at one layer would propagate to the others. It didn’t. It can’t. The pull is too constant, the alternative interfaces too convenient, the capital too impatient. The architecture that resists re-centralisation has to be designed at every layer at once — protocol, application, governance, economics — or capital and convenience fills the gaps with centralised solutions."

- Cameron Burgess et al. [2]

Key Resources

Articles

* Decentralized Social Media (DeSco): 15 Years in the Making. Parallel Citizen. [3]

"This essay traces the 15-year arc of decentralized social media: its failed experiments, quiet successes, and the unresolved dilemmas still haunting the vision. The goal is not to predict a single “Facebook killer,” but to map how protocols, incentives, and culture have evolved - and what that means for builders, investors, and communities exploring new digital sovereignties."

Books

"Documenting 6 years of research on crypto, cultural economies, and internet subcultures."

Research

[5]


Technology

* Introduction to Web5, "a new paradigm that integrates the usability of Web2 with the decentralized values of Web3".

Pages in category "Crypto Technology"

The following 108 pages are in this category, out of 108 total.

Media in category "Crypto Technology"

This category contains only the following file.