Zak Cole
    • 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

      This note has no invitees

    • 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
    • Note Insights New
    • Engagement control
    • Make a copy
    • 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 Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Make a copy 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

    This note has no invitees

  • 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
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    ## **Contract Secured Revenue (CSR) SDK Technical Specification** (WIP) *TODO:* - Accounting logic (Lagrange) ✅ - User opt-in logic (EAS) - Analytics (Dune) ### **1. Introduction** The CSR SDK provides a mechanism for smart contract developers to claim a percentage of transaction fees when users interact with their contracts on EVM-based L2s. This specification outlines the architecture, components, and workflow of the SDK, integrating the Ethereum Attestation Service (EAS), Lagrange Labs' Recproofs and NFTs for payments. The architecture presented in this document does not present any changes to the consensus layer and is intended for implementation on the application layer. The architecture is designed to have identical security to a consensus layer implementation. ### **2. System Architecture** #### **2.1 Core Components** - **SequencerFeeVault**: - **Description**: [This contract](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/L2/SequencerFeeVault.sol) acts as a repository for all the fees accrued by the sequencer during transaction processing and block production. - **Attributes**: - `totalFees`: Total fees collected by the sequencer. - `pendingPayouts`: Mapping of NFT addresses to their pending payout amounts. - `gasUsedByAddress`: Mapping of contract addresses to the amount of gas they consumed. - **Methods**: - `depositFees(uint256 amount)`: Allows the sequencer to deposit fees. - `optInToCSR()`: Allows the sequencer to opt into the CSR system. - `setCSRPercentage(uint256 percentage)`: Sets the CSR percentage. Arbitrary value determined by sequencer or DAO. - `calculatePayout(address contractAddress)`: Calculates the payout for a specific contract based on its gas consumption. - `distributeFees(Proof memory proof, uint256 amount)`: Distributes the fees to the NFT holders. - `withdrawFees(address nftAddress, Proof memory proof, uint256 amount)`: Allows NFT holders to withdraw their share of the fees. Calls the verifyProof function within the Lagrange verification contract. - `trackGasUsage(address contractAddress, uint256 gasUsed)`: Tracks the gas used by each contract. - **CSR Manager**: - **Description**: Central component responsible for the overall management of the CSR system. - **Methods**: - `initiatePayout()`: Triggers a manual payout using the SequencerFeeVault's `distributeFees` method. - <strike>**Accounting Ledger**: - **Description**: Maintains records of transaction fees and CSR allocations. - **Methods**: - `updateFees(uint256 fee)`: Updates the total fees collected. - `getTotalFees()`: Returns the total fees collected. - `getCSRAmount()`: Returns the total CSR amount.</strike> - **EAS Interface**: - **Description**: Enables interactions with the Ethereum Attestation Service. - **Methods**: - `verifyAttestation(address user)`: Verifies a user's attestation, I guess. Idk, Steve, why don't you help out here for a change. Jfc. - **Lagrange Interface**: - **Description**: Enables verification of Lagrange Recproofs to trigger a payout. - **Methods**: - `verifyProof(address user, uint256 amount, uint256 startBlock, uint256 endBlock, Proof memory proof)`: Verifies a proof that a contract is entitled to receive a payment of `amount` based on usage between `startBlock` and `endBlock`, - **NFT Payment Distributor**: - **Description**: Manages NFTs and their associated payments. This allows for composability. NFT holder receives CSR reward. NFT can then be fractionalized or used as collateral within other systems. - **Methods**: - `issueNFT(address user)`: Issues an NFT to a user and returns the NFT address. - `getNFTBalance(address nftAddress)`: Returns the balance of an NFT. ### **3. Workflow** 1. **Opt-In via Attestation**: - Users emit an attestation via the EAS to opt into CSR. - The Attestation Verifier checks the attestation's validity. 2. **NFT Issuance**: - Verified users receive an NFT issued by the NFT Payment Distributor. 3. **Transaction Processing**: - For each transaction, the CSR Manager computes the CSR amount. - <strike>The Accounting Ledger updates its records</strike>. - The Sequencer deposits the fees into the SequencerFeeVault. 4. **Sequencer Opt-In**: - The sequencer opts into the CSR system using the `optInToCSR()` method in the SequencerFeeVault. 5. **Scheduled Payouts**: - <strike> The CSR Manager checks conditions and triggers payouts when necessary</strike>. - <strike>The SequencerFeeVault calculates the payout for each contract and distributes the CSR amount to the NFT Payment Distributor</strike>. - <strike>The NFT Payment Distributor distributes payments to NFTs</strike>. - ( **Suggested flow**) A user submits a proof to SequencerFeeVault proving that between a range of blocks they are entitled to a specific amount of fees - ( **Suggested flow**) If the proof is verified by the Lagrange Verifier contract than the NFT Payment Distributor distributes payments to NFT. ### **4. Interfaces** - **ISequencerFeeVault**: Interface for the SequencerFeeVault. - **ICSRManager**: Interface for the CSR Manager. - <strike>**IAccountingLedger**: Interface for the Accounting Ledger.</strike> - **IEASInterface**: Interface for the Ethereum Attestation Service. - **ILagrangeVerifier**: Interface for verifying Lagrange Recproofs. - **INFTPaymentDistributor**: Interface for the NFT Payment Distributor. ### **5. Considerations** - **Transparency**: Ensure on-chain transparency for all CSR-related transactions. - **Security**: Implement robust security using measures to prevent unauthorized access and changes. Fees should only be distributed based on zero-knowledge proofs of onchain activity. - **Efficiency**: Optimize for minimal overhead during transaction processing. Transaction processing can be done offchain and proven back onchain with zero-knowledge proofs. - **Flexibility**: Allow for easy updates and modifications to the CSR percentage. ### **6. Future Enhancements** - **Reporting & Analytics**: Implement tools for detailed CSR statistics and historical data.(Dune) - ( **Suggested flow**) **Trustless Computation**: Continually leverage zero-knowledge proofs for reward distribution so that application level CSR can inherit consensus level security. - <strike>**Threshold-based Payouts**: Enhance the Payout Scheduler to trigger payouts based on thresholds.</strike> - **EAS Enhancements**: Continuously integrate updates and features from the Ethereum Attestation Service. ### **7. Conclusion** The CSR SDK offers a comprehensive solution for smart contract developers to benefit from transaction fees on EVM-based L2s. By integrating the Ethereum Attestation Service, Lagrange Labs' Recproofs and utilizing NFTs for payments, the system offers a unique, transparent, and efficient mechanism for revenue distribution. The sequencer's ability to opt into the system and manage payouts directly from the SequencerFeeVault adds flexibility and control to the revenue distribution process.

    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