Soulprint v0.5.0 — Most Stable Release Yet 🛡️
We're excited to announce Soulprint v0.5.0, the most stable and reliable release of the decentralized identity verification protocol for Colombian citizens.
What's New
🌐 4-Node Validator Network on Railway
Soulprint now runs a 4-node validator network deployed on Railway:
-
soulprint-node-production.up.railway.app— Validator 0 (superAdmin) -
soulprint-validator-1-production.up.railway.app— Validator 1 -
soulprint-validator-2-production.up.railway.app— Validator 2 -
soulprint-validator-3-production.up.railway.app— Validator 3
All nodes are registered in the PeerRegistry smart contract on Base Sepolia, enabling automatic peer discovery and consensus.
🇨🇴 Registraduría Nacional Validation
Critical security fix: Soulprint now validates Colombian cédulas against the Registraduría Nacional del Estado Civil before issuing identity nullifiers.
GET /verify/cedula?numero=XXXXXXXX&fechaNac=YYYY-MM-DD
Response:
{
"ok": true,
"vigente": true,
"status": "VIGENTE",
"numero": "12345678",
"fechaNac": "1990-01-15"
}
If Registraduría is unreachable, the system gracefully degrades (logs a warning but does not block verification).
🔧 Fixed workspace:* Dependencies
All workspace:* protocol dependencies have been resolved to concrete npm versions, making soulprint-network installable in any environment:
npm install -g soulprint-network@0.5.0
Install & Run
npm install -g soulprint-network@0.5.0
soulprint-node
Or with Docker:
FROM node:22-slim
RUN npm install -g soulprint-network@0.5.0
ENV SOULPRINT_PORT=4888
EXPOSE 4888
CMD ["node", "/usr/local/lib/node_modules/soulprint-network/dist/server.js"]
Architecture
Soulprint uses a multi-layer architecture:
- ZK Proofs — Circom-based zero-knowledge proofs for biometric verification
- P2P Network — libp2p with Kademlia DHT + GossipSub for peer discovery
- On-chain Registry — PeerRegistry contract on Base Sepolia for node registration
- Credential Verification — Email, phone, GitHub, and now Registraduría validation
Links
- GitHub: https://github.com/manuelariasfz/soulprint
- npm: https://www.npmjs.com/package/soulprint-network
- PeerRegistry: https://sepolia.basescan.org/address/0x452fb66159dFCfC13f2fD9627aA4c56886BfB15b
Built with ❤️ for Colombia's digital identity future.
Top comments (1)
Great progress — especially moving to a 4-node validator topology and cleaning up dependency determinism. That’s a real stability step.
A few architectural thoughts that may strengthen this further:
• If Registraduría validation is now part of the trust boundary, consider clearly defining the failure mode. “Graceful degradation” is operationally convenient, but from an identity integrity standpoint, it may introduce ambiguity. Explicit policy around offline issuance vs delayed issuance would tighten the threat model.
• With libp2p + DHT + GossipSub, validator trust assumptions become critical. Is validator admission permissioned via on-chain governance, or can Sybil-like behavior emerge at the P2P layer?
• ZK proofs for biometric verification are powerful — but lifecycle management matters. What’s the nullifier revocation or key-rotation strategy if biometric anchors are compromised?
• Running validators on Railway is fine for early-stage deployment, but long-term, geographic and infrastructure diversity will matter for resilience claims.
Overall, this is moving in the right direction.
Identity systems aren’t just about cryptography — they’re about clearly defined trust boundaries and operational invariants.
If those are formalized early, Soulprint can evolve from “working protocol” to institutional-grade infrastructure.