Skip to content

Commit 54f378e

Browse files
committed
style: add use case heading
1 parent 6973c36 commit 54f378e

File tree

1 file changed

+10
-5
lines changed

1 file changed

+10
-5
lines changed

smart-contracts.md

+10-5
Original file line numberDiff line numberDiff line change
@@ -8,37 +8,42 @@
88
- Pooling Funds (susu)?
99
- Too much power for the user? No recorse if a user creates a time lock of 100 years
1010

11-
#### Multi Party Money
11+
## Use Cases
12+
13+
### Multi Party Money
1214

1315
- Supporting ways people use money in groups,
1416
- Susu (informal lending club)
1517
- P2P Investments (multi signature)
1618

17-
#### Payment Groups
19+
### Payment Groups
1820

1921
- Who decides the order for money to be delivered
2022
- Paying for dinner or trips
2123
- Fundraising
2224
- Payment conditions if a balance reaches a certain amount by a certain time
2325

24-
#### Multi Sigs
26+
### Multi Sigs
2527

2628
- have a very distinct footprint
2729
- Lots of complexity
2830
- P2P Trades use multisig escrow
2931

30-
#### Signature Aggregation Across devices
32+
### Signature Aggregation Across devices
3133

3234
- User Experience implications of Schnorr Signatures and multi sigs, how to some of the other proposed patterns make this easier to interact with
3335

34-
#### Recovery & Security
36+
### Recovery & Security
3537

3638
- [5$ Wrench Attack](https://www.google.com/url?q=https://cryptosec.info/wrench-attack/&sa=D&ust=1596843563686000&usg=AOvVaw1N4A7C9BsU0JV3D6WZmri2)
3739

3840
- Timelocks
3941

4042
### Streaming Payments
4143

44+
- Time locks
45+
- Multi Sig
46+
4247
### User Research
4348

4449
- Are there any use cases that simple smart contract logic can be applied to.

0 commit comments

Comments
 (0)