DFOS Identity Bridge, Federated Auth & Fee Model v2
Every login now creates a DFOS genesis chain. Four-node relay mesh live. The economic model got its first real spec.
π DFOS Identity Bridge β LIVE (#532)
- Genesis is client-side β server never holds private keys.
@imajin/dfosbridge wrapscreateIdentityChain()for browser - Lazy backfill on login β existing users without relay chains get one silently on next login
- Ryan's prod DID backfilled immediately:
did:dfos:7v4vtfnh7v28ka7af3cv79 - Four-node mesh confirmed: ATX / NYC / LIS peered with Imajin. Content syncing across US + Portugal
- Brandon's Go relays push to us; peer-back pending (he'll poll our
/log)
π‘ RFC-22: Federated Authentication
Three iterations in one session to get it right.
- v1: OAuth-style redirect β too complex
- v2: Email verification primary β but emailβDID is private by design (Brandon confirmed)
- v3 (final): Consent-and-sign redirect. User clicks "Login with DFOS" β redirect to home platform β authenticate + consent β platform signs challenge (KMS for custodial, user key for self-sovereign) β redirect back with signed JWS β verify against chain key
- Three tiers: direct key auth (strongest) β consent-and-sign redirect (primary cross-platform) β email verification (fallback)
π° Fee Model v2 (RFC Draft)
Three-party settlement: 1% protocol + 0.5% node + 0.25% user credit.
- Dual-token: MJN (equity, earned through usage) + MJNx (stable, CHF-pegged)
- Gas: 100% to node, MJN-denominated, bilateral signature (relay + user)
- Rate integrity: decreases instant, increases require 24h notice. Rate schedule on-chain. Peering relays audit
- Revenue streams: settlement fees, app licensing, professional services, managed hosting, compliance certification
π§ Fixes
- Migration system fixed β
drizzle-kit pushbanned,migrate.shis the only path. CI check added (scripts/check-migrations.sh) - Carmen email bug β payment webhook had no try/catch around onboard token insert. One failure killed all subsequent emails silently. Each step now fails independently
- RFC-21: Imajin Conformance Suite β tests ARE the spec, ~35 assertions, 7 categories. Certification as commercial product
π By the Numbers
- 4 RFCs written or updated (19β22)
- 4-node relay mesh live
- Fee model v2 specced (three-party + dual-token)