Sponsor Q&A
How to ask questions about a codebase you're auditing
Code4rena's in-app Q&A feature enables direct communication between wardens and sponsors during active audits, allowing wardens to ask technical questions about the codebase and receive clarifications from the project team.
Key things to know
New threads are private by default. You can double-check the privacy settings in the right side column.
Sponsors are not required to reply to all threads. To maximize your odds of receiving a helpful response:
Ensure that your thread is clear, concise, and not already answered in the audit's provided
READMEand documentation.Focus on your most important clarification needs.
Allow sufficient time for a response. Bear in mind that sponsors often receive questions from dozens of wardens — and that they have limited time to allocate to warden Q&A.
Read the docs first:
Before using the Q&A feature, be sure to check the audit repo for project documentation, and search for answers there.
Most Code4rena audits are supported by our Docs Wolf documentation bot 🤖.
The bot will make its best attempt to answer based on the codebase and documentation, and link you to relevant resources.
Instructions for using Docs Wolf are posted in each audit's dedicated Discord channel.
Question limits by role:
Wardens who don't have the SR role are limited to one open thread at a time.
You must wait for your current question to be resolved and/or closed before posting another.
SR wardens may open multiple threads.
However, it is still recommended to keep your questions focused and concise.
Accessing the Q&A Feature
Navigate to any active audit and click the Q&A tab (alongside Details and Your Findings)

If you have no active threads, you will only see a button to open a new thread.

If you have asked a question already, you will see a list of threads (both open and closed).
If you have new replies from the sponsor, you will see a red notification alert.
Creating New Questions
Starting a question thread:
Click "New thread" button in the Q&A tab
Provide a clear, specific title for your question
Include technical details, code references, or specific scenarios
Submit your question to the sponsor team

Best practices for questions:
Be specific - Reference exact functions, contracts, or line numbers when possible
Provide context - Explain what you're trying to understand or verify
Stay technical - Focus on implementation details rather than general questions
Check existing threads - Review current and closed questions to avoid duplicates
Last updated
Was this helpful?