AMA Transcript July 7th, 2025

TL;DR:

The dHealth team is introducing a new access token for their dHealth Intelligence AI agent, following community feedback. The new token will enable both crypto and non-crypto users to access services, with a target annual price of $50 USD. Holding DHI tokens will reduce the cost. A large airdrop is planned for current DHP holders (1:1 ratio), with the initial rollout likely on Solana and/or the dHealth chain. The system aims to avoid inflation by eliminating staking rewards for the new token. It will include strong onboarding and referral incentives, controlled by a proof-of-personhood mechanism to block bots. The team will release more details soon (whitepaper, roadmap, etc.) and is open to feedback and suggestions. Wallet management will be simplified by the AI agent to reduce friction, especially for non-crypto users. The innovation fund remains available for community proposals, and the team emphasises transparency and increased communication moving forward.

Transcript:

Filip:

Hello everyone, and welcome to the dHealth AMA. It’s time for us to update the community on everything that has been happening behind the scenes with dHealth intelligence. Joining me is Eberhard Scheuer, whom you’re all familiar with, so we can skip the introduction and get right to it! The dHealth community put forth a lot of questions; if we went through each one individually, this AMA would be very, very long—and repetitive. Instead, we’ve broken the questions down into five broad topics and will address each one individually.

If you feel that a specific question has not been answered, please relay it in the community chat or any other way, and we'll address it.

So let's get started. There were a lot of questions about the economics and financial model of our new technology, the dHealth intelligence. So I'll leave Eberhard to start on this topic, and then we’ll move forward to the next ones.

Eberhard, you have the floor.

Eberhard: 

Hi everybody. The tokenomics and financial model of DHP in relation to the dHealth intelligence were among the main concerns, as we originally suggested that DHP is the access token for the dHealth intelligence, i.e. you have to hold a certain number of DHP tokens in order to be able to access the AI agent.

However, considering token volatility—if you set a fixed amount, its fiat value can fluctuate significantly—using the agent could become unattractive due to this friction.

So we came up with a different model. Jumping ahead a little bit, one of the major target groups will be people outside of crypto. Therefore, we need to set a fiat price in US dollars—whether for individual users accessing it or for corporate customers onboarding a large number of users.

The idea was that the target price is around $50 US per year, and if you hold tokens, you can reduce the price dramatically, even so that you can give non-crypto users access to the service, but also at the same time, you give the token a utility.

That already brings me to the second part of the most-asked question: why don't we introduce a second token? Initially, I thought—I'm not a big fan of producing endless tokens —but there are certain beneficial aspects related to the current situation of DHP.  For one, DHP is a very low-cap token, and the truth of the matter is that releasing a new token makes it much easier to raise funds.

So that's one aspect of it, and the second one is—we still have the dHealth network as a network for data sharing. The dHealth Network’s original use case will be realised by allowing the dHealth agent to facilitate its value proposition.  Among other things, these include data recording, data sharing, encrypted data storage, intelligent hands-free data management, and automatic data conversion to the appropriate format. I’m referring to FHIR here.

The agent can already open a dHealth wallet upon user request, which speaks volumes in terms of how the new technology will benefit DHP. So the dHealth network remains, and we will continue to develop the broader ecosystem. The AI Agent is our pivot point that will drive the very adoption we were looking to encourage with the dHealth network.

Furthermore, in the context of the dHealth Network utility, we’ve experienced a revived interest in medication tracking. DHP will definitely have its role in that. However, that aside, the AI-agent token will be a new token enabling access to the dHealth Agent. As suggested by the community.

We haven't decided on the name of the token yet. Naturally, the obvious name would be DHI, but we’ve noticed that when we are talking about DHP and DHI, we sometimes get kind of confused reactions, so we might have to select a different name, and you're welcome to make suggestions for the new name of the token.

We should ensure we don't confuse the community and future users as well. To summarise, the current decision is to release a new dHealth Intelligence token. Then, pertaining to another question: how will the current holders of DHP be valued in that new context?

Before we get to that, let me elaborate a little on the new token and its tokenomics. If we are talking about an access token, we don't need this token to have its own blockchain. This will be a token that exists on another chain, and we can choose whichever chain suits us. We can pick chains on which the token can live. The obvious starting choice would be the dHealth chain itself. The other obvious choices would be chains with large liquidity. This means that if we launch on such chains, we can also have access to much bigger ecosystems of potential buyers, currently, that is, Solana. If we are to go from the DEX volumes, we should also consider BNB Chain (Binance Smart Chain). For the moment, since we have a DHP to SOL bridge, that also highlights the benefit of choosing Solana as the initial deployment target with the new token. 

