We Moved DHP to Solana. The Real Story Is What Comes Next.

We have moved. DHP now lives on Solana, together with the attestation and mandate services. The old Cosmos chain is being shut down.

This is a good moment to explain what changed and where we are heading. We will take the protocol first and the AI second. The protocol is the foundation. The AI is what people actually touch.

1. The Protocol

The reason for the move is not ideological. Running a standalone chain made sense once, but continuous care is a high-frequency, low-latency workload, and carrying a separate chain for it meant taking on operational risk and spending resources on infrastructure rather than on product. Solana provides the throughput and settlement speed this kind of activity needs, and it offers the Solana Attestation Service to build on directly.

After the migration, DHP has one clear job. It is the protocol's accountability asset. It is not a payment coin. Network fees are paid in SOL, real payments are made in stablecoins, and DHP is what you lock to participate. Locking is the point. To take part in the protocol, a participant commits a reclaimable DHP deposit: individuals lock a small amount, organisations more, and machine actors their own tier. The deposit is returned after the lock period. Nothing is spent; it is committed and reclaimed.

This is the structural change worth understanding. Before, holding DHP was passive. Now participating requires locking it, which means issuers and organisations have to acquire it and take it out of circulation to operate. That is the mechanism that should pull demand beyond the current community.

We will be honest about the rest. The liquidity pool on Solana is live but small. It is a two-sided pool, so it needs both a base and a quote token, and at today's DHP price, we will not flood it with DHP that is then locked away, nor overfund the USDC side and watch it drain. The market cap is poor, and we are not going to pretend otherwise. We once named five cents as a goal. We are not making price predictions. A fair price is set by supply and demand. Our work is on the demand and the locking mechanics, not on forecasting a number.

What the protocol actually produces is verifiable evidence. An attestation answers three questions: what happened, who claims it, and under what authority. Raw health data never goes on the chain. Only cryptographic proofs, references, and revocation states do. The application keeps the data; the chain keeps the proof.

2. The AI

dHealth Intelligence is the agent people interact with. Two real deployments show what it does.

At Apodro, the pharmacy uses the agent to read new prescriptions, reconcile them with the existing medication plan, update the data, and generate a CHMED16 QR code containing the medication record. At Spitex Biel, in Swiss home care, the agent supports the client onboarding process and calculates the care effort for the application to the payer. The care professional stays responsible at every step. Data stays with the client.

These deployments are small, a handful of transactions a day. That is fine. Their job is to prove the capability in a real, regulated setting, and they do. The growth does not come from there.

It comes from Individual Care Agents, and within them, Care Ally. This is, right now, the most promising path to scale. The reasoning is simple. Care demand is rising faster than human capacity can supply it. The most important care happens between appointments, where extending clinician time does not scale. An agent delivers personalised support at low marginal cost today, and becomes the intelligence layer for connected devices and care robots later.

Like Care Ally, the Individual Care Agent is triggered by a QR code. A sponsor, provider, or patient shares a code or an invitation. Care Ally is the variant aimed at the people around the patient: family and friends, and the unpaid, untrained care team that forms the moment someone is ill. Scanning the code opens a journey tailored to that specific diagnosis, so a relative arrives informed rather than guessing what a discharge letter means or whether a symptom is urgent.

The barrier to entry is low because, at that stage, the user does not need to register. They scan, the journey opens, and the support is there. Sponsorship covers the cost: an industry partner or a patient organisation can sponsor access, and that sponsorship provides the user with temporary access to the AI, not a standing account.

How It Works Together

The QR mechanism is the clearest example of why both are needed.

A sponsor configures an agent: a system prompt, a subject, a goal, and a set of QR codes. Here is the part that matters. Each QR code also serves as the agent's API access code and is registered via an on-chain attestation upon creation. The issuer locks additional DHP to do this, which ties the whole program to an accountable economic footprint.

When a caregiver scans a code, the agent does not simply trust it. It checks the attestation. Was this QR genuinely issued by an accountable party for this program? Or is it an unregistered code carrying a malicious system prompt, an injection attempt dressed up as a care journey? Only a registered QR loads the journey. Every meaningful action the agent then takes is logged the same way.

That is the whole argument for combining AI and a trust layer. The AI does the last mile, turning messy real-world records into something a worried relative can act on. The protocol guarantees the agent acts only on genuine instructions, under verified authority, with an audit trail. Neither half is worth much alone. Together, they answer a question nobody else answers well: how do you let an AI agent act in someone's care without trusting whoever sent the link?

Gating Access

We are working on gating end-user access to the AI. There will be three ways to pay for it. You can pay in AIDH tokens, with each token set to roughly one cent of compute at the start, and paying in tokens carries a discount. You can pay in a stablecoin. Or you can pay by credit card, which means no one has to touch a token to use the product. Sponsored journeys stay free for the person using them; the sponsor covers the cost.

Where This Goes

The protocol is now on the right chain for the work it has to do. The AI is real and deployed. The lock model gives DHP a reason to be acquired that does not rely on speculation, and Care Ally gives us a product that can scale through sponsorship rather than by asking caregivers to understand crypto. That combination, an accountable trust layer under a care agent people will actually use, is the part competitors cannot copy by building yet another health chatbot.

More updates as the pieces ship.