Skip to content

Conversation

@bengyles
Copy link

@bengyles bengyles commented Jan 9, 2025

Motivation

Solution

@bengyles bengyles requested a review from pegahcarter January 9, 2025 22:02
@pegahcarter
Copy link
Contributor

@bengyles I'm a little bit overwhelmed at the amount of code to review here. Can you break it down this way per contract?

  • Rating from 1 - 10 of degree of confidence
  • Areas of concern / desired review
  • Readiness for mainnet. Are there things you're considering to add / change before production?

Can you also add the audit report?

@bengyles
Copy link
Author

@pegahcarter Most changes are in contracts/repfi, some changes have been done in the deploy scripts to enable testing/deploying these contracts as well. Last but not least tests are in the /test/unit/repfi folder. There are a few tests not working yet though because they depend on the improvements to be made in PeerValue/PeerStaking and will be finished to 100% when that's done.

Here's a short breakdown of the contracts/folders:

  • peerStaking: Work in progress, to be improved (confidence 6)
  • peerValue: Work in progress, to be improved (confidence 6)
  • reputationMining: Almost finished, though needs some finetuning (confidence 6)
  • Token: AUT: audited, already live on mainnet (confidence 10)
  • Token: cAUT: Work in progress, to be improved (confidence 8)
  • Token: Distributor: already audited and executed on Mainnet (confidence 10)
  • UtilsRegistry: Should be done, but has not been audited yet as it works with cAUT which will be audited in the next round (confidence 9)
  • Vesting: all contracts have been audited but are not deployed yet, awaiting usage (confidence 10)

Please look into reputationMining especially and see if you know a better way to enhance the token locking for each period (if any) as the full amount of tokens (36 million AUT) is sent to this contract before mining starts and this could be tricky

@bengyles
Copy link
Author

bengyles commented Jan 20, 2025

@pegahcarter Could not push my commit with the audit report pdf for some reason, will look further into that tomorrow, in the meantime you can check it out on their github: https://github.com/blaize-security/blaize-security-audits/blob/main/a/autlabs/Aut-Labs-(token-repfi)-audit-report-%5B4-Dec-2024%5D.pdf

@bengyles
Copy link
Author

@pegahcarter I was able to add the pdf here now as well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants