Whitepaper

Version: 1.3

support@trustchaintechnologies.io
www.trustchaintechnologies.io
 TrustChainTechnologies - Whitepaper

September 11, 2017

Contents
1 Abstract 3

2 Introduction 3

3 Features 4
3.1 MetaChain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1.1 PoT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1.2 PtA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.1.3 Smart Contracts . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.1.4 Alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.1.5 Automated Transfers . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.1.6 Deductive Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.2 Wallet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.2.1 Internal Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.3 App . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.3.1 PtA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.3.2 Payments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.3.3 Secure Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.3.4 GPS Mapped Acceptances . . . . . . . . . . . . . . . . . . . . . . 14

4 Budget 14

5 Roadmap 16

6 Conclusion 17

7 Document Versions 18

2
TrustChainTechnologies, 11.09.2017 2 INTRODUCTION

1 Abstract
The TrustChain aims at integration into our daily lives.
This includes a fair selection process of choosing the trustees, fair rewards among the
participating devices, usage of daily live technology in our BlockChain as well as easy
to use interfaces. Were developing a new signing algorithm based on a Proof of Trust,
chapter 3.1.1 on page 5, concept to tackle the signing problems current BlockChain
technologies face. With our focus on consumer demand and usage, it is our main goal
to create a new BlockChain that easily integrates into our daily lives.

2 Introduction
As a non-business conglomerat weve been analyzing the crypto scene since years, trad-
ing, selling, mining and having especially a closer look on all ICOs and new coins. The
most disturbing part was, that many ICOs which nowadays are starting, finishing with
great success but only few have it set as a goal to make it into our lives.
They seem to target just a special group - alt coin investors. Many great ideas are
around that possibly will succeed, but in our opinion only if the base strategy on the
market changes focus. Thats why we chose to work together since more than a year to
forge an idea of a blockchain that has a potential of changing the market acceptance.
This will be done through a complete transparent process of development, implementing
a new signing technology as well as focus on consumers and customers demand.

The name TrustChainTechnologies obviously comes from our new signing algorithm,
the Proof of Trust, chapter 3.1.1 on 5.
As of our persons we are currently a group of 45 developers, designers, marketers, busi-
ness owners and entrepreneurs working together on this project. All of our developers
have years of experiences in various development languages, worked on international
projects and are highly skilled and motivated.
Our team of designers make sure that we have easy to use interfaces for our customers
and business partners to support daily life integration.
Our business owners and entrepreneurs in the meantime are working on customer rela-
tionships. This means that we want to have business partners with finished integrations
of our technology as soon as we run live.

Do you feel you can support our team?

Do you have the skills we need and want to enrichen our team?
Please contact us via our forums1 or via email2 .

1
https://forums.trustchaintechnologies.io
2
office@trustchaintechnologies.io

(c) TrustChainTechnologies, 2017 3

www.trustchaintechnologies.io
Version 1.3
TrustChainTechnologies, 11.09.2017 3 FEATURES

3 Features
This new blockchain technology consists of many new aspects which need to be clarified
and described further. With TrustChainTechnologies we are introducing a new style of
blockchain, the MetaChain, chapter 3.1 on page 4.
This means that multiple blockchains can run on the same environment using the in-
frastructure and proven signing techniques to fulfill certain daily life tasks. The signing
technology of new blocks will be a new algorithm concept - Proof of Trust, chapter 3.1.1
on page 5 - which means that we sign the blocks based on how much the network trusts
an individual device. The main challenge in this technique is to ensure that a device
can be trusted and on how to check its reliability.
This also includes a brand new task of proofing blocks through our mobile devices - the
so called Proof through App, chapter 3.1.2 on page 8.
All those main features will be described closely on the following pages - if there are still
unanswered questions please dont hesitate to ask us via our forums3 or via email4 .

