Welcome to the Empeiria’s development update from April 2025
Over the past weeks our team focused on reliability, identity‑centric functionality, and polishing the end‑user experience.
Take a look at some of the key milestones that move our Self‑Sovereign Identity (SSI) stack closer to a public launch – and what they mean for builders and the wider community.
1. Test Infrastructure: From Unit to Full‑Stack Confidence
Testing is mission‑critical for an identity network, so we invested heavily in new automation.
Core libraries now sit at nearly 100 % unit‑test coverage, giving us early warning when edge‑cases creep in.
On top of that, we built a Docker‑orchestrated end‑to‑end (E2E) framework that spins up the complete stack – blockchain nodes, agents, and auxiliary services—in a disposable network.
Every pull request now runs the same interactions a production system would perform, catching integration bugs before they leave the branch.
2. Linked Resources Module: On‑Chain Proof for Any Asset
Our new linked‑resources Cosmos‑SDK module lets a DID owner anchor versioned resources -revocation lists, credential schemas, media, or arbitrary JSON directly on‑chain.
Each upload is signed by the DID controller, timestamped, and assigned a monotonic version so consumers can verify both authenticity and freshness.
This unlocks lightweight, verifiable registries without a separate storage service and paves the way for richer ecosystem integrations.
3. MCP Server: Faster QR Flows & Cloud‑Native Deployment
We released a brand‑new Model Context Protocol (MCP) Server, now hosted in its own repository at https://github.com/empe-io/mcp-server
The server exposes the complete set of SSI operations through a streamlined API and ships with plug‑and‑play Issuer and Verifier services you can deploy in a single click.
Test API keys and sandbox addresses are pre‑configured in the .env.test.example file, letting developers issue and verify credentials in minutes. A convenient /qr endpoint can also return wallet‑ready QR codes on demand, smoothing agent‑to‑wallet hand‑offs without extra libraries.
Learn more about EMPE MCP Server: https://x.com/empe_io/status/1920826190756995091
4. EMPE DID Wallet: Fresh Look, Secure Backups, Biometric Login
The wallet received its first full design overhaul since alpha.
Users will notice a cleaner layout, clearer credential previews, and snappier navigation on low‑power devices.
Under the hood we introduced an encrypted backup/export option that lets you download all credentials in a single protected file, while a companion seed‑word export secures your DID keys. Restoration stays a one‑tap operation—ideal for device migrations.
We also enabled biometric authentication and broadened deep‑link support for seamless transitions between any on‑device app and the wallet.
5. EMPE Hub: Credential‑Gated Airdrops & Faucet
On the platform side, the Airdrop section of the Empe Hub now issues an eligibility credential that doubles as anti‑sybil protection.
Holding that credential unlocks a new faucet protected by rate‑limits and on‑chain revocation checks, dramatically reducing the risk of bots draining test funds.
The flow showcases how Verifiable Credentials can safeguard token distribution without sacrificing user experience.
Stay tuned for upcoming details about on-chain airdrop!
6. AI Credential Agent Prototype: Conversational Issuance Demo
Our prototype conversational agent now begins each session with a quick KYC validation, confirming the user’s identity before any sensitive data is exchanged.
Once verified, the agent gathers only the necessary details about the user’s tax profile and – when the criteria are met the agent issues a compliant credential via the MCP pipeline.
The entire flow happens in a single chat, concluding with a wallet‑ready QR code, and demonstrates how SSI agents can seamlessly combine identity proofing and document issuance while keeping the user in control.
7. Backend & API: Launch‑Ready Clean‑Up
Finally, the API layer underwent a spring clean: we removed deprecated endpoints, unified error codes, and tightened request validation. Container hardening, SBOM generation, and stricter CI gates round out the picture, positioning us for external security audits and the forthcoming mainnet launch.
Looking Ahead
With confidence in our test coverage, a powerful new on‑chain resource model, and user‑facing tools ready for prime‑time, we are gearing up for performance tuning under load and a full security review.
May will also bring an external developer preview of the wallet SDK—stay tuned and, as always, thank you for building the future of trust with us!