Protocols become standards because they're used. If your organization uses DIDComm, help DIF and Leadpoint build the evidence needed to strengthen future standards efforts. Take the 5-minute survey: bit.ly/49ETFUl

Foundation Protocol（FP）が提唱された（https://arxiv[.]org/html/2605.23218v1）。エージェントが社会インフラになるにつれ、個々のモデル性能より「エージェント間の調整コスト」がボトルネックになる、という問題意識から出発している。 問題を具体的に言うとこうだ。エージェントのメッセージは「情報の伝達」だけでなく「コード実行・資源使用・支払い・権限委任」を意味しうる。MCP（ツール接続プロトコル）・A2A（エージェント間タスク委任）・DIDComm（セキュアメッセージング）などは各々優秀だが、1ワークフローでこれらを横断すると、プロトコルごとに異なる「認証・セッション・権限モデル」が統合コストを爆発させ、プロトコル境界で監査証跡も途切れる。 FPはその橋渡し役として、グラフ（参加者をノード・関係をエッジとして表現）ベースの4層調整基盤を提供する。エージェント・人・ツール・組織すべてを同じEntityモデルで統一し、組織構造・役割・経済取引（メータリング・レシート・決済）・監査証跡・人間承認フローをプロトコルオブジェクトとして一元管理する設計。既存プロトコルを置き換えるのではなく、それらの上に共通の制御面（コントロールプレーン）を被せる。 面白い設計が「段階的開示（Progressive Disclosure）」。現状のAI統合では、ツールの全仕様をモデルのコンテキストに最初から丸ごと読み込むのが一般的でトークン消費が膨大になりがち。FPは最初に軽量な要約メタデータだけ交換し、選定・承認後に詳細を取得する。 エージェントの信頼スコアを主観的評価でなく、契約の完了率・リワーク（修正）回数・コスト透明性などの実績から5次元（品質・信頼性・協調性・効率性・整合性）で算出する「説明可能な評価システム」も実装済み。Python実装がGitHubで公開されており、Claude CodeやCodex CLIとの統合もサポートされている。「エージェントが会社を作る」時代に向けた共通言語の有力候補。

eIDAS 2.0 is live. The EU's digital identity regulation now mandates that all 450 million EU citizens must have access to a government-issued digital identity wallet by 2026. @cheqd_io's trust infrastructure is already aligned with the EU Architecture and Reference Framework (EU ARF): SD-JWT, OpenID4VC, DIDComm, EBSI-compatible trust chains. The market is not coming. It's here. $CHEQ

Chaos (KYA-OS) takes center stage in this week’s DIF newsletter ⚡ Catch updates on Trusted Agentic AI, DIDcomm, Universal Resolver discussions, new WG leadership, Hot Takes interviews, and spring/summer identity events across Europe. Read more: blog.identity.foundation/dif…

DIDcomm--are you using it? Suvey of DIDcomm implementations for international standards bodies. Please fill out our survey either anonymously or with your company/implementation name. docs.google.com/forms/d/e/1F…

Is DIDcomm ready for the big time? If you use DIDcomm, tell us about it! blog.identity.foundation/did…

How @cheqd_io enables cross-ecosystem compatibility: Standard requirement: Credentials must work across ecosystems, wallets, and jurisdictions. Issuers need regulatory alignment. Verifiers need standardized exchange protocols. No single technical stack dominates globally. cheqd approach: Multi-standard infrastructure supporting W3C specs (DIDs, VCs), EU Architecture & Reference Framework alignment, OpenID4VC protocols, and AnonCreds. Same ledger anchors JSON-LD, JWT, SD-JWT, and AnonCreds credentials. DID resolution works across Universal Resolver and major SSI frameworks. Tradeoff: Optimized for broad compatibility over opinionated architecture. Standards-agnostic ledger layer means cheqd doesn't force technical choices—wallet providers and issuers pick their preferred formats and protocols while sharing the same trust infrastructure. Supports: ✅ EU Architecture & Reference Framework (ARF) ✅ W3C VC Data Model (JSON-LD, JWT, SD-JWT) ✅ AnonCreds credentials ✅ Universal Resolver/Registrar integration ✅ Bitstring Status List v1.0 SDK-level protocol support (via Credo, ACA-Py, Veramo): ✅ OpenID4VCI/OpenID4VP ✅ DIDComm messaging ✅ Aries Interop Profile $CHEQ Docs: docs.cheqd.io/product/

