BEHOLD
the future is upon us!

A recap, some highlights and a view ahead on Substrate

benjamin kampmann

gnunicorn.org // ben@parity.io

dec 6th, 2019

@ Sub0.1, Berlin

Cumulus
    Smart Contracts
Offchain Workers

becoming a parachain

next-gen chain development

interacting with the outside world

Honorable Mentions

substrate.dev

our amazing developer hub

Shawn Tabrizi

@shawntabrizi:matrix.parity.io

  • THE entry point to all Substrate docs
  • Tutorials, recipes, guides
  • upcoming restructure with a lot more background information

Hacktoberfest '19

Seminars

  • weekly zoom call – Tuesdays 14:00 UTC
  • learning a new topic each week
  • with show & tell, Q & A and open discussions

Joshy Orndorff

@joshyorndorff:matrix.parity.io

relaychain.fm

  • almost bi-weekly 45min podcast
  • nine episodes in
  • all the things substrate & polkadot

Joe Petrowski

@joe:matrix.parity.io

Nicole Zhu

@nicole:matrix.parity.io

RustInBlockchain.org

monthly newsletter on the combinations of the "hypest of hypest of technologies"

SubstrateMarketplace.com

BlockUnison's searchable index of substrate modules (now "FRAME pallets") from all over the internwebs. Submit yours now.

BABE
SelectChain
Proof of Work

slot-based block authoring

define the strategy for selecting heads for consensus

proving in substrate consensus is truly pluggable

tx Weights
SignedExtensions

Random Coin Flip

advanced transaction payment infrastructure

your on-chain source for randomness

secured header information

EVM
PeerSetManager
Child tries

run solidity contracts

cost-economics network connection management

build your own trie inside the substrate runtime

Substrate/FRAME

the big repo reorg

towards 2.0

/client
/frame
/primitives

the outer node infrastructure

the inner chain functionality

the interface between the two

primitives

  • interface between inner and outer node
  • prefixed `sp-`

Terms

client

  • the outer node infrastructure
  • prefixed `sc-`

FRAME

  • our opinionated modular, infrastructure to build chain logic
  • prefixed `frame-`

pallets

  • optional modules for FRAME
  • prefixed `pallet-`

Upgrade.txt

with the release of 2.0

  • publishing on crates.io
  • full Semantic Versioning for all crates
    though some (e.g. networking, consensus) will be < 1.0
  • docs/Upgrade.txt will record all steps necessary to upgrade to latest version
    continuously updated, also on master

Does it mean it's stable?

It's complicated.

  1. We are building on it: Kusama
  2. You don't need build against master for the latest changes
  3. It's on crates.io; Semantic Versioning; release notes

Should you build on it?

Does it mean it's stable?

– YES

It's complicated.

"Already know about potentially breaking changes" –like what?

  • Long running offchain workers
  • On-chain data migration paths
  • Reducing the macro-magic
  • Networking, consensus

consensus

consensus

is this the future yet?

let's give it a reality check

the
building
blocks
for Web3

Web 1.0

Web 2.0

publish / read

write

collaborate

socialise

Web 2.5

mobile

on-the-go

Web 3.0

trust

transparency

ownership

PoC: Gather.wtf

hackathon project–a meetup replacement on substrate with:

  • global registry of groups  & events
  • on-chain governance (awesome!)
  • email+pw-login (translates to Account-keys)
  • email-auth-flow via json_rpc
  • notification-emails via Offchain Workers
  • offchain metadata through IPFS

more in the blog post

Interoperability

 

Safe Data Storage

 

 

Data Privacy

Gather.wtf is still lacks ...

what's Parity doing about it?

Interoperability

Polkadot

  • parachain
  • parathreads
  • XCMP

Bridges

Offchain-Worker

  • substrate2substrate
  • substrate2X
  • SPREE

connecting to the non-chain-world, e.g.:

  • email or push notifications
  • external login mechanism

Large File Storage

  • Extension to Substrate & FRAME (in research)
  • Storing & retrieving non-consensus off-chain data easy (and native to) in Substrate
  • Have a "native" reference to off-chain data on-chain
    make Substrate "understand" offchain data
  • Piggy-back on existing Substrate network to distribute the data
  • Allow for data validation to ensure safety-at-write

Data Privacy & Security

  • Zero Knowledge Proofs in Substrate
    maybe some ZEXE, ZK-Rollup/ZK-Sync
  • Multi-Sign/ Threshold-Schemes for Offchain Work
  • QUIC support for libp2p
  • Substrate SecretStore
  • Trusted Compute execution

and so many more...

what will YOU make the future to be?

thanks!

benjamin kampmann // gnunicorn.org

matrix:  @ben:matrix.parity.io
email:    ben@parity.io

parity.io/newsletter

Behold the future is upon us!

By Benjamin Kampmann

Behold the future is upon us!

A quick recap of what happened at Sub0.1, some more projects and honorable mentions, we didn't have time for and other changes that happened and a quick reality check and view into the future of Substrate.

  • 872