3.1 MetaChain
Looking at the latest developments, ICOs and new blockchains there was one big thing
which really caught our attention - the needed hardware infrastructure and energy re-
sources for those projects. As we all know a blockchain is as trustworthy and stable as
the number of engaged partners, in most cases these are nodes or mining devices. So
the biggest problem in our opinion is that new blockchains or coins mostly dont have
the power to attract very many devices to ensure the security of the network.

Normally the term MetaChain refers to a relatively new blockchain that is based on
an already developed and working blockchain. In this case we turn this term around.
This means that we develop a blockchain technology that has per design the capability
of running multiple coins with changing demands on one single blockchain.
This removes the problem of new coins that they dont have the resources of a big and
working network, since the whole infrastructure of TrustChainTechnologies can be used
- out of the box!

There are multiple ways on how to get a new coin on the TCT network to run.
The easiest way is a simple mouse click in our wallet where you can also make multiple
settings for your coin which will be, after successful creation, spread throughout the
TCT network.
The second way is more complex but also ensures the flexibility of our MetaChain. There
will be a C++ based API for nodes which allow to develop your own modules. If certain
special functions are needed, for example a different signing technique, different com-
munication ways or other external components can be developed. Node admins need to
upload and activate the module manually to ensure security on the nodes.
3
https://forums.trustchaintechnologies.io
4
office@trustchaintechnologies.io

(c) TrustChainTechnologies, 2017 4

www.trustchaintechnologies.io
Version 1.3
TrustChainTechnologies, 11.09.2017 3 FEATURES

Figure 1: The TCT blockchain is able to handle multiple coins within one blockchain

Through this API and module system we removed the need of new coins to create their
own infrastructure; they just need to convince node admins to use their module if they
even need one.

One might ask himself now, do I need a coin within an existing blockchain?
Lets give an example: youre a private organization that deals with pre-paid car leasing.
You want to use this new technology for all kind of automation, see smart contracts in
chapter 3.1.3 on page 8. You still work with excel sheets for your calculations or have a
small website that shows your customer their current payment status and credit. This
is very ineffective and possibly dangerous for malicious attacks or data loss.
Heres where the MetaChain comes in. You simply create a non-tradeable coin in our
MetaChain and use a simple wallet for your customers to show them their status. All
car leasing details can be added and handled through smart contracts and deductive
payments, chapter 3.1.6 on page 11.
So your pre-paid car leasing company runs securely without any further costs on a trust-
worthy network with the whole TrustChainTechnologies community resources behind it.

3.1.1 Proof of Trust

Proof of Trust (well refer to it as PoT ) is a new concept that tackles problems of current
signing technologies:

Proof of Work (PoW) :

This type of singing technology is one of the most used ones. It uses miners or
other calculating devices to proof that they have worked in order to get the al-
lowance of signing blocks.
This in general is a very good idea since nobody will work, if they wont get
rewarded. The biggest problem here is the waste of electrical energy. Why calcu-
lating and therefore using energy if there is nothing to calculate?
Furthermore this concept has the flaw of the widely known 51% attack, meaning

(c) TrustChainTechnologies, 2017 5

www.trustchaintechnologies.io
Version 1.3
TrustChainTechnologies, 11.09.2017 3 FEATURES

that if 51% of the network is owned by one individual, he has overtaken the net-
work and can sign any request no matter how truthful this transaction is. For
bigger coins this might be not a problem, for example BitCoin, but for smaller
coins it most certainly is.
Another big disadvantage is the current calculating power seen on a global scale.
Most of the mining equipment is produced in China, where also most of the mining
power is located. There are just a few mining pools that can compete with the
mining power coming from the two main manufacturers in China. This leads into
rising complexity of the hashes and thus making current mining equipment useless
and forcing miners to buy new hardware every year, resulting in more hardware
waste.

Proof of Stake (PoS) :

