Permissionless

A system is permissionless when participation in it does not require approval from any gatekeeper. Anyone can run the software, connect to the network, publish, or transact, and the system itself has no mechanism — and no actor with the standing — to refuse. The internet's original design was permissionless in this sense: no application form to send an email, deploy a server, or write a client.

Bitcoin, Ethereum, Nostr, IPFS, and the broader free-software ecosystem extend the same principle into domains — money, identity, social communication, storage — that the legacy financial and platform infrastructure mediates through permission. The property is structural, not normative: permissionless does not mean rules-free or moderation-free. Communities, clients, and relays make their own choices about what to amplify or block; the protocol underneath has no actor with standing to lock anyone out.

The contrast is with permissioned systems — SWIFT, the credit-card networks, app stores, the corporate platforms whose business model depends on deciding who is allowed to participate. In a permissioned system, the right to participate is granted; in a permissionless one, it is presupposed. Permissionlessness is what makes the parallel-society thesis operational rather than rhetorical: whistleblowers publish without approval, counter-economic transactions clear without licensing, cypherpunk code spreads without export controls. The cost is that abuse must be handled at the edges rather than at the protocol — the cypherpunk position is that the asymmetry is correct.