├── .gitignore
├── CODE_OF_CONDUCT.md
├── CONTRIBUTING.md
├── LICENSE
├── README.md
├── chronological-updates.md
├── how-to-answer-a-question.md
├── how-to-ask-a-question.md
├── images
    ├── 0kage.jpeg
    ├── aderyn.png
    ├── background-image-security.png
    ├── background-updated.jpg
    ├── backgroundv3.jpg
    ├── boss-bridge.png
    ├── course-background.jpg
    ├── course-hero.jpg
    ├── course-post2.jpg
    ├── course-posts.jpg
    ├── curriculum.png
    ├── gas-bad.png
    ├── horse-store.png
    ├── math-master.png
    ├── mev-thumbnail.png
    ├── password-store-logo.png
    ├── puppy-png.png
    ├── puppy-raffle.svg
    ├── red-guild-png.png
    ├── t-swap-youtube-dimensions.png
    ├── the-red-guild.jpeg
    ├── thunder-loan.svg
    ├── tincho-is-a-monster.png
    ├── tincho.jpeg
    ├── top-10-attack-vectors.png
    ├── top-attack-vectors-updated.png
    ├── updraft-landing-p.png
    ├── vault-guardians-logo.png
    └── vault-guardians.png
└── improvement_points.md


/.gitignore:
--------------------------------------------------------------------------------
 1 | .env
 2 | .DS_Store
 3 | 
 4 | 3-*
 5 | 4-*
 6 | 5-*
 7 | 6-*
 8 | 7-*
 9 | 8-*
10 | 9-*
11 | 10-*
12 | 11-*
13 | 12-*
14 | 13-*
15 | 14-*
16 | 15-*
17 | 
18 | images/
19 | zksync-challenge-nfts/
20 | zksync-challenge-nfts-hardhat/
21 | 
22 | sc-exploits-minimized/
23 | challenge-nfts/
24 | 
25 | .notes.md 
26 | 
27 | .cringe/
28 | cringe/
29 | nfts/


--------------------------------------------------------------------------------
/CODE_OF_CONDUCT.md:
--------------------------------------------------------------------------------
  1 | # Contributor Covenant Code of Conduct
  2 | 
  3 | ## Our Pledge
  4 | 
  5 | We as members, contributors, and leaders pledge to make participation in our
  6 | community a harassment-free experience for everyone, regardless of age, body
  7 | size, visible or invisible disability, ethnicity, sex characteristics, gender
  8 | identity and expression, level of experience, education, socio-economic status,
  9 | nationality, personal appearance, race, religion, or sexual identity
 10 | and orientation.
 11 | 
 12 | We pledge to act and interact in ways that contribute to an open, welcoming,
 13 | diverse, inclusive, and healthy community.
 14 | 
 15 | ## Our Standards
 16 | 
 17 | Examples of behavior that contributes to a positive environment for our
 18 | community include:
 19 | 
 20 | * Demonstrating empathy and kindness toward other people
 21 | * Being respectful of differing opinions, viewpoints, and experiences
 22 | * Giving and gracefully accepting constructive feedback
 23 | * Accepting responsibility and apologizing to those affected by our mistakes,
 24 |   and learning from the experience
 25 | * Focusing on what is best not just for us as individuals, but for the
 26 |   overall community
 27 | 
 28 | Examples of unacceptable behavior include:
 29 | 
 30 | * The use of sexualized language or imagery, and sexual attention or
 31 |   advances of any kind
 32 | * Trolling, insulting or derogatory comments, and personal or political attacks
 33 | * Public or private harassment
 34 | * Publishing others' private information, such as a physical or email
 35 |   address, without their explicit permission
 36 | * Other conduct which could reasonably be considered inappropriate in a
 37 |   professional setting
 38 | 
 39 | ## Enforcement Responsibilities
 40 | 
 41 | Community leaders are responsible for clarifying and enforcing our standards of
 42 | acceptable behavior and will take appropriate and fair corrective action in
 43 | response to any behavior that they deem inappropriate, threatening, offensive,
 44 | or harmful.
 45 | 
 46 | Community leaders have the right and responsibility to remove, edit, or reject
 47 | comments, commits, code, wiki edits, issues, and other contributions that are
 48 | not aligned to this Code of Conduct, and will communicate reasons for moderation
 49 | decisions when appropriate.
 50 | 
 51 | ## Scope
 52 | 
 53 | This Code of Conduct applies within all community spaces, and also applies when
 54 | an individual is officially representing the community in public spaces.
 55 | Examples of representing our community include using an official e-mail address,
 56 | posting via an official social media account, or acting as an appointed
 57 | representative at an online or offline event.
 58 | 
 59 | ## Enforcement
 60 | 
 61 | Instances of abusive, harassing, or otherwise unacceptable behavior may be
 62 | reported to the community leaders responsible for enforcement at
 63 | .
 64 | All complaints will be reviewed and investigated promptly and fairly.
 65 | 
 66 | All community leaders are obligated to respect the privacy and security of the
 67 | reporter of any incident.
 68 | 
 69 | ## Enforcement Guidelines
 70 | 
 71 | Community leaders will follow these Community Impact Guidelines in determining
 72 | the consequences for any action they deem in violation of this Code of Conduct:
 73 | 
 74 | ### 1. Correction
 75 | 
 76 | **Community Impact**: Use of inappropriate language or other behavior deemed
 77 | unprofessional or unwelcome in the community.
 78 | 
 79 | **Consequence**: A private, written warning from community leaders, providing
 80 | clarity around the nature of the violation and an explanation of why the
 81 | behavior was inappropriate. A public apology may be requested.
 82 | 
 83 | ### 2. Warning
 84 | 
 85 | **Community Impact**: A violation through a single incident or series
 86 | of actions.
 87 | 
 88 | **Consequence**: A warning with consequences for continued behavior. No
 89 | interaction with the people involved, including unsolicited interaction with
 90 | those enforcing the Code of Conduct, for a specified period of time. This
 91 | includes avoiding interactions in community spaces as well as external channels
 92 | like social media. Violating these terms may lead to a temporary or
 93 | permanent ban.
 94 | 
 95 | ### 3. Temporary Ban
 96 | 
 97 | **Community Impact**: A serious violation of community standards, including
 98 | sustained inappropriate behavior.
 99 | 
