-
# Handle
Reigada
# Vulnerability details
## Impact
There are functions marked as public but they are never directly called within the same contract or in any of its descendants, hence they can be …
-
# Lines of code
https://github.com/code-423n4/2024-01-salty/blob/53516c2cdfdfacb662cdea6417c52f23c94d5b5b/src/Upkeep.sol#L107
# Vulnerability details
## Impact
The rewards earned from the DAOs PO…
-
# Handle
0xRajeev
# Vulnerability details
## Impact
Giving max approval (total supply) for DAO's SPARTA/tokens to ROUTER is risky because if ROUTER contract gets compromised then DAO's SPARTA/tok…
-
There are too many projects that fit into Other. I'd suggest breaking them down:
- Anti-Abuse (or Security)
- Onboarding (or Account Creation)
- Voting
- Data Tools
- Proposal Tools (or similar, …
-
### Describe the problem
i would like to add short info boxes atz the top of both DAO tools pages that contain a very short description of what each tool does and how it works and what it means for…
-
# Handle
0xRajeev
# Vulnerability details
## Impact
setParams() is authorized to be called only from the DAO (per modifier) but DAO contract has no corresponding functionality to call setParams()…
-
# Handle
0xRajeev
# Vulnerability details
## Impact
Given that there are only three proposal types (GRANT, UTILS, REWARD) that are actionable, it is unclear if 'DAO' type checked in voteProposal(…
-
# Handle
0xRajeev
# Vulnerability details
## Impact
Event log poisoning is possible by griefing attackers who have no DAO weight but vote and emit event that takes up event log space.
## Proof o…
-
We're building the entire app from the ground up, not importing pre-existing components. We have had to conceptually rebuild the entire system from scratch because of all the new functionality for Baa…
-
This proposal suggests transferring a 10% commission to tools from the lifetime earnings of realms and packages. The goal is to incentivize Gno tool makers (e.g. GnoIDE) to create better tools for rea…