FAKTÜRY

FAKTÜRY March 14, 2022

FAKTÜRY

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: FAKTÜRY
Currency: FAKTURY (46414B5455525900000000000000000000000000)
Issuing account: rNwBNkHz3ZAnx77XFjGR8nRnZHw4gKgmpr
Distribution accounts: rG3qGSDskfbFmiftWFBXMroJUSSjmGrADE, rs9i4d9jECRqWmhMk6Nupbg9Pxocco8EsU

This is revision number 1, signed March 14, 2022 by rs9i4d9jECRqWmhMk6Nupbg9Pxocco8EsU

Description: FAKTÜRY represents a luxury street fashion brand bridging physical and digital collectibles via the backing of NFTs. We will host DROPs consisting of 5 products, 326 items of each for a total of 1,630 items. Each DROP we plan to collaborate with a PFP NFT project and the NFT minted to the user will reflect the physical item purchased, designed in the partnering projects art style. i.e. 8 bit pixels
These NFT's will be an access pass to enable conversion to wearables in the partnering Metaverses on avatars and possibly other entities. FAKTÜRY™ will conclusively evolve into an ecosystem of products


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

- Phygital collectibles
- Phygital marketplace
- Auction House
- exclusive luxury street fashion


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?

-0.5 $FAKTURY to receive pre-launch access to a DROP
-Staking mechanism called FakFi, (Read more in FakFi chapter of whitepaper)
-All payments for DROP's
-Select amount of products outside of the DROP offerings


Whitepaper/sales material: https://faktury.gitbook.io/whitepaper/

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: faktury.dev/

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 1March 14, 2022