100 | **Consequence**: A temporary ban from any sort of interaction or public
101 | communication with the community for a specified period of time. No public or
102 | private interaction with the people involved, including unsolicited interaction
103 | with those enforcing the Code of Conduct, is allowed during this period.
104 | Violating these terms may lead to a permanent ban.
105 | 
106 | ### 4. Permanent Ban
107 | 
108 | **Community Impact**: Demonstrating a pattern of violation of community
109 | standards, including sustained inappropriate behavior,  harassment of an
110 | individual, or aggression toward or disparagement of classes of individuals.
111 | 
112 | **Consequence**: A permanent ban from any sort of public interaction within
113 | the community.
114 | 
115 | ## Attribution
116 | 
117 | This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118 | version 2.0, available at
119 | https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
120 | 
121 | Community Impact Guidelines were inspired by [Mozilla's code of conduct
122 | enforcement ladder](https://github.com/mozilla/diversity).
123 | 
124 | [homepage]: https://www.contributor-covenant.org
125 | 
126 | For answers to common questions about this code of conduct, see the FAQ at
127 | https://www.contributor-covenant.org/faq. Translations are available at
128 | https://www.contributor-covenant.org/translations.


--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
 1 | # How do I make a contribution?
 2 | 
 3 | Never made an open-source contribution before? Wondering how contributions work in this project? Here's a quick run-down!
 4 | 
 5 | - Find an issue that you want to address or a feature that you want to add.
 6 | 
 7 | - Fork the repository associated with the issue to your local GitHub organization. This means that you will have a copy of the repository under `your-GitHub-username/repository-name`.
 8 | 
 9 | - Clone the forked repository to your local machine using `git clone https://github.com/github-username/repository-name.git`. E.g. for a repo named "xyzRepo", the user can run https://github.com/github-username/xyzRepo.git.
10 | 
11 | - Create a new branch for your fix using `git checkout -b branch-name-here`. E.g `git checkout -b main`
12 | 
13 | - Make the appropriate changes for the issue you are trying to address or the feature that you want to add.
14 | 
15 | - Use `git add insert-paths-of-changed-files-here` to add the file contents of the changed files to the "snapshot" git uses to manage the state of the project, also known as the index.
16 | 
17 | - Use `git commit -m "Insert a short message of the changes made here"` to store the contents of the index with a descriptive message.
18 | 
19 | - Push the changes to the remote repository using `git push origin branch-name-here`.
20 | 
21 | - Submit a pull request to the upstream repository.
22 | 
23 | - Title the pull request with a short description of the changes made and the issue or bug number associated with your change. For example, you can title an issue like so **"Added more log outputting to resolve #4352"**.
24 | 
25 | - In the description of the pull request, explain the changes that you made, any issues you think exist with the pull request you made, and any questions you have for the maintainer. It's OK if your pull request is not perfect (no pull request is), the reviewer will be able to help you fix any problems and improve it!
26 | 
27 | - Wait for the pull request to be reviewed by a maintainer.
28 | 
29 | - Make changes to the pull request if the reviewing maintainer recommends them.
30 | 
31 | - Celebrate your success after your pull request is merged!
32 | 
33 | # Where can I go for help?
34 | 
35 | If you need help, you can ask questions on our **discussions** tab.


--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
  1 | GNU GENERAL PUBLIC LICENSE
  2 | Version 3, 29 June 2007
  3 | 
  4 | Copyright © 2007 Free Software Foundation, Inc. <https://fsf.org/>
  5 | 
  6 | Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
  7 | 
  8 | Preamble
  9 | The GNU General Public License is a free, copyleft license for software and other kinds of works.
 10 | 
 11 | The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply it to your programs, too.
 12 | 
 13 | When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things.
 14 | 
 15 | To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others.
 16 | 
 17 | For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.
 18 | 
 19 | Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it.
 20 | 
 21 | For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and authors' sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions.
 22 | 
 23 | Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users' freedom to change the software. The systematic pattern of such abuse occurs in the area of products for individuals to use, which is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice for those products. If such problems arise substantially in other domains, we stand ready to extend this provision to those domains in future versions of the GPL, as needed to protect the freedom of users.
 24 | 
 25 | Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures that patents cannot be used to render the program non-free.
 26 | 
 27 | The precise terms and conditions for copying, distribution and modification follow.
 28 | 
 29 | TERMS AND CONDITIONS
 30 | 0. Definitions.
 31 | “This License” refers to version 3 of the GNU General Public License.
 32 | 
 33 | “Copyright” also means copyright-like laws that apply to other kinds of works, such as semiconductor masks.
 34 | 
 35 | “The Program” refers to any copyrightable work licensed under this License. Each licensee is addressed as “you”. “Licensees” and “recipients” may be individuals or organizations.
 36 | 
 37 | To “modify” a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a “modified version” of the earlier work or a work “based on” the earlier work.
 38 | 
 39 | A “covered work” means either the unmodified Program or a work based on the Program.
 40 | 
 41 | To “propagate” a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well.
 42 | 
 43 | To “convey” a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.
 44 | 
 45 | An interactive user interface displays “Appropriate Legal Notices” to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion.
 46 | 
 47 | 1. Source Code.
 48 | The “source code” for a work means the preferred form of the work for making modifications to it. “Object code” means any non-source form of a work.
 49 | 
 50 | A “Standard Interface” means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language.
 51 | 
 52 | The “System Libraries” of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A “Major Component”, in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it.
 53 | 
 54 | The “Corresponding Source” for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work.
 55 | 
 56 | The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source.
 57 | 
 58 | The Corresponding Source for a work in source code form is that same work.
 59 | 
 60 | 2. Basic Permissions.
 61 | All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law.
 62 | 
 63 | You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you.
 64 | 
 65 | Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary.
 66 | 
 67 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
 68 | No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures.
 69 | 
 70 | When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures.
 71 | 
 72 | 4. Conveying Verbatim Copies.
 73 | You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program.
 74 | 
 75 | You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee.
 76 | 
 77 | 5. Conveying Modified Source Versions.
 78 | You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:
 79 | 
 80 | a) The work must carry prominent notices stating that you modified it, and giving a relevant date.
 81 | b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to “keep intact all notices”.
 82 | c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it.
 83 | d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so.
 84 | A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an “aggregate” if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.
 85 | 
 86 | 6. Conveying Non-Source Forms.
 87 | You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:
 88 | 
 89 | a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange.
 90 | b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge.
 91 | c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b.
 92 | d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements.
 93 | e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d.
 94 | A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work.
 95 | 
 96 | A “User Product” is either (1) a “consumer product”, which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, “normally used” refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product.
 97 | 
 98 | “Installation Information” for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.
 99 | 
100 | If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).
101 | 
102 | The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network.
103 | 
104 | Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying.
105 | 
106 | 7. Additional Terms.
107 | “Additional permissions” are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions.
108 | 
109 | When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission.
110 | 
111 | Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:
112 | 
113 | a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or
114 | b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or
115 | c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or
116 | d) Limiting the use for publicity purposes of names of licensors or authors of the material; or
117 | e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or
118 | f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors.
119 | All other non-permissive additional terms are considered “further restrictions” within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.
120 | 
121 | If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms.
122 | 
123 | Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way.
124 | 
125 | 8. Termination.
126 | You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11).
127 | 
128 | However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.
129 | 
130 | Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.
131 | 
132 | Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10.
133 | 
134 | 9. Acceptance Not Required for Having Copies.
135 | You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.
136 | 
137 | 10. Automatic Licensing of Downstream Recipients.
138 | Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License.
139 | 
140 | An “entity transaction” is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts.
141 | 
142 | You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.
143 | 
144 | 11. Patents.
145 | A “contributor” is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's “contributor version”.
146 | 
147 | A contributor's “essential patent claims” are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, “control” includes the right to grant patent sublicenses in a manner consistent with the requirements of this License.
148 | 
149 | Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version.
150 | 
151 | In the following three paragraphs, a “patent license” is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To “grant” such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party.
152 | 
153 | If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. “Knowingly relying” means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid.
154 | 
155 | If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it.
156 | 
157 | A patent license is “discriminatory” if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007.
158 | 
159 | Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law.
160 | 
161 | 12. No Surrender of Others' Freedom.
162 | If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program.
163 | 
164 | 13. Use with the GNU Affero General Public License.
165 | Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such.
166 | 
167 | 14. Revised Versions of this License.
168 | The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
169 | 
170 | Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License “or any later version” applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation.
171 | 
172 | If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program.
173 | 
174 | Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version.
175 | 
176 | 15. Disclaimer of Warranty.
177 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
178 | 
179 | 16. Limitation of Liability.
180 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
181 | 
182 | 17. Interpretation of Sections 15 and 16.
183 | If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.
184 | 
185 | END OF TERMS AND CONDITIONS
186 | 
187 | How to Apply These Terms to Your New Programs
188 | If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.
189 | 
190 | To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the “copyright” line and a pointer to where the full notice is found.
191 | 
192 |     <one line to give the program's name and a brief idea of what it does.>
193 |     Copyright (C) <year>  <name of author>
194 | 
195 |     This program is free software: you can redistribute it and/or modify
196 |     it under the terms of the GNU General Public License as published by
197 |     the Free Software Foundation, either version 3 of the License, or
198 |     (at your option) any later version.
199 | 
200 |     This program is distributed in the hope that it will be useful,
201 |     but WITHOUT ANY WARRANTY; without even the implied warranty of
202 |     MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
203 |     GNU General Public License for more details.
204 | 
205 |     You should have received a copy of the GNU General Public License
206 |     along with this program.  If not, see <https://www.gnu.org/licenses/>.
207 | Also add information on how to contact you by electronic and paper mail.
208 | 
209 | If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode:
210 | 
211 |     Security & Auditing Course  Copyright (C) 2023 Cyfrin 
212 |     This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
213 |     This is free software, and you are welcome to redistribute it
214 |     under certain conditions; type `show c' for details.
215 | The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an “about box”.
216 | 
217 | You should also get your employer (if you work as a programmer) or school, if any, to sign a “copyright disclaimer” for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see <https://www.gnu.org/licenses/>.
218 | 
219 | The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read <https://www.gnu.org/licenses/why-not-lgpl.html>.


--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
  1 | # Assembly, EVM Opcodes, and Formal Verification
  2 | 
  3 | Welcome to the repository for the Assembly, EVM Opcodes, and Formal Verification Course by Cyfrin Updraft!
  4 | 
  5 | This repository houses the written content of our courses, organized to facilitate easy access and contribution from our community.
  6 | Please refer to this for an in-depth explanation of the content:
  7 | 
  8 | -   [Website](https://updraft.cyfrin.io/) - Join Cyfrin Updraft and enjoy 50+ hours of smart contract development courses
  9 | -   [Twitter](https://twitter.com/cyfrinupdraft) - Stay updated with the latest course releases
 10 | -   [LinkedIn](https://www.linkedin.com/school/cyfrin-updraft/) - Add Updraft to your learning experiences
 11 | -   [Discord](http://discord.gg/cyfrin) - Join a community of 3000+ developers and auditors
 12 | -   [Newsletter](https://www.cyfrin.io/newsletter) - Weekly security research tips and resources to level up your career
 13 | -   [Codehawks](https://www.codehawks.com/) - Smart contracts auditing competitions to help securing web3
 14 | 
 15 | 
 16 | This was considered part 2 of the [security and auditing course](https://updraft.cyfrin.io/courses/security), but now, it's it's own living breathing course!
 17 | 
 18 | # Table of Contents
 19 | - [Assembly, EVM Opcodes, and Formal Verification](#assembly-evm-opcodes-and-formal-verification)
 20 | - [Table of Contents](#table-of-contents)
 21 | - [Introduction, Resources, and Prerequisites](#introduction-resources-and-prerequisites)
 22 |   - [Link to video: *Coming soon...*](#link-to-video-coming-soon)
 23 |   - [Resources For This Course](#resources-for-this-course)
 24 |     - [Challenge Contracts Registry](#challenge-contracts-registry)
 25 |   - [Prerequisites](#prerequisites)
 26 |     - [Tools](#tools)
 27 |   - [Outcomes](#outcomes)
 28 | - [Curriculum](#curriculum)
 29 | - [Section 0: Welcome](#section-0-welcome)
 30 |   - [Why EVM, Opcodes, and Formal Verification?](#why-evm-opcodes-and-formal-verification)
 31 |   - [Best Practices](#best-practices)
 32 |     - [Section 0 NFT](#section-0-nft)
 33 | - [Section 1: EVM Assembly, Opcodes, Yul, \& Huff | Horse Store](#section-1-evm-assembly-opcodes-yul--huff--horse-store)
 34 |     - [Section 1 NFT](#section-1-nft)
 35 | - [Section 2: Introduction to Formal Verification \& Symbolic Execution | Math Master](#section-2-introduction-to-formal-verification--symbolic-execution--math-master)
 36 |     - [Certora Signup](#certora-signup)
 37 |   - [Symbolic Execution / Formal Verification Tools in Web3](#symbolic-execution--formal-verification-tools-in-web3)
 38 |   - [Certora](#certora)
 39 |   - [Issues](#issues)
 40 |     - [Section 2 NFT](#section-2-nft)
 41 | - [Section 3: Advanced Formal Verification | Gas Bad NFT Marketplace](#section-3-advanced-formal-verification--gas-bad-nft-marketplace)
 42 |   - [Certora](#certora-1)
 43 |     - [Section 3 NFT](#section-3-nft)
 44 | - [Congratulations](#congratulations)
 45 |   - [Where do I go now?](#where-do-i-go-now)
 46 |   - [Learning More](#learning-more)
 47 |   - [Disclosures](#disclosures)
 48 | - [Thank you](#thank-you)
 49 |   - [Sponsors](#sponsors)
 50 |   - [Lead Lecturers / Code Builders](#lead-lecturers--code-builders)
 51 |   - [Guest Lecturers](#guest-lecturers)
 52 |   - [Special thanks](#special-thanks)
 53 |   - [Huge Extra Thank YOU](#huge-extra-thank-you)
 54 | 
 55 | # Introduction, Resources, and Prerequisites
 56 | 
 57 | ## Link to video: *Coming soon...*
 58 | 
 59 | > ⚠️ All code associated with this course is for demo purposes only. They have been audited, but we do not recommend them for production use and should be used at your own risk. 
 60 | 
 61 | ## Resources For This Course
 62 | 
 63 | Join [Cyfrin Updraft](https://updraft.cyfrin.io/) for the best learning experience!
 64 | 
 65 | - AI Frens
 66 |   - [ChatGPT](https://chat.openai.com/)
 67 |       - Just know that it will often get things wrong, but it's very fast!
 68 |   - [Phind](https://www.phind.com/)
 69 |       - Like ChatGPT, but it searches the web
 70 |   - [Bard](https://bard.google.com/)
 71 |   - [Other AI extensions](https://twitter.com/aisolopreneur/status/1654823630155464704?s=42&t=-pu_sCYtfrfPJU7OXfifrQ)
 72 | - Github Discussions 
 73 |     -   Ask questions and chat about the course here!
 74 | -   [Stack Exchange Ethereum](https://ethereum.stackexchange.com/)
 75 |     -   Great place for asking technical questions about Ethereum
 76 | -   [Peeranha](https://peeranha.io/)
 77 |     -   Decentralized Stack Exchange! 
 78 | 
 79 | ### Challenge Contracts Registry
 80 | 
 81 | - [Challenge Contracts (Arbitrum)](https://arbiscan.io/address/0xDe0e797bfAd78F0615d75430C53F8fe3C9e49883#code)
 82 | - [Challenge Contracts (Sepolia)](https://sepolia.etherscan.io/address/0x31801c3e09708549c1b2c9e1cfbf001399a1b9fa#code)
 83 | - It's just numbers 11 -> 13
 84 |   - The rest are from the [security and auditing](https://updraft.cyfrin.io/courses/security) or the [Web3 DevOps](https://updraft.cyfrin.io/courses/wallet-and-deployment) course. 
 85 | 
 86 | ## Prerequisites
 87 | An intermediate understanding of solidity. You don't need to be a pro, but you should be familiar with:
 88 | 
 89 | - [Security & Auditing Course](https://updraft.cyfrin.io/courses/security)
 90 | - [Basic Understanding of bits, bytes, and binary](https://www.youtube.com/watch?v=zDNaUi2cjv4)
 91 | 
 92 | ### Tools
 93 | 
 94 | We assume you have a solid grasp of the following tools for this course.
 95 | - Foundry
 96 | - Solidity
 97 | - VSCode/Text Editor
 98 | - Basic Linux/Unix/Bash terminal commands
 99 | - Git & GitHub
100 | - WSL (if you're on windows)
101 |   - https://youtu.be/C3U0_LKw970
102 | 
103 | Note: You can get through this course with just having an advanced grasp of solidity & foundry. However, having at least a shallow understanding of security and low-level EVM will make this course much easier to grasp. And you doing the security coruse will make you a better EVM developer!
104 | 
105 | 
106 | 
107 | ## Outcomes
108 | * Be able to decompile a smart contract right from the raw bytecode
109 | * Be able to understand exactly how EVM opcodes work so you can write more gas-efficient code
110 | * Learn the Huff smart contract programming language
111 | * Be able to write formal verification in Halmos & Certora
112 | * Be able to understand the difference between Fuzzing & Formal Verification
113 | * Have an intermediate understanding of how to write Formal Verification tests for solidity 
114 | 
115 | # Curriculum
116 | 
117 | # Section 0: Welcome
118 | 
119 | ## Why EVM, Opcodes, and Formal Verification?
120 | 
121 | ## Best Practices 
122 |   - TODO: Add link to "how to ask a question" and "how to answer a question" and "how to work with AI"
123 |   - Register for [Cyfrin Updraft](https://updraft.cyfrin.io/)
124 |     - USE THIS SITE!!! It's specfically made to make learning easier
125 |   - **Follow the repository:** While going through the course be 100% certain to follow along with the github repository. If you run into in an issue check the chronological-updates in the repo.
126 |   - **Be Active in the community:** Ask questions and engage with other developers going through the course in the discussions tab, be sure to go and say hello or gm! This space is different from the other industries, you don't have to be secretive; communicate, network and learn with others :)
127 |   - **Learn at your own pace:** It doesn't matter if it takes you a day, a week, a month or even a year. Progress >>> Perfection
128 |   - **Take Breaks:** You will exhaust your mind and recall less if you go all out and watch the entire course in one sitting. 
129 |     **Suggested Strategy** every 25 minutes take a 5 min break, and every 2 hours take a longer 30 min break
130 |   - **Refer to Documentation:** Things are constantly being updated, so whenever Patrick opens up some documentation, open it your end and maybe even have the code sample next to you.
131 |   - **Use ChatGPT and/or the course chat**
132 | 
133 | 🎯🎯🎯🎯🎯🎯🎯🎯🎯🎯🎯🎯🎯🎯🎯🎯🎯🎯🎯🎯🎯🎯🎯
134 | 
135 | 🎯 Exercise: Write *yourself* a message about why you want this
136 |   - This will be important for when things get hard
137 |   - Is it money? Save web3? Become someone? Write down as many reasons as possible. 
138 | 
139 | ### Section 0 NFT
140 | - *No section 0 challenge NFT for this one!*
141 | 
142 | 🎯🎯🎯🎯🎯🎯🎯🎯🎯🎯🎯🎯🎯🎯🎯🎯🎯🎯🎯🎯🎯🎯🎯
143 | <p align="right">(<a href="#table-of-contents">back to top</a>) ⬆️</p>
144 | 
145 | # Section 1: EVM Assembly, Opcodes, Yul, & Huff | Horse Store
146 | 
147 | <br/>
148 | <p align="center">
149 | <a href="https://updraft.cyfrin.io/" target="_blank">
150 | <img src="./images/horse-store.png" width="300" alt="Smart Contract Audit & Security Review, Horse Store">
151 | </a>
152 | </p>
153 | <br/>
154 | 
155 | 🧑🏾‍💻 [Horse Store Code](https://github.com/Cyfrin/1-horse-store-s23): https://github.com/Cyfrin/1-horse-store-s23
156 | 
157 | 
158 | <table border="1" style="border-collapse: collapse;">
159 |   <thead>
160 |         <tr>
161 |             <th>Horse StoreV1 (Solidity)</th>
162 |             <th>Horse StoreV2 (Solidity)</th>
163 |         </tr>
164 |     </thead>
165 |     <tbody>
166 |       <tr>
167 |       <td>
168 |       <a href="https://remix.ethereum.org/#url=https://github.com/Cyfrin/1-horse-store-s23/blob/main/src/horseStoreV1/HorseStore.sol&lang=en&optimize=false&runs=200&evmVersion=null&version=soljson-v0.8.20+commit.a1b79de6.js" target="_blank" style="display: inline-block; padding: 10px 15px; font-size: 16px; cursor: pointer; text-align: center; text-decoration: none; outline: none; color: #fff; background-color: #4CAF50; border: none; border-radius: 15px; box-shadow: 0 5px #999;" target="_blank">View in Remix</a>
169 |       </td>
170 |       <td>
171 |       <a href="https://remix.ethereum.org/#url=https://github.com/Cyfrin/1-horse-store-s23/blob/main/src/horseStoreV2/HorseStore.sol&lang=en&optimize=false&runs=200&evmVersion=null&version=soljson-v0.8.20+commit.a1b79de6.js" target="_blank" style="display: inline-block; padding: 10px 15px; font-size: 16px; cursor: pointer; text-align: center; text-decoration: none; outline: none; color: #fff; background-color: #4CAF50; border: none; border-radius: 15px; box-shadow: 0 5px #999;" target="_blank">View in Remix</a>
172 |       </td>
173 |       </tr>
174 |     </tbody>
175 | </table>
176 | 
177 | - [Huff Documentation](https://docs.huff.sh/)
178 | - [EVM Opcodes](https://evm.codes/)
179 | - [View of Places the EVM can hold info](https://x.com/pcaversaccio/status/1651926715931738112?s=20)
180 | - [OpenZeppelin Deconstructing a Solidity Contract](https://blog.openzeppelin.com/deconstructing-a-solidity-smart-contract-part-i-introduction-832efd2d7737)
181 | - [HEVM](https://github.com/ethereum/hevm)
182 | - Foundry libraries
183 |     - [foundry-huff](https://github.com/huff-language/foundry-huff)
184 |     - [huff-runner](https://github.com/whitenois3/huff-runner)
185 | - Introduction to Yul
186 |     - Security considerations (compiler doesn’t keep you safe anymore!)
187 | - Introduction to Huff
188 |     - [huff docs](https://huff.sh/)
189 | - Forge debugger
190 | - Tenderly Debugger
191 | - Decompilers
192 |     - [Dedaub](https://library.dedaub.com/ethereum/address/0x6b175474e89094c44da98b954eedeac495271d0f/decompiled)
193 |     - [Heimdall](https://github.com/Jon-Becker/heimdall-rs)
194 | - [Metadock](https://blocksec.com/metadock)
195 | 
196 | 🐴🐴🐴🐴🐴🐴🐴🐴🐴🐴🐴🐴🐴🐴🐴🐴🐴🐴🐴🐴🐴🐴🐴🐴🐴🐴
197 | 
198 | 🐴 Exercises: 
199 | 
200 | 1. Convert a minimal contract of your own into Huff or Yul
201 | 
202 | ### Section 1 NFT
203 | - [Good luck (Arbitrum)](https://arbiscan.io/address/0xFCA3dAeF78be6a9443Af48195Fb882d881b02644#code)
204 | - [Good luck (Sepolia)](https://sepolia.etherscan.io/address/0x444aE92325dCE5D14d40c30d2657547513674dD6)
205 | 
206 | 🐴🐴🐴🐴🐴🐴🐴🐴🐴🐴🐴🐴🐴🐴🐴🐴🐴🐴🐴🐴🐴🐴🐴🐴🐴🐴
207 | <p align="right">(<a href="#table-of-contents">back to top</a>) ⬆️</p>
208 | 
209 | 
210 | # Section 2: Introduction to Formal Verification & Symbolic Execution | Math Master
211 | 
212 | <br/>
213 | <p align="center">
214 | <a href="https://updraft.cyfrin.io/" target="_blank">
215 | <img src="./images/math-master.png" width="300" alt="Smart Contract Audit & Security Review, Math Master">
216 | </a>
217 | </p>
218 | <br/>
219 | 
220 | 🧑🏾‍💻 Code: [https://github.com/Cyfrin/2-math-master-audit](https://github.com/Cyfrin/2-math-master-audit)
221 | 
222 | - [What is WAD?](https://ethereum.stackexchange.com/questions/27101/what-does-wadstand-for)
223 | - [Introduction to FV & SE](https://www.youtube.com/watch?v=izpoxfTSaFs) 
224 |   - [Article](https://medium.com/@patrickalphac/formal-verification-symbolic-execution-38e0ac9072eb)
225 |   - [Troy Interview](https://www.youtube.com/watch?v=H52U4ibkf5Q)
226 |   - [Josselin Interview](https://www.youtube.com/watch?v=3pWYvtx_sjA)
227 | - [How to quit concrete testing with FV](https://hackmd.io/@SaferMaker/EVM-Sym-Test)
228 | - [sc-exploits-minimized](https://github.com/Cyfrin/sc-exploits-minimized/tree/main)
229 | - Z3 Solution with AI 
230 | - Solidity SMT Checker 
231 | - [Halmos](https://github.com/a16z/halmos)
232 | - [Case Study: PRBMath](https://twitter.com/zachobront/status/1679540903030013952)
233 | 
234 | ### Certora Signup
235 | *click me* :)
236 | - [Certora Signup](https://www.certora.com/signup?plan=prover&utm=updraft)
237 | - [What is Formal Verification (from Mooly)](https://www.youtube.com/watch?v=VGSsPIsbb6U)
238 | - [Install Certora](https://docs.certora.com/en/latest/docs/user-guide/getting-started/install.html)
239 | 
240 | ## Symbolic Execution / Formal Verification Tools in Web3
241 | - [Halmos](https://github.com/a16z/halmos)
242 | - [Certora](https://www.certora.com/)
243 | - [Manticore](https://github.com/trailofbits/manticore)
244 | - [Mythril](https://github.com/ConsenSys/mythril)
245 | - [hevm](https://github.com/ethereum/hevm)
246 | - [Kontrol](https://docs.runtimeverification.com/kontrol/overview/readme)
247 | - [ETH BMC](https://github.com/baolean/EthBMC/tree/forge)
248 | - [Comparison](https://hackmd.io/@SaferMaker/EVM-Sym-Exec)
249 | - [FV specifically for ERC20s](https://ercx.runtimeverification.com/)
250 | 
251 | ## Certora 
252 | - Rules 
253 | - Harnessing 
254 | - Methods Block 
255 | - Config Files / Scene
256 | - Linking
257 | - Invariants
258 | - Prover Args
259 | 
260 | ## Issues
261 | - Path Explosion
262 | - [Halting Problem](https://en.wikipedia.org/wiki/Halting_problem)
263 | 
264 | 🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮
265 | 
266 | 🧮 Exercises: 
267 | 
268 | 1. Attempt to use another FV tool
269 | 2. Look into the [Solady LibClone.sol](https://github.com/Vectorized/solady/blob/main/src/utils/LibClone.sol)
270 |    1. It's a really cool codebase
271 | 3. [Watch this awesome video](https://www.youtube.com/watch?v=Wm3t8Fuiy1E) 🎥
272 | 4. [Audit this!](https://github.com/Cyfrin/2023-07-foundry-defi-stablecoin) 🪙
273 | 
274 | ### Section 2 NFT
275 | - [I accidentally verified the helper contract so this one is a bit easier (Arbitrum)](https://arbiscan.io/address/0x8983dc5E9bC4Be1E2C7FE241637D8E6b999755b1#code)
276 | - [Since I verified the arbitrum one, I also verified the sepolia one](https://sepolia.etherscan.io/address/0x3DbBF2F9AcFB9Aac8E0b31563dd75a2D69148D64)
277 | 
278 | 🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮
279 | 
280 | <p align="right">(<a href="#table-of-contents">back to top</a>) ⬆️</p>
281 | 
282 | 
283 | # Section 3: Advanced Formal Verification | Gas Bad NFT Marketplace
284 | 
285 | <br/>
286 | <p align="center">
287 | <a href="https://updraft.cyfrin.io/" target="_blank">
288 | <img src="./images/gas-bad.png" width="300" alt="Smart Contract Audit & Security, Gas Bad">
289 | </a>
290 | </p>
291 | <br/>
292 | 
293 | 🧑🏾‍💻 Code: [https://github.com/Cyfrin/3-gas-bad-nft-marketplace-audit](https://github.com/Cyfrin/3-gas-bad-nft-marketplace-audit)
294 | 
295 | ## Certora 
296 | - Parametric rules
297 | - Ghosts
298 | - Hooks
299 | - Dispatching & Summaries
300 | - Sanity 
301 | 
302 | 🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮
303 | 
304 | 🧮 Exercises: 
305 | 
306 | 1. Compete in a formal verification contest!
307 | 
308 | ### Section 3 NFT
309 | - [I can't stop you anymore (Arbitrum)](https://arbiscan.io/address/0x349364769030dAB260eF2771610C4860EE367202#code)
310 | - [I can't stop you (Sepolia)](https://sepolia.etherscan.io/address/0x7D4a746Cb398e5aE19f6cBDC08473664ADBc6da5)
311 | 
312 | 🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮🧮
313 | 
314 | <p align="right">(<a href="#table-of-contents">back to top</a>) ⬆️</p>
315 | 
316 | # Congratulations
317 | 
318 | 🎊🎊🎊🎊🎊🎊🎊🎊🎊🎊🎊🎊 Completed The Course! 🎊🎊🎊🎊🎊🎊🎊🎊🎊🎊🎊🎊 
319 | 
320 | ## Where do I go now?
321 | 
322 | _Coming soon: The EVM, Assembly, and Formal Verification Course!!_
323 | 
324 | - Competititve Audits
325 |   - [CodeHawks](https://codehawks.com)
326 |     - We are working on many things to get you more deals. Stay tuned...
327 |   - [Code4rena](https://code4rena.com/)
328 |   - [Hats Finance](https://hats.finance/)
329 | - [CodeHawks Discord](https://discord.gg/cyfrin)
330 | - Start marketing your services
331 |   - Twitter, Farcaster, LinkedIn, etc
332 |   - Blogging: Medium, Mirror, etc
333 | - Bug Bounties
334 |   - [Immunefi](https://immunefi.com/)
335 |   - [Hats Finance](https://hats.finance/)
336 | 
337 | ## Learning More
338 | - [Patrick Collins YouTube](https://www.youtube.com/c/patrickcollins)
339 | - [Solodit](https://solodit.xyz/)
340 | - [Block Threat Intelligence](https://newsletter.blockthreat.io?r=2mgsm7) (Referral Link)
341 | - [Consensys Diligence Newsletter](https://consensys.io/diligence/newsletter/)
342 | - [Owen Thurm YouTube](https://www.youtube.com/@0xOwenThurm)
343 | - [The Red Guild YouTube](https://www.youtube.com/channel/UC7bn5DeABT6zQz-bn6GS1Yw)
344 | - [Cyfrin YouTube](https://www.youtube.com/@CyfrinAudits)
345 | 
346 | ## Disclosures
347 | 
348 | The Cyfrin team runs CodeHawks, Cyfrin Updraft, and private security reviews. They are an advisor to the Peeranha project, and run various blockchain nodes like Chainlink & Ethereum. Additionally, they are responsible for the creation of the Aderyn and Solodit tools.  
349 | 
350 | # Thank you
351 | 
352 | ## Sponsors
353 | 
354 | - [Cyfrin](https://www.cyfrin.io/)
355 |   - [Updraft](https://updraft.cyfrin.io/)
356 |   - [CodeHawks](https://codehawks.com/)
357 |   - [Solodit](https://solodit.xyz/)
358 | - [Arbitrum Foundation](https://arbitrum.foundation/)
359 | - [Chainlink Labs](https://chainlinklabs.com/)
360 | 
361 | ## Lead Lecturers / Code Builders
362 | 
363 | - [Patrick Collins | Cyfrin](https://twitter.com/PatrickAlphaC)
364 | 
365 | ## Guest Lecturers
366 | 
367 | - [Josselin from Trail of Bits](https://twitter.com/Montyly)
368 | - [Troy from Trail of Bits](https://twitter.com/0xalpharush)
369 | 
370 | ## Special thanks
371 | 
372 | - [hansfriese](https://twitter.com/hansfriese) 
373 | - [carlitox477](https://twitter.com/carlitox477)
374 | - [0Kage](https://twitter.com/hansfriese)
375 | - [giovannidisiena.eth](https://twitter.com/giovannidisiena)
376 | - [Dacian](https://twitter.com/DevDacian)
377 | - [Alex Roan](https://twitter.com/alexroan)  
378 | 
379 | ## Huge Extra Thank YOU
380 | 
381 | Thanks to everyone who is taking, participating in, and working on this course. These courses are passion project data dumps for everyone in the web3 ecosystem. 
382 | 
383 | Let's level up so we can keep web3 safer, and thank you again for taking this course!
384 | 
385 | [![Cyfrin Twitter](https://img.shields.io/badge/Twitter-1DA1F2?style=for-the-badge&logo=twitter&logoColor=white)](https://twitter.com/cyfrinaudits)
386 | [![Cyfrin YouTube](https://img.shields.io/badge/YouTube-FF0000?style=for-the-badge&logo=youtube&logoColor=white)](https://www.youtube.com/@CyfrinAudits)
387 | 
388 | <p align="right">(<a href="#table-of-contents">back to top</a>) ⬆️</p>
389 | 


--------------------------------------------------------------------------------
/chronological-updates.md:
--------------------------------------------------------------------------------
1 | Please visit [Cyfrin Updraft](https://web3education.dev/) for updates to the course content. 


--------------------------------------------------------------------------------
/how-to-answer-a-question.md:
--------------------------------------------------------------------------------
 1 | # How to answer questions
 2 | 
 3 | Thank you for wanting to answer questions! This is how we grow as a community :)
 4 | 
 5 | 1. Make sure the question follows the "how-to-ask-a-good-question" guide
 6 | 2. Make sure your answer unblocks the user
 7 | 3. Remember, this is living documentation!
 8 | 4. Format your answers, like in the `how-to-ask-a-question` guide. 
 9 | 
10 | 
11 | # 1. Make sure the question follows the "how-to-ask-a-good-question" guide
12 | 
13 | If the question is poorly formatted and you know how to reformat it reformat it and ask them next time to format their code.
14 | 
15 | If the question is posted in the wrong place (like a theoretical question posted on stackoverflow) kindly let them know that it's in the wrong place. 
16 | 
17 | If the question has already been asked and answered, answer with a link to the question that has already been asked and answered and ask if that solves the problem.
18 | 
19 | If the problem has a poor title, doesn't make sense to others, etc, feel free to edit the question to what does if you can understand it. If not, you can answer saying "I don't quite understand what you're asking, could you reformat your question following the "how to ask a question" guide? 
20 | 
21 | If they used screenshots, feel free to ask them to copy-paste the code. 
22 | 
23 | Or, feel free to ignore it. This is a community run forum and no one is "entitled to" answers! Be nice, be respectful, and have fun. But if you do know how to help someone, a little "could you please refactor your question" can go a long way!
24 | 
25 | ### Don't feel obliged to help right away if they are not asking well-formatted questions. Make them ask a well-formatted question first before you answer!
26 | 
27 | But don't be a jerk about it. If they just need a little formatting touch up, just touch up their question for them. 
28 | 
29 | # 2. Make sure your answer unblocks them
30 | 
31 | Often times, people will ask questions where the answer might be X, but they are trying to do Y. Try to anticipate what people are trying to do. Answer the question at face value, and then maybe give more information on where to go next. 
32 | 
33 | Often, giving a summary of your answer at the top with copy pasteable code, and then a "more information" is a best practice. 
34 | 
35 | # 3. Remember this is living documentation!
36 | 
37 | Treat it as such. Go back and update answers if you find them!
38 | 
39 | # 4. Format your answers, like in the `how-to-ask-a-question` guide. 
40 | 
41 | See that guide for more information. 


--------------------------------------------------------------------------------
/how-to-ask-a-question.md:
--------------------------------------------------------------------------------
  1 | # How to ask a question 
  2 | 
  3 | > Note: Before reading this, you might want to read my guide on [top 6 tips to solve any software engineering error](https://medium.com/better-programming/top-6-tips-to-solve-any-software-engineering-error-a794a162fcaf).
  4 | 
  5 | Also note, take this pledge: "I solemnly swear that after asking a question I will spend at least 5 minutes trying to answer someone else's question. I will consult the 'How to answer a question' page before I do so. "
  6 | 
  7 | The internet is our documentation, and we want to treat is as such. **Every** *specific* question we have *should* be able to be found by typing it into a web search bar. 
  8 | 
  9 | Now, there are no "bad" questions, but there are poorly-formatted questions. A poorly formatted question has a low chance of being answered, poor chance of being discovered, and can "clutter up" forums and discussion boards. So let's make sure we strive for well-formatted questions!
 10 | 
 11 | # Full Examples at the bottom!
 12 | 
 13 | Here are the steps to ask a well-formatted question:
 14 | 
 15 | 1. Search to see if the question has already been asked
 16 | 2. Know where to post your question
 17 | 3. Make a title that summarizes the problem
 18 | 4. Introduce the problem before writing any code
 19 | 5. Make sure you format code using backticks (```) and a language tag
 20 | 6. Make sure you copy paste your code instead of using screenshots
 21 | 7. Make sure your code is a minimal example
 22 | 
 23 | 
 24 | # 1. Search to see if the question has already been asked
 25 | 
 26 | ## Do not skip this step!
 27 | 
 28 | We should think of the internet as one giant document. If a question has already been asked and you can find it on the first page of your search engine, it's good! Don't ask the question again! 
 29 | 
 30 | And if it's not on the first page of your search results, then **yes, you should 100% ask the question on a forum even if you know the answer.**
 31 | 
 32 | We want every tech question ever to be:
 33 | 
 34 | 1. Indexed by search engines
 35 | 2. Easy to find
 36 | 3. Easy to reproduce
 37 | 
 38 | So that in 6 months when you forget the answer, you can just google it and it'll show up!
 39 | 
 40 | We don't want there to be multiple questions, because that can fragment where people look! We want to add answers, comments, etc all in one place
 41 | 
 42 | # 2. Know where to post your question
 43 | 
 44 | I categorize questions into one of three:
 45 | 
 46 | - Specific code based questions
 47 | - Generic theoretical questions
 48 | - "In the know", support, or emergency questions
 49 | 
 50 | ## Specific code based questions
 51 | 
 52 | These are what we strive for. These are reproducible questions that help the world. You'll want to put these questions in places like:
 53 | 
 54 | - The "Q&A" discussions section of this course
 55 | - stackoverflow
 56 | - stack exchange ETH. 
 57 | 
 58 | These are questions that typically can have a "right" or "many right answers". Generally, these are not very opinionated questions. 
 59 | 
 60 | These are questions like "How to convert bytes32 to uint256". 
 61 | 
 62 | ## Generic Theoretical Questions
 63 | 
 64 | These are questions that likely do not have a canonical answer. These are questions like "which blockchain should I deploy to?" or "How could I make a game that involves many random characters?". They belong in places like:
 65 | 
 66 | - The "General" discussions section of this course
 67 | - A generic forum like Reddit, Twitter
 68 | - Discord (like some of the ones people have started here)
 69 | 
 70 | Ideally, you put these on an indexed forum like reddit and the general discussions section instead of discord so others can do a web search for the problems.
 71 | 
 72 | ## "In the know", support, or emergency questions
 73 | 
 74 | These are very specific use cases and 99% of your questions will not be these kinds. These are questions like "we just got hacked, can you help us?", "Want to join my team", etc. They are questions that likely only apply to your situation and what you are doing. They belong in:
 75 | 
 76 | - Discord DMs
 77 | - Email
 78 | - etc
 79 | 
 80 | And should be used *very* sparingly. 
 81 | 
 82 | # 3. Make a title that summarizes the problem
 83 | 
 84 | It should be minimal, searchable, indexable (by search engines).
 85 | 
 86 | ## Examples:
 87 | Bad:
 88 | - I'm stuck, please help
 89 | 
 90 | Good:
 91 | - Could Not Detect Network using WSL & Ganache
 92 | 
 93 | Bad:
 94 | - hardhat error
 95 | 
 96 | Good:
 97 | - TypeError: Cannot read property 'length' of undefined - when deploying contract
 98 | 
 99 | # 4. Introduce the problem before writing any code
