Solana has a transparency issue - many programs are launched closed-source with no IDL, no SDK, and even as fully permissioned protocols, going against the idea of a decentralized, open and permissionless financial ecosystem. At the same time, this benefits hackers who can move funds through opaque protocols. It follows an idea of security through obscurity, which is not a sustainable approach to secure our ecosystem.

At Accretion, we believe in security by design, and not by obscurity. Therefore, we sponsor a track to lift the veil and introduce more transparency and accountability in the Solana ecosystem by throwing some light on closed source programs.

Deliverable

We are looking for new tools, frameworks, dashboards, or research that specifically target closed source Solana programs. Your tool, framework, dashboard, or research should in some way reveal non-trivial information about a closed source program. It should move the needle forward and get us a step closer to more transparency. Ideally, you should develop new methods or ideas on how to get as much information out of a closed source program as possible. Some examples could be:

• An open source tool which extracts all Instructions from a closed source program, enriched with information about accounts and argument formats

• A tool or plugin that assists in manual reverse engineering of closed source programs

• A general guide or blogpost about how to reverse engineer a closed source program

• An exemplary walkthrough of reverse engineering a popular closed source program as a blogpost or long form video

• A dashboard which collects and enriches non-trivial information about arbitrary closed source programs

• A reverse engineering framework or toolkit to work with closed source programs

• A database of useful information for Reverse engineering - function signature, discriminators, account names, etc.

• etc.

The common theme: Anything that would help someone else with reverse engineering a Solana program!

Your deliverable should be openly accessible and free to use. It can be a tool hosted on github, a blogpost, an sdk, a ghidra (or other tool) plugin, or a publically available dashboard on Dune or another platform.

If you choose to write a blogpost, make sure it’s in-depth.

Judging Criteria

We will judge submissions based on their practicality, novelty, technical depth, correctness, and completeness. All submissions must be original — any plagiarized work will be disqualified. If you want to win, don’t just regurgitate existing knowledge - innovate!

Submission Requirements:

Your submission will be rejected:

• If it is not written in English.

• If your submission is a text-submission (e.g. blogpost) and the contents of the submission are less than 1,000 words

• If it is found to be plagiarized or stolen

• If it fails to include and cite proper references

• If it is a tool, dashboard, or similar, and it simply doesn’t work

• Your submission is not publicly viewable on and after the submission deadline. Submissions of private links will not be eligible.

Brownie points for tweeting about [REDACTED] Hackathon and tagging @accretion_xyz and @SuperteamEarn in your tweet.