Security audit of a smart contract on Solana (Rust/Anchor) — token price betting platform

Budget: 27000 UAH Deadline: 14 days

For such a contract, the benchmark is from 65,000 UAH and 10-14 working days, including the initial audit, criticality report, and re-check of corrections. The budget of 1,111 UAH here, unfortunately, does not correspond to the mainnet risk - a cheap audit in DeFi often costs more after the first incident =/

We can take a non-formal check, but rather a normal security review - Anchor account constraints, signer and ownership checks, PDA seeds, SPL Token authority flow, escrow model, overflow/rounding, final price resolver, claim/refund logic, pause/emergency scenarios, and privilege escalation through admin authority. Separately, I would look at edge cases with empty or unbalanced rounds, many participants, zero pools, rounding of payouts, and repeated claim attempts.

You will need to provide the repository, a description of the expected economy of rounds, a list of roles/authority keys, instructions for running tests, and the desired report format. Note, there is a nuance here - without local test execution and code reading, the exact estimate may vary slightly, but the budget order will be just like that.

Questions:
> Is there already a test suite for Anchor, especially on refund/claim/emergency scenarios?
> Is the price resolver centralized, multisig, oracle, or a custom admin mechanism?

Similar complexity cases from Ingello:
> https://business.ingello.com/vorfahr - complex automation with financial and operational logic, where the reliability of scenarios is important
> https://business.ingello.com/fractal - agent architecture and complex processes, useful as an example of a systematic approach to logic verification
> https://systems-fl.ingello.com/ua Expand

Budget: 20000 UAH Deadline: 7 days

Hello! I will conduct an audit and prepare a document with a classification of the identified vulnerabilities as well as details on how to fix them. I suggest we discuss this in more detail in private messages, and I am also ready to provide links to completed projects that have gone through my audit or were developed by me.

Budget: 27000 UAH Deadline: 3 days

Hello, we will conduct a professional audit with a company signature. Please message me privately about the price, approximately $1200.

Budget: 5000 UAH Deadline: 3 days

I have already done many audits; I can send an example in private messages if you are interested in a quality audit with bug fixes verification - write to me.

Budget: 4000 UAH Deadline: 1 day

Good day! I have been working with Solana for over two years. I have developed and audited programs in Rust + Anchor, including PDA, CPI, SPL Token, escrow mechanics, fund distribution systems, staking, and DeFi logic. I have also analyzed contracts for errors in account checks, authority, PDA, integer overflow, logical edge cases, and other typical Solana issues. For a contract of this size, approximately 4–7 working days will be needed. The cost depends on the actual size of the code and the complexity of the logic, but it is approximately $1000–2000, including a re-audit after corrections are made. I provide a report in the form of a document describing each identified issue: severity level (Critical / High / Medium / Low), risk description, exploitation scenario, recommendations for fixes, and, if necessary, code examples. After corrections, I conduct a follow-up audit and add the status for each finding (Fixed / Partially Fixed / Unresolved).

Budget: 27000 UAH Deadline: 8 days

We already have a practically ready format for such an audit, which can be quickly adapted to your repository and launched now, I'm here on the marketplace))
For Solana, we work with Rust, Anchor, SPL Token, PDA escrow, signer and ownership checks, authority model, and payout logic.
The cost estimate is 48,000 UAH, the timeframe is 8 working days for one compact contract, including a re-check of corrections.
The format is a practical report with Critical, High, Medium, Low, proof of risk, recommendations, a file or instructions where the problem is found.
We look not only at typical Anchor vulnerabilities but also at the economics of rounds, rounding, edge cases with many participants, abuse of pause, refund, and resolver.
To start, we need the repository, a description of the business rules for the rounds, a testnet or local scenario, a list of admin authority keys, and the desired report format.
Please clarify the size of the repository - the number of Anchor instructions and whether there are tests or a local validator scenario.
Is the price resolver a centralized admin authority, oracle, or external backend?
A closely related example in terms of logic complexity is https://business.ingello.com/svitbus - payments, roles, returns, financial panel.
Another relevant example is https://business.ingello.com/platforma - complex corporate logic, roles, processes.
Our profile for FLH is https://systems-fl.ingello.com/ua Expand