the future is upon us!
A recap, some highlights and a view ahead on Substrate
gnunicorn.org // email@example.com
dec 6th, 2019
@ Sub0.1, Berlin
becoming a parachain
next-gen chain development
interacting with the outside world
our amazing developer hub
- THE entry point to all Substrate docs
- Tutorials, recipes, guides
- upcoming restructure with a lot more background information
- weekly zoom call – Tuesdays 14:00 UTC
- learning a new topic each week
- with show & tell, Q & A and open discussions
- almost bi-weekly 45min podcast
- nine episodes in
- all the things substrate & polkadot
monthly newsletter on the combinations of the "hypest of hypest of technologies"
BlockUnison's searchable index of substrate modules (now "FRAME pallets") from all over the internwebs. Submit yours now.
Proof of Work
slot-based block authoring
define the strategy for selecting heads for consensus
proving in substrate consensus is truly pluggable
Random Coin Flip
advanced transaction payment infrastructure
your on-chain source for randomness
secured header information
run solidity contracts
cost-economics network connection management
build your own trie inside the substrate runtime
the big repo reorg
the outer node infrastructure
the inner chain functionality
the interface between the two
- interface between inner and outer node
- prefixed `sp-`
- the outer node infrastructure
- prefixed `sc-`
- our opinionated modular, infrastructure to build chain logic
- prefixed `frame-`
- optional modules for FRAME
- prefixed `pallet-`
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?
- We are building on it: Kusama
- You don't need build against master for the latest changes
- It's on crates.io; Semantic Versioning; release notes
Should you build on it?
Does it mean it's stable?
"Already know about potentially breaking changes" –like what?
- Long running offchain workers
- On-chain data migration paths
- Reducing the macro-magic
- Networking, consensus
is this the future yet?
let's give it a reality check
publish / read
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
Safe Data Storage
Gather.wtf is still lacks ...
what's Parity doing about it?
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
and so many more...
what will YOU make the future to be?
benjamin kampmann // gnunicorn.org
Behold the future is upon us!
By Benjamin Kampmann