owned this note changed 6 years ago
Linked with GitHub

Plasma Implementers 2.0 Agenda

  • Welcome! Note the call is recorded and will be posted on youtube.
  • Status Updates (one per team)
    • Name of your project (we will link in description)
    • The plasma implementation you've built
    • The biggest challenge you've faced running Plasma
  • Experience running Plasma in the wild
    • Successes, challenges, dreams.
  • Plasma Implementers Goals & Deliverables
  • Meta Feedback / Discussions
  • Bye! <3

Notes

  • Georgios / Kelvin organizational & non-technical notes:

    • Split into Implementers and Researchers (?)
    • Let's keep spitballing/unstructured discussions out of the recording
    • "Ringleader", who shuts down discussions that go out of topic
    • Assign a note-taker (either permanent, or one that's different per call)
    • Dedicate a call on what we have tried and what doesn't work
    • RFCs/Standardization
    • If somebody is presenting something they've built, have slides. If it's research, make sure you've made the design document/blogpost available to the interested parties so that they've all read it.
  • Fees matic

  • Leap DAO work together

  • specs from chat

  • create a forum post for data structures

  • standardize wallet interface

  • d


Some notes from plasma.build forum:

General

  • "The role of Plasma in crypto-mass-onboarding" Johann
  • "Experience running Plasma in the wild" Johann

Plasma Interoperability

  • "possibility to have a “committer chain” for both interoperability and saving storage" Alex
  • "an initial MVP vs Cash “debate”" Georgios
  • "decided to implement following PG spec because we wanna avoid conflicts" Shuhei
  • "What are the risks to developers to take care when implementing exit contract interfaces?" Jaynti
  • "How to make NFTs interoperable between side-/child-chains." Johann
  • "abstract fees from plasma, so one can use/experiment different fee models without touching plasma specs." Jaynti

Plasma Implementers Meta

  • "Potentially split into implementers and researchers calls. There are many who are doing research but not much implementation, and the opposite." Georgios
  • "primary research/implementation calls should be to present well-specified ideas" Kelvin

Calls for:

  • data structures
  • contract interfaces
  • wallet functionalities
    • shared repository?
    • burner wallet as an onboarding app store
Select a repo