search

ZencypherSolutions / semaphore-stellar-contracts

MIT License
0 stars 0 forks source link

feat: Testing for Semaphore Groups contract #3

Open bitfalt opened 13 hours ago

bitfalt commented 13 hours ago

Test the Semaphore Groups contract.

Blocked by #1. Once the implementation of the Semaphore Groups contract is complete, this issue will be assigned.

Jemiiah commented 12 hours ago

@bitfalt my first time on this repo I would love to work on this issue and contribute to the project

Benjtalkshow commented 12 hours ago

Hello @evgongora I have written over 4 test cases on onlydust projects using Rust, Cairo and Python. I will be glad if this task is assigned to me. I will deliver in 48hrs max. Thanks

martinvibes commented 11 hours ago

Could I take over this issue? kindly assign and i'll get to work asap

Issue Summary for Semaphore Groups Contract Testing

This issue focuses on developing and running tests for the Semaphore Groups contract to ensure functionality and reliability.

**Testing will cover essential functions of the contract to validate its operation in various scenarios.**

ETA: 24HRS

KoxyG commented 11 hours ago

Hi @bitfalt @evgongora, 👋

I’m applying for this issue through the OnlyDust platform.

About My Background and Skills

I’m Koxy, a Rust developer with experience in blockchain and Stellar ecosystem contributor. I also host the YouTube series Let’s Get Soroban, where I share hands-on content on Rust and Stellar development.

My open-source background and in-depth understanding of Stellar’s framework make me well-suited to migrate the Semaphore Groups contract to Soroban. I’m eager to provide immediate, impactful solutions while collaborating with the team to advance the Semaphore protocol for the future.

My Approach to Addressing the Issue

To execute this migration, I intend to:

  1. Develop a SemaphoreGroups Trait: Implement a trait and convert it into a compatible contract for Soroban. As i already proposed here.

  2. Perform Comprehensive Testing: Design tests covering multiple scenarios, with a focus on edge cases.

  3. Update and Refine Documentation: Adjust CLI documentation and help texts to reflect the new changes.

  4. Submit a Detailed PR: Include thorough explanations of each modification and its purpose.

  5. Work Closely with Maintainers: Integrate feedback and enhance the solution as required.

This is a sample contract written in soroban.

Thanks for considering my application. I look forward to contributing!.

No-bodyq commented 7 hours ago

Hello @bitfalt I would love to contribute to this project I have written test for smart contracts in Cairo on other projects on the only dust platform ETA is 48 hrs Please do assign