Evidence at a glance

157,149,246

people live in designated Mental Health Professional Shortage Areas (as of June 30, 2026).

Source: HRSA, 2026

96.3%

of people with a 12-month DSM-IV disorder who perceived a need and did not seek treatment reported an attitudinal barrier (24 countries, n = 4,583).

Source: Andrade et al., 2014

290,054,222

individuals affected, reported as a combined total by the 741 breach filings affecting 500 or more individuals submitted to HHS in 2024 (portal tally, Sept 30, 2026).

Source: HHS OCR breach portal

52.1%

of trial participants understood randomization, the least-understood consent component (103 studies).

Source: Tam et al., 2015

Data and code: rv-evidence.csv · build-rv-charts.py

Connect a desktop EIP-6963 wallet to explore the live ecosystem prototype. Tested with Rainbow, MetaMask, Coinbase Wallet, Brave Wallet, Rabby and Keplr.
Permission Bridge

FSL Evidence Portfolio

SOVEREIGN by Design

Decentralized infrastructure for sovereign data governance — using regulated behavioral health as a deliberate proving ground

Phase 1 Demonstration — Sepolia Testnet

All contracts and tokens on Ethereum Sepolia testnet. No real monetary value. Honest framing — this is a working prototype, not a finished product.

Connect a desktop EIP-6963 wallet. Tested with Rainbow, MetaMask, Coinbase Wallet, Brave Wallet, Rabby and Keplr. A wallet is optional — the architecture is explained throughout for reviewers who prefer not to connect.

Connecting here asks your wallet to sign a single-use ecosystem sign-in message, and the EncryptHealth links in the connected panel carry that sign-in over with a single-use, 60-second handoff code. Known limitation: desktop browser-extension wallets are the supported path for this proof-of-concept; mobile WalletConnect signing is not yet reliable.

Every system on this site was designed and built end to end by Margarita Montañez Davenport: product definition and requirements, UX research and UI design, front-end and back-end engineering, smart contracts, data models and FHIR/HL7 interoperability mappings, security review, testing, infrastructure, and deployment.

This ecosystem is the Applied Project for Margarita Montañez Davenport's Doctor of Engineering (Engineering Management) application to Arizona State University's Ira A. Fulton Schools of Engineering.

Doctoral framework: Praxis-track applied engineering — the deployed system IS the research contribution; the Research Document formalizes methodology, results, and generalizability.

Target enrollment: Spring 2027 (priority deadline October 1, 2026). BS MIS from Colorado State University conferred July 2026 (GPA 3.91, direct-qualifying applicant).

Research focus: FSL is a decentralized infrastructure framework for sovereign data governance, with behavioral health as the deliberate proving ground — chosen because it imposes the strictest regulatory load (HIPAA + 42 CFR Part 2), the highest stigma cost for data leakage, and the most complex consent topology of any deployable domain. The architecture is generalizable to real estate, supply chain, identity, government records, and other domains where participant-controlled data sovereignty is load-bearing.

Central research question: Can wallet-signed bilateral consent serve as a defensible governance primitive for sovereign behavioral health data?

Faculty alignment (Arizona State University):

Three necessary lenses: BUILD — Dr. Dragan Boscovic (Blockchain Research Lab): ecosystem architecture, on-chain bilateral attestation engineering, smart contract verification. PROVE — Dr. Gail-Joon Ahn (Fellow of IEEE and ACM; Cybersecurity / SEFCOM): consent formalization, formal access-control rigor, protocol property verification. VALIDATE — Dr. Hassan Ghasemzadeh (EMIL Lab): operational validation methodology, live deployment evidence.

