Content and Style update

+ more text @ bitshares-general
+ tweaked bitshares-financial
+ much better way to deal with first header

AUTHORS.tex

@@ -1,6 +1,8 @@
 \author{
  Fabian~Schuh\\
  BitShares Europe, BitShares.eu\\
+ BitShares Europe, BitShares.eu\\
+ BitShares Europe, BitShares.eu\\
  Erlangen, Germany\\
  \texttt{[email protected]}\\[2ex]
  %%%%%%%

bitshares-financial-platform.tex

@@ -81,6 +81,8 @@
 %\subsection    { 3rd Party Services and Business Opportunities    } \input { content/fp-dex-roles           } 
 \subsubsection  { Fiat Gateways                                    } \input { content/fp-dex-gateway         } 
 
+\section        { Platform for Further Smart Contracts             } \input { content/fp-morecontr           }
+
 % \section      { Collateralized Bond Market                       } \input { content/fp-bond                } 
 % \subsection   { Avoiding Margin Calls                            } \input { content/fp-bond-margin         } 
 % \subsection   { Proposing and Creating a Bond                    } \input { content/fp-bond-create         } 
@@ -99,3 +101,4 @@
 % - review all occurrences of ``delegate''
 % - add QR code for more information?
 % - improve abstract and conclusions
+% - settlement & clearing

bitshares-general.tex

@@ -17,7 +17,6 @@
  future direction and products. This paper gives a brief overview over the
  whole BitShares platform, recapitulates known blockchain technologies and
  redefines \emph{state-of-the-art}.
-
 \end{abstract}
 
 \section       { Introduction                      } \input { content/bts                 } 
@@ -26,34 +25,34 @@
 \subsection    { Public Ledger                     } \input { content/spec-bc             } 
 \subsection    { Low Latency Peer-to-Peer Network  } \input { content/spec-net            } 
 \subsection    { Distributed Consensus Mechanism   } \input { content/bts-consensus       } 
-\subsection    { Operations                        } \input { content/bts-ops             } 
-\subsection    { Transactions                      } \input { content/bts-txs             } 
-\subsection    { Objects                           } \input { content/bts-objs            } 
-
-\section       { Named Account                     } \input { content/bts-acc             } 
-\subsection    { Transferability                   } \input { content/org-transfacc       } 
-\subsection    { Dynamic Permissions               } \input { content/org-dynacc          } 
-\subsection    { Recurring \& Scheduled Payments   } \input { content/org-recurr          } 
-\subsection    { Costumer Privacy                  } \input { content/bts-priv            } 
 
 \section       { Crypto Token                      } \input { content/bts-token           } 
 \subsection    { Distribution of BTS               } \input { content/bts-token-dist      } 
 \subsubsection { Bitshares PTS                     } \input { content/bts-token-dist-pts  } 
 \subsubsection { Bitshares AGS                     } \input { content/bts-token-dist-ags  } 
-\subsection    { Supply of BTS and Fees            } \input { content/bts-token-supply    } 
+\subsection    { Bitshares Genesis Distribution    } \input { content/bts-token-dist-gene } 
 
-\section       { Financial Smart Contract Platform } \input { content/whatis-financial    } 
-
-\section       { Blockchain Entities               }
-\subsection    { BitShares Witnesses               } 
-\subsection    { BitShares Committee               } 
-\subsection    { BitShares Budget Items            } 
+\section       { Business Units                    } \input { content/bts-orga            }
+\subsection    { BitShares Witnesses               } \input { content/bts-orga-witness    }
+\subsection    { BitShares Committee               } \input { content/bts-orga-committee  }
+\subsection    { BitShares Budget Items            } \input { content/bts-orga-budget     }
 
 \section       { BitShares: A profitable DAC       } \input { content/whatis-business     } 
-\subsection    { Fee Schedule and Fee Flow         } \input { content/bts-fee             }
-\subsection    { System Parameters                 } \input { content/bts-parameters      } 
+\subsection    { The products                      } \input { content/bts-products        }
+\subsection    { Revenue and Expenses              } \input { content/bts-revenue-expense }
+\subsection    { Fee Schedule and Cash Flow        } \input { content/bts-fee             }
 \subsection    { Growth Considerations             } \input { content/whatis-growth       } 
 
+\section       { Technical Specifications          } \input { content/bts-specs           }
+\subsection    { Operations                        } \input { content/bts-ops             } 
+\subsection    { Transactions                      } \input { content/bts-txs             } 
+\subsection    { Objects                           } \input { content/bts-objs            } 
+\subsection    { Named Account                     } \input { content/bts-acc             } 
+\subsubsection { Transferability                   } \input { content/org-transfacc       } 
+\subsubsection { Dynamic Permissions               } \input { content/org-dynacc          } 
+\subsubsection { Recurring \& Scheduled Payments   } \input { content/org-recurr          } 
+\subsubsection { Costumer Privacy                  } \input { content/bts-priv            } 
+
 \section       { Discussion                        } \input { content/bts-discussion      } 
 
 \section       { Conclusion                        } \input { content/bts-conc            } 

btswhitepaper.cls

@@ -7,6 +7,7 @@
 \RequirePackage{fancyhdr}
 \RequirePackage{amsmath,amssymb,amssymb}
 \RequirePackage{paralist}
+\RequirePackage[shortlabels]{enumitem}
 \RequirePackage[hyphens]{url}
 \RequirePackage{breakurl} 
 \RequirePackage[breaklinks]{hyperref}
@@ -69,37 +70,9 @@
 \definecolor{btslight}{HTML}{00a9e0}
 
 %% -----------------------------
-%% Headers
-%% -----------------------------
-\fancypagestyle{wp}{%
- \fancyhf{}
- \fancyhead[R]{{\color{black}\sffamily\thepage}}
- \fancyhead[L]{{\color{black}\sffamily \nouppercase{\textsc{\rightmark}}}}
- \fancyfoot{}
- \fancyfoot[R]{\includegraphics[height=2cm]{figures/btslogo4.png}}
- \renewcommand{\headrule}{\color{btslight}\hrule}
- \renewcommand{\headrulewidth}{0.4pt}
-}
-\fancypagestyle{plain}{%
- \fancyhf{}
- \fancyhead{}
- \fancyfoot{}
- \renewcommand{\headrule}{}
- \renewcommand{\headrulewidth}{0pt}
-}
-\pagestyle{wp}
-
+%% Makros
 %% -----------------------------
-%% Diverse
-%% -----------------------------
-\hyphenpenalty=750
-\hbadness=1350
-\frenchspacing
-\binoppenalty=1000
-\relpenalty=800
-\clubpenalty=1000
-\widowpenalty=1000
-\displaywidowpenalty=1000
+\newcommand{\note}[1]{ {\color{red}(#1)} }
 
 %% -----------------------------
 %% Title
@@ -110,7 +83,7 @@
  contents={%
  \begin{tikzpicture}[remember picture,overlay]
   \path [fill=btsdark] (-0.5\paperwidth, 0.50\paperheight) 
-              rectangle ( 0.5\paperwidth, 0.25\paperheight);
+             rectangle ( 0.5\paperwidth, 0.25\paperheight);
  \end{tikzpicture}}
 }
 
@@ -120,25 +93,47 @@
  \newpage
  \BgThispage
  \let \footnote \thanks
- \begin{flushright}
- \color{white}
-  {\LARGE\bfseries\textsc{\@title} \par}%
-   \vskip 3.5em%
-   {\normalsize
-     \lineskip .5em%
-     \begin{minipage}{.3\linewidth}
-     \end{minipage}
-     {\color{white}\vrule width 2pt}\hskip.5em
-     \begin{minipage}{.3\linewidth}
-      \@author
-     \end{minipage}
-   }%
- \end{flushright}
- \vskip 3.5em
+ \begin{minipage}[t][.25\paperheight][t]{\textwidth}
+  \begin{flushright}
+  \color{white}
+   {\LARGE\bfseries\textsc{\@title} \par}%
+    \vskip 3.5em%
+    {\normalsize
+      \lineskip .5em%
+      \begin{minipage}{.3\linewidth}
+      \end{minipage}
+      {\color{white}\vrule width 2pt}\hskip.5em
+      \begin{minipage}{.3\linewidth}
+       \@author
+      \end{minipage}
+    }%
+  \end{flushright}
+ \end{minipage}
  \thispagestyle{plain}
 }
 \makeatother
 
+%% -----------------------------
+%% Headers
+%% -----------------------------
+\fancypagestyle{wp}{%
+ \fancyhf{}
+ \fancyhead[R]{{\color{black}\sffamily\thepage}}
+ \fancyhead[L]{{\color{black}\sffamily \nouppercase{\textsc{\rightmark}}}}
+ \fancyfoot{}
+ \fancyfoot[R]{\includegraphics[height=2cm]{figures/btslogo4.png}}
+ \renewcommand{\headrule}{\color{btslight}\hrule}
+ \renewcommand{\headrulewidth}{0.4pt}
+}
+\fancypagestyle{plain}{%
+ \fancyhf{}
+ \fancyhead{}
+ \fancyfoot{}
+ \renewcommand{\headrule}{}
+ \renewcommand{\headrulewidth}{0pt}
+}
+\pagestyle{wp}
+
 %% -----------------------------
 %% Abstract
 %% -----------------------------
@@ -158,3 +153,16 @@
 \titleformat{\subsubsection}
   {\normalfont\sffamily\large\bfseries\color{btslight}}
   {\thesubsubsection}{1em}{}
+
+%% -----------------------------
+%% Diverse
+%% -----------------------------
+\hyphenpenalty=750
+\hbadness=1350
+\frenchspacing
+\binoppenalty=1000
+\relpenalty=800
+\clubpenalty=1000
+\widowpenalty=1000
+\displaywidowpenalty=1000
+

content/bts-consensus.tex

@@ -56,7 +56,7 @@
 trust concentrating in the hands of those with the most resources. DPOS allows
 the network to reap some of the major advantages of centralization, while still
 maintaining some calculated measure of decentralization. Furthermore, once a
-delegates has reached approval by shareholders, surpasses the threshold of the
+witness has reached approval by shareholders, surpasses the threshold of the
 most $N$ active witnesses, and, hence, is elected to actively participate in
 the block production procedure, its power is \emph{equivalent} to all other
 active witnesses. This system is enforced by a fair election process where
@@ -68,15 +68,15 @@
 the following reasons:
 \begin{itemize}
 \item When a fork is produced it is
-      very likely that all delegates have seen and processed your transaction and
-      thus no alternative transactions can be broadcast and the next delegate is
-      almost certain to include your transaction.  All delegates are much more
+      very likely that all witnesses have seen and processed your transaction and
+      thus no alternative transactions can be broadcast and the next witness is
+      almost certain to include your transaction. All witnesses are much more
       trusted than miners.
 \item The probability of a fork after a block has been produced is very low (<
       0.01\%) where as Bitcoin has 25 orphans in the last 22 days (about 1 per day in
       Dec 3,2014) which translates into 0.7\% of blocks are orphaned.
 \item On normal operations, DPOS achieves a 100\% witness participation rate and when
-      we are less than that it is more often because a delegate went offline and didn't
+      we are less than that it is more often because a witness went offline and didn't
       produce a block than because they produced a fork. 
 \item In BitShares 1.0 forks have almost always been resolved within 30 seconds. 
 \end{itemize}

content/bts-fee.tex

@@ -0,0 +1 @@
+% GFX

content/bts-ops.tex

@@ -11,20 +11,13 @@
 The release version of BitShares 2.0 comes with 
 \begin{inparaenum}[(a)]
  \item transfer ops,
- \item limit-order ops,
- \item call-order ops,
- \item fill-order ops,
+ \item trading order ops,
  \item account ops,
  \item asset ops,
  \item witness ops,
- \item withdraw-permission ops,
- \item committee-member ops,
- \item vesting-balance ops,
- \item worker ops,
- \item custom ops,
- \item assert ops,
- \item balance ops, and
- \item override ops.
+ \item committee ops,
+ \item worker ops, and
+ \item vesting ops,
 \end{inparaenum}
 However, since BitShares allows for shareholder approved, live protocol
 upgrades, the set of operations can be extended and modified. 

content/bts-token-dist-ags.tex

@@ -13,17 +13,7 @@
 that donations to this address never resulted nor will result in any
 obligations whatsoever.
 
-\bigskip
-
-%% BTS Genesis
-Having attracted two different groups of investors with a mined crypto token
-via PTS and a donation based book of donors via AGS, everyone had a chance to
-participate and be rewarded with stake in the genesis block of BitShares 1.0.
-This genesis block solely consisted of AGS and PTS holders on a 50\%/50\% ratio
-such that the BTS tokens initially issued by this genesis can be considered
-\emph{well distributed}.
-
-%% Social consensus update
-However, ever since the BitShares network has launched, the social consensus
-has shifted towards \emph{sharedropping} onto holders of BTS directly instead
-of PTS/AGS.
+Since the social consensus includes AGS, the industry recommendation again is
+to give at least 10\% to holders of AGS. Similar to BitShares PTS, the 47\% of
+the total BTS supply have been sharedropped onto members of the AGS
+mailing-list proportionally.

content/bts-token-dist-pts.tex

@@ -1,15 +1,18 @@
-The original grandfather prototype formerly called proto-shares (PTS).
-BitShares PTS, our \emph{prototype bitshares coin}, was a simple minable
-crypto-currency (similar to Bitcoin) that was created to allow people to
-advertise their interest in receiving free token samples in future DACs. PTS
-functions as a high-tech \emph{mailing list} for distributing free sample
-bitshares from many developers of decentral autonomous companies (DACs). The
-only people who tended to own PTS tokens were those who understand DACs, so DAC
-developers prefer to target them with free samples rather than \emph{air
-dropping} their samples onto a much less interested general population.
+The original grandfather prototype, formerly called proto-shares (PTS),
+BitShares PTS was a simple minable crypto-currency (similar to Bitcoin) that
+was created to allow people to advertise their interest in receiving free token
+samples in future DACs. PTS functions as a high-tech \emph{mailing list} for
+distributing free sample bitshares from many developers of decentral autonomous
+companies (DACs). The only people who tended to own PTS tokens were those who
+understand DACs, so DAC developers prefer to target them with free samples
+rather than \emph{air dropping} their samples onto a much less interested
+general population.
 
 The industry recommendation was that when a DAC is launched, at least 10\% of
 the DAC's total tokens are given proportionally to holders of PTS. This was not
 a contract or a guarantee; it was a \emph{social consensus} of those in the DAC
 community about what percentage of a new DAC's tokens should be distributed to
 those who have supported the BitShares industry by owning its PTS tokens.
+
+The BitShares DAC honored this social consensus and even sharedropped 47\% of
+its ever existing supply onto BitShares PTS holders.

content/bts-token-dist.tex

@@ -3,23 +3,8 @@
 future chain will always benefit by choosing to align itself with the ones who
 worked hard at making the technology possible.
 
-Hence, the seed allocation (initial distribution) of BitShares, which took
-place over a 1 year period, from November 2013 to November 2014, was achieved
-by sharedropping 47\% to BitShares PTS and another 47\% to BitShares AGS.
-%
-This way, the full, fairness was defined by equal opportunity and in the case
-of BTS we have distributed \emph{fairly} by CPU mining of PTS while,
-alternatively, everyone had an additional equal opportunity by contribute to
-AGS~\cite{}.
-
-The other 6\% are set aside to secure the future of BitShares and funds its
-development. However, in contrast to many other crypto-currencies, every
-shareholder has a say as to who these funds are spend (see
-\cref{sec:token:supply}).
-
 The base tokens of BitShares \emph{2.0} will be distributed on a 1:1 basis
-fully honoring the BTS tokens in the BitShares \emph{1.0} network.  For the
-sake of completeness, the following paragraphs will describe the initial
-distribution of BTS tokens in the aforementioned BitShares 1.0 network.
-
-The following will discuss PTS and AGS in more detail.
+fully honoring the BTS tokens in the BitShares \emph{1.0} network. For the sake
+of completeness, the following paragraphs will describe the initial
+distribution of BTS tokens in the aforementioned BitShares 1.0 network from PTS
+and AGS.