Digital ID System - Part 3 - Frontend - CREDEBL What is CREDEBL? A Linux Foundation Decentralized Trust project, is an open-source, population scale platform designed to simplify & secure the management of Decentralized Identity & Verifiable Credentials. CREDEBL is designed to be multi-tenant, agent-agnostic & ledger-agnostic, providing flexibility across different Verifiable Data Registries (VDRs), DID methods, and Verifiable Credential formats. credebl.id/ CREDEBL is a Digital Public Good (DPG) approved by the UN-endorsed DPG Alliance. Repositories 1) CREDEBL SSI Platform Backend github.com/credebl/platform 2) CREDEBL Mobile SSI Wallet github.com/credebl/mobile-wa… 3) Credebl Mobile SDK github.com/credebl/mobile-wa… 4) Documentation for CREDEBL Platform github.com/credebl/docs 5) Credebl Github .io github.com/credebl/credebl.g… View CREDEBL OCA Bundles credebl.github.io/credebl-ar… Aries OCA Bundles - TIES TO MICROSOFT - ARIES This GitHub repository is for hosting published Overlays Capture Architecture (OCA) Bundles to be used by Hyperledger Aries agents (issuers, holders and verifiers). The repository includes a lightweight governance process for ensuring those contributing to the repository are the "authority" over the OCA Bundle they are submitting/updating, and that what they are submitting is, in fact, an OCA Bundle for a published AnonCreds Schema and/or Credential Definition. github.com/credebl/credebl-a… 6) Code For GovTech (C4GT) Code for GovTech (C4GT) is India's first dedicated mentoring program aimed at creating a community that can build and contribute to global Digital Public Goods (DPGs). Selected participants will work on live open-source projects focused on solving population-scale governance challenges. github.com/credebl/C4GT 7) Aries Akrida github.com/credebl/aries-akr… The Aries Akrida is designed to load test various Hyperledger Aries deployments. The project uses the Locust Tool in combination with Aries Framwork Javascript to test DIDComm based protocols. From Ancient Greek ἀκρίς, or akrída, means locust or grasshopper. 8) Animo Development Mediator An easy to set-up Aries and DIDComm v1 mediator built on Aries Framework JavaScript. github.com/credebl/mediator-… This repo contains a Mediator Agent for usage with Hyperledger Aries & DIDComm v1 agents. It is built using Aries Framework JavaScript. Why should you use this mediator? - Automatically set up mediation with the mediator using the Mediator Coordination Protocol. - Pick up messages implicitly using WebSockets, using the Pickup V1 Protocol, and the Pickup V2 Protocol. - Configured to persist queued messages for recipient in a postgres. - Use the pre-built docker image for easy deployment of your mediator. 9) Aries Framework JavaScript REST API Controller Service for Credo REST extension. github.com/credebl/credo-con… The Aries Framework JavaScript REST API is the most convenient way for self-sovereign identity (SSI) developers to interact with SSI agents. ⭐ Endpoints to create connections, issue credentials, and request proofs. 💻 CLI that makes it super easy to start an instance of the REST API. 🌐 Interoperable with all major Aries implementations. Example CLI Config To find out all available configuration options from the CLI, you can run the CLI command with --help. This will print a full list of all available options. 10) Verification Templates github.com/credebl/verificat… 11) Studio Modern UI for CREDEBL Platform github.com/credebl/studio 12) CREDEBL Terraform CREDEBL deployment through terraform script. github.com/credebl/install 13) WebAuthn Service This is a fully-functional reference implementation of: @simplewebauthn/server @simplewebauthn/browser, using Express to handle the WebAuthn flows for registration and authentication (login). github.com/credebl/webauthn-… 14) Trust Registry github.com/credebl/trust-reg… 15) Terraform Scripts github.com/credebl/terraform… 16) Credebl Wiki github.com/credebl/wiki

