Page tree
Skip to end of metadata
Go to start of metadata

Attendees

  • Ram Jagadeesan
  • Mic Bowman
  • Hart Montgomery
  • Alex Yakovlev
  • Danno Ferrin
  • Clive Boulton

Notes

Self-describing characteristics for blockchain interchain integration and APIs.

Trust

  • Does it have finality
  • Key in ledger

Resilience

  • Bitcoin several billion in mining compute (highly resilient)
    • PoW 51% cost 
  • Altcoins little mining compute (little resilience)

Automated self-describing requirements (not characteristics of one offs)

  • Translation not census co-ordinator
    • How do you identify 
      • Fabric expose identity to API (or reach into for key)
    • How do you query state of ledger
      • Sawtooth meta categories

Use case

  • Switch ownership 
    • not switch chains (still not trivial) 
  • Lever both chains to do swap (smart contracts on both)
    • Degree of trust characteristics
  • Harder swap bitcoin/lightcoin
    • Are chains strong enough (no > 3rd chain)
    • centralize / decentralize
  • IRL 
    • Online house sale (overpriced)
    • Side agreement to sweeten the deal > integrate an additional smart contract on an additional blockchain (degree of trust)

APIs

  • IRL
    • Solidity on-contract hashmap > key get hash > salting > key + offset > need to know source code (query does not cost gas)
    • Hyperledger projects read source code or read API...(consider funelling requirements back to projects)  










   

  • No labels

2 Comments

  1. What did you guys talk about?

    1. Self describing characteristics for blockchain interchain integration and APIs (notes to follow)