Whitepaper - Factom With Cover
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
After purchase, the Entry Credit Chain(s) will allocate the Entry Credits to the appropriate public<br />
key. That Entry will look like:<br />
●<br />
●<br />
Public Key<br />
Number of Entry Credits purchased<br />
Using <strong>Factom</strong> without Factoids<br />
Many users of <strong>Factom</strong> may not want a wallet, and will not want to hold any cryptocurrency<br />
asset. But they will want to create their Chains (ledgers) and add their Entries. <strong>Factom</strong>’s two<br />
step recording process allows for the separation of Factoids, <strong>Factom</strong>’s tradeable token, from the<br />
right to post Entries to <strong>Factom</strong>, represented by Entry Credits. Servers and other recipients of<br />
<strong>Factom</strong> Tokens can sell Entry Credits to customers for payment via Bitcoin, conventional credit<br />
card payments, etc. The user would provide a public key to hold the Entry Credits. The seller<br />
would convert the appropriate amount of Factoids to Entry Credits and assign those rights to the<br />
user’s public key. Users could thus buy Entries Credits for <strong>Factom</strong> without ever owning the<br />
Factoids that drive the <strong>Factom</strong> servers.<br />
From a regulation point of view, this is powerful. The servers earn Factoids from the protocol.<br />
The only parties to that transaction are the server and the protocol. Then the server sells Entry<br />
Credits to users, who eventually return Factoids to the rest of the system. Entry Credits are non<br />
transferable, so the user cannot assign them to another user’s public key, and selling private<br />
keys isn’t practical or useful. In neither transaction is a tradable token (the Factoid) transferred<br />
between two parties.<br />
First Entries on Entry Chains: Support for Homesteading<br />
<strong>Factom</strong> preserves the first Entry of every Chain to the user who first claims it with a payment. A<br />
convention can be adopted where the first Entry documents the auditing rules for the chain,<br />
including a URL to documentation, or the rules in Text, or a hash of an audit program for the<br />
chain. This convention can be understood as homesteading.<br />
Through a set of revealed secrets, <strong>Factom</strong> can ensure that the user who creates the Chain<br />
determines the contents of the first Entry. (See Appendix 2 for the Man in the Middle Attack)<br />
21