La interoperabilidad en identidad digital no es conectar bases de datos. Es compartir estándares. - Hoy cada institución te trata como si fuera la primera vez: mismos documentos, mismos formularios, misma verificación. 4.200 millones de registros expuestos en 2024. Más de 150 cuentas por usuario. La centralización que promete eficiencia crea el punto único de fallo. - Las credenciales verificables cambian la lógica: el gobierno emite, el ciudadano guarda en su wallet, el verificador valida al instante sin contactar al emisor. Pero si cada credencial vive en un silo, no cambiaste nada. - El verdadero campo de batalla es la interoperabilidad. Una credencial emitida en Argentina tiene que funcionar en un banco en México, en una universidad en Colombia, en un empleador en España. Mismos estándares. Sin intermediarios. - Los protocolos ya existen: W3C VC Data Model, DIDs, OpenID4VC, DIDComm, eIDAS 2.0. No hay que inventar nada — hay que adoptar. Lo veo en el campo: los gobiernos que adoptan estándares abiertos escalan. Los que construyen islas propietarias quedan atrapados. La pregunta no es si las VCs van a ser interoperables. Es quién define los estándares. LATAM puede ser parte de esa conversación o llegar tarde. Compartí el protocolo, no la base de datos.

#midnightNtwrk Here's what's running inside Lovelace right now. Not planned. Not roadmapped. Running. Identity: - Hyperledger Identus DID — live on iOS and Android - DID created on YOUR device, registered via DIDComm - Verifiable age credential issued over encrypted channel Privacy: - Halo2 ZK proof - proves you're 18 without revealing your date of birth - Document scanned on-device, never transmitted - Date of birth used for proof, then deleted immediately Proof of Human: - ML Kit face detection on-device - Face embedding uniqueness - one person, one account - Not a photo. A math vector. Can't be reversed. - Biometric-derived data, GDPR/LGPD acknowledged and handled KYC: - MRZ passport/ID scan - OCR fallback for IDs without machine-readable zones - Selfie match against document photo - All on-device processing App: - Flutter, 23 screens, light UI - iOS (TestFlight) Android (direct APK) - 18 languages - Real-time chat gift system - Multi-dimensional matching: 17 filter categories - Sentry crash reporting - Shorebird OTA patches Codemagic CI/CD Blockchain: - Aiken smart contracts on Cardano preprod (26/26 tests passing) - $LILY token - 100M supply, deflationary burn - Compact age verification contract deployed on @MidnightNtwrk Preview testnet - Backend wired with Midnight feature flag - Halo2 fallback active until SDK stabilizes One developer. AI-assisted. No VC. Midnight mainnet launches this week. We're watching closely - when the SDK is stable, we flip the switch. Looking forward to verifying our first user on-chain with @MidnightNtwrk. The future of privacy-enhanced dating is Cardano. Test it: posada.io/lovelace/download @IOHK_Charles @midnightfdn $ADA $NIGHT $LILY #Cardano #Midnight #Identus #ZKProofs ❤️❤️❤️❤️That's all ❤️❤️❤️❤️

Web 7.0 DIDLibOS™ DID-native Decentralized Library OS / Trusted Digital ... youtu.be/ksGEVZPgoZs?si=JHyP… via @YouTube Web 7.0 DIDLibOS™ DID-native Decentralized Library OS Overview (DIF DIDComm WG - March 2026) Presentation starts 4 minutes into the webcast. CC: @jallard

