Closed gershon closed 1 month ago
Would be happy to take on this by tomorrow 💫
Hi @ikemHood, let's go 🚀
@gershon have you started assigning issues
I am applying to this issue via OnlyDust platform.
hello, can i take on this?
ETA within 24hrs
write a ts script that get abi for contracts/target folder and save to a specified folder
add a custom build:contract
to package.json to first build the contract with scarb build the calls the script to extract the abi
I am applying to this issue via OnlyDust platform.
Hi, I'm Emmanuel and I'll be working on issue:
I estimate this will take 3 days to finish Basecamp graduate
Here is how I would tackle this issue Understand the scope of work better by asking questions. Build contracts first Get the corresponding ABI or ABIs from contract_class.json file after a successful build. create a constants file for storing the ABI , Like abi-constant.cairo Create a constant for each ABI. Put ABI in constants like: const MY_CONTRACT_ABI: felt* = [ // The ABI data goes here ]; Export the constants for use and manipulations.
I am applying to this issue via OnlyDust platform.
i'm a solidity and cairo smart contract developer with over 2 years experience and belive i have the skill set for the task
hello @gershon i would love to take up this issue.
I am applying to this issue via OnlyDust platform.
I am a Blockchain Dev
I would take this steps in solving the issues:
I am applying to this issue via OnlyDust platform.
have a solid background in blockchain development, specializing in writing and testing smart contracts using Solidity. I’ve worked on various decentralized applications (dApps), where I've built and deployed secure and efficient smart contracts on Ethereum. Additionally, I have experience in testing these contracts using frameworks like Hardhat and Truffle, ensuring they function as expected under different scenarios. My expertise in both Solidity development and rigorous testing practices will be valuable for this task.
Modify the Build Configuration:
Organize ABI Files:
/build/abis
) to store the generated ABI files for each contract, ensuring they are easily accessible.Create a Constants File:
constants.js
(or equivalent) file that imports the generated ABIs from the ABI directory and exports them in a structured format (e.g., as an object with contract names as keys).Automate Exporting:
Verify and Test Integration:
I am applying to this issue via OnlyDust platform.
I am a skilled fullstack developer with a wealth of experience in both frontend and backend JavaScript as well as my knowledge of Rustlang, With a solid foundation in testing,I have mastered frameworks like Mocha, Chai, and Jest to ensure robust, reliable code in every project. In addition to traditional web development, I have a strong background in blockchain technology, with hands-on experience in Solidity for Ethereum-based smart contracts. Moreover, I have delved into the emerging world of StarkNet, working with Cairo, a cutting-edge language tailored for STARKs, making them a versatile developer capable of bridging both traditional and decentralized web applications.
Having a background in blockchain development makes this easy as working with ABIs is an everyday thing, i will handle thecreating of abis on build, with well define exports
🚀
We should generate and export all contract ABIs to facilitate their usages and manipulations.