PoS tries to remove the negative parts of PoW by leaving miners and their calcu-
lating power out, simply focusing on the idea that If you have very many coins,
you want this project to succeed.
This is, from the basic thought, correct but it also does one thing that the whole
blockchain scene tries to get rid of - rich people getting richer. And this is basically
what it is, since you earn coins with your node and the amount of blocks you can
forge is defined by the number of coins you have. So running a simple node and
enriching the network for more security and stability makes no sense if you just
joined and dont have much of this digital currency.
There is also a theoretical concept of an attack, which tries to proof that the idea
of PoS is flawed in a complete objective network5 .

Because of the problems with the signing techniques mentioned above we thought that
the most important part nowadays is trust.
So there needs to be a way to ensure that you can determine and proof trust within a
computer network, even though you dont know the participating devices. This is why
we have three parties to sign a single block:

Nodes :
Nodes are one of the most important parts within our network.
They are the ones that can gain a trust factor. The trust factor is based on the
credibility of a node over a certain amount of time, the time factor the node ac-
tively participated in the network, the number of correct transactions delivered, a
connected stake as well as its computational power.
All nodes will be ranked by this factor and the better the ranking the more blocks
can be signed.

5
https://papers.ssrn.com/sol3/papers.cfm?abstract_id=2393940

(c) TrustChainTechnologies, 2017 6

www.trustchaintechnologies.io
Version 1.3
TrustChainTechnologies, 11.09.2017 3 FEATURES

Clients :
Clients are servers, miners, traditional PC systems that run software we provide
or use a certain protocol standard. These are the ones really creating the back-
bone of computational power within our blockchain technology. As already known
from BitCoin a massive amount of calculating devices can ensure the stability and
trustworthiness of a network.
In this case we change this principle a bit by not calculating 24/7 but by calculating
per demand, which means that energy and computing power can be saved, since
there is no increasing complexity of the hashes and clients are chosen randomly
for block signing.

Mobile Devices :
Nearly everyone nowadays has a cell phone but currently there is no way to use
those in a blockchain network. The reason is simple, because your battery packs
wont last that long.
We integrate mobile devices into our network by changing the computational part
to only use single devices on demand to ensure that a signing is correct and trust-
worthy. This can simply be done by installing the signing app, chapter 3.1.2 on
page 8 - everything will be done automatically in the background.

Figure 2: The PoT algorithm combines nodes, clients and mobile devices to generate a
trustworthy network

All those three participating systems will get their share on transaction fees ensuring

(c) TrustChainTechnologies, 2017 7

www.trustchaintechnologies.io
Version 1.3
TrustChainTechnologies, 11.09.2017 3 FEATURES

that their work was worthwhile. Our biggest focus here is to be fair and equal - not that
the one with the most mining power earns the most money, nor that the one with the
highest volume of coins earns the most - trustworthy nodes earn less because they are
chosen more frequently, clients and mobile devices are chosen randomly.
This ensures a fair spread revenue as well as security within the network. All the parts
have different computational tasks and if one is faulty, for example by manipulation, it
gets a penalty within the network.
These penalties are spread throughout the network and devices can be blocked for good
if they have been proven faulty.

3.1.2 Proof through App

Proof through App (PtA) is a new concept that integrates mobile devices into our
blockchain to widen the network.
Within a group of people, on a global scale, there are a few with bad goals - a few who
want and will try to manipulate. Most of the people are good people, who will be happy
to participate and strengthen the network.

This means that if we can add more devices into our network, we increase the num-
ber of trustworthy partners and this is the main goal for a Proof of Trust concept. The
app will verify that the devices indeed is a cell phone used in a regular way, which means
that it cant be placed in a server farm with thousands of other mobile devices.
The calculations done with the mobile phone will not be continuous. Through push calls
the mobile device will go into live mode, calculating and then sending back the result
into the network.
This means that the impact on the battery life of your device will be nearly zero and
every one can use this app to gather some transaction fees and ensure the security of
the network.

3.1.3 Smart Contracts

Smart Contracts, thanks to Ethereum, are in everyones focus these days.
Since were trying to build a BlockChain technology that can integrate into our daily
lives, a smart contract system is needed. The spectrum of what can be done and how
it will evolve in the near future cannot be estimated. We thought many months about
different smart contract languages to integrate, but we came to the conclusion that it
would be the best in this stage to orient on Etherum. This allows us to be interchange-
able and compatible for smart contracts that currently run at Ethereum.

This is why the main interpreter language for the TCT Network will be Solidity6 which
is a Java-Script like language. In the code example 1 you can see the style how So-
lidity is working. This example features a blind auction running automatically on the
blockchain. This means that everyone can see products that are up for auction, can bid
6
https://solidity.readthedocs.io/en/develop/

(c) TrustChainTechnologies, 2017 8

www.trustchaintechnologies.io
Version 1.3
 TrustChainTechnologies, 11.09.2017 3 FEATURES

for them, but wont know the winning bid until the auction is over.

Listing 1: Code example of a blind auction

1 pragma solidity 0 . 4 . 1 1 ;
2
3 contract SimpleAuction {
4 // P a r a m e t e r s o f t h e a u c t i o n . Times a r e e i t h e r
5 // a b s o l u t e u n i x timestamps ( s e c o n d s s i n c e 19700101)
6 // o r time p e r i o d s i n s e c o n d s .
7 address p u b l i c beneficiary ;
8 uint p u b l i c auctionStart ;
9 uint p u b l i c biddingTime ;
10
11 // C u r r e n t s t a t e o f t h e a u c t i o n .
12 address p u b l i c highestBidder ;
13 uint p u b l i c highestBid ;
14
15 // Allowed w i t h d r a w a l s o f p r e v i o u s b i d s
16 mapping ( address => uint ) pendi ngRetur ns ;
17
18 // S e t t o t r u e a t t h e end , d i s a l l o w s any change
19 bool ended ;
20
21 // Events t h a t w i l l be f i r e d on c h a n g e s .
22 event H i g h e s t B i d I n c r e a s e d ( address bidder , uint amount ) ;
23 event AuctionEnded ( address winner , uint amount ) ;
24
25 // The f o l l o w i n g i s a soc a l l e d n a t s p e c comment ,
26 // r e c o g n i z a b l e by t h e t h r e e s l a s h e s .
27 // I t w i l l be shown when t h e u s e r i s a s k e d t o
28 // confirm a transaction .
29
30 // C r e a t e a s i m p l e a u c t i o n with b i d d i n g T i m e
31 // / s e c o n d s b i d d i n g time on b e h a l f o f t h e
32 // / b e n e f i c i a r y a d d r e s s b e n e f i c i a r y .
33 function SimpleAuction (
34 uint _biddingTime ,
35 address _beneficiary
36 ) {
37 beneficiary = _beneficiary ;
38 auctionStart = now ;
39 biddingTime = _biddingTime ;
40 }
41
42 // / Bid on t h e a u c t i o n with t h e v a l u e s e n t
43 // / t o g e t h e r with t h i s t r a n s a c t i o n .
44 // / The v a l u e w i l l o n l y be r e f u n d e d i f t h e
45 // / a u c t i o n i s not won .
46 function bid ( ) payable {
47 // No arguments a r e n e c e s s a r y , a l l
48 // i n f o r m a t i o n i s a l r e a d y p a r t o f
49 // t h e t r a n s a c t i o n . The keyword p a y a b l e
50 // i s r e q u i r e d f o r t h e f u n c t i o n t o
51 // be a b l e t o r e c e i v e Ether .
52
53 // R e v e r t t h e c a l l i f t h e b i d d i n g
54 // p e r i o d i s o v e r .
55 require ( now <= ( auctionStart + biddingTime ) ) ;
56
57 // I f t h e b i d i s not h i g h e r , send t h e
58 // money back .

(c) TrustChainTechnologies, 2017 9

www.trustchaintechnologies.io
Version 1.3
 TrustChainTechnologies, 11.09.2017 3 FEATURES

59 require ( msg . value > highestBid ) ;

60
61 i f ( highestBidder != 0 ) {
62 // S e n d i n g back t h e money by s i m p l y u s i n g
63 // h i g h e s t B i d d e r . send ( h i g h e s t B i d ) i s a s e c u r i t y r i s k
64 // b e c a u s e i t can be p r e v e n t e d by t h e c a l l e r by e . g .
65 // r a i s i n g t h e c a l l s t a c k t o 1 0 2 3 . I t i s a l w a y s s a f e r
66 // t o l e t t h e r e c i p i e n t s withdraw t h e i r money t h e m s e l v e s .
67 pendi ngRetur ns [ highestBidder ] += highestBid ;
68 }
69 highestBidder = msg . sender ;
70 highestBid = msg . value ;
71 H i g h e s t B i d I n c r e a s e d ( msg . sender , msg . value ) ;
72 }
73
74 // / Withdraw a b i d t h a t was o v e r b i d .
75 function withdraw ( ) returns ( bool ) {
76 var amount = pend ingRetur ns [ msg . sender ] ;
77 i f ( amount > 0 ) {
78 // I t i s i m p o r t a n t t o s e t t h i s t o z e r o b e c a u s e t h e r e c i p i e n t
79 // can c a l l t h i s f u n c t i o n a g a i n a s p a r t o f t h e r e c e i v i n g c a l l
80 // b e f o r e send r e t u r n s .
81 pendi ngRetur ns [ msg . sender ] = 0 ;
82
83 if ( ! msg . sender . send ( amount ) ) {
84 // No need t o c a l l throw h e r e , j u s t r e s e t t h e amount owing
85 pendi ngRetur ns [ msg . sender ] = amount ;
86 return f a l s e ;
87 }
88 }
89 return true ;
90 }
91
92 // / End t h e a u c t i o n and send t h e h i g h e s t b i d
93 // / t o t h e b e n e f i c i a r y .
94 function auctionEnd ( ) {
95 // I t i s a good g u i d e l i n e t o s t r u c t u r e f u n c t i o n s t h a t i n t e r a c t
96 // with o t h e r c o n t r a c t s ( i . e . t h e y c a l l f u n c t i o n s o r send Ether )
97 // i n t o t h r e e p h a s e s :
98 // 1 . c h e c k i n g c o n d i t i o n s
99 // 2 . p e r f o r m i n g a c t i o n s ( p o t e n t i a l l y c h a n g i n g c o n d i t i o n s )
100 // 3 . i n t e r a c t i n g with o t h e r c o n t r a c t s
101 // I f t h e s e p h a s e s a r e mixed up , t h e o t h e r c o n t r a c t c o u l d c a l l
102 // back i n t o t h e c u r r e n t c o n t r a c t and modify t h e s t a t e o r c a u s e
103 // e f f e c t s ( e t h e r payout ) t o be p e r f o r m e d m u l t i p l e t i m e s .
104 // I f f u n c t i o n s c a l l e d i n t e r n a l l y i n c l u d e i n t e r a c t i o n with e x t e r n a l
105 // c o n t r a c t s , t h e y a l s o have t o be c o n s i d e r e d i n t e r a c t i o n with
106 // e x t e r n a l c o n t r a c t s .
107
108 // 1 . C o n d i t i o n s
109 require ( now >= ( auctionStart + biddingTime ) ) ; // a u c t i o n d i d not y e t end
110 require ( ! ended ) ; // t h i s f u n c t i o n has a l r e a d y been c a l l e d
111
112 // 2 . E f f e c t s
113 ended = t r u e ;
114 AuctionEnded ( highestBidder , highestBid ) ;
115
116 // 3 . I n t e r a c t i o n
117 beneficiary . transfer ( highestBid ) ;
118 }
119 }

(c) TrustChainTechnologies, 2017 10

www.trustchaintechnologies.io
Version 1.3
TrustChainTechnologies, 11.09.2017 3 FEATURES

3.1.4 Alias
Aliases are a way of storing information in a more rememberable way.
Everyone knows that your personal wallet address is a Reed Solomon feed consisting
of many letters and numbers. But nobody can really remember their personal wallet
address out of their mind, especially when they have multiple addresses. With an alias
you can define a simple to remember name for your Reed Solomon address.
Aliases will be developed as a dynamic changeable field, meaning that they can be widely
used within the network to represent data, no matter what, and used throught certain
applications.

For example within our app, chapter 3.3 on page 12, you can use your alias to connect
to other users within the TCT network for sending and receiving encrypted messages,
chapter 3.3.3 on page 13, or sending money, chapter 3.3.2 on page 13. Aliases will be
used regularly for any type of connection in the network due to their unique appearance.

3.1.5 Automated Transfers

Automated Transfers, or AT in short, are a feature well known from the current banking
system.
You can repeatedly send money to a different walllet in different time periods without
any interaction. This feature will also be included within our blockchain and realized
by using smart contracts, chapter 3.1.3 on page 8.

AT can be used within the TCT network and are not dependable on the coin youre
using. This means you can for example automatically transfer monthly 10 coins from
coin A in wallet A to coin B in wallet C. This would be the easiest example of an AT,
but AT are much more configurable.
You could create an AT that transfers 90% of your coins every hour from your trading
hot-wallet to your cold-wallet to ensure that your successfully traded profits are secured.