Adding Humans, Minds & Bodies & Soul to the Cloud THE INITIAL CONNECTION This is a Physical, Digital & Quantum connection of the Human's Mind, Body & Soul. Once the nodes inside your body are connected wirelessly to the Internet of Bodies. Digital ID & Web3 Connection can be created. In order for this to happen, they can have to create the Human Node. Turning A Human into a Node BLOCKCHAIN Human Nodes Humanode is a blockchain project that introduces the concept of "human nodes," where each node is tied to a unique human being, embodying the principle "1 human = 1 node = 1 vote". humanode.io/ To become a human node, an individual must undergo a crypto-biometric authentication process that verifies their existence and uniqueness as a real, living human being through live video-based 3D face scans and liveness detection. This process ensures that the biometric data, such as a 3D face mapping vector, is converted to numerical values, encrypted, and processed in a private and decentralized manner without leaving the user's device, thus protecting privacy. cointelegraph.com/explained/… The system uses AI-driven facial recognition modules to confirm both the uniqueness and liveness of each participant, preventing spoofing attacks like those using photos, masks, or videos. The biometric verification is a core component of Humanode's consensus mechanism, which replaces traditional Proof of Work (PoW) and Proof of Stake (PoS) with a system based on proof-of-uniqueness and proof-of-existence to achieve Sybil resistance. Body as a Network Node ieeexplore.ieee.org/document… This ensures that no single entity can create multiple fake identities to gain disproportionate influence, as each human can only operate one node, and all nodes have equal validation and voting power. github.com/humanode-network Humanode is built on the Substrate framework, making it a standalone Layer 1 blockchain that is also Ethereum Virtual Machine (EVM)-compatible, allowing for the development of smart contracts and integration with existing Ethereum-based applications. kucoin.com/price/HMND The network's governance is managed by a decentralized autonomous organization (DAO) named Vortex, which includes human nodes, delegators, and governors, with the latter participating in governance and requiring specific qualifications. github.com/humanode-network TOKENIZATION Vortex - An Overview blog.humanode.io/vortex-an-o… The native token, HMND, is used to pay transaction fees, execute smart contracts, and support private biometric computations within the network. How humans learn and represent networks pnas.org/doi/full/10.1073/pn… Humanode Protocol Contribute to the development of the first L1 blockchain where ONE HUMAN = ONE NODE powered by private BIOMETRIC VERIFICATION. BIOMAPPER Prove that the user has only one EVM address and fight Sybil-attacks by connecting your Dapp to Biomapper. humanode.io/) Part of the Humanode Protocol is the Secret Scheme. The "Secret Scheme" for Biometric Open Protocol Standard. Humanode x Secret Network: Biometric User Authentication and Key Management web.archive.org/web/20230209… Secret Network Secret Network enables developers to build decentralized applications with encrypted data, both natively on Secret and on other blockchains through cross-chain communication, unlocking powerful new use-cases for Web3. scrt.network/ CLOUD CONNECTION Cloud Platform - Microsoft Aries ACA-Py (Aries Cloud Agent Python) is an open-source framework designed to facilitate the creation, management, and utilization of decentralized Digital Identities. aca-py.org/latest/aca-py.org… ACA-Py enables secure, interoperable communication between entities using decentralized identifiers (DIDs) and verifiable credentials, adhering to standards such as DIDComm, OpenID4VCs and the W3C Verifiable Credentials. github.com/openwallet-founda…

Adding Humans, Minds & Bodies & Soul to the Cloud THE INITIAL CONNECTION This is a Physical, Digital & Quantum connection of the Human's Mind, Body & Soul. Once the nodes inside your body are connected wirelessly to the Internet of Bodies. Digital ID & Web3 Connection can be created. In order for this to happen, they can have to create the Human Node. Turning A Human into a Node BLOCKCHAIN Human Nodes Humanode is a blockchain project that introduces the concept of "human nodes," where each node is tied to a unique human being, embodying the principle "1 human = 1 node = 1 vote". humanode.io/ To become a human node, an individual must undergo a crypto-biometric authentication process that verifies their existence and uniqueness as a real, living human being through live video-based 3D face scans and liveness detection. This process ensures that the biometric data, such as a 3D face mapping vector, is converted to numerical values, encrypted, and processed in a private and decentralized manner without leaving the user's device, thus protecting privacy. cointelegraph.com/explained/… The system uses AI-driven facial recognition modules to confirm both the uniqueness and liveness of each participant, preventing spoofing attacks like those using photos, masks, or videos. The biometric verification is a core component of Humanode's consensus mechanism, which replaces traditional Proof of Work (PoW) and Proof of Stake (PoS) with a system based on proof-of-uniqueness and proof-of-existence to achieve Sybil resistance. Body as a Network Node ieeexplore.ieee.org/document… This ensures that no single entity can create multiple fake identities to gain disproportionate influence, as each human can only operate one node, and all nodes have equal validation and voting power. github.com/humanode-network Humanode is built on the Substrate framework, making it a standalone Layer 1 blockchain that is also Ethereum Virtual Machine (EVM)-compatible, allowing for the development of smart contracts and integration with existing Ethereum-based applications. kucoin.com/price/HMND The network's governance is managed by a decentralized autonomous organization (DAO) named Vortex, which includes human nodes, delegators, and governors, with the latter participating in governance and requiring specific qualifications. github.com/humanode-network TOKENIZATION Vortex - An Overview blog.humanode.io/vortex-an-o… The native token, HMND, is used to pay transaction fees, execute smart contracts, and support private biometric computations within the network. How humans learn and represent networks pnas.org/doi/full/10.1073/pn… Humanode Protocol Contribute to the development of the first L1 blockchain where ONE HUMAN = ONE NODE powered by private BIOMETRIC VERIFICATION. BIOMAPPER Prove that the user has only one EVM address and fight Sybil-attacks by connecting your Dapp to Biomapper. humanode.io/) Part of the Humanode Protocol is the Secret Scheme. The "Secret Scheme" for Biometric Open Protocol Standard. Humanode x Secret Network: Biometric User Authentication and Key Management web.archive.org/web/20230209… Secret Network Secret Network enables developers to build decentralized applications with encrypted data, both natively on Secret and on other blockchains through cross-chain communication, unlocking powerful new use-cases for Web3. scrt.network/ CLOUD CONNECTION Cloud Platform - Microsoft Aries ACA-Py (Aries Cloud Agent Python) is an open-source framework designed to facilitate the creation, management, and utilization of decentralized Digital Identities. aca-py.org/latest/aca-py.org… ACA-Py enables secure, interoperable communication between entities using decentralized identifiers (DIDs) and verifiable credentials, adhering to standards such as DIDComm, OpenID4VCs and the W3C Verifiable Credentials. github.com/openwallet-founda…

