LittleFingerrr/Littlefinger

AI Summary: Implement a `sync` function in a Starknet smart contract (written in Cairo) to update the contract's internal balance tracker (`available_funds`) to match the actual ERC20 balance held by the contract's address. This function should be called before or after other state-changing functions to ensure balance accuracy. Arithmetic operations updating the balance should be replaced with calls to the `sync` function.

AI Summary: Prevent zero-amount and zero-address transactions within a Starknet-based payment vault. This involves reviewing and modifying the vault's code to add assertions that prevent such transactions and updating the transaction history to exclude them. The solution should be implemented as a pull request from the master branch.

AI Summary: Remove the optional `Option` enum from the `last_execution` field within the `DisbursementSchedule` struct in a Starknet-based payment solution. This requires modifying the struct and associated code to handle the removal without breaking functionality, ensuring all tests continue to pass.

AI Summary: Implement a DAO Controller smart contract on Starknet for a payment solution. This contract will manage proposals, voting, and decision-making within a decentralized organization. It should include functions for creating proposals, voting, setting thresholds, and storing proposal statuses, along with appropriate event emissions. Thorough testing is required.

AI Summary: Integrate a DAO Controller component into a disbursement component for a Starknet-based payment solution. This involves using the DAO Controller to manage proposals, and conditionally using these proposals (based on organization configuration) to control disbursement schedule creation and updates. The solution must be thoroughly tested and build successfully.

AI Summary: Integrate a DAO controller into a member management component to handle member onboarding and other actions as proposals requiring votes, depending on the organization's decentralized configuration. This involves creating a three-step onboarding process (invite, acceptance, vote) and using match logic to conditionally manage other member management functions.

AI Summary: Implement different organization configurations (centralized and decentralized) for a Starknet-based payment solution. This involves defining organization structs and enums, creating/managing configuration functions with role-based access control (RBAC), and implementing these interfaces within the organization component. Testing and ensuring build success are crucial.

AI Summary: Integrate changes from issue #36 (improving organization configuration for centralized and decentralized setups) into the `setup_org` function within the Starknet-based payment solution's factory contract. This involves incorporating the organization component into the contract's initialization and constructor calldata. Successful completion requires a building contract, integrated tests, and a conflict-free pull request.