marigold-dev / marigold-dev/deku
Spam Protection
Open
Nobody has claimed this yet.
backlog
- Dominant language
- OCaml
- Stars
- 82
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
We need to implement some kind of spam protection to make attacks more expensive:
Ideas off the top of my head:
- we're PoA, so we can blacklist validators who spam us effectively, since < 1/3rd of the validators are bad.
- We can use PoW before we accept blocks from a validator. Maybe same thing for clients submitting transactions?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by clarifying the threat model and deciding whether validator blacklisting, proof of work, or both are intended. Done requires an agreed design for protecting block acceptance and transaction submission, followed by implementation and tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blockchain, ocaml
- Domain
- blockchain, distributed-systems, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100