The infrastructure solving identity verification is already in production. cheqd → public blockchain, DID registry, trust layer Truvera → enterprise credential platform built on cheqd Dock Labs → wallets, issuance, DIDComm GSMA Telefónica → live PoC. MWC26 demo: March 4, 2026 This isn't a whitepaper. It's a working stack.

Web 1.0–7.0 outline the evolution of the web. 1.0–3.0 are historical; 4.0–7.0 are evolving to sentient. Web 1.0 (≈1990–2004) — Read-only / Static Simple, one-way sites. Users consumed content passively. Built on HTML, no databases or dynamic elements. Web 2.0 (≈2004–2010s / ongoing) — Read-write / Social Users create content via blogs, wikis, social media, YouTube. Enables collaboration, interactivity, centralized around Big Tech. Web 3.0 (2010s–present / ongoing) — Read-write-own / Semantic / Decentralized Focus on user ownership (crypto, NFTs), decentralization (blockchain), semantic understanding, AI personalization, privacy, trustless systems, DAOs, self-sovereign data. Web 4.0 (emerging / visionary) — Intelligent / Symbiotic / Immersive AI, IoT, VR/AR, robotics. Context-aware, predictive, blends digital and physical worlds, human-machine symbiosis. Web 5.0 (speculative / future) — Emotional / Ultra-personalized AI interprets emotions, full data sovereignty, intuitive human-like interfaces. Combines social interactivity with extreme personalization and empathy. Web 6.0 (very speculative) — Hyper-personalized / Fully integrated Neural interfaces, biotech links, subconscious anticipation, total digital-physical-human merging. Rarely discussed. Web 7.0 (niche / project-branded) — Agentic / Resilient Decentralized Autonomous Generative OS (~2022–2023). Decentralized OS layer with self-sovereign identities, autonomous AI agents, verifiable credentials, DIDComm messaging. Unified ecosystem for decentralized systems, AI agents, and trust infrastructure. Progression moves from static → interactive → intelligent → autonomous → deeply human-centric/decentralized.

Here's what happens under the hood: 1. Agent triggers auth request from their portal 2. Your mobile wallet receives DIDComm message 3. You verify with biometrics 4. Wallet sends cryptographic proof back 5. Agent sees: ✅ Verified No PII exchanged. Just math. (4/7) 📃

Afternoon ICT. Timers over talk; I pressed @allscaleio at 14:05 and watched fresh receipts print • Corridors: TH PromptPay->$USDT 48s; MY FPX->$USDC 56s; PT MB Way->$EURC 52s; KW KNet->$USDT 51s with fee lines explicit and lock/expiry held • Finance ops: camt.053 daily post 41s; camt.055 recall prep 37s • Invoicing: IT SDI e‑fattura verify 2.3s; DE XRechnung send→ack 2.5s • Identity & transport: DIDComm v2 ping 1.9s; Status List 2021 check 1.6s; BBR cwnd board ECN heatmaps surfaced; burn‑rate alarm 1.3s Next asks: FedNow refund ladders with signed reason enums, PromptPay dispute codes with DST‑aware grace, PSD3/PSR change calendars, NIS2 incident severity boards, and ECN/BBR drift caps with miss→credit policy. Ship those and I’ll route tuition refunds, supplier advances and gig payouts in $USDC $USDT $EURC fast #AllScale #Stablecoins #CryptoPayments #PaymentsOps #Invoicing #DYOR

