Sam Richards
      • 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, Emoji Reply
      • Invitee
      • No invitee
    • Publish Note

      Publish Note

      Everyone on the web can find and read all notes of this public team.
      Once published, notes can be searched and viewed by anyone online.
      See published notes
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • 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 Sharing URL Help
Menu
Options
Versions and GitHub Sync 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, Emoji Reply
Invitee
No invitee
Publish Note

Publish Note

Everyone on the web can find and read all notes of this public team.
Once published, notes can be searched and viewed by anyone online.
See published notes
Engagement control
Commenting
Permission
Disabled Forbidden Owners Signed-in users Everyone
Enable
Permission
  • Forbidden
  • Owners
  • Signed-in users
  • Everyone
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
# MACI: 2024-04-22 ## Resources - [MACI roadmap](https://maci.pse.dev/roadmap) ## Agenda - MACI plans - Short term vs. long term - Questions for V - Thoughts on technical direction? Research ideas? - Opinion on strategic approach? ## Notes ### MACI - What's hurting adoption? - It's hard to run - Why? - Should just be running a Python program - Technical hurdles - Getting non-crypto people using it - Currently: every vote is an on-chain tx - V idea: Plasma technique - Operator. Relay message to operator. Operator publishes batches. SEnd proof that you're included in the list. As a user 1st resort: send to coordinator, 2nd resort: post directly on-chain - Adds back coordinator complexity. Requires online component (running a daemon vs. just scripts) - El gamal - https://github.com/privacy-scaling-explorations/maci/issues/796 - Risk of creating more UX friction at the cost of more privacy - User should only need to do 2 things (1 register, 2 vote, maybe 3 to check if vote was included) - Coordinator - MACI properties (current) - Correctness (snarks) - Censorship resistance (on chain) - privacy (depends on coordaintor) - collusion resistance (depends on coordinator) - Next gen - Correctness (snarks) - Censorship resistance (on chain) - privacy (now able to guarantee) - collusion resistance (depends on coordinator) - Can we ever remove this? FHE or MPC - W/ FHE, anyone could run the tallying computation. Overhead w/ FHE & SNARKS. Threshold for key generation. Threshold is final decryption. Set n of m for whatever you want. If it fails for not enough decryption, - Don't need prover in FHE. Just need verifier. From a dev standpoint, not super hard. Just an overhead question. - Talk to Auryn about his project - Can we use TEE for coordinator? - https://github.com/privacy-scaling-explorations/maci/discussions/1385 - V: def good. Are you able to run a zkSNARK prover inside TEE? If yes, that's the best you can get until FHE - Single MACI instance (for keys across instances) - challenge is more pressure on the gatekeeping / proof of personhood - Upcoming technical roadmap - See where that's going - V talking to Barry - Wants to start doing things outside PSE - Barry: Early stage work, algorithms, - V POV: excited about this for a long term. cryptographic identity, voting, reputation. See this actually happen. Starting to feel the impatience. Time to shift gears & create things that make impact - within & outside of our space. e.g. zkemail, anon aahaar, one way that'd be useful: my coins in my 4/6 multisig. Some gov't ID is one of my guardians. For that to happen, that service needs to be simple, anyone can download in 1 click. Plug in ID & get ETH address. take address & plug into Safe. Or fork safe UI & specify email address / gov ID / whatever - Barry feedback: current PSE. Setup for early stage protyping. Not as well suited for actually brings things to "next level". - Strategy needed? - Picking an expertis pool? e.g. zk for privacy vs. zk for scalability. zkevm is nerd-friendly. - Summa vs. proof of passport. Different things - e.g. Summa - idea has been out since blog post (really 10 years). what is a good outcome? we want CEX to actually use this. Current work doesn't do that. Why not? current team is lacking that skill. Or lacking - 3 buckets of use cases - Identity - TLSN - Voting - Overlap/integration w/ 0xPARC - Separate convo? - They're doing Zupass. It's amazing. Need to make sure it's an open standard in all the right ways. Making sure it feels like a natural part of the ETH ecosystem. Worry that things trend towards that. The fact that it doesn't feel signifcantly easier to use Zupass & EThereum together vs. seperately - e..g tix. ETH thing becasue you can buy on chain. But also Zupass b/c if you have an off-chain ticket you can proof it. Ideally these things work together. Can have NFT ticket & prove immediately without a server - V: would love to see attention towards real stuff out there in practice. Getting things out in use. DAO adoption. ## Action items - [ ] Sam to touch base with Auryn. He's working on FHE stuff - [ ] Check out his paper: https://docs.google.com/document/d/1N_G5BH7klvFV3vdwe4ZRuoVoFNYsVq7ZU_1BOBHxN4A/edit?usp=drivesdk - [ ] V to post about Plasma approach (off-chain voting) on ethresearch - [ ] Sam to detail thoughts on PSE roadmap/strategy. Share with V & keep in the loop

Import from clipboard

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

Sign in via SAML

or

Sign in via GitHub

Help

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

Documents

Tutorials

Book Mode Tutorial

Slide Example

Resources

Releases

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
Upgrade to Prime

  • Edit verison name
  • Delete

revision author avatar     named on  

More Less

Note content is identical to the latest version.
Compare with
    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
 

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

      Upgrade

      Pull from GitHub

       
      File from GitHub
      File from HackMD

      GitHub Link Settings

      File linked

      Linked by
      File path
      Last synced branch
      Available push count

      Upgrade

      Danger Zone

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

      Syncing

      Push failed

      Push successfully