hvancann
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee
    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee
  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       owned this note    owned this note      
    Published Linked with GitHub
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    # KERI MOOC [![hackmd-github-sync-badge](https://hackmd.io/nuUu5S8UQjOHXw_a53LvvA/badge)](https://hackmd.io/nuUu5S8UQjOHXw_a53LvvA) Goal is to facilitate self-education culminating in KERI knowlegde. Level: starters, novices, beginners and alike. ## Why KERI is ground-breaking technology. It has the potential to truly distribute and decentralize the anchoring of public digital identifiers and maintain verifiable attribution to their root of trust. It's mankind's path to personal digital freedom by keeping control over your digital self and still comply with rules of domains you live in. ## What The content of the Massive Online Opensource Course (MOOC) should be 1. Universal Cryptography theory 2. Universal Identifier theory 3. General Key management 4. KERI 5. Specific KERI issues: CESR, KELs, TELs, KAACE, SAID, ACDC 6. Roots of trust and Wallet software 7. Delegation and Agency 8. Revocation, (Pre)Rotation 9. DIDs 10. Governance and Credentials ## KERI solves... ![](https://hackmd.io/_uploads/SyBaKmMct.png) Source: Sam Smith 2021, [KERI.one](http://keri.one) ## What is not specifically KERI - Keeping your private keys private - Network Security, Security related to social behavior - Veracity; we need governance for this KERI solves the public secure attribution problem. ## For Who My goal is to reach out for the smart young people in third world countries who own a smart phone. I focus on personal development and learning to empower individuals. The MOOC is aimed at them. If we can seduce young people to learn the fundamentals of digital key management and true autonomic identifiers while they are learning English at the same time, we might 1. train fundamental key management skills* 2. spread KERI knowledge 4. expand KERI programming capacity Be aware that in this MOOC, that is individually focussed, we skip the more team-oriented topics, like multisig schemes, network security, verifiable credentials and governance and alike. *including keeping your priv keys private ## By Who: The creators - Content - Current team members are busy programming. We should not disturb them too much. We might call on non-programming volunteers that have advanced fudamental knowledge. - e-Learning Management System (LMS) - Moodle ## Use of English For Central Europeans a non-native proficient use of English could be satisfactory. Personally I think it is *not* a good idea to have KERI theory translated into Spanish, Mandarin, etc. KERI theory sounds like English, but it's not and we'll create even more hurdles to overcome when we translate to another foreign language. ### Native speaking Maybe a **non-native speaker is better** than native speakers from the UK, Canada or the US because native speakers in a complex technology field tend to use hard to grasp constructions? For US, Canada and UK, we might need to record a native speaker to come across more convincingly. But in that case we need to be careful that the wording is simple and understandable for laymen. ## How it's done - e-learning with vids. - Presentation skills of the creators will certainly help to bring the message across smoothly. - Incentive program - On mobile phone - offline - Asynchronous learning - practise on prototypes and test environments - Synchronous learning and participation - [AMA sessions](https://hackmd.io/nuUu5S8UQjOHXw_a53LvvA#Pre-recorded-video-play-and-text-chat) - Test and graduation / certification ### Pre-recorded video play and text chat #### AMA 1 First we play a video for first timers, and **in the meanwhile we'll be available on the chat for guidance and first answers** and after this prerecorded video with text-chat option we'll go over to interactive Q&A. #### AMA 2 Full-swing Zoom Q&A and text chat We could open up on Zoom with other interested Newbies who join in later (because they've already seen the pre-recorded stuff) for live discussion and Q&A, of course with a host that repeats questions posed in the chat and gives the person that has sent in the question the opportunity to repeat the question with voice & vid. We've tested this concept in the Netherlands and it went well. ### Example program bi-weekly So the example program could be: ``` Wednesday 4 PM CEST Pre-recorded video play and text chat Wednesday 4:30 PM CEST Zoom Q&A and text chat, **this week's topics only!** ``` ### Repetition every 8 weeks The whole series will be repeated and revised every 8 weeks. New tutors can be trained (train the teacher) and within 2 month play a role in teaching others. | Topic | Wk | Date | Pre | Post | | -------- | --- | -- |----------------| ----------------| | You get to decide | 1 | date | general knowledge of identity systems and identifiers|know three types of identifier systems and why they are important| | Practise Self Sov | 2 | date | Awareness of status of algoritmic and autonomic identifier systems | Knowledge and practise of pseudonymous self determining identifiers in social media: creation, binding and removal. | Universal IDs | 3 | date | Knows where to draw the line between administrative identifiers and self-sovereign identifiers | Fundamental knowledge about the pre-requisites and features of a truly universal identifier | |Basic cryptographical one way functions|4| date | Cryptography: hiding, encryption and decryption minimal knowledge | Hashing, Signing, Public Private keys | Hashpointers | KERI why and basics | 5 | date |Universal identifiers, basic Internet technology expertise, "https:" and certificates, decentralization in general, basic cryptographical one way functions| KERI thin layers, KERI's unique universal objective, self-certifying and self-admin identifiers, key event logs, primairy and secondary roots of trust.| | Key event logs, KERI duplicity game | 6 | date |KERI basics, basic crypography, gamification: eavesdropping, hostile behaviour, etc |Fully grasp what KERI is about and what it isn't. What KERI cares about and what not. Understand the set bounderies of KERI core and its expandable thin layering. | | KERI and DIDs | 7 | date |Knowledgeable about what KERI is, and what DIDs comprise of |Similarities, Differences, mutual positioning, combination, challenges | | Key rotation and key delegation, Consensus protocols for secondary roots of trust | 8 | date |Legal identifiers in general |Understanding of the new concepts introduced by KERI and their impact on the internet and self-sovereign public identifiers | ## Supportive resources When students find our 'KERI MOOC" in the middle of an ongoing series, then there are two options: 1. work backwards in high speed 2. wait until the next series ### Backward learning We will have more than one video of half an hour pre-recording of which the text-chat will also be recorded. And the Q&A will also be recorded. To facilitate catching up for students that want to hop on the bandwagon the latest series will be available publicly as Zoom recording. ### Further reading Every lesson will have sufficient links to Keri.one resources, but the level of abstraction should increase step by step. ### Legal setting We can only re-use or create Open Source course material, e.g. CC by SA ### Example video #### Future Internet Identity This example is a general introduction about the why of autonomic IDs and tries to put listeners to work at the end. We could also focus more specific on KERI in future recordings or even the relationship between KERI and DIDs, KERI and other algorithmic and autonomic ID systems. Henk van Cann's presentation about (the why of) autonomic identifiers called: "You control, therefore you are, and you get to decide" https://vimeo.com/552459966/2586f0e23c. It is a first-time, one-take presentation based on this article: https://medium.com/happy-blockchains/you-control-therefore-you-are-and-you-get-to-decide-2e2e615714a9. ## How Moodle expert Peter Haasdijk, working from the Netherlands thinks along with us. His first recommendations: - don't depend too heavily on the off-line capacities of the Moodle e-learning system - two VP servers needed, one for **Moodle** (e-learning), one for **BigBluebutton** ( online video conferencing ) - Forget about HSP content (too heavy) - It's going to be a flat MOOC, no java, no graphical highlights - How's the KERI specific content currently served, like video's, articles, etc. For a first set-up he needs these parameters: - # participants - # concurrent participants - content - mobile adaptive content #### Henk's prediction We're going to fail. To do continuous development and deployment in a Moodle stack and also alter content in a 24x7 available system that needs to serve mobile phones and authenticate users is doomed to fail. But let's fail fast and let's fail often. From what we learn by failure, we'll adjust the solution every MOOC cycle. ## When? As soon as possible, but it's done when it's done. #### First steps to take: 1. Select an e-LMS (Moodle is a good candidate) 2. Find experts to create the MOOC 3. Gather open source course material to reference for further reading 4. Write high abstraction level articles which have a narative flow 5. Practise presenting the content of the articles 6. Professionally record the first three half hour pre-recorded vids 7. Get the series started and see where we get

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully