Adding pre-balance descriptions and transaction chapter

merge_sections.sh

@@ -27,6 +27,11 @@ cat NeoVM.md >> ../specification.md
 echo "" >> ../specification.md
 echo "  \newpage" >> ../specification.md
 
+echo "" >> ../specification.md
+cat Transaction.md >> ../specification.md
+echo "" >> ../specification.md
+echo "  \newpage" >> ../specification.md
+
 echo "" >> ../specification.md
 cat NeoContract.md >> ../specification.md
 echo "" >> ../specification.md

sections/NeoContract.md

@@ -1 +1,33 @@
 # NeoContract
+
+
+## Payable applications
+
+Payable applications are all applications that are `payable` or pays any `network_fee` or `sys_fee`;
+
+### Balances updates
+
+#### Pre-balances
+
+Pre-balances are updated when transactions enter in the `mempool`, throughout the `verification` process.
+In this sense, `verification` updates pre-balances.
+
+In this sense, when a transaction is relayed, we are ensured that all network fees can be correctly payed.
+
+#### After blocks persists
+
+In the meanwhile, while transaction are being executed, pre-balances are again updated for all `payable transactions` given a parameter defined as `maximum_gas_payable`.
+
+In this sense, Invocation transaction should declare the intention to spend an amount of `X` GAS;
+
+## Appendices
+
+### Native Contracts
+
+#### NEO Native
+
+#### GAS Native
+
+#### SimplePolicy
+
+#### Voting

sections/Transaction.md

@@ -0,0 +1,14 @@
+# Transactions
+
+## How it works
+
+## Signer and co-signers
+
+## Attaching network and system fees
+
+The fields of the transaction in which this values are attached are:
+
+* system fee is attached as GAS (To be updated)
+* network fee is attached as Sender (To be updated)
+
+As soon as transaction enters in the mempool, these values are updated in the pre-balance.