crytic / crytic/building-secure-contracts
Create list of risks when interacting with the most common DeFi
Open
help wanted
- Dominant language
- Solidity
- Stars
- 2.5k
- Forks
- 391
- PR merge metrics
- No merged PRs in 30d
Description
This issue has no description.
Contributor guide
Research direction
The issue body does not name any files, tests, or entry points. Start by reviewing the repository's existing training and documentation structure, then determine which common DeFi interactions are in scope. Done means a reviewed, agreed-upon list of associated risks is incorporated into the appropriate documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- solidity
- Domain
- blockchain, documentation, security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100