Skip to content

130 each game of rankify instance shall be a separate contract#178

Draft
peersky wants to merge 13 commits intodevfrom
130-each-game-of-rankify-instance-shall-be-a-separate-contract
Draft

130 each game of rankify instance shall be a separate contract#178
peersky wants to merge 13 commits intodevfrom
130-each-game-of-rankify-instance-shall-be-a-separate-contract

Conversation

@peersky
Copy link
Member

@peersky peersky commented May 10, 2025

No description provided.

peersky added 5 commits May 10, 2025 12:13
…te Solidity contracts, libraries, and scripts related to the Rankify instance and diamond architecture.
…t and DiamondDistribution, streamlining the project structure.
- Added `viaIR` and `evmVersion` settings in the Hardhat configuration.
- Adjusted optimizer runs from 2000 to 200 for better performance.
- Introduced contract sizer settings for improved contract management.
- Updated package dependencies:
  - Changed `@peeramid-labs/eds` to a local file reference.
  - Upgraded `hardhat` to version 2.22.19.
  - Updated `@openzeppelin/contracts` and `@openzeppelin/contracts-upgradeable` to version 5.3.0.
- Changed function visibility from private to internal for several functions to allow access from derived contracts.
- Updated the transferFromAny, fulfillERC72Balance, and _release functions accordingly.
@changeset-bot
Copy link

changeset-bot bot commented May 10, 2025

🦋 Changeset detected

Latest commit: 5b56259

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
rankify-contracts Major

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@coderabbitai
Copy link
Contributor

coderabbitai bot commented May 10, 2025

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@peersky peersky marked this pull request as draft May 10, 2025 04:27
@peersky peersky linked an issue May 10, 2025 that may be closed by this pull request
@peersky peersky added this to the Owner driven Upgradability milestone May 10, 2025
@peersky peersky self-assigned this May 10, 2025
peersky and others added 8 commits May 10, 2025 12:54
* Remove unused files and clean up project structure by deleting obsolete Solidity contracts, libraries, and scripts related to the Rankify instance and diamond architecture.

* Remove obsolete Solidity contracts related to ArguableVotingTournament and DiamondDistribution, streamlining the project structure.

* Remove LibEIP712Storage library to streamline project structure and eliminate obsolete code.

* Remove DAODistributor contract and deprecated code to streamline project structure.
…de to prepare for future refactoring and updates.
* feat: add Fellowship contract and related interfaces

- Introduced the Fellowship contract to manage game mechanics and user ranks.
- Added IFellowship interface for contract interactions.
- Implemented LibACID library for handling tournament logic and state management.
- Created FellowshipAgent script for game setup and management.
- Established mock voting and environment setup for testing purposes.

* Refactor Fellowship contract to integrate RankToken functionality and streamline initialization. Removed deprecated code and adjusted state variables for improved clarity and efficiency. Updated interfaces and library dependencies to reflect new structure.

* Refactor setupMockEnvironment to export setupAddresses function for improved accessibility. Update RankToken tests to utilize the new setup function, enhancing clarity and organization of test cases.

* Integrate LibMiddleware and AuthorizationMiddleware into Fellowship contract. Update FELLOWSHIP_STORAGE_POSITION calculation for improved storage management. Enhance code clarity with additional comments.

* Implement BaseEnvironmentSimulator class for enhanced testing capabilities. Refactor FellowshipAgent to extend BaseEnvironmentSimulator, improving code organization. Update hardhat.config.ts for conditional contract sizing. Add Fellowship contract tests for installation, uninstallation, and upgrades, while removing obsolete test files.

* changeset

* changeset
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.

Each game of rankify instance shall be a separate contract

1 participant