Skip to content

Review the code for bugs and security vulnerabilities #15

Closed

Description

@mudgen

If you find any bugs or security issues, please report them here or in a new issue.

Activity

  1. shubu258 commented on Oct 20, 2025

    @shubu258

    hey , I am a security researcher and developer would like to audit your contract . I you can assign me the issue here , i have total of 1 year of experience doing auditing and have 25 findings in my portfolio with 3 critical, 6 High, 4 Medium , 10 Low.

  2. shubu258 commented on Oct 20, 2025

    @shubu258

    I have taken a overview of your contract , i found few gas optimization and certain function which can follow best security practices . Should i make a request ?

  3. mudgen commented on Oct 20, 2025

    @mudgen
    ContributorAuthor

    Yes, make an issue or pull request or both.

  4. shubu258 commented on Oct 20, 2025

    @shubu258

    okay cool

  5. farismln commented on Oct 21, 2025

    @farismln
    Contributor

    Hi @mudgen is it intended that ERC20Facet.sol does not implement external mint function?
    where can I read more about what function that should/should not be added in ERCs Facet?

    I want to learn more about this.
    thanks

    edit: maybe because usually mint is a privileged function and Compose try to not using modifier?

  6. mudgen commented on Oct 21, 2025

    @mudgen
    ContributorAuthor

    @farismln A mint external function would require authentication which we don't have in ERC20Facet.sol.

    Remember we are making composable, reusable, onchain facets.

    So someone making a diamond would add all the external functions from the deployed ERC20Facet to their diamond. And to have external mint functionality such a user would make their own custom facet with an external mint function (which used LibERC20.sol), and they would deploy their custom facet and add its functions to their diamond.

    I certainly need to write more user documentation to show how Compose is intended to be used by users.

  7. adamgall commented on Oct 26, 2025

    @adamgall
    Collaborator

    @mudgen is there expected to be an explicit deliverable for this issue?

  8. mudgen commented on Oct 26, 2025

    @mudgen
    ContributorAuthor

    @adamgall No, so I am converting this to a discussion.

  9. locked and limited conversation to collaborators on Oct 26, 2025
  10. converted this issue into a discussion #130 on Oct 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    BugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions