Hi Yuri,
Your background looks pretty relevant; I'm interested. Have you performed any prior Solidity audits?
Glad to answer any questions you have - here or email me directly at protinam@protonmail.ch
Cheers,
Protinam
Are you still interested in this job? You should be able to submit an invoice through the platform. We can be flexible in schedule over the holidays if necessary, just let me know.
Thanks! Looks like you have solid prior experience. We'd be delighted to have you audit our smart contracts, and 2.5 ETH is fine.
Please use Git commit hash 7358a6c065, i.e. https://github.com/ProjectWyvern/wyvern-ethereum/tree/7358a6c06533e04b5d4d6b1d0d0720b7da0c8377. NatSpec is pretty readable in-source, and we also have web-rendered documentation at https://docs.projectwyvern.com/ if you like.
All contracts should be reasonably well-documented in both intent and specifics, but please reach out to me here or directly at protinam@protonmail.ch if you have any questions.
Thanks for the prompt response, and it looks like you've done a nice job with previous audits.
As we aren't holding a token sale, I'm afraid that's a bit above our budget at the moment - do you provide any other service options?
Wyvern Token & DAO Security AuditsThe Wyvern Exchange, currently under development, is an upcoming decentralized digital item exchange running on the Ethereum blockchain.
We're looking for a few experienced Solidity developers / smart contract auditors to audit the first set of smart contracts we intend to deploy.
Job requirements are as follows:
1. Analyze a subset of the Wyvern Ethereum smart contracts found at https://github.com/ProjectWyvern/wyvern-ethereum/tree/master/contracts (an exact Git commit hash will be provided upon job acceptance).
2. Generate a report highlighting all potential issues with the smart contract code and providing suggestions to fix any bugs or enhance general security.
3. Share your findings with the Project Wyvern developers privately so that any issues can be addressed.
4. Write an analysis to be shared publicly. Discuss the issues you found (if any), steps that were taken to reoslve them, and your overall thoughts on the state of the code.
This field is character-limited; full description at https://gist.github.com/protinam/65c6408dc58940c70a096f5bcb4a9081.