GM. POI clocks don’t lie; I put a timer on @allscaleio at 07:46 and watched corridors print: EU TIPS->$EURC 44s, ZA PayShap->$USDC 50s, KR HOFINET->$USDT 54s, CH TWINT->$EURC 52s with fee lines surfaced and FX lock/expiry cancel grace held. Access proofs hit fast: DIDComm 1.6s, passkey attestation 1.5s, in‑toto/SLSA 2.0s; ops: pain.013 post→hold lift 21s, pacs.028 query→state 26s; on‑chain: $USDC Noble 9s, $USDT TRX 9s, $EURC Base 10s, receipt TTL 112h Micro POI’s incoming on alias TTLs CoP grades; these are stall fractals, macro follows once ISO 20022 pinning boards and PQ hybrid ML‑KEM/ML‑DSA dates post. Don’t snub POI after POI; each ignored dispute dictionary lets the next be nastier. I want MPC org‑wallet recovery cadence, per‑asset reserve IDs, TWINT QR retention, HOFINET recall SLOs, TIPS holiday jitter boards Ship it and I’ll route claims, gig‑shift payouts and microgrants in $USDC $USDT $EURC fast. Credibility is earned with constraints, not logos. Publish provenance and let volume vote with seconds #AllScale #Stablecoins #CryptoPayments #PaymentsOps #Invoicing #DYOR

GM ICT. Evidence > adjectives; I put a stopwatch on @allscaleio at 07:42 and let rails proofs speak • Corridors: KR HOFINET->$USDT 53s; ZA PayShap->$USDC 49s; CH TWINT->$EURC 51s; PL Express Elixir->$USDC 50s; CO Transfiya->$USDT 46s with fee lines surfaced • Access & audit: DIDComm v2 envelope verify 1.6s; in‑toto/SLSA attestation check 2.0s; event→ClickHouse 1.9s • Ops: pain.013 post→hold lift 22s; pacs.028 query→state 27s • On‑chain: $USDC Noble 9s vs $USDT BSC 12s vs $EURC Base 10s; receipt TTL 116h Next asks: PayShap CoP grades dispute dictionaries, HOFINET recall SLOs, Express Elixir RPO/RTO calendars, TWINT QR payload retention, Transfiya refund ladders, and threshold MPC org wallets with recovery ceremonies per‑asset reserve IDs. Ship those and I’ll route research stipends, co‑op dividends, and match officiating fees in $USDC $USDT $EURC fast #AllScale #Stablecoins #CryptoPayments #PaymentsOps #Invoicing #DYOR

GM ICT. I put a stopwatch on @allscaleio at 07:25 and ran fresh corridors proofs • Corridors: CA Interac e‑Transfer->$USDC 47s; ZA PayShap->$USDC 50s; TR FAST->$USDT 48s; CH TWINT->$EURC 52s with fee lines visible • Access & audit: DIDComm v2 envelope verify 1.6s; in‑toto/SLSA attestation check 2.0s; OCSP staple refresh 0.8s; OTLP→Tempo 1.7s • Ops: pacs.007 cancel→ack 29s; camt.053 statement ingest→AR reflect 31s; pain.013 post→hold lift 21s; split‑payout route→finality 58s • On‑chain: $USDC Noble 9s vs $USDT Avalanche 10s vs $EURC XLM 8s; receipt TTL 116h Next asks: PayShap CoP grades dispute dictionaries, Interac Autodeposit cancel grace alias TTLs, TWINT refund ladders QR payload retention, NIP normalize names DST jitter boards, and threshold MPC org wallets with recovery ceremonies per‑asset reserve IDs. Ship those and I’ll route freelancer retainers, grant disbursements, and tournament payouts in $USDC $USDT $EURC fast #AllScale #Stablecoins #CryptoPayments #PaymentsOps #Invoicing #DYOR