Post

@MultiversX Start with the codebase.
Protocol correctness, VM interactions, cross-shard behavior, resource exhaustion — go looking for real weaknesses in how the protocol works.
github.com/multiversx
English

A good report includes reproduction steps, logs, environment details, and a clear impact statement.
Quality matters — it affects your score within the severity band.
Scoring policy →
drive.google.com/file/d/1i2rb0Q…
Example report ↓
drive.google.com/file/d/1AaWB2M…
English

20 submissions per participant.
One week left.
bon.multiversx.com/protocol-secur…
English
