Introduction

Hello, Memelordzcommunity! We have exciting updates regarding the smart contract functionalities for approval and minting. Our recent focus has been on resolving issues and ensuring our system is ready for multichain operations. Let's dive into the details.

Smart Contract Adjustments

Minting Fee and VRF Cost

Initially, we encountered some confusion with the minting fee and VRF cost settings. By default, the VRF fee was set to 0.01 ETH, while the mint fee was set to 0. However, during our contract deployment, we noticed discrepancies.

Jaimy de Vries identified that even though the mint fee was changed, the VRF cost seemed hardcoded, which raised concerns about its flexibility during contract calls. After thorough investigation, including direct minting tests on the contract, we confirmed that the contract logic itself does not force these amounts.

Hardcoded Data and Contract Redeployment

To ensure the integrity of our contracts, we redeployed the minting contract multiple times. Despite initial issues like incorrect wallet addresses and ABI visibility problems, we managed to deploy a fully functional contract. This new contract confirms that we are not forced to spend the default VRF cost of 0.01 ETH.

Felix and the team conducted several tests, revealing that while the minting itself works flawlessly, there might be misconfigurations on the client-side that force the higher VRF cost during transactions.

Multichain Compatibility

Our goal is to make Memelordz available across multiple blockchain networks. Each chain handles transactions and costs differently, so it's crucial to validate our contracts on various chains to ensure consistent behavior.

Key Findings and Next Steps

1. Validation of Contract Logic: We confirmed that the contract logic does not enforce the 0.01 ETH VRF cost, suggesting that adjustments might be needed in the client codebase.
2. Deployment and Testing: We have successfully deployed and tested the new minting contract, ensuring no mandatory ETH expenditure for minting.
3. Further Investigation: We will continue testing the client-side parameters and gas estimates to identify any discrepancies causing the higher cost display.
4. Multichain Readiness: With the validated contract logic, we can confidently proceed with preparing our system for multichain deployment, ensuring flexibility and adaptability across different blockchain networks.
5. We succesfully identified the solution and deployed the first Lordz NFT on the Base Blockchain 

Ryan's Endless Testing and Data Confirmation

A special shoutout goes to Ryan for his relentless dedication to testing and validating our data. His meticulous approach has been instrumental in ensuring the accuracy and reliability of our smart contracts.

Ryan has been tirelessly conducting tests across various scenarios to confirm that our contracts are functioning as intended. His efforts have not only identified potential issues but also provided valuable insights into the underlying data. By simulating different transaction conditions and scrutinizing every detail, Ryan has helped us achieve a higher level of confidence in our system.

Through his persistent testing, Ryan has confirmed that the contract logic does not enforce unnecessary costs and that any discrepancies observed are likely due to client-side parameters. His work has been crucial in refining our approach and ensuring that Memelordz is robust and ready for multichain deployment.

Thank you, Ryan, for your unwavering commitment and exceptional attention to detail! Your contributions are greatly appreciated by the entire team and the Memelordz community.