In summary, the new token serves as an access token, and the initial distribution of the token should be an airdrop to existing DHP holders. Similarly to what happened with NEM creating Symbol, it's not a fork. We will set a specific date in the future for the snapshot. We’re looking into 8 to 12 weeks from now to launch the new token. Eligibility for the new token will depend on your DHP stake. A standard blockchain snapshot will be utilised to realise this.

That means, for example, let's say August 31st. That's not a definite date. That's just an example. The amount of DHP that you stake on the current chain will be the amount of dHealth intelligence tokens that you will receive in your wallet.  The process of registering, checking balances, and distributing new tokens to you depends on the initial chain we choose to release the dHealth Intelligence token on.

So if we look at the distribution of the new token, we will have a large airdrop for DHP holders. Then we're looking at people who want to buy the new token and buy into the narrative. We then need to have an initial release of tokens for the liquidity pool. We can sum that together to gain an approximate understanding, without delving too deeply into the distribution, which will be elaborated on in an article and whitepaper over the next couple of days. 

We must be mindful that we need to maintain a low circulating supply of the tokens. That means that the airdrop tokens and the investor tokens come with an initial release, a couple of per cent of the new tokens. Then, there will be a cliff of, let's say, three months, and after that, the remaining tokens that people are eligible for will be released according to schedule. For example, several tools are available to facilitate this. So every hour, you get tokens that you're eligible for, and after a year or 15 months, you have all the tokens that you qualify for.

That way, we keep the circulating supply at the beginning very low, and that includes all team members as well. Utilising a DEX for a successful launch means that the circulating supply must be lower than the supply of the tokens that we put into a liquidity pool on a DEX.  So let's say the circulating supply will be 140 million dHealth intelligence tokens at the beginning, not counting the liquidity pool, which are technically burned tokens. The liquidity pool itself must have at least 150 million tokens. Just an example, I'm not saying that it's going to be that way. But something we will aim for.

So we need to use the funds we receive from investors to fill the pool with a larger amount of US dollars. The market cap will be a couple of million US dollars in the beginning. The goal is to start with 4 million, and then we'll see how the public sale goes. This is the whole idea about a second token, and currently, we're still open for suggestions.

Nothing is set in stone. No information has been released to the public at this time. So, you're the first ones to hear it. The current holders will be valued. Everybody who has a stake now will be more than happy with what they get. A one-to-one ratio. A key aspect of the access token is that it is not associated with staking inflation. That means currently, with the DHP we have inflation due to the staking rewards.

Since we're not having a separate chain for the new token, because there is no need, inflation through staking is not something we will have with the access token, which is a good thing.

And this will also be interesting considering the last SEC proposal that only staking on layer one networks will be considered legal and not a security. That is very important to note. The new access token has no natural inflation. However, there will be very generous onboarding incentives because the network grows through people onboarding others. Likewise, there will be incentives for holding tokens, being part of the network, participating in certain milestones, and also using the AI agent. And every time you onboard someone—you receive tokens—you also get an initial set of early adopter rewards.

The ones who come later will get much lower amounts of tokens.  This will determine the natural inflation in the whole system, and of course, since we don't know how many people will be onboarded, there is no token cap involved. For some, that sounds a little scary—an uncapped token—but in fact, most of the top-10 tokens are uncapped. However, you have to have a clear inflation rule to manage an uncapped token. The rule will be that only human beings who onboard or help onboard other human beings will receive a referral amount as part of the onboarding incentives.

Before we close the tokenomics and financial model, one very crucial aspect of the whole thing is that we have to be sure that no bots are onboarding, so that bots are not grabbing all the onboarding incentives. We have developed, with the assistance of experts from Universities, a proof-of-personhood based on physiological parameters that can be measured using a smartphone. Unlike Worldcoin, which requires a retina scan, this method allows people to complete the process using their smartphone. That's the prerequisite of onboarding rewards, and this allows for a controlled inflation of an uncapped token while having a stable economy.

There’s one aspect we haven’t touched on yet: How do DHP and the dHealth intelligence token correlate, apart from the airdrop? I've already mentioned that, of course, if you're sharing data generated or structured by the agent, you should share it through the dHealth network, as there will be a deep integration of the dHealth network into the agent itself. It already has significant integration that will continue to be expanded.

For example, the agent can also open accounts and do transactions on your behalf. This also allows transactions to be paid in the background without the user's knowledge by the agent. When you share data, they pay the gas fees on the dHealth network. So there's a very close intercorrelation between DHP and the use of the agent. Speaking of agent autonomy, we will examine the legality of offering the ability to stake DHP with the assistance of the dHealth AI agent. 

Filip: 

Thank you very much, Eberhard. To summarise for our community, the decision has been made to proceed with a second token that will provide access, and the tentative launch date is between 8 and 12 weeks.

