Part 2 — The Stack
Part 1 established the problem and the philosophy. Part 2 explains the choices made to solve it.
We look first at what the EU's eIDAS 2.0 regulation actually mandates — not in legal language, but in practical terms: which standards, which formats, which flows, and what the implementation timeline looks like for anyone building in or for Europe.
Then we take an honest look at the generation of SSI technology that came before: Hyperledger Aries, ACA-Py, Indy, and DIDComm. Why was it built the way it was? What worked? What made it hard to adopt at scale?
Finally, we look at the stack that replaced it — OID4VCI + OID4VP + SD-JWT + did:web — and explain specifically why this set of choices simplifies everything. Standard HTTPS instead of DIDComm. JWTs instead of AnonCreds. A static JSON file instead of a blockchain.