Feng Group
      • 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
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
      • 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
    • 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
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Write
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
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
[toc] ###### tags: `Reading sessions` # 2024 https://fc24.ifca.ai/program.html ## [Scan, Shuffle, Rescan: Two-Prover Election Audits With Untrusted Scanners](https://fc24.ifca.ai/preproceedings/188.pdf) * [LH] The paper proposes a new paradigm and protocols for risk-limiting audits where the margin of victory for the election is small. The paradigm is called "rescan audit" and is based on the idea of a "multi-prover proof". Two scanners separately scan a random sample of ballots and the scans are checked for consistency. This is combined with a smaller manual check to provide assurance on the election result. To prevent collusion between the scanners, the ballot list is shuffled. * The protocols are empirically evaluated against the conventional ballot polling audit and ballot comparison audit. For margins less than $1\%$, the rescan audits perform better in time and monetary cost, whereas the ballot comparison audit performs better for margins greater than $1\%$. * The security proof assumes that all ballots for one candidate are indistinguishable from one another, which is difficult to enforce in some settings. Additionally, the paper only covers plurality voting and not other voting methods, e.g., ranked-choice. ## [SAVER: SNARK-compatible Verifiable Encryption](https://fc24.ifca.ai/preproceedings/61.pdf) * [MD] In applications involving zero-knowledge succinct non-interactive arguments of knowledge (zk-SNARK), there is often a need to combine the proof system with encryption. For example, a user might want to encrypt their identity while proving that it satisfies a given authorized function (e.g., credit checks). A naive solution would be to extend the zk-SNARK circuit to include the encryption code. In other words, the entire encryption process becomes part of the SNARK circuit. However, this approach has practical limitations: * Circuit Size: Including complex cryptographic operations (like encryption) in the SNARK circuit increases its size significantly. * Proving Time: Larger circuits lead to impractically long proving times. * Common Reference String (CRS) Size: The CRS (used in zk-SNARKs) also becomes unwieldy due to the added encryption components * [MD] SAVER detaches encryption from the SNARK circuit. Instead of including encryption operations directly in the circuit, SAVER allows the encryptor to prove predefined properties while encrypting the message separately from the SNARK. It is also Additively-Homomorphic. SAVER allows anyone to verify arbitrary properties of encrypted messages by connecting them with the SNARK system. Even without the secret key, one can verify that the decrypted message corresponds to the given ciphertext.Both the proof and the ciphertext can be independently rerandomized, preventing the encryptor (or prover) from identifying their origin. * [MD] Representative Application: SAVER can be used in scenarios like voting systems. For instance, the Vote-SAVER ensures receipt-freeness, individual verifiability, vote verifiability, tally uniqueness, and voter anonymity ## [The Costs of Swapping on Decentralized Exchanges](https://fc24.ifca.ai/preproceedings/206.pdf) * ## [The Power of Default: Measuring the Effect of Slippage Tolerance in Decentralized Exchanges](https://fc24.ifca.ai/preproceedings/155.pdf) ## [ZeroSwap: Data-driven Optimal Market Making in Decentralized Finance](https://fc24.ifca.ai/preproceedings/40.pdf) ## [Blockchain Price vs. Quantity Controls](https://fc24.ifca.ai/preproceedings/139.pdf) * By Abdoulaye Ndiaye (NYU) [Economist] * [MN] Address demand fluctuations in blockchain in a transaction fee mechanism. * [MN] Models the blockchain designer’s choice between price control (eg. base fee) and quantity control (block size limit). * [MN] Analytical expression for the relative advantage of price controls over quantity controls under demand uncertainty and uncertain marginal costs. * [MN] Study optimal mechanisms that are resistant to complete value extraction by validators. # 2023 <https://fc23.ifca.ai/program.html> ## [Short Paper: DeFi Deception – Uncovering the prevalence of rugpulls in cryptocurrency projects](https://fc23.ifca.ai/preproceedings/76.pdf) * By Sharad Agarwal, Gilberto Atondo-Siu, Marilyne Ordekian, Alice Hutchings, Enrico Mariconti, and Marie Vasek. * The paper gives an empirical analysis of rugpulls in DeFi based on data gathered from forums. * **Exit scams**: project developers abandon the project and run away with investors' funds. * **Rugpulls** are exit scams in DeFi. ###### tags: `` `` ## [Byzantine Generals in the Permissionless Setting](https://fc23.ifca.ai/preproceedings/49.pdf) * By Andrew Lewis-Pye and Tim Roughgarden * Describe a formal framework for the analysis of both permissioned and permissionless systems * first capable of modelling all significant features of PoW and PoS protocols simultaneously, as well as other approaches like proof-of-space * Prove general impossibility results for permissionless protocols. * Facilitates the application of a rich history of proofs and techniques for permissioned systems to problems in blockchain and the study of permissionless systems. * establish a framework capable of dealing with permissionless protocols, but which is as similar as possible to the standard frameworks in distributed computing for dealing with permissioned protocols. * produce a framework which is as accessible as possible for researchers in blockchain without a strong background in security # 2020 <https://fc20.ifca.ai/program.html> ## [Decentralized Privacy-Preserving Netting Protocol on Blockchain for Payment Systems](https://link.springer.com/chapter/10.1007/978-3-030-51280-4_9) * By Shengjiao Cao, Yuan Yuan, Angelo De Caro, Karthik Nandakumar, Kaoutar Elkhiyaoui & Yanyan Hu * [MN] Proposes a decentralized netting protocol decentralized netting protocol that does not require any central party but still guarantees correctness and fairness * [MN] An enhanced privacy-preserving extension that protects the confidentiality of the payment amounts using homomorphic Pedersen commitments and zero-knowledge proofs * [BB] Short rview by BB ###### tags: `` ``

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