New technology offers new opportunities that leverage what we’ve built so far. Great synergy! Imagine many of the use cases we’ve worked on so far, or even just theorised, will receive a massive boost in terms of adoption and realisation. Again - and this is important to note - we’re still open to suggestions, as the final deployment decisions haven’t been made. As many probably know, the dual token system was suggested by the community, and after recent team deliberation, we concluded that it is the best path.

So, please, if you have feedback or ideas, we're all ears. You can drop them in the chat or use any other means that work for you. I think we’ve wrapped up this topic and can move on to the next one. We had a lot of questions that were about technical stuff, and you've already addressed some things, but let's go deeper into the topic.

You mentioned that we're going to go with a multi-chain strategy. Can you tell us more in-depth about the technological aspect of this new access token?

Eberhard:

As I said, we have to choose the initial blockchain, which we want to release. For us, if we are just releasing a token, it doesn't matter where we release it. Because it's just a token and it can live on different chains. My personal preference, but this is up for discussion, is the Solana chain because it offers high liquidity and excellent tooling out of the box, which is not available in the Cosmos ecosystem. What you have in Cosmos is something you cannot get anywhere else, which is a straightforward way of having your network with your validators. You have independence in terms of governance, validation, security, and staking rewards, as well as inflation.

As far as releasing the token is concerned, as I said, we can do it on Solana, we can do it for the sake of low transaction fees and for the liquidity and the ease of releasing a token. IBC Eureka, developed by the new Cosmos team, will enable users to transfer tokens across any blockchain. They have just integrated Ethereum, so we can now explore when we can have a real, fully decentralised bridge for DHP on Cosmos and Ethereum.

The Cosmos team is planning to implement the Solana bridge in Q4, and we will utilise this bridge for DHI and DHP. The upcoming release will allow us to actually manage the token in terms of the token amount, across all different chains, easily. That means wherever we release it, it can be bridged more or less anywhere else, after the Cosmos team releases the bridge.

But there's a point where you have to start, and that's actually where we want to start—Solana. And the dHealth chain, of course.

Filip: 

Excellent, let’s move on with technology. We had a question specifically about wallets.

Can you tell the community more about this subject? What is our current situation? What is our strategy? Thoughts on recovery strategies and reducing cryptonative friction?

Eberhard: 

The wallet issue is the primary obstacle to the adoption of any blockchain project. So the large ecosystems—people are already in there. They use their Trust Wallet. They use Metamask. But if we look at those people, the truth of the matter is—not many people really understand it. And when examining the healthcare industry, this is even more true for these individuals.  And this is also why we started dHealth Intelligence. For one, digitising health data is the main bottleneck for making healthcare thrive, not just on blockchain, but in general. Typical healthcare users are often older individuals.

If you come to them, to say: okay, you have to set up a wallet, you have to save your 12 or 24 mnemonic words—you're lost even to people who have worked in healthcare IT for a long time. I’ve seen them fail, and this is strange to see— these are not stupid people, they're just not used to thinking in terms of decentralisation. We have to make the wallets disappear somehow, magically. The solution to that is an AI agent.

We can use the same agent as a single interface, not only for their health data but also as a single interface for their wallet. We have also implemented the capability for the agent to open your wallet. You can tell the agent where to save your credentials. The agent can do that, and it can do it safely, as it's guarding your personal health data. It's also guarding your credentials.

So the goal is not to deal with wallets at all in healthcare. The goal is to have one single interface that does everything for you. Currently, most of you likely have multiple health applications on your phone. The entire future will revolve around anchoring all utilities one uses or interacts with to the least number of points, preferably one—your AI agent.

There will be a lot of agent-to-agent communication in the future to facilitate this.

Since the agent cannot have a bank account, it needs to have a crypto wallet. But that shouldn't be the task of the person to set it up, despite the decentralisation ethos.

If we cannot solve the interface problem, we cannot have adoption.

Filip: 

Very true, wallets have been a huge obstacle. Let's move on to the third topic or section. So our community has been very vocal, and we appreciate it very much. Some have been critiquing more than, let's say, positively commenting. Some have been very appreciative of our work. So the question from the community is how the team perceives the community, and how we perceive the excitement versus the critique.

Eberhard: 

Let's be honest here. Since we launched the Cosmos chain, the team has been an integral part of the community. We do not have any significant funds available to pay people. Everybody working right now is doing so because they have a stake, and with that attitude, you are part of the community as well as in Cosmos. And that's a beautiful thing. There are several governance tools that you can utilise. It's not on us to use them. Although so far, all the proposals have come from us.

So anybody with a DHP stake can submit proposals. If they are going to be accepted—that's a different matter, but everybody can come up with a proposal. There is an innovation fund in DHP. I mean, it's still 300 million DHP in there that has never been touched and doesn't participate in staking.

This fund can be accessed by anybody in the community, in the way that you are basically saying: okay, we have this great idea of doing something, but we need x amount of tokens for that and with the tokens we will do that. The proposal, of course, must be made public to the community so that they can actually vote on it. If you go into the stake explorer, you can submit proposals there. You can even do it in Kepler. The community is there to build.

Over the past few years, I've experienced the dHealth community as an investor, and, for investors, we haven't performed well. However, if the community were more focused on builders, it would be more conducive to growth. dHealth is open to building and governing. Every proposal and every project that someone commits to adds value to the platform, ultimately improving the performance of the token.

To summarise, I hear your critique. I don't take it lightly. However, we must, as a community, work together and not just be spectators.  If you believe in what we're doing, you can contribute, and this is true for Filip, for me, Son, and for others who are here. We believe in it, and whatever we do is because we want to do it, not because we think we will get rich from it.

To tell you the truth, for the past two years, I didn't really know what the utility of the DHP token was, besides staking and transacting. None of the use cases we created or facilitated with partners have caught up to a significant degree. Then, at the end of last year, agent AI came along, and now you can do so many great things. What I've experienced by demonstrating the technology, and what I've gathered from talking to people, is that we are on an excellent track, and that's essentially already touching on the fourth topic, which is adoption. This time, we have a solution to a problem that doesn’t require the permission of the healthcare industry to be solved, and it also has a massive cost-to-benefit ratio. 

Did you see my post on my experience at the Nordic blockchain conference, where we met the DeSCI platform initiators and the believers in DeSCI? The reality is: nobody cares about DeSCI. I mean that's a little bit too harsh, of course—there are interesting projects. There's Bio Protocol and VitaDAO, but they're essentially just platforms to finance research that has not received pharma financing. So, where do we go from here? We need to have a utility, a strong value proposition in what we're doing, and we must have a cause that we're passionate about, and we need to solve a problem. And especially if we want mass adoption, we need to solve a problem that many people have.

Filip: 

Excellent, wholeheartedly agree. Let’s move on to the next point, transparency and how you expect to see transparency of our team and the project in the future.

Eberhard:

To communicate now is a vastly different game than it was before. As you said, we were working, but did we have a solution ready? Not quite. Therefore, communicating about no progress or little progress is always challenging. Now we have something to say, and we still have the “ticket” of one tweet to the Cosmos Interchain Foundation community, which is more than 500,000 people, where we can introduce dHealth intelligence specifically to crypto natives.

Finally, as a reminder and a clarifier, those who want to be early on the access token can buy DHP via Osmosis.

Coming back to communication, now we have a lot to communicate. And we will.

The question now is how we serve it to the dHealth community and the wider crypto community. We are definitely implementing a bot very soon to divulge all information to those who want to know more or get an answer to a particular inquiry. We will be communicating more because now we have more to say. And we can be concrete. To finalise with an important remark—we hear you, and we will improve. Roadmap, whitepaper and a holistic article pertaining to all the details around this new development will be released very soon.

Since non-crypto natives don’t have crypto to buy the dHealth Intelligence token, this would act as a very big obstacle to adoption. That’s why we are integrating a service provider’s solution that will allow non-crypto natives to purchase DHP and have access to the token via a credit card.

Continuing on the topic of adoption, as I mentioned already—there's a huge part of very attractive onboarding incentives, and I think apart from that, the solution itself is attractive, and of course, as I said—you can pay it in fiat. We will also add a discount option for paying in dHealth intelligence tokens. We are also considering creating premium accounts that never require payment in the future if you hold a certain amount of Health Intelligence tokens. We are looking to gamify the ecosystem to maximise healthy growth of both the agent’s user base and the dHealth network.

Filip: 

And last topic, you mentioned it before, the innovation fund, but maybe you could tell us a bit more about the requirements, because this was an inquiry from the community. They would like more information on the open source requirements, the timing, and the cap amounts. 

Eberhard: 

So with technical upgrades and voting, it's very easy for the community to participate in the governance. Once it is accepted, the technological updates are automatically implemented in the chain.  In terms of fund allocation, we need to develop a smart contract that, once approved, will automatically release DHP from the innovation fund account to the submitting account.

We’re always open to suggestions. There has to be an upper limit for each proposal to protect the innovation fund from being drained by malicious people.

Filip:

That is something we will address in more detail later, after the release of the health intelligence token. This concludes all the questions we had. Maybe there is something else you think would be worthwhile to mention or…

Eberhard:

Yeah, that's about all.

Filip:

Thank you very much, Eberhard. That's all for today, then. We're gonna have another AMA for sure, soon. If you have any questions, please feel free to ask them in the chat. Furthermore, our amazing Japanese community members will be getting a transcript so they can translate and learn about these amazing new developments. We will also release a comprehensive article and white paper soon. Stay tuned and see you in the next AMA. Thank you. Bye-bye.

Eberhard: 

Thank you. Bye-bye.