3.1.6 Deductive Transfers

Deductive Transfers, in short DT, are kind of the same as Automated Transfers, the
only difference is that with a DT an external wallet is authorized to pull coins from your
wallet under certain restrictions that you allowed it. This feature will also be realized
by using smart contracts, chapter 3.1.3 on page 8.
An easy example for DT would be a monthly leasing rate for a car. The leasing com-
pany deducts the monthly leasing rate on the 5th each month and also blocks the next
rate in advance to ensure proper creditability. All those parameters and settings are
configurable for every single DT.

Also again, the same situation as with AT, the DT are available throughout the whole
TCT network, regardless what coins youre working with.

(c) TrustChainTechnologies, 2017 11

www.trustchaintechnologies.io
Version 1.3
TrustChainTechnologies, 11.09.2017 3 FEATURES

3.2 Wallet
The wallet we provide will use our general API and will be available as open source. It
will be developed in regular PHP7 to provide a basic example for all future developments
to come.
When we talk about basic example we are not talking about basic features. All before
mentioned features, as outlined in the subchapters of chapters 3, will be included in this
wallet with our main focus on consumer experience and great usability.
Our wallet will furthermore integrate all MetaCoins, chapter 3.1 on page 4, in one simple
wallet. This doesnt mean its a multiwallet where the innovation is integrating different
blockchains, this means that we make a dynamic wallet which includes all coins that are
going to be organized through our MetaChain. This includes all coins that will be run im-
mediately at the go-live and any other coins that might be created in the TCT Network.

Since we run multiple coins within our MetaChain, we also will integrate an easy internal
coin exchange, chapter 3.2.1 on page 12, into this wallet.

3.2.1 Internal Exchange

The internal exchange for coins will allow users of the TCT Network to exchange coins
within the blockchain. Meaning that when we have for example 5 different coins in the
TCT blockchain, it is possible to trade and exchange these 5 different coins with one
single wallet in real time.
No external exchanges are needed for trading coins. This furthermore means also that if
one coin is tradable on a certain exchange, all coins are automatically tradeable on that
exchange. To trade a coin that is not listed on that specific exchange, you can always
trade into the coin that is tradable and use this coin then for an internal exchange.

