Katon.
io
Connect to the Web3
Unlock new revenue streams with our seamless blockchain
integration ecosystem.
Whitepaper
Mission 3
Mass Adoption 4
Problems 4
Acquisition & Retention 4
Risk 4
Solution 5
Use Cases 5
Ecosystem 7
Overview 7
About Regulation 8
Core API 8
REST API 8
SDKs 9
Projects & Accounts 10
Seamless blockchain integration 12
Sandbox Environment 14
Security 15
Tokenomics 17
KTON 17
Utility 17
Token Details 18
Allocation 18
Applications 20
Dashboard 20
Wallee 21
Roadmap 24
Launch 24
Expansion 24
Funding 24
Exchange 24
Resources 25
Whitepaper · [Link] 1
Mission
[Link] was born after embracing the evolution of internet-related technologies.
As crypto-enthusiasts, we acknowledge the paradigm shift in both application
development and user incentivization.
Fig 1: Screenshot of [Link] site.
We want to meet an exponentially-growing need. Our platform dedicated to
seamless blockchain integration aims to:
- Democratize the use of digital assets (Cryptocurrencies, NFTs).
- Bring low-cost/fractionalized diversified investment to the masses.
- Help businesses create meaningful sustainable circular economies in the
Web3.
We position ourselves as the catalyst towards the mass adoption of Web3.
Mass Adoption
Mass adoption is the next step of Web3. Around 300M people adopted blockchain
technology. The question is, how do we onboard the next billion people?
We believe there are two primary options. Education and user incentivization.
Whitepaper · [Link] 2
Amazing work is done by major actors of Web3 such as Binance, Coinbase, and
MultiversX to democratize knowledge of Web3. They partner with schools, build
courses, or create interactive tutorials. It will take time, but in the end, the next
generation will embrace decentralization.
On the other hand, we see a real opportunity to catalyze mass adoption through
user incentivization. Indeed, blockchain technology empowers companies to
create virtuous circles of remuneration benefiting them and their users.
We want to power the development of a society where interacting with
decentralized networks is transparent for consumers but is also the norm. Thus
emerges our philosophy of “Adopt and grow, live to earn.”, meant to drive the
adoption of the next billion blockchain users.
Problems
Acquisition & Retention
Customer Acquisition & Customer Loyalty costs are critical to the success of
businesses. Often companies with viable & successful business models go
bankrupt due to skyrocketing acquisition/retention costs driven by competitors.
Consumers are drowning in an ocean of offers, discounts, and alternatives where
it is hard for companies to stand out.
Risk
Despite offering great perspectives and growing interest, blockchain technology is
not largely ignored by corporations. Why is that? Because it is too much of a risk
to take in these uncertain times.
Indeed, implementing decentralized applications forces a different approach to
software development that software engineers are not familiar with. One must,
for example, take into consideration the immutability and transparency of data,
as well as all the risks related to wallet management.
Whitepaper · [Link] 3
It is very costly for large/medium size companies and is simply not accessible for
small businesses.
Solution
Our solution is an ecosystem, offering all the tools for meaningful exposure, and
straightforward/automated management of digital assets, requiring no previous
experience.
On one hand, companies can connect to Web3 and build decentralized
experiences thanks to our SaaS platform, allowing quick and flexible integrations.
On the other hand, with Wallee, our consumer-facing mobile app, end users can
access all the assets earned, bought, or received from the different projects of our
ecosystem in one application automatically syncing the different accounts to
one’s profile.
This allows for the creation of sustainable circular economies. Companies create
& share valuable assets that are sold by their clients, earning them money, and
generating perpetual royalties for the companies.
Use Cases
Fractionalization
Bring low-cost investment to the masses. From real estate to collectibles, art, or
luxury products, fractionalizing ownership of expansive items allows for lower risks
due to higher diversification, and exposure to a wider range of investors, while
also creating passive income from royalties.
Gaming
Rewards the success and involvement of gamers just like other professional
athletes with valuable artifacts and collectibles in the gameplay.
Whitepaper · [Link] 4
E-commerce
Turn customer acquisition & retention costs into a new stream of revenue with
decentralized customer loyalty and digital rewards.
Crowdfunding
Fund projects differently. Involve communities in developing your ideas with
financial support against success-based rewards. This is particularly attractive for
startups as well as the music, and cinema industries.
Whitepaper · [Link] 5
Ecosystem
Overview
Fig2: Ecosystem
- The Core API is the foundational block of our ecosystem. It is responsible for
managing digital assets, wallets, accounts & teams, API keys, and
interacting with the different decentralized networks.
- The API can be accessed via our SaaS solution: The dashboard (no code
integration) or the REST HTTP API (remote access for integration within any
application).
Whitepaper · [Link] 6
- Wallee, our consumer mobile application offers meaningful exposure
community to businesses/projects connected through the Core API. End
users see their accounts (per project) automatically linked to their profile
so they can interact with the assets they earned, fostering the generation of
royalties, and thus creating passive income for both companies and their
clients.
About Regulation
Regulation regarding Web3 is rapidly evolving. It’s hard to keep track of what’s
happening and where. The regulation discrepancies between areas like Europe
and the US cause headaches to blockchain developers.
It makes sense for companies to use tools that offer out-of-the-box features in
compliance with those regulations. No need to worry, no need to follow evolutions.
Our solution will take care of that for companies.
Our ecosystem is constituted of several foundational pieces that we will now
explain further. Let’s start with the Core API.
Core API
REST API
Our REST API allows for direct interaction with [Link] from any application. The
documentation with all the available APIs can be found in the Swagger at
[Link]
Whitepaper · [Link] 7
[Link] Core API Swagger.
The API provides all the endpoints for one to manage projects, accounts, and
assets in our ecosystem. The following will detail how it is structured.
SDKs
To accompany the Core API, we are developing a set of plug-and-play modules
to facilitate interactions from any application. Each SDK will provide public and
private contexts to protect sensitive data in public-facing layers (e.g.: Using
private keys in browsers/mobile applications).
Javascript/Typescript For Web & [Link] developers to
(NPM Package) connect with [Link] in browsers and
js servers.
Java/Scala For Java JEE and JVM-based software.
C# (Unity) For game developers, to easily migrate
or build play-2-earn applications.
Whitepaper · [Link] 8
Native Mobile (Kotlin/Swift) For Native Android & IOS Developers.
Ideal to build mobile consumer-facing
applications.
Dart / Flutter For cross-platform developers. Flutter
is a native cross-platform solution for
IOS, Android, Web, and more…
Projects & Accounts
The journey of companies and individuals willing to build in our ecosystem starts
with creating a project. The assets and accounts created belong to the project.
Figure 3: Project/Account Structure.
Isolation
Projects are isolated from one another. The content one can access is scoped to
the context. It means the accounts created on behalf of the end-users and
unpublished assets are not accessible by other projects. Users have a global
profile and a maximum of one account per project.
Whitepaper · [Link] 9
A wallet is attached to each profile, account, and wallet. Users have full control
over their profile wallet. Companies have full control over their project wallet.
Finally, control over account wallets is shared between users and companies. It is
used as a common deposit/withdrawal space.
Account Locking
By default, the management of account wallets is shared between the end user
and the project. Consequently, both can use it to create assets or withdraw them
to their primary wallet or to other platforms.
We reckon in specific cases, it might not be practical from the project’s
perspective. That is why we implemented the account locking feature. Projects
can be configured to lock all new accounts by default or decide to lock/unlock
specific ones as part for example, of an upgrade experience.
Account Tagging & Labeling
Accounts can be labeled and tagged. It means projects can create different types
of accounts.
Let’s take the example of a ticketing company willing to let performers associate
NFTs with the tickets they sell. The company will tag accounts for performers with
“performer” and let them create NFTs for their shows, and tag attendees with
“attendee”.
Adding a label and logo to the performer accounts allows for a better user
experience:
“NFT xxx by <Performer Label> powered by <Project Name>”.
Context Duality
Not only do we facilitate the creation and management of cryptocurrencies & NFT
collections for projects, but we also allow projects to create and manage assets
for their own users. This additional depth of our Core API dramatically expands the
scope of applications that can be built thanks to [Link]. From Play-2-earn
games to NFT marketplaces, or Exchange platforms, the sky's the limit.
Whitepaper · [Link] 10
Seamless blockchain integration
Building decentralized applications is hard. Especially when the blockchain
aspect of a project is not the primary focus.
Game developers, for example, want to focus on building the best possible user
experience. Adding play-2-earn support is important to stay competitive and
incentivize more users to pick your game instead of the competitors. It is
nevertheless not the primary focus. And it should not be a burden.
That is where [Link] comes into play. We built the ecosystem to facilitate
blockchain integration at scale and allow companies to get started within
minutes.
Cross Chain Support
Fig.4: Blockchain integration and interactions.
🌱🌱🌱
Whitepaper · [Link] 11
We choose not to support Proof-of-Work (PoW) networks. We believe that
everybody should contribute to building a greener, decarbonated, and
sustainable future. A tremendous, unnecessary, amount of energy is spent to run
PoW-based blockchains. Therefore supporting these networks misaligns with the
stand we take in the fight against climate change.
🌱🌱🌱
Crypto-Assets Management
We have been talking about [Link] APIs, blockchains, cryptocurrencies, and APIs,
but what does it mean exactly? What do [Link] APIs bring to
applications/services?
Project/Accounts:
➔ Create end-user accounts.
➔ Get account balances (tokens & NFTs/SFTs).
➔ Get project balances (tokens & NFTs/SFTs).
Coins:
➔ Issue custom coins (ESDT/ERC-20 standards).
➔ Supply Management with Coin Minting & Burning
➔ Transfer from, to, and between accounts, or to external wallets.
Token Collections:
➔ Create Non-Fungible or Semi-Fungible tokens (NFT/SFT) Collections.
➔ Specify royalties for subsequent NFT/SFT transactions.
➔ Issue tokens for the collection.
➔ Supply Management with Token Burning/Minting
➔ Transfer from, to, and between accounts, or to external wallets.
➔ Sell, Auction NFTs on our marketplace.
A large variety of APIs, for a large variety of applications. We believe that [Link]
should empower software developers to build meaningful user experiences.
Whitepaper · [Link] 12
Content Drafting
Immutability is a major advantage of blockchain technology. There is no going
back after a transaction is processed. It ensures consistency and prevents
tempering with the data. However, it thus requires a very careful approach to
content publishing.
That’s why we added a safety layer to the Core API. One can safely draft a coin, a
collection, or a token. Update as much as one wants the parameters, and share
them with the project’s team for approval. Once it’s finalized, the asset can safely
be published.
Funding Strategy
For every transaction on a blockchain, gas fees are paid to reward either miners
or validators for contributing to the network's functioning. The traditional flow
makes the transaction sender pay these gas fees.
It would require in a project’s context that every single user fund their own
account wallet to be able to perform transactions. Or, require the project to send
the amount needed to the account wallet before each transaction.
We feel like it is a cumbersome process creating friction for users and companies.
That is why we implemented a funding strategy. Projects can decide with a simple
query parameter, to directly fund themselves the transaction gas fees. Therefore
avoiding extra steps and facilitating interactions.
Custodial & Non-Custodial
We’re bringing together the best of two worlds. On one hand, users can connect
external wallets to manage projects or perform transactions in the ecosystem.
This keeps the experience decentralized for users familiar with Web3.
On the other hand, can decide not to worry about the management of their
private key and leave it to us. This is meant for beginners to get started quickly
(and safely).
Sandbox Environment
Our ecosystem offers a Sandbox environment meant for companies/developers
to try out our Core API for free. It works exactly as the production environment
Whitepaper · [Link] 13
except that limitations are removed for the Free Tier Plan and digital assets are
not created on the main network of the chosen blockchain.
For example, a project using Elrond will see assets created on the Devnet
[Link] for the Sandbox environment, where they
can have free EGLDs to fund transactions.
The Sandbox environment is thought of as a risk-free playground for developers
to test their code before moving to production.
Security
As part of the Fintech industry, we dedicated a significant amount of time and
resources to securing our APIs. Data is protected through encryption/hashing,
and access to critical features is granted through a permission system managed
by the project’s owner.
Encryption
Wallet management and API access require dealing with extremely sensitive
data, such as wallet private keys & mnemonics or API Keys (public & private keys).
We implemented several layers of security to protect this data.
First Layer
Access to the data is limited. We provide no access at all to wallets' private keys &
mnemonics. It is unnecessary because all the transactions are signed securely on
our servers.
Management of API Keys is authorized only by the project owner or collaborator
with developer permissions (or project owner). The project’s API private keys are
returned upon creation only.
Second Layer
Critical data is encrypted in the database. The cipher used is generated with a
secret key securely stored on our servers (and accessible only to critical staff
members) and an initialization vector specific to each wallet.
API Keys
API Keys are required to authenticate interactions with the Core API.
Whitepaper · [Link] 14
They are constituted of a public and a private key. The public key allows “read”
interactions such as fetching a wallet balance or the list of accounts for a project.
The private key allows “write” interactions, such as asset creation, currency
transfers, or account management.
As mentioned above, the private key is available only upon creation. Only the
hash is stored in the database. It means nobody can access the key except the
project owner/collaborator responsible for the creation of the key. It also means
that if the key is lost, it cannot be recovered.
To improve security, we implemented a mechanism allowing project owners or
contributors with developer permissions to enable/disable API keys. Therefore, if a
private key is mistakenly exposed, it can be disabled so all following interactions
can immediately be prevented.
Multi-Factor Authentication (MFA)
For applications in the ecosystem, we opted for passwordless authentication
doubled with multi-factor verification. Indeed on registration, users will be
required to provide an email that will be verified using a one-time 6-digit code. If
the user enabled MFA, they will be required to also provide the MFA code. This
modern approach to online authentication reduces the complexity and risk
related to password management.
Permissions
The projects are created and managed using our dedicated dashboard
application (see applications below). Projects owners have by default all
permissions. They can also add collaborators and grant permission to work on
specific aspects of the project. The permissions are segmented as follows:
All All permissions.
Developer Create & Manage API Keys.
Creation Create & Manage Coins/NFT
Collections.
Whitepaper · [Link] 15
Finance Publish & Transfer Assets.
Management Manage Team permissions.
Tokenomics
⚠️The tokenomics is not final!!
KTON
KTON is the Elrond Standard Digital Token (ESDT) that will power the growth of the
ecosystem. It will serve as a common asset for projects whose scope is not large
enough to maintain their token/currency. It is also a way for us to incentivize
companies to choose [Link] to migrate their applications to the web3. Indeed,
part of the liquidity will be dedicated to funding projects in our ecosystem. Users
will be offered reduced prices & fees when using directly KTONs on the
marketplace. Holding KTON tokens allows the ability to create a passive income
thanks to the rewards program in the wallet application.
Utility
Power the Ecosystem
The KTON will be the default and preferred currency to perform transactions in the
[Link] ecosystem. Payable methods in Elrond Smart Contracts can directly
receive ESDT tokens like the KTON. Paired with relayed transactions, it allows the
implementation of a Smart Contract Layer dedicated to managing the fees
generated through interacting with the Core API.
As a consequence, the Core API will be able to favor the use of the KTON by
creating events, decreasing the fees, or offering discounts for projects interacting
with the ecosystem's preferred token.
Thus it would allow the platform to grow and make it even more seamless for the
different blockchains.
Whitepaper · [Link] 16
Governance
Token owners will also have the opportunity to vote on various matters regarding
the project, allowing us to make decisions in agreeance with the community!
Token Details
Ticker KTON
Identifier KTON-e1626e
Supply 1, 000, 000, 000 (1B)
Decimals 18
Can Mint No
Can Burn No
Network Elrond
Allocation
Whitepaper · [Link] 17
Fig 5: KTON Token Allocation.
30% of the supply will be used to incentivize companies to build projects in
[Link]’s ecosystem. 20% of the supply will be used to reward our users through
diverse means such as airdrops and staking. 20% of the supply will be available
for early investors through different private sales and a final ICO.
Vesting Schedule
15% of the total supply is dedicated to the founders & advisors of [Link]. The
following vesting schedule will be implemented.
Vesting 24 Months
Cliff 6 Months
1st Block 15%
2nd Block 25%
3rd Block 25%
4th Block 35%
Whitepaper · [Link] 18
Applications
Dashboard
Fig 6: [Link] Dashboard Project Wallet Page.
The dashboard helps companies manage projects in our ecosystem.
Wallet Project Cryptocurrency & NFT
balances.
API Usage Project API usage insights.
Team Collaborators & permissions for the
project.
API Keys API key management.
Accounts End-user account management.
Coins & NFT Collections Digital asset management.
Whitepaper · [Link] 19
Wallee
The consumer application is intended for end-users to access their earnings
across every account in our ecosystem that was created on their behalf. It
simplifies access for users and offers meaningful exposure to all projects using
our solution.
A full demo of the app is available on the app landing page
[Link] It can also be viewed directly on Youtube:
[Link]
Fig 7: Wallee’s logo.
Assets can be withdrawn to the primary wallet of users when accounts are
unlocked. They can also be transferred to external users or sent via hero tags.
Marketplace
The marketplace will also be available directly to users in the consumer
application. It will showcase online shops for companies to directly sell their NFTs
and users to resell the ones they collected, thus generating royalties for
companies.
Whitepaper · [Link] 20
Fig 9: Screenshot of Wallee’s Marketplace.
The KTON will serve as the base currency throughout the marketplace to facilitate
sales and auctions of assets issued from different projects.
As the ecosystem is interconnected, companies will be able to create shops and
publish sales/auctions directly from the dashboard.
Exchange
Coins themselves have low to no value if there is no capitalization associated.
Especially if the project that owns it has low visibility. That is why we aim to build a
fully connected swap exchange whose currencies can be deployed directly from
the dashboard app.
As a consequence, project owners will be able to enable capitalization.
Whitepaper · [Link] 21
Note: The development of the swap application will be led by the expansion of the
Core API to support pricing and token exchange. Hence the opportunity for other
projects to implement swap features.
KTON Utility
[Link]’s token, the KTON, will serve as a reference to measure the value of other
ESDT token pairs created thanks to the Core API.
Fig 8: Exchange integration
Whitepaper · [Link] 22
Roadmap
Launch
Q2 2023
➔ Core API v1 (MultiversX & BNB Chain)
➔ Dashboard Application
➔ Sandbox Environment
➔ Wallee v1
Expansion
Q3 2023
➔ BNB Chain Marketplace
➔ JS/TS SDK
➔ Client onboarding
➔ Digital Art Sales
Funding
Q4 2023
➔ Private Sales & ICO
➔ ICO Deployment
Exchange
Q1 2024
➔ Core API v2
➔ Swap Application
➔ Governance
Whitepaper · [Link] 23
Resources
Home
[Link]
Sandbox Dashboard
[Link]
Wallee
[Link]
Documentation
[Link]
API Reference
[Link]
Blog
[Link]
Telegram
[Link]
Twitter
[Link]
[Link]
Instagram
[Link]
TikTok
[Link]
Whitepaper · [Link] 24
KTON
[Link]
Whitepaper · [Link] 25