Introducing attested.network: Proof of Payment for ATProtocol - Nick's Blog
attested.network is an open spec for decentralized proof of payments on ATProtocol, built on what we learned making atprotofans.com. It formalizes the three-party attestation model and opens it up for any app to implement.
Decentralization Trade Offs in AT Protocol and ActivityPub DWeb Camp 2026
Christine Lemmer Webber is lead author and co-editor of the W3C ActivityPub specification. Daniel Holmgren is Head of Protocol at Bluesky, working on the AT Protocol specification at the IETF. Join us for a discussion on decentralization trade-offs and other design decisions in the two protocols, and what that means for different architectures, structures, and even future points of convergence. Moderated by Boris Mann
The Specification Is Not a Document - The Phoenix Architecture
Imagine joining a software project a few years from now. It is a large, mature system. It has thousands of business rules, years of operational experience,…
ATProtocol Attestations: Cryptographic Signatures for the Decentralized Web - Nick's Blog
This post introduces the formal ATProtocol attestation specification, a framework for adding cryptographic signatures to ATProto records through two complementary patterns: inline attestations that embed signatures directly in records, and remote attestations that store proof in separate repository records. The specification prevents replay attacks through repository binding, uses CID-based content addressing for integrity, and provides the cryptographic foundation for verified credentials, trusted content, and authenticated interactions in the decentralized ATProtocol ecosystem.
Rocket Pool - Decentralised Ethereum Liquid Staking Protocol
Your friendly decentralised Ethereum liquid staking protocol
attested.network — Proof of Payment for ATProtocol
An open specification for decentralized, cryptographically verifiable proof of payments.
The 2026-07-28 Specification
The 2026-07-28 Model Context Protocol specification is out, bringing a stateless protocol core, Multi Round-Trip Requests, header-based routing, cacheable list results, authorization hardening, a formal extensions framework, and updated Tier 1 SDKs.
The CRDT Dictionary: A Field Guide to Conflict-Free Replicated Data Types - Ian Duncan
A comprehensive guide to CRDTs and their tradeoffs, from counters to sequences. Written in the spirit of the Typeclassopedia, exploring how different CRDTs solve the distributed consensus puzzle.
You. Must. Build. A. Raft! Consul's Consensus Protocol Explained
If you've used HashiCorp Consul, you may have heard of the Raft consensus algorithm it uses. This talk will explain Raft in plain English.
On Consensus and Humming in the IETF
The IETF has had a long tradition of doing its technical work through a consensus process, taking into account the different views among IETF participants and coming to (at least rough) consensus on technical matters. In particular, the IETF is supposed not to be run by a "majority rule" philosophy. This is why we engage in rituals like "humming" instead of voting. However, more and more of our actions are now indistinguishable from voting, and quite often we are letting the majority win the day without consideration of minority concerns. This document explains some features of rough consensus, what is not rough consensus, how we have gotten away from it, how we might think about it differently, and the things we can do in order to really achieve rough consensus. Note: This document is quite consciously being put forward as Informational. It does not propose to change any IETF processes and is therefore not a BCP. It is simply a collection of principles, hopefully around which the IETF can come to (at least rough) consensus.
On forking the Web
This document contains a set of informal notes on how to build an alternative specification to the Web, in such a way that hopefully prevents many of its drawbacks while still preserves many of the good points. This document is not an specification, and is therefore subject to change over time.
Writing about attested.network, an open spec for decentralized proof of payments on ATProtocol. It builds on what we learned making atprotofans.com. Draft is up and feedback is welcome.
Introducing attested.network: Proof of Payment for ATProtocol
ngerakines.leaflet.pubThe FOSDEM 2027 AT Protocol devroom proposal is taking shape. @edouard.paris and @viivi.rocks are leading the submission, due October 4. The draft covers protocol infrastructure, applications, governance, and critical perspectives. Share project ideas and use cases in the Discourse thread.
FOSDEM 2027 ATProto devroom proposal
discourse.atmosphere.communityI've been working on an "at protocol notion". One of the things that has been holding it up has been coming to terms with the oddities of putting this data on a PDS. A document is a collection of edits, whose edits we collect will change that document pretty substantially. This is a feature
What if a PDS became more than a repository for posts? We propose using AT Protocol as a creator-controlled publication layer for declaration metadata describing digital works, making rights, provenance, and other trusted metadata independently verifiable and easier to discover.
From Personal Data Server to Personal Metadata Server
liccium.leaflet.pubThis repository hosts the Ethereum proof-of-stake specifications for consensus-layer clients. Design rationale and proposed changes are discussed in issues. Agreed-upon changes are made through pull requests. Specifications can be found in specs, arranged by upgrade. Each upgrade builds on the previous, specifying only what it changes. Individual features are developed in parallel and are folded into an upgrade when ready.