3.3 App
The main focus of TrustChainTechnologies regarding market positioning is the integra-
tion of our technology into our daily lives.
The only way to achieve this is with an app that supports this kind of easy usability.
On the one hand we integrate our Proof through App, chapter 3.1.2 on page 8, and on
the other hand we add daily use features like sending and receiving money, chapter 3.3.2
on page 13, secure messaging within our network, chapter 3.3.3 on page 13, and GPS
mapped coin acceptances, chapter 3.3.4 on page 14.
The developed app will not only work for our main coin, this app will be developed
dynamically to ensure that all newly added coins will be supported out of the box. This
means, that also for new coins no special app is needed for trading, exchanging and
paying.

(c) TrustChainTechnologies, 2017 12

www.trustchaintechnologies.io
Version 1.3
TrustChainTechnologies, 11.09.2017 3 FEATURES

3.3.1 Proof through App

As described earlier in the feature section in chapter 3.1.2 on page 8 the Proof through
App feature, in short PtA, is one of a kind.
Within the app this feature will be automatically enabled as soon as you log into your
account. An option to disable this feature will be also given.
Certain checks will be implemented to the app to ensure that your mobile device is really
a generic device and not simply put into a cell phone farm to gather more coins. Those
checks will use GPS movement, frequent usage of your data plan, incoming and outgoing
call frequencies as well as unlocking of the phone. This does not mean that any of these
factors will be stored or used in any kind of way.
As the app will be developed under open source license, everyone can check themselves
- these algorithms are only used to ensure the authenticity of a mobile device and thus
securing the network against fraudulent usage.

The PtA feature allows every single end user who installs the app to widen the TCT
network. They automatically grow the number of signing endpoints and possibly earning
transaction fees without any work or knowledge. This is the perfect way of splitting up
the transactional fees fairly between all blockchain users.

3.3.2 Payments
Payments are the key in daily live. Its self explaining that sending and receiving pay-
ments with QR Codes will be included.
Furthermore the current status of payments will be visible, as well as all coin transac-
tions from the past.
This feature is available for all coins within the TCT Network.

3.3.3 Secure Messaging

Mobile phones in our daily private lives are mostly used for communications.
Sadly, the currently known and used communication apps are owned by big international
companies and the real truth behind the usage of our communications will never be
known. This is something we will change with our secure and private messages.
The messages will be encrypted and decrypted using an asymmetric cryptography that is
based directly on the blocks within the blockchain. This feature is known as public-key
cryptography7 .
By using this technique we can ensure that the communication between two endpoints
is encrypted and that it is not readable by anyone else than the receiver. This may not
be limited to regular text messages and could also be expanded into file sharing.
For an easier contact handling were spanning the gap between Reed Solomon adresses
and remember able names by using aliases as closer described in chapter 3.1.4 on page
11.

7
https://en.wikipedia.org/wiki/Public-key_cryptography

(c) TrustChainTechnologies, 2017 13

www.trustchaintechnologies.io
Version 1.3
TrustChainTechnologies, 11.09.2017 4 BUDGET

3.3.4 GPS Mapped Acceptances

Daily integration of a payment system also means for customers knowing where they
can use this technology to purchase products.
In the app well integrate a GPS based mapping technique to pin point locations that
currently accept coins that are traded within the TCT network. New locations can be
added by users when they report a certain location through the app or by store owners
themselves via a small web interface provided by us.

4 Budget
A project like TrustChainTechnologies needs some substantial amount of budget for de-
velopment and resources to ensure a proper market introduction. Thats why we chose
to split our financing into 3 parts.

Pre-Investments :
These investments are made before the ICO and during the development time.
This is what we call trusting - if you trust us and our idea, you can be part of it
and secure your spot in the first row of the show.

Community :
We really need users - every single project is only as good as its community. Thats
why we chose to make a special bounty hunt for community members. For a small
fee you can join the TCT community earlier than the ICO and earn yourself coins
by referring new community members to us.

ICO :
At the change of the year 2017 to 2018 well start our ICO phase. More information
about this will be published throughout the year.