Evidence portfolio:

  • Ten current smart contracts on Ethereum Sepolia (13 deployed: 10 current, 2 superseded — SovereignLedger v2 and BenevolenceFund v2 — and SovereignLedger v4, awaiting its production switch)
  • 4 platforms operational + 1 scaffolded backend (NeuroBalance biosensor integration layer). NeuroBalance is the planned collection methodology that runs on this wearable scaffold — consent-gated longitudinal tracking of sleep architecture, heart-rate variability, activity rhythm, and circadian regularity as observable signals hypothesized to correlate with neurotransmitter-system function; its consent registry (NeuroBalanceConsent, source-verified on Sepolia) is deployed and the methodology is scaffolded.
  • Four flagship demos deployed and playable with on-chain HNT reward minting across three tiers: Bilateral Stimulation (L1), Build Your Plate (L2), Companion (L2), Constellation (L3). The L1/L2/L3 framework is architecturally wired for full build by 3D game designers. Each is playable at encrypthealth.io with a connected wallet on Sepolia; the recorded walkthrough plays Bilateral Stimulation end to end, with all four on the dashboard.
  • 3 open-source contributions (bcgov/aries-vcr #811, openmrs/fhir2 #577, openmrs/fhir2-ig #63)
  • Consent-gated wearable data — working demonstration against the Google Health API, with on-chain permission attestation
  • AI council defined on self-hosted infrastructure
  • Ethereum Sepolia testnet + XRPL multi-chain readiness (scaffolded)
  • Wallet-gated file vault: files are encrypted on the participant’s device, stored on IPFS via Pinata, and decryption keys are released only against an active participant consent grant. The vault is enabled in production, with zero participant files stored as of October 2026.
ResourceLink
CVView CV →
GitHubgithub.com/Future-Systems-Lab
OSS PRsaries-vcr #811 (merged) · fhir2 #577 · fhir2-ig #63
Giteagit.futuresystemslab.io

Why This Exists

My older brother EJ and I carried what happened to us in that house long after we left. We understood each other in a way only people who survived the same thing can. He made it to 50. He got a promotion. He felt overwhelmed and did what I had done - he asked for help. He went to his doctor. He was put on mental health medication. He noticed it did not feel right and said so. He called the office. He made an appointment. The office cancelled it. And cancelled it again. And cancelled it a third time. While he was on medication that was altering his neurochemistry, in a window of acute vulnerability that required urgency, the system sent him a cancellation notice. Three times.

On October 29, 2023 - six days after his 50th birthday - EJ took his own life.

I had sat in that psychiatrist’s chair and been told my absence was not her responsibility. EJ had made three appointments and been turned away every time. We came from the same house. We fought the same battles. We both reached for the same system. The difference in our outcomes was not effort. It was not willingness. It was not strength. It was a cancelled appointment. It was a doctor who decided follow-up was not her job.

EJ did not fail the system. The system failed EJ — specifically, precisely, and preventably. The gaps that killed him aren’t edge cases; they’re architectural features of a system designed around institutional convenience rather than human need. Future Systems Lab is the response: infrastructure that puts the person at the center of their own record, consent, and continuity of care. Behavioral health is the proving ground because it’s the hardest domain — the most regulated, the most identity-sensitive, the most consequential when systems fail. If the architecture holds here, it holds anywhere data sovereignty matters.

Advisory Targets · Arizona State University

CENTRAL RESEARCH QUESTION

Can wallet-signed bilateral consent serve as a defensible governance primitive for sovereign behavioral health data?

One doctorate. Three necessary lenses: BUILD → PROVE → VALIDATE. Remove any one and the work does not stand.

THE PERMISSION BRIDGE — THE FSL MARK

The logo at the top of this page was derived from the research question, not chosen for it.

Circle — wholeness; the complete, integrated system.

Triangle — three load-bearing properties, all required: Autonomous · Pseudonymous · Secure.

Center — bilateral consent. Where two parties meet to sign; neither acts alone.

The center of the mark is the research question.

BUILD PRIMARY ADVISOR TARGET

Dragan Boscovic

Director · Blockchain Research Lab · ASU

Can bilateral consent be implemented as an atomically-verified on-chain attestation that holds across a deployed multi-platform ecosystem?

Smart contract architecture and on-chain data structures. His lab is the direct intellectual ancestor — Vishnoi’s 2020 MedFabric4Me thesis (NuCypher proxy re-encryption) placed an intermediary in the trust path; FSL removes it by deriving keys from the participant’s own wallet signature. The doctoral contribution extends this to bilateral HKDF-derived session keys, so a session can only be established with both parties’ consent.

Detailed advisor brief →
PROVE

Gail-Joon Ahn

Professor · Cybersecurity · ASU

Does the dual-signature protocol satisfy formal properties of verifiability, attributability, revocability, and non-repudiation?

Co-advisor target for consent formalization and formal access-control rigor. The Phase 5 dual-signature bilateral consent flow — EIP-191 paired with EIP-712, HKDF session-key derivation so a session can only be established with both parties’ consent — engages his formal access-control expertise. Section 10.3 of the manuscript names formal verification of these properties as an open problem; his access-control formalism (Frankenstein, S&P 2025; CLEARS, CIC 2025) offers a path to closing it.

Detailed advisor brief →
VALIDATE

Hassan Ghasemzadeh

Professor · EMIL Lab · ASU

Does the protocol hold up in live behavioral-health deployment — comprehension, workflow, engagement?

Digital health systems, behavioral-health informatics, and AI-driven intervention methodology. His EMIL Lab’s work on deployed health-monitoring systems and real-world validation methods maps directly to the operational research question: does wallet-signed bilateral consent hold up in live sessions? Workflow impact, completion rates, latency, and participant comprehension are empirical questions — his methodology turns the deployed architecture into evidence.

Detailed advisor brief →

Thesis

DOCTORAL APPLIED PROJECT

DEng, Arizona State University — target Spring 2027

“Bilateral Wallet-Signed Consent: A Custom Signature Protocol for Decentralized Sovereign Data Governance, with Behavioral Health as Proving Ground.”

Central research question: Can wallet-signed bilateral consent serve as a defensible governance primitive for sovereign behavioral health data?

Behavioral health is the proving ground — the hardest regulatory, ethical, and identity-sensitive environment in which to validate that participant-controlled data architecture can scale. The infrastructure operates across six interlocking layers: Financial (XRPL multi-chain scaffold for future payment acceptance and ISO 20022 alignment, HNT tokenomics), Identity (deployed: EIP-191 single-signer wallet-gated consent — your wallet is your pseudonymous identity, no email, no password, no conventional direct personal identifiers; doctoral contribution: EIP-191 + EIP-712 dual-signature bilateral consent with HKDF session-key derivation, U.S. Provisional Patent Application No. 64/106,748, filed July 2026), Governance (SovereignLedger session attestation, AI orchestration pipeline), Compliance (regulation-aware architecture operating outside HIPAA scope), Therapeutic (HypnoNeuro L1/L2/L3 game framework — four demos deployed and playable with on-chain HNT reward minting: Bilateral Stimulation L1, Build Your Plate L2, Companion L2, Constellation L3; AlchemistForge shadow integration, Sovereign Guide framework), and Research (manuscript under peer review at Blockchain in Healthcare Today (BHTY), submitted August 30, 2026, revised October 6, 2026, IRB scaffold, 3 open-source contributions).

If the architecture survives behavioral health, it generalizes. Legal records, education, identity, supply chain — anywhere data sovereignty matters.

This page is the evidence.

Publication

Manuscript Under Peer Review

Manuscript under review, Blockchain in Healthcare Today (submitted August 30, 2026; revised manuscript submitted October 6, 2026). Citation and access will be published here upon journal acceptance.

Doctoral Research Contribution — Phase 5: Open Problem

✓ Deployed

Phase 1

Contract deployment

SovereignSession deployed + signaling server operational

⚠️ Scaffolded

Phase 2

Bilateral consent capture

Deployer-signed SovereignLedger claims (server-authoritative). Guide-initiated claim signing pending Phase 5

⚠️ Specified

Phase 3

EncryptHealth integration

Architecture specified. Direct contract calls pending

⚠️ Specified

Phase 4

Session attestation

Schema designed. Awaiting bilateral co-signing (Phase 5)

🔴 Open Research Problem

Phase 5

Doctoral applied-project contribution

Phase 5 — Bilateral Dual-Signature Consent (EIP-191 + EIP-712 + HKDF)

Both Sovereign Guide AND Participant produce two signatures each: an EIP-191 plain-language consent signature and an EIP-712 typed structured session attestation signature. The second party’s EIP-712 signature cryptographically embeds the first party’s, creating bilateral interdependence. Session encryption keys derive via HKDF from both EIP-712 signatures, so a session can only be established with both parties’ consent.

Why this is an open research problem: EIP-191 is single-signer by design. EIP-712 provides typed structured data but no canonical bilateral consent pattern exists. Existing multi-sig wallets (Safe, etc.) solve treasury, not session attestation. Threshold signatures (Lindell’s two-party ECDSA; FROST threshold Schnorr) require interactive multi-round protocols incompatible with consumer wallets. No published system among those surveyed combines EIP-191 plain-language consent + EIP-712 typed session attestation in a bilateral architecture with HKDF-derived session keys — this is the active research problem (patent-pending; Provisional Application No. 64/106,748, filed July 7, 2026).

Status: Phase 1 deployed; Phases 2–4 scaffolded and specified. Phase 5 is the applied research frontier this proof-of-concept investigates, as submitted with the ASU DEng (Spring 2027) application. The bilateral consent protocol is patent-pending under U.S. Provisional Application No. 64/106,748 (filed July 7, 2026); the single-party consent architecture of Phases 1–4 is covered by 64/063,037 (filed May 11, 2026).

Live Demo Recording

Recorded July 12, 2026 — Sepolia testnet, simulated data.

Note: the storage panel at 1:42 shows July 12, 2026 interface copy, retired in the July 15, 2026 claims audit.

Download recording (2.9 MB, mp4)

Recorded July 12, 2026 — a participant connects via the EIP-6963 wallet picker, signs plain-language informed consent, completes a bilateral-stimulation Sovereign Exercise (bilateral stimulation — rhythmic, alternating left-right sensory engagement — is a technique widely discussed in published psychology literature for its calming, focus-settling effects; here it is taught as a self-guided educational exercise, not a clinical procedure), HNT mints to the participant (owner-signed, server-side) and the reward is recorded in the participant chart; the participant can add HNT to their wallet display via EIP-747 (wallet_watchAsset); the mint is independently verifiable on Sepolia Blockscout. Why this matters: the on-chain mint demonstrates verifiable engagement incentives — the contingency-management principle of rewarding verified behaviors, implemented here as an auditable, participant-owned token for educational engagement rather than a clinic-administered voucher. Educational rewards, not clinical treatment. View participant address on Blockscout →

Doctoral Scope + Future Research Directions

The doctoral scope is Phase 5 (bilateral consent capstone). Three parallel advisor tracks extend the architecture: ecosystem architecture + on-chain verification engineering (Dr. Boscovic, primary advisor target), consent formalization + formal access-control rigor (Dr. Ahn, co-advisor target), and AI-driven intervention methodology + operational validation (Dr. Ghasemzadeh, co-advisor target). The biosensor + clinical track below is potential post-doctoral research, not a committed build.

Phases 1–4 — Single-Party Consent Infrastructure (Phase 1 deployed; Phases 2–4 scaffolded and specified.) FOUNDATION ESTABLISHED

Baseline established — EIP-191 wallet auth, on-chain attestation, WebRTC media, zero PHI on-chain.

Established the baseline: EIP-191 single-signer wallet authentication, deployer-signed on-chain session claims (SovereignLedger), peer-to-peer WebRTC media, self-hosted TURN relay. Demonstrated wallet-signed sign-in in place of username/password accounts in a regulated-domain testbed (behavioral health). No protected health information written on-chain; operates outside HIPAA scope by architectural design. Wallet compatibility tested (Rainbow, MetaMask, Coinbase Wallet, Brave Wallet, Rabby, Keplr). Internal security review documented; formal third-party audit planned pre-mainnet.

Contracts: SovereignLedger v3 0x0562E4BD...262B (session claims) · SovereignSession 0xbeb13A...65A1 (deployed; called by the session app’s Guide controls)

Phase 5 — Bilateral Mutual Authorization + HKDF-derived Bilateral Session Encryption DOCTORAL CAPSTONE

The open problem: extend wallet-signed consent from single-signer to bilateral dual-signature.

The open research problem: extend wallet-signed consent from single-signer to bilateral dual-signature. Each party produces an EIP-191 plain-language consent signature and an EIP-712 typed session attestation signature. The second party’s EIP-712 signature embeds the first party’s, creating cryptographic interdependence. Session keys derive via HKDF from both EIP-712 signatures — a session can only be established with both parties’ consent. Among systems surveyed, no existing platform implements this combination of bilateral wallet-signed consent with HKDF-derived encryption and on-chain attestation (Provisional 64/106,748).

Biosensor + Clinical Track (Dr. Ghasemzadeh) PARALLEL TRACK

Independent track — orthomolecular AI and biosensor precursor detection feeding the sovereign record.

Independent clinical research track: orthomolecular AI integration (Phase 1) and biosensor amino-acid precursor detection (Phase 2), feeding measured data into the participant’s sovereign record. This is Dr. Ghasemzadeh’s domain — parallel to, not downstream of, the bilateral consent capstone.

Doctoral scope: bilateral dual-signature consent (Phase 5, capstone — Provisional 64/106,748). Primary advisor target: Dr. Boscovic (ecosystem architecture, Blockchain Research Lab). Co-advisor targets: Dr. Ahn (consent formalization), Dr. Ghasemzadeh (operational validation). The deployed system is the testbed for the research contribution.

Research Artifacts

Research Potential / Vision

BUILT — DEMO LIVE

Consent-Gated Wearable Biometrics → FHIR R4

Biometric data from the Google Health API — heart rate, steps, sleep — mapped to FHIR R4 Observations (LOINC 8867-4, 41950-7, 93832-4). In the live demo the readings display as an ordinary dashboard, and each reading’s FHIR Observation and access token are released only under a Participant-signed consent grant with a Merkle-anchored, revocable permission history. Device data never touches the chain; only the Merkle root of the consent history does.

Standalone module. A provider-agnostic device-source interface, with the Google Health API (v4) as the first implementation. Google OAuth (OAuth 2.0 with PKCE) handles account access. The consent layer adds explicit scope, a revocation history, and tamper-evident evidence on top of it. In the module, the consent gate admits data only for a wallet whose NeuroBalanceConsent healthDataAccess flag is set on Sepolia (admit and refuse demonstrated October 8, 2026); the gate backed by the on-chain permission tree is the next phase.

Access, not copies. A signed grant issues 15-minute access tokens, each scoped to one metric. Revoking the grant invalidates every outstanding token at once.

Signature verification runs at grant time: ecrecover for EOA wallets, ERC-1271 for smart accounts. Re-verification at read time is the direction.

Limits, stated plainly. Revocation stops future access; it does not recall data already delivered. Selective disclosure through a Merkle proof works; the completeness of a disclosed history cannot be proven.

Companion interface-engine channel. HL7v2 ORU^R01 OBX segments become FHIR R4 Observations, with the same LOINC set, on Open Integration Engine (the open-source fork line of Mirth Connect). HL7v2 interface feeds and consumer device APIs therefore normalize to the same resources.

Live demo: demo.futuresystemslab.io. The wallet connection, signatures, verification, Merkle computation and Ethereum Sepolia testnet chain reads are real. Each metric card labels its source:

  • Sleep: a dated Google Health API snapshot.
  • Heart rate and steps: labeled sample data.

When the live readings route is restored, it takes over any metric with readings from the last 7 days.

RESEARCH DIRECTION — IN VALIDATION ON THE INVESTIGATOR’S OWN DATA

Current phase: protocol and pipeline validation on the investigator’s own device; no participants enrolled beyond the investigator (Participant 1); no data published. IRB submission precedes any participant study.

Daily records are encrypted, stored on decentralized storage (testnet), and hash-anchored on chain; the record itself is not published.

Study plan — Part 1 (evening sessions, A/B, Oct 6 – Dec 4 2026): does the bilateral stimulation exercise improve sleep quality? Planned follow-ons: Part 2, morning-only sessions; Part 3, morning and evening sessions. No data is published.

EMDR-Informed Bilateral Stimulation with Wearable Outcome Signals

The deployed bilateral-stimulation exercise is the intervention; the wearable pipeline above is the measurement. Proposed: consent-gated collection in three windows — before (prior-night sleep, resting heart rate, 60 minutes pre-session), during (heart-rate samples at the finest available resolution, session boundaries stamped by the exercise), and after (60 minutes post-session, that night’s sleep, next day) — as observable signals hypothesized to correlate with autonomic and neurotransmitter-system function. Research design only — no clinical or diagnostic claim.

The exercise exists and is live at encrypthealth.io as L1 — Bilateral Stimulation (the Bilateral Focus Exercise): a self-regulation education exercise, not EMDR therapy.

The measurement pipeline runs on the investigator’s own data (Participant 1, since October 6, 2026). IRB review has not begun; it precedes any participant study.

N-of-1 design on own data first; any further participation waits on institutional review.

Primary outcome (Part 1): the Fitbit Charge 6’s sleep readings — time to fall asleep, time awake, REM and deep sleep — compared across the 30 nights without the exercise and the 30 nights with it. Heart-rate trajectory before, during and after each session is recorded as a descriptive time-course measure.

Study plan — as of October 7, 2026

Phase 1, protocol validation. The investigator as Participant 1; Fitbit Charge 6 → Google Health API → FHIR R4 through the consent-gated pipeline; Part 1: 30 evenings without the 2D bilateral-stimulation exercise (October 6 – November 4, 2026), then 30 evenings with it (November 5 – December 4, 2026), with before/during/after windows around each session. Outputs: the measurement pipeline, pre-registered outcome definitions (Part 1 sleep readings with and without the exercise; heart-rate trajectory before, during and after each session), and a measured cost, access, and privacy ledger. No physiological data is published from this phase.

Phase 2, institutional review. IRB submission with the investigator as subject and a self-consent form; sessions repeated under the approved protocol form the research dataset; the IRB decides whether validation data may be included.

Phase 3, expansion. Additional Participants through the consent-gated wearable demo once the wearable consent scope is added in the planned re-anchor pass. Device data stays off-chain; only consent grants and integrity hashes anchor.

Study arms. (1) Bilateral time-course: before/during/after windows around each exercise session. (2) Daily-habit arm: one yes/no or timestamp habit at a time, in randomized alternating blocks, with sleep, resting heart rate, HRV, and breathing-rate outcomes. (3) Combined arm: the exercise crossed with one habit variable (2×2), run only after arms 1 and 2 have baselines. Delivery comparison: 2D and VR sessions of the same exercise alternate (ABAB) with identical settings and windows, reported side by side. All arms are descriptive only.

Descriptive outcomes only — no clinical, diagnostic, or effect claim.

BUILT — DEMO LIVE

VR Bilateral-Stimulation Exercise

The bilateral-stimulation exercise in WebXR, live at xr.futuresystemslab.io (VR headset browser; a 2D fallback runs in any browser). Its settings match the 2D exercise: 20 sweeps × 2,200 ms (44 s), with sound and haptics off by default. It writes the same session record as the 2D exercise, so 2D and VR sessions feed the ABAB comparison.

FUTURE VISION — NOT BUILT, NOT NEAR-TERM

Spaced-Repetition Learning Architecture in Immersive 3D/VR

Four deployed demos establish the pedagogical pattern; the expanded library, VR delivery, and spaced-repetition layer are proposed research contributions.

Proposed. Four demos are deployed today across three tiers (L1 hypnosis-informed, L2 orthomolecular-informed ×2, L3 inner-child-informed), each ending in the same three-part structure: a documented side effect, an orthomolecular food and amino-acid association, and an inner-child stillness practice.

Extended across a full session library, that repeated structure produces spaced repetition and associative conditioning — the participant repeatedly links internal state to food, mood, amino-acid pathways, and embodied practice. The repetition is the pedagogy; the token reward reinforces it; the game wrapper keeps it experiential rather than clinical.

The proposed delivery is immersive 3D/VR rather than the current 2D interface — embodiment being central to the therapeutic modalities the framework encodes. The bilateral-stimulation exercise already runs in WebXR (xr.futuresystemslab.io); the expanded library and VR delivery of the other modalities are not built. The 27-session design catalog exists as a design artifact, not implemented.

This is behavioral-health learning architecture — Dr. Ghasemzadeh’s health-informatics domain. The four deployed demos establish the pattern; the expanded library, VR delivery, and the spaced-repetition pedagogical layer are the proposed research contribution his lab would shape.

Immersive 3D/VR Delivery of the Therapeutic Framework

VR as the natural medium for bilateral stimulation, guided induction, and embodied learning, extending the WebXR bilateral-stimulation exercise already live — not built, aspirational.

future vision

The three modalities the framework encodes — hypnosis-informed induction, orthomolecular-informed education, and inner-child-informed integration — each depend on attention, embodiment, or spatial engagement. A 2D interface flattens all three.

Bilateral stimulation is the clearest example and the first delivered (live in WebXR): its mechanism is spatial and bilateral by definition, and a VR environment can deliver it as designed rather than as approximation. The same reasoning extends to guided induction (immersive attentional control), nutritional education (embodied, situated learning), and inner-child work (presence and spatial memory).

Delivered on decentralized infrastructure, the session attestation, consent record, and encrypted artifacts remain participant-owned regardless of the rendering layer — the sovereignty architecture is orthogonal to the interface.

Beyond the WebXR bilateral-stimulation exercise, none of this is built. It is the direction the deployed framework points.

Known Limitations

Documented gaps between what is built and what is claimed, maintained as an engineering backlog.

  • Session state: the header derives connection from a single flag that can report connected from a cached address with no live provider. Authenticated (may view) and can-sign (live provider present) need to be separate states. A fix was attempted and reverted July 30, 2026 — isolating them broke dashboard access, and correctness matters more than speed here.
  • Cross-origin: a single-use, 60-second handoff code carries the evidence-site sign-in to EncryptHealth; EncryptHealth links elsewhere in the portfolio use EncryptHealth’s own sign-in.
  • Mobile: WalletConnect signing unreliable; desktop browser-extension wallets are the supported path.
  • Smart-account wallets: EncryptHealth verifies standard (EOA) wallet signatures only; smart-account signatures (ERC-1271, ERC-6492) are not yet supported there.
  • Contract test coverage: 3 of the 8 contracts in the EncryptHealth Hardhat project have passing test suites (39 tests). No coverage tooling or fuzzing yet.
  • Session attestation in production is deployer-signed on SovereignLedger v3. SovereignLedger v4, deployed October 13, 2026, adds the participant's EIP-712 signature and reaches production in a planned switch. Bilateral signing by participant and guide is Phase 5, the doctoral contribution.
  • Claim registration on v3: the contract accepts a claim from the owner or from the guide address named in the call, so any wallet can register a claim by naming itself as the guide. v4 requires the participant's EIP-712 signature on every claim.
  • Full backlog: 49 items tracked in PRE_DEPLOYMENT_FORMALIZATION.md.
  • Encryption is wallet-locked: keys derive from the string form of an EIP-191 signature rather than the signature bytes, so a participant who switches wallet providers loses access to prior entries until the original provider is reconnected. Access is suspended, not destroyed — the signature is deterministic, so the key is reproducible. Demonstrated August 3, 2026. A multi-casing recovery path is deployed; deriving from signature bytes, recording provider identity at encryption time, and surfacing the creating address are scoped future work. Loss of the private key itself remains unrecoverable by design.

Regulatory Notice

This platform is an educational technology demonstration. It does not provide medical advice, diagnosis, or treatment. Content is for informational and research purposes only.

No protected health information is written on-chain. On-chain attestations contain only wallet addresses, cryptographic hashes, and timestamps. The system operates outside HIPAA regulatory scope by architectural design.

Open-Source Contributions

Contributions to open-source health-informatics and decentralized-identity projects. One merged after maintainer review; others in submission.

Platforms

ModuleLocationStatus
EncryptHealth (unified platform)encrypthealth.ioLive ✓
HypnoNeuro (therapeutic games)encrypthealth.io/participant/dashboard?tab=sessionsLive ✓
SovereignLedger (session records)encrypthealth.io/participant/dashboard?tab=ledgerLive ✓
AlchemistForge (encrypted journal)encrypthealth.io/alchemist-forgeLive ✓
NeuroBalance (biosensor layer)—Scaffolded
Sovereign Clinical (practice platform)clinical.futuresystemslab.ioLive ✓
VR Bilateral-Stimulation Exercise (WebXR)xr.futuresystemslab.ioDemo live ✓
Wearable→FHIR demo (consent-gated wearable data)demo.futuresystemslab.ioDemo live ✓ labeled sample data and a dated Google Health API snapshot
HL7v2→FHIR interface-engine module (Open Integration Engine)repository private pending public-flip preflightBuilt

Smart Contracts Sepolia Testnet

ContractAddressPurposeExplorer
HNT v2 (ERC-20)0x1ae1e10929f008d1f9883ce574a318abd86084e2HypnoNeuro platform token — earned via session engagementView →
EHTv2 (ERC-20)0x93583a7A24e50075c79b06db0be8Cf4D45B0bd88EncryptHealth platform token — supply capped 144KView →
HypnoNeuroNFT (HNNTKRN)0xCb9EcB00574DB29976c7C54045d443666D5C7771Minimal custom achievement-token contract (owner mint, burn, ownerOf, pause); no ERC-721 transfer interface or level stateView →
SovereignLedger v30x0562E4BD813250C65518e911d8624A8A8415262BSession attestation — claims, verification, pause; claim registration by the owner or the guide address named in the callView →
SovereignLedger v40xb24AF640Eb768400f5ddc7f516490dA67522CB5CSession attestation with the participant’s EIP-712 signature verified on-chain — deployed and source-verified October 13, 2026; production switch plannedView →
SovereignLedger v2 (historical — 18 attestations)0x4afA577fA914068451e0Aa97b61F23960f02aCc4Superseded by SovereignLedger v3View →
AlchemistForge0x5e1757441D7d4a29788e6A59892d9F159DAB3c3BShadow work — Identify/Transmute/CelebrateView →
BenevolenceFund v30x804C41CA6A688a33A0FC33F8B13Dab5C02Fa2C503% session fee — annual 44/33/22 + 1% distribution (top 3 Guides + top participant)View →
FSL Sovereign Achievement (ERC-1155)0xC3F11d2F1F12bB96b9DCF7e8f85e9704D2869B8DSoulbound NFTs — 10 participant + 10 guide tiersView →
NeuroBalanceConsent0x21571805e57f792b66604b140a45D8C1b2E196b8On-chain consent registry — 11 granular consent flags, user-gated setConsent + revokeAll (called by the wearable demo’s Enroll and Withdraw controls; EncryptHealth integration pending)View →
SovereignSession0xbeb13A360C6F0C77Ea3af3650Ab9762a1B9965A1Guide-signed session attestation (SessionStarted/SessionEnded) — Phase 1 deployed; any wallet can start a session, and the contract records the caller as the GuideView →
MerkleAnchor0x09f318717B44a22919Bd0B0EA445A41Ad889168cOn-chain Merkle root anchoring — msg.sender-keyed consent tree — first participant root anchored July 22 2026 (block 11329792).View →
BenevolenceFund v2 (superseded)0x96E8006a1fBB693B55fFf6254B8BF19EC605251BSuperseded by BenevolenceFund v3View →

SovereignLedger, October 13, 2026. EncryptHealth records session claims on SovereignLedger v3. On v3 the platform relay submits each claim; the contract also accepts the guide address named in the call, so any wallet can register a claim by naming itself as the guide. SovereignLedger v4, deployed and source-verified on October 13, 2026, adds the participant's own authorization. Each claim carries the participant's EIP-712 signature, which the contract verifies on-chain; the platform submits the transaction. The first v4 claim, claimId 0, was signed by a test participant wallet in a preview build. EncryptHealth moves to v4 in a planned production switch.

Mainnet requires security audit

Wallet-Native Session Infrastructure

Identity + Therapeutic layers — operates outside HIPAA scope by architectural design

Replaces third-party video tooling with cryptographic identity at every layer. The wallet address is the identity; the only name in a session is the optional display name a person gives their avatar, kept in that browser and relayed through the signaling server to the other person in the session. No PHI captured, no centralized recording. EIP-191 wallet authentication for both Sovereign Guide and participant. Verified end to end on October 31, 2026: the guide on a MacBook with Rabby, the participant on an iPhone with Rainbow through WalletConnect in Safari. Each person can design an avatar and appear as it during the call, and the participant chooses to see the guide on video or as the guide’s avatar. WebRTC media flows peer-to-peer and is encrypted end to end (DTLS-SRTP). When a direct path fails, FSL’s self-hosted TURN server relays the encrypted stream without the keys to read it; FSL stores no video or audio. On-chain, the Guide’s wallet records SessionStarted and SessionEnded events naming both wallets; the participant authenticates with EIP-191 off-chain and does not sign on-chain, and the contract does not restrict callers.

Contract

0xbeb1...65A1

Verify on Blockscout →

Phase Status

Phase 1 deployed; Phases 2–4 scaffolded and specified.

Phase 5 (mutual auth + encrypted recording) post-acceptance

Architecture: Self-hosted coturn TURN server · WebSocket signaling with EIP-191 auth · STUN/TURN ICE negotiation · On-chain attestation (SessionStarted/SessionEnded events) · Downloadable proof card

Multi-chain readiness infrastructure

FSL’s architecture is scaffolded for optional XRPL integration alongside Ethereum. Ethereum Sepolia is the live architecture for governance, identity, credentialing, and session attestation. XRPL integration is scaffolded for future multi-chain payment acceptance and ISO 20022 alignment — the mainnet wallet is funded for readiness, but settlement integration is not yet active. Reviewers can verify the wallet activation and balance directly on XRPL Explorer — no wallet required.

XRPL Mainnet Wallet

rwR3...Pd

Balance

...

Status

...

Full address: rwR3etLJVxtQXYs2d9jgBQxzHBivtCMdPd

Verify on XRPL Explorer →

Trademarks

Mark Serial Filed Class Status
FUTURE SYSTEMS LAB 99533250 Dec 6, 2025 42 (Software/Tech) Notice of Allowance — July 14, 2026
FUTURE SYSTEMS LAB 99821948 May 13, 2026 35 (Marketplace) Non-final Office action — August 5, 2026

Planned filings: SovereignLedger (Classes 9, 36, 42).

Patents

Subject App. No. Filed Status
Single-party wallet-signed consent architecture (Phases 1–4) 64/063,037 May 11, 2026 Provisional (Filed + Assigned)
Bilateral dual-signature consent protocol (Phase 5) 64/106,748 July 7, 2026 Provisional (Filed + Assigned)
64/063,037: Assigned (ID 1803665) · Deadline May 11, 2027 64/106,748: Assigned (ID 1930496) · Deadline July 7, 2027 Non-provisional: one application claiming both provisionals (35 U.S.C. 119(e))

Entity Information

Entity
Future Systems Lab LLC
State
Wyoming

METHODOLOGY NOTE

This is a proof-of-concept demonstration system deployed on Ethereum Sepolia testnet. All contracts operate with zero real monetary value. The system has been tested by a single evaluator (the principal investigator). No external participants have been onboarded and no formal user study has been conducted. These limitations are intentional and documented as part of the proof-of-concept scope.