XLoyalitY

XLoyalitY September 20, 2022

XLoyalitY

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.

Basic information

Project name: XLoyalitY
Currency: XLY (XLY)
Issuing account: rfQNEfqLQc5L34rS92Xh5nVtk9NVHbv4Gj
Distribution accounts: rLmhFNgLng8pYT6etmL4wuL8vmFLnhg9NU

This is revision number 2, signed September 20, 2022 by rLmhFNgLng8pYT6etmL4wuL8vmFLnhg9NU

Description: XLoyalitY stands for creating a secure XRPL network. XLoyalitY examines coins that apply and want to qualify for our Rug pull prevention & Quality mark. After screening we issue a status to the submitted coin. If it is approved, we will make it known to our community. We only publish information about our approved partners.
We are working to create a safe platform for coin holders and buyers. We where scamcoins have no chance.


Unique selling points: What makes this token unique, compared to the broader landscape of tokens?

XLoyalitY is unique in that we create a platform with affiliated XRPL projects. In this way we want to inform the coin buyer that the approved partner is researched and safe. We have contact with coinfounders, so safety is guaranteed. When in doubt we restart the investigation to assess if the approved partner meets our quality requirements.


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?

We are the first project on the XRPL network to research and issue our logo as a seal of approval. The pay valute for our compensation program concerns XLY


Whitepaper/sales material: https://linktr.ee/xloyality

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: This is not applicable for this token.

Legal Entity

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: www.xloyality.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).

Self-assessment revisions
RevisionDate
Revision 3September 20, 2022
Revision 2September 20, 2022
Revision 1September 20, 2022