The coin will hold a volume of 8.978.156.324 pieces in total. This number was chosen
based on the worlds population on day X. In our minds there is a day, we refer to it as
day X, when crypto currency will supersede FIAT money and on this day we want to
have one coin available for every person worldwide.
No coins will be premined - they will be discovered within the first few weeks by our
PoT system!
From this initial coin volume we will distribute the coins as shown in table 1.

The issuance budget will be held back for a later issuance into the network. This budget
will be released in small doses at predefined block transaction amounts.
At what blocks exactly will be determined within the community during the develop-
ment with a regular vote to ensure that the community decides this important key fact.

(c) TrustChainTechnologies, 2017 14

www.trustchaintechnologies.io
Version 1.3
TrustChainTechnologies, 11.09.2017 4 BUDGET

Coin Receiver Amount [%]

Bounties 2
TrustChainTechnologies 8
Community Members 10
Issuance Budget 15
ICO Sale 28
Trusting Members 37

Table 1: Initial budget distribution

In the issuance budget there is also 53% on coins for the signing process as special reward
for the first participating devices.

The TCT network itself will work with transaction fees. The fees for each transac-
tion will be split up as shown in table 2.

Coin Receiver Amount [%]

TrustChainTechnologies 4
Community Members 4
Trusting Members 12
Proof of Trust 80

Table 2: Transaction fees split up

To ensure that we have a proper development budget for further development,

we integrate a 4% fee into the transaction costs. Our trusting and community members,
those who really stood behind the idea by investing early, will get rewarded.
The main part is for the three devices that work in the Proof of Trust, chapter 3.1.1
on page 5, calculations, since they do all the work and ensure the network stability.
The exact amount which these devices get, how much of the 80%, will again be
decided within the community through discussion and vote within our forums8 during
development.
It is important that a project like this makes decisions based on the input of the
community since they reflect the users and customers of this blockchain technology.

(c) TrustChainTechnologies, 2017 15

www.trustchaintechnologies.io
Version 1.3
 5 Roadmap

TrustChainTechnologies, 11.09.2017
The roadmap of development is frequently updated and always visible in our forums9 .
There are too many milestones in our roadmap to cover them all and also there are too many frequent changes, this is why
well only name the most important ones:

Name of the milestone Calender Week Year Short Description

Nemesis 24 2017 beginning developement of the blockchain technology
Panoptes 38 2017 finishing PoT and block signing
(c) TrustChainTechnologies, 2017

Bellerophon 44 2017 starting development of the wallet

www.trustchaintechnologies.io

ICO Start 01 2018 Initial Coin Offering

Tyche 05 2018 beginning developement of the internal exchange
Morpheus 22 2018 going live
Version 1.3

Table 3: Technical Milestones

5 ROADMAP
16

9
https://forum.trustchaintechnologies.io/showthread.php?tid=13
TrustChainTechnologies, 11.09.2017 6 CONCLUSION

6 Conclusion
Current blockchain technologies may have the right thought behind it, but as in every
single new technology there is always something to improve.
Nobody ever knew that BitCoin would become that big and that energy and hardware
waste will become a potential problem. With our new signing algorithm we can elimate
this waste and start integrating blockchain technology into our daily lives by handing
out needed tools and interfaces to customers and vendors.
Blockchain technology will change the way we pay in the future, all it needs is that one
thing that closes the gap between real life and technology.

Thats where we come in place.

(c) TrustChainTechnologies, 2017 17

www.trustchaintechnologies.io
Version 1.3
TrustChainTechnologies, 11.09.2017 7 DOCUMENT VERSIONS

7 Document Versions
- Version 1.0: 24.06.2017
initial commit of the document
- Version 1.1: 01.07.2017
polishing with graphics
- Version 1.2: 05.07.2017
fixed some typos
- Version 1.3: 11.09.2017
reworking content in order to improve readability (thanks to crowi)

(c) TrustChainTechnologies, 2017 18

www.trustchaintechnologies.io
Version 1.3