100 | 
101 | In the body of the question, say what you're trying to do, what you've done, and give a summary of your problem.
102 | 
103 | With this course in the discussions tab, you may also give a timestamp of where you're getting the issue (in fact, please give a timestamp with a link to the location in the video).
104 | 
105 | # 5. Make sure you format code using backticks (```) and a language tag
106 | 
107 | You'll want to format your question so it's as easy as possible to read! Especially with your code snippets.
108 | 
109 | Your code should show up like this:
110 | 
111 | ```javascript
112 | // my code here
113 | ```
114 | 
115 | In your question, you'll type it like this:
116 | 
117 | ````
118 | ```javascript
119 | // my code here
120 | ```
121 | ````
122 | 
123 | If it doesn't get formatted, you can edit your question (usually, you can click the three little dots at the top right of your question) to make it formatted nicely. 
124 | 
125 | # 6. Make sure you copy paste your code instead of using screenshots
126 | 
127 | We want web crawlers to index every word you write, so even copy paste errors (and format them with 3 backticks!)
128 | 
129 | 
130 | # 7. Make sure your code is a minimal example
131 | 
132 | There are two types of code questions:
133 | 
134 | - Debug me
135 | - Specific questions
136 | 
137 | Don't be a "Debug Me"
138 | 
139 | ## Example of a poorly formatted question (a debug me question):
140 | 
141 | Hi I'm confused my code isn't working here is all my code
142 | 
143 | ```javascript
144 | // pretend I pasted like 300 lines of code here
145 | ```
146 | 
147 | ## Example of a much better question
148 | 
149 | I'm getting `error x` on line 42 of my code:
150 | 
151 | ```javascript
152 | const some_var = "dog"
153 | // this is the line that is erroring
154 | ```
155 | 
156 | [More information on reproducible code.](https://stackoverflow.com/help/minimal-reproducible-example)
157 | 
158 | 


--------------------------------------------------------------------------------
/images/0kage.jpeg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Cyfrin/assembly-evm-opcodes-and-formal-verification-course/e1419bc2a33aaab477a797e810c1e55290d73e21/images/0kage.jpeg


--------------------------------------------------------------------------------
/images/aderyn.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Cyfrin/assembly-evm-opcodes-and-formal-verification-course/e1419bc2a33aaab477a797e810c1e55290d73e21/images/aderyn.png


--------------------------------------------------------------------------------
/images/background-image-security.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Cyfrin/assembly-evm-opcodes-and-formal-verification-course/e1419bc2a33aaab477a797e810c1e55290d73e21/images/background-image-security.png


--------------------------------------------------------------------------------
/images/background-updated.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Cyfrin/assembly-evm-opcodes-and-formal-verification-course/e1419bc2a33aaab477a797e810c1e55290d73e21/images/background-updated.jpg


--------------------------------------------------------------------------------
/images/backgroundv3.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Cyfrin/assembly-evm-opcodes-and-formal-verification-course/e1419bc2a33aaab477a797e810c1e55290d73e21/images/backgroundv3.jpg


--------------------------------------------------------------------------------
/images/boss-bridge.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Cyfrin/assembly-evm-opcodes-and-formal-verification-course/e1419bc2a33aaab477a797e810c1e55290d73e21/images/boss-bridge.png


--------------------------------------------------------------------------------
/images/course-background.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Cyfrin/assembly-evm-opcodes-and-formal-verification-course/e1419bc2a33aaab477a797e810c1e55290d73e21/images/course-background.jpg


--------------------------------------------------------------------------------
/images/course-hero.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Cyfrin/assembly-evm-opcodes-and-formal-verification-course/e1419bc2a33aaab477a797e810c1e55290d73e21/images/course-hero.jpg


--------------------------------------------------------------------------------
/images/course-post2.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Cyfrin/assembly-evm-opcodes-and-formal-verification-course/e1419bc2a33aaab477a797e810c1e55290d73e21/images/course-post2.jpg


--------------------------------------------------------------------------------
/images/course-posts.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Cyfrin/assembly-evm-opcodes-and-formal-verification-course/e1419bc2a33aaab477a797e810c1e55290d73e21/images/course-posts.jpg


--------------------------------------------------------------------------------
/images/curriculum.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Cyfrin/assembly-evm-opcodes-and-formal-verification-course/e1419bc2a33aaab477a797e810c1e55290d73e21/images/curriculum.png


--------------------------------------------------------------------------------
/images/gas-bad.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Cyfrin/assembly-evm-opcodes-and-formal-verification-course/e1419bc2a33aaab477a797e810c1e55290d73e21/images/gas-bad.png


--------------------------------------------------------------------------------
/images/horse-store.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Cyfrin/assembly-evm-opcodes-and-formal-verification-course/e1419bc2a33aaab477a797e810c1e55290d73e21/images/horse-store.png


--------------------------------------------------------------------------------
/images/math-master.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Cyfrin/assembly-evm-opcodes-and-formal-verification-course/e1419bc2a33aaab477a797e810c1e55290d73e21/images/math-master.png


--------------------------------------------------------------------------------
/images/mev-thumbnail.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Cyfrin/assembly-evm-opcodes-and-formal-verification-course/e1419bc2a33aaab477a797e810c1e55290d73e21/images/mev-thumbnail.png


--------------------------------------------------------------------------------
/images/password-store-logo.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Cyfrin/assembly-evm-opcodes-and-formal-verification-course/e1419bc2a33aaab477a797e810c1e55290d73e21/images/password-store-logo.png


--------------------------------------------------------------------------------
/images/puppy-png.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Cyfrin/assembly-evm-opcodes-and-formal-verification-course/e1419bc2a33aaab477a797e810c1e55290d73e21/images/puppy-png.png


--------------------------------------------------------------------------------
/images/red-guild-png.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Cyfrin/assembly-evm-opcodes-and-formal-verification-course/e1419bc2a33aaab477a797e810c1e55290d73e21/images/red-guild-png.png


--------------------------------------------------------------------------------
/images/t-swap-youtube-dimensions.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Cyfrin/assembly-evm-opcodes-and-formal-verification-course/e1419bc2a33aaab477a797e810c1e55290d73e21/images/t-swap-youtube-dimensions.png


--------------------------------------------------------------------------------
/images/the-red-guild.jpeg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Cyfrin/assembly-evm-opcodes-and-formal-verification-course/e1419bc2a33aaab477a797e810c1e55290d73e21/images/the-red-guild.jpeg


--------------------------------------------------------------------------------
/images/tincho-is-a-monster.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Cyfrin/assembly-evm-opcodes-and-formal-verification-course/e1419bc2a33aaab477a797e810c1e55290d73e21/images/tincho-is-a-monster.png


--------------------------------------------------------------------------------
/images/tincho.jpeg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Cyfrin/assembly-evm-opcodes-and-formal-verification-course/e1419bc2a33aaab477a797e810c1e55290d73e21/images/tincho.jpeg


--------------------------------------------------------------------------------
/images/top-10-attack-vectors.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Cyfrin/assembly-evm-opcodes-and-formal-verification-course/e1419bc2a33aaab477a797e810c1e55290d73e21/images/top-10-attack-vectors.png


--------------------------------------------------------------------------------
/images/top-attack-vectors-updated.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Cyfrin/assembly-evm-opcodes-and-formal-verification-course/e1419bc2a33aaab477a797e810c1e55290d73e21/images/top-attack-vectors-updated.png


--------------------------------------------------------------------------------
/images/updraft-landing-p.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Cyfrin/assembly-evm-opcodes-and-formal-verification-course/e1419bc2a33aaab477a797e810c1e55290d73e21/images/updraft-landing-p.png


--------------------------------------------------------------------------------
/images/vault-guardians-logo.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Cyfrin/assembly-evm-opcodes-and-formal-verification-course/e1419bc2a33aaab477a797e810c1e55290d73e21/images/vault-guardians-logo.png


--------------------------------------------------------------------------------
/images/vault-guardians.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Cyfrin/assembly-evm-opcodes-and-formal-verification-course/e1419bc2a33aaab477a797e810c1e55290d73e21/images/vault-guardians.png


--------------------------------------------------------------------------------
/improvement_points.md:
--------------------------------------------------------------------------------
1 | 1. SEAL Drills 


--------------------------------------------------------------------------------