Git Product home page Git Product logo

agoric-lecture-content's Introduction

Chainboard Academy Agoric Bootcamp

We will be updating this repository with our lecture content as we deliver the lectures.

Course Overview

Lecture Subject
1 Introduction To Agoric and Hardened JavaScript
2 Introduction to ERTP and Zoe
3 APIs In Depth: ERTP and Zoe
4 Higher-order Smart Contracts
5 REPL and Deploy Scripts
6 Notifiers and Subscriptions
7 Multiuser Dapps, Lending Protocol
8 Agoric pre-built contracts & Price Authority
9 The Inter Protocol
10 Wrap-up

Video Recordings

Video recordings of lectures are also available:

image

agoric-lecture-content's People

Contributors

anilhelvaci avatar dckc avatar aliyadav avatar jorge-lopes avatar erights avatar

Stargazers

Osman Nuri Yıldız avatar avatar Palash A. avatar avatar avatar Ruslan Hlaznov avatar

Watchers

avatar

Forkers

dneprdevaleksandr toliaqat erights dckc bugratr gacogo

agoric-lecture-content's Issues

ag-solo problem is more backups than powerful objects

The core issue that prompted development of the on-chain smart wallet was really backups:

The market norm is: if you have your 24 words, you can walk up to any computer and start doing business. But with ag-solo, you need the state of all your vats. If your machine crashes and you don't have a backup of your client-side wallet vat, poof! There went your assets. (well, not completely... recovering the vat state isn't as hard as cracking private keys, but it would involve a huge forensics effort.) So we moved the state of the wallet from the client machine on to the blockchain.

Aside: the initial prototype of the smart wallet was a nifty demonstration of the overall distributed object framework: We just changed where the wallet vat was deployed from the client side to on-chain, without changing the code inside the vat at all. I'm pretty sure @michaelfig did it, but I can't find it. Michael? Help?

So this point in the lecture doesn't seem like right thing to emphasize:

agoric-lecture-content/lectureNine/lectureNine.md

Line 68 in 2b33810

* We should not expose objects that powerful to normal users

It comes up at about 19:50 in the recording.

The overall security properties of ag-solo are pretty good. The home object only has capabilities that, in due course, we do want users to have.

There are some security issues that postponing ag-solo access allows us to postpone for the short/medium term:

But by mainnet 3, we do want E(home.zoe).install(...) and E(home.zoe).startInstance(...) (or something equivalent) to be permissionless.

cc @jeetraut @hielo777

ag-solo problem is more backups than powerful objects (lectureNine)

The core issue that prompted development of the on-chain smart wallet was really backups:

The market norm is: if you have your 24 words, you can walk up to any computer and start doing business. But with ag-solo, you need the state of all your vats. If your machine crashes and you don't have a backup of your client-side wallet vat, poof! There went your assets. (well, not completely... recovering the vat state isn't as hard as cracking private keys, but it would involve a huge forensics effort.) So we moved the state of the wallet from the client machine on to the blockchain.

Aside: the initial prototype of the smart wallet was a nifty demonstration of the overall distributed object framework: We just changed where the wallet vat was deployed from the client side to on-chain, without changing the code inside the vat at all. I'm pretty sure @michaelfig did it, but I can't find it. Michael? Help?

So this point in the lecture doesn't seem like right thing to emphasize:

agoric-lecture-content/lectureNine/lectureNine.md

Line 68 in 2b33810

* We should not expose objects that powerful to normal users

It comes up at about 19:50 in the recording.

The overall security properties of ag-solo are pretty good. The home object only has capabilities that, in due course, we do want users to have.

There are some security issues that postponing ag-solo access allows us to postpone for the short/medium term:

But by mainnet 3, we do want E(home.zoe).install(...) and E(home.zoe).startInstance(...) (or something equivalent) to be permissionless.

cc @jeetraut @hielo777

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.