ILP Workshop: Cryptoconditions
•Download as PPTX, PDF•
2 likes•1,361 views
A solid foundation for ILP. Presented on 2/25/2016 at Ripple headquarters in San Francisco, CA. Presenters include Stefan Thomas, Evan Schwartz, and Adrian Hope-Bailie.
Recommended
Recommended
More Related Content
More from Interledger
More from Interledger (12)
Recently uploaded
Recently uploaded (20)
ILP Workshop: Cryptoconditions
- 1. Crypto Conditions Stefan Thomas A Solid Foundation for ILP
- 3. Connector gets receipt from ledger 3 Umm...
- 4. Connector passes on the receipt 4 Excuse me...
- 5. Connector passes on the receipt 5 What's that thing?
- 6. Ledger Needs to Decide 6 EXECUTEROLLBACK ?
- 10. As a sender I want to be certain
- 11. As a sender I want to be certain that my donation was received
- 12. As a sender I want to be certain that the invoice was paid
- 13. As a sender I want to be certain that my debt is settled
- 14. As a sender I want non-repudiable proof-of-settlement
- 15. The Receipt 15 ● Signed by recipient ● Proves receipt-of-funds ● Non-repudiable ● Might have data attached ● Pre-agreed before payment
- 16. How do we describe the receipt? 16 EXECUTEROLLBACK
- 17. How do we describe the receipt? 17 EXECUTEROLLBACK
- 18. How do we describe the receipt? 18 EXECUTEROLLBACK
- 19. Condition 19 ● Describes some signed message ● Fulfilled by that message ?
- 20. Why Are Conditions so Important? 20
- 21. Why Are Conditions so Important? 21 EXECUTE
- 22. Why Are Conditions so Important? 22 EXECUTEROLLBACK
- 23. Conditions Must Be Bit-Perfect 23 EXECUTE EXECUTE
- 24. Others Have Done The Hard Part 24
- 28. Prior Art: Bitcoin Scripts 28 2 <K1> <K2> <K3> 3 CHECKMULTISIGVERIFY ● Forth-like language ● Many opcodes disabled ● Primary use case: m-of-n multi-signature
- 29. Other Ideas 29 ● Pay-to-script-hash — Andresen ● Tree Signatures — Wuille ● Merkleized Abstract Syntax Trees (MAST) — Rubin et al ● Script2 — Blockstream ● Smart Signatures — Allen et al ● State Channels — Coleman
- 31. Security vs Flexibility Single Signature Turing Completeness Bit-perfect, standardized programming language
- 32. Security vs Flexibility Single Signature Turing Completeness "ActiveX of blockchain"
- 34. Smart Oracles
- 37. Delegation
- 38. If Bob says yes, then yes. Single Signature
- 39. If Bob and Lina say yes, then yes. 2-of-2 Multi Signature
- 40. If any two of Bob, Chandra, Lina say yes, then yes. 2-of-3 Multi Signature
- 41. If Bob and (Chandra or Lina) say yes, then yes. 2-of-3 Multi Signature?
- 47. Putting it all together
- 50. Fulfillment
- 51. Signature Condition CONDITION = VARUINT BITMASK = 2 UINT256 HASH VARUINT MAX_FULLFILLMENT_LENGTH
- 52. Signature Condition CONDITION = VARUINT BITMASK = 2 UINT256 HASH VARUINT MAX_FULLFILLMENT_LENGTH HASH = SHA256( SHA256("https://...#rsa-sha-256") VARSTR MODULUS VARSTR MESSAGE_PREFIX )
- 54. Signature Fulfillment FULFILLMENT = VARUINT BITMASK = 2 VARSTR MODULUS VARSTR MESSAGE_PREFIX VARSTR MESSAGE UINT8[LENGTH(MODULUS)] SIGNATURE VARUINT BYTES_UNUSED
- 56. Threshold Condition CONDITION = VARUINT BITMASK UINT256 HASH VARUINT MAX_FULLFILLMENT_LENGTH
- 57. Threshold Condition CONDITION = VARUINT BITMASK UINT256 HASH VARUINT MAX_FULLFILLMENT_LENGTH HASH = SHA256( SHA-256("https://...#threshold-sha-256") VARUINT THRESHOLD VARUINT NUM_ELEMENTS FOR EACH ELEMENT ELEMENT_CONDITION )
- 59. Threshold Fulfillment FULFILLMENT = VARUINT BITMASK VARUINT THRESHOLD VARUINT NUM_ELEMENTS FOR EACH ELEMENT VARUINT PARAMS ELEMENT_CONDITION/FULFILLMENT
- 61. Merkle Circuits
- 65. Recap ● Two Condition Types ○ Signature ○ Threshold ● Conditions are constant size ● Falsy branches can be omitted ● Complex logic is delegated
- 66. Other Features ● Conditions can be generated from fulfillments ● Max fulfillment length in condition ● Extensible with new crypto primitives ● Required feature set in condition
- 67. First Editor's Draft Coming Soon Interledger.org