This is a self-assessment, meaning, it is information that the issuer has written themselves. The XRP Ledger Foundation does not recommend or endorse any individual token. Read more.
Project name: XRP Healthcare
Currency: XRPH (5852504800000000000000000000000000000000)
Issuing account: rM8hNqA3jRJ5Zgp3Xf3xzdZcx2G37guiZk
Distribution accounts: rU8fx7EA8JqfckVa1pgPat6aZdCrea1ovz
This is revision number 3, signed November 18, 2022 by rU8fx7EA8JqfckVa1pgPat6aZdCrea1ovz
Description: XRP Healthcare (XRPH) is a Web3 scalable solutions provider, focused on revolutionizing the Pharma and Healthcare industry. XRPH intends to do this by simplifying and creating fast payments/transactions between market participants, and by bringing transparency by way of tracking pharmaceuticals from “inception to the consumer” combating the multi-billion dollar counterfeit medicine industry, with an interface for interactive engagement between consumers and healthcare service providers via our mobile and web app.
Unique selling points: What makes this token unique, compared to the broader landscape of tokens?
• The first Pharma and Healthcare platform to be built on the XRP Ledger
• Decentralized market place for the Pharma and Healthcare services
• Interactive engagement between consumers and Healthcare providers
• Track pharmaceuticals from "inception to consumer"
Purpose: What is the reason for issuing a new token, rather than using an existing? What purpose does this token serve, that is not possible with the native XRP token or other already existing tokens?
This tokens main purpose will be to bring in new aspects of help and support to the existing healthcare and pharma structure. We wanted to create XRPH so that we could have a unique native token for our project that only had this use case.
Whitepaper/sales material: https://www.xrphealthcare.com/XRP-Healthcare-Whitepaper.pdf
The whitepaper includes concepts of how and when are the tokens created, total supply and if applicable the distribution models and total amount of allocation.
Risk reminder: The issuer has disclosed a warning or a reminder of the risks associated with crypto/tokens.
Bug bounty program: The issuer does not have a bug bounty program.
The self-assessment is made on behalf of a legal entity (for example the issuer is a general partnership, limited partnership, private limited company, public limited company, corporation, commercial association or other).
Website: https://www.xrphealthcare.com/Website information: The website should disclose the following information:
- Details of the legal entity: official name and registry code, company headquarters mailing address
- Contact information: e-mail and other contact information
- Core team members
- Whitepaper if available
The website contains relevant information.
Business plan: A business plan should entail:
- the amount of revenue and expenditure by area of activity
- obligations related to the issuing of the token
- the technical administration of the company
- operational strategy
- the intended activities related to the token
- general principles of risk management and strategy of risk management
- policy for the financing of activities.
The issuer has developed a business plan for the next 3 years.
Risk assessment: A risk assessment should include identification of, assessment of impact and likelihood and mitigation measures and status of implementation for applicable risk scenarios.
The issuer has conducted risk assessment and implemented risk management activities.
Internal policies: Critical internal policies are necessary to manage risks.
The issuer has adopted and implemented appropriate internal policies and procedures in the areas of information security, business continuity, risk management and accounting.
Legal requirements: Legal requirements may vary per country and project. It is the responsibility of the legal entity to ensure legal compliance.
The issuer has assessed whether and what legal requirements apply to the project (licenses, jurisdictions, anti-money laundering regulations etc).
|Revision 3||November 18, 2022|
|Revision 2||November 9, 2022|
|Revision 1||November 9, 2022|