feat: added position manager

[Thektonic]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @Thektonic, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request primarily integrates functionality for interacting with Uniswap V3's Non-Fungible Position Manager, which is essential for managing liquidity positions. A key architectural improvement is the introduction of a generic Interactions struct, which standardizes how various smart contracts are handled. This refactoring has been applied to existing ERC20 and ERC721 interaction layers, resulting in a more consistent, modular, and maintainable contract interaction framework.

Highlights

• Uniswap V3 Position Manager Integration: I've added the necessary ABI, Solidity interface, and Go bindings for the INonfungiblePositionManager contract. This enables the project to interact with Uniswap V3's concentrated liquidity positions, allowing for operations like minting, increasing/decreasing liquidity, collecting fees, and burning positions.
• Introduction of Generic Contract Interaction Model: A new generic base.Interactions struct has been introduced. This struct serves as a standardized wrapper for various contract sessions (e.g., nftPositionManager, ERC721A, ERC721Complete, ERC20Burnable), promoting a more consistent and reusable approach to contract interactions across the codebase.
• Refactoring of Existing Interaction Modules: Existing erc20 and nft interaction modules have been refactored to leverage the newly introduced generic base.Interactions struct. This significantly reduces boilerplate, improves code maintainability, and ensures a unified interface for interacting with different types of smart contracts.
• New NFT Signature Utilities: I've added new BaseNFTSignature constants and a GetHex() method. These utilities are designed to simplify the process of deriving and checking function selectors for common NFT contract methods, enhancing the robustness of contract interface verification.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces a generic Interactions struct to reduce code duplication across different contract interaction wrappers, which is a great improvement for maintainability. It also adds support for a new INonfungiblePositionManager contract, expanding the library's capabilities. The review identified several areas for improvement, including copy-paste errors in comments, misplaced files, and a potentially unused method. Please address them to improve the quality and clarity of the codebase.