feat: enlarged notes styles to support far-from-laptop presenter setup

This commit is contained in:
Joshua Seigler 2017-01-27 11:35:05 -05:00
parent fed382f2ac
commit ed85fb348a
3 changed files with 54 additions and 49 deletions

View file

@ -65,11 +65,10 @@
<ul janus-timeline janus-future="down">(Acceptable)</ul>
</li>
</div>
<div class="notes">
<u>Medium of exchange:</u> portable, durable, fungible
<u>Unit of account:</u> divisible, fungible
<u>Store of value:</u> durable, scarce, fungible
One more property: acceptable (people like using it)
<div class="notes"><u>Medium of exchange:</u> ➫portable, ➫durable, ➫fungible
<u>Unit of account:</u> ➫divisible, fungible
<u>Store of value:</u> durable, ➫scarce, fungible
One more property: ➫acceptable (people like using it)
Next: things we've used as money</div>
</section>
@ -153,8 +152,7 @@
</tr>
</tbody>
</table>
<div class="notes">
Precious metals, gold and silver.
<div class="notes">Precious metals, gold and silver.
Used widely today as money but not currency.
Less portable and divisible than its competitors.</div>
</section>
@ -225,7 +223,7 @@
</tbody>
</table>
<div class="notes">A ledger keeps track each person's money.
To send money, reduce my account and increase their account.
To send money, reduce my account and increase their account.
Like Paypal.
BUT - requires trust. One way to reduce the trust required is with...</div>
@ -281,7 +279,7 @@
</tr>
</tbody>
</table>
<div class="notes">Then instead of sending a payment from "Joshua" to "Jack", it's a payment from "private keys A and B" to "public key C".</div>
<div class="notes">Then instead of sending a payment from "Joshua" to "Jack", it's a payment from "private keys A and B" to "public key C".</div>
</section>
<section janus-future="down" janus-past="down">
@ -346,7 +344,7 @@
<img janus-timeline janus-future="left" src="styles/hashpointers-new-entry.svg" alt="" class="contain" style="object-position: 50% 50%">
<h2 janus-timeline>= Blockchain</h2>
</div>
<div class="notes">A good structure for a ledger is a linked list: each block of transactions points to the previous block. But we want this log to be tamper-proof. Hash pointers can make it so that changes earlier in the chain affect every item after that. To change history, you have to redo all the work after that point. But new blocks are still being added.</div>
<div class="notes">A good structure for a ledger is a linked list: each block of transactions points to the previous block. Each participant will trust the longest log they hear about. But we need this log to be tamper-proof. ➫➫Hash pointers can make it so that changes earlier in the chain affect every item after that. ➫➫Add proof-of-work. Now to change history, you have to redo all the work after that point. But new blocks are still being added.</div>
</section>
<section>
@ -406,8 +404,7 @@
<i class="cc SIA"></i>
<i class="cc NXT"></i>
</div>
<div class="notes">
Cloud storage is just one step further than proof-of-existence.
<div class="notes">Cloud storage is just one step further than proof-of-existence.
(Storj, Maidsafe, SIAcoin, NXT)</div>
</section>