Held on Apr. 14, 15:00 UTC | Videos / livestreams: Part 1, Part 2

Discover how an Aragon organization is architected and structured on-chain in Ethereum.

We'll go into the important emitted events of organization contracts and discuss the strategy we currently use to load information into the Aragon client.

Resources (specs/diagrams)

Agenda

Ethereum 101

• How are contracts, state, and events actually represented?
• What are some of the trade-offs?
• Non-determinism, both with nodes as well with APIs

Aragon organizations on-chain

• The entire contract network and infrastructure of Aragon organizations
  • Base contracts
  • aragonPM
  • Factories and Templates
  • An actual organization
    • Kernel
    • ACL
    • Installed apps
    • ENS naming
    • EVMScripts (Part 2; 0:03)

Aragon organizations off-chain (Part 2; 10:23)

• Aragon client / aragon.js / Aragon apps (Part 2; 11:25)
• Deep dive into aragon.js (Part 2; 14:56)
  • All relevant "first class" state (Part 2; 15:12)
    • Contract events
    • IPFS metadata (Part 2; 45:39)
  • "Client-facing" APIs
  • App state and an example reducer (Part 2; 1:15:50)
  • Caching strategy (Part 2; 1:38:48)
• Transaction pathing (Part 2; 1:43:41)
  • Types:
    • Direct (Part 2; 1:44:55)
    • "Normal" pathing (Part 2; 1:58:54)
    • "External" pathing (Part 2; 1:55:33)
      • "Internal", but not currently running application
      • Arbitrary contract outside organization
    • "Final forwarder" pathing (currently only ACL) (Part 2; 2:42:28)
    • "Intent basket" (Part 2; 3:06:15)