ZencypherSolutions / semaphore-stellar-contracts

MIT License
0 stars 0 forks source link

feat: Implement Semaphore Groups contract #1

Open bitfalt opened 13 hours ago

bitfalt commented 13 hours ago

Migrate the Semaphore Groups contract to Soroban.

Resource: https://github.com/semaphore-protocol/semaphore/blob/main/packages/contracts/contracts/base/SemaphoreGroups.sol https://github.com/semaphore-protocol/semaphore/blob/main/packages/contracts/contracts/interfaces/ISemaphoreGroups.sol

mubarak23 commented 12 hours ago

I am applying to this issue via OnlyDust platform. @bitfalt

here is my recent soroban smart contract work: - https://github.com/mubarak23/soroban-bank

Other recent rust work

Josh-121 commented 12 hours ago

I am applying to this issue via OnlyDust platform.

My background and how it can be leveraged

software engineering background, backend & smart contract dev looking to make first contribution on this project

How I plan on tackling this issue Perform the necessary migrations and be sure to work on feedback & recommendations. Can deliver with a day upon assignment

ChrisFernandezVivas commented 12 hours ago

hi , im from dojo coding, I can take this issue, is only convert to soroban env :) for be honest I don't know about soroban coding languages but I can learn about that

Gerson2102 commented 12 hours ago

Hey! I'm Gerson. 👋

Member of Dojo Coding. I have contributed before to other Rust projects like:

Can I work on this issue?

Check my OnlyDust profile, I've contributed to many projects: Profile


Plan to Solve the Issue:

  1. Study the codebase to understand the current structure and functionality.
  2. Understand the problem that needs to be solved by thoroughly reading the issue details.
  3. Leverage all provided resources within the issue to get a better grasp of the task at hand.
  4. If I encounter roadblocks, I will ask questions ASAP in the Telegram group to move forward effectively.
  5. I will open a PR and wait for ur feedback

josephpdf commented 11 hours ago

Hi!, my name is Joseph Poveda. I am a student of the Systems Programming degree, I am a recent member of the Dojo Coding community, where I am getting started in the world of Web3. I have basic knowledge of different programming languages ​​and thanks to this I hope to be able to resolve the issue. To migrate the Semaphore Groups contract to Soroban, follow these steps:

Analyze the Original Contract: Review the functionalities in SemaphoreGroups.sol and ISemaphoreGroups.sol from the provided links, understanding group management, permissions, and events in Ethereum.

Get Familiar with Soroban: Learn Soroban's SDK and libraries, as its syntax and features may differ from Ethereum.

Port the Code: Adapt the group creation and management functionalities to Soroban, keeping its unique structure in mind.

Testing: Develop unit tests in Soroban to ensure the migrated contract works as expected.

martinvibes commented 11 hours ago

I'd like to take this issue.

1. Key Components:

1. Main Functions to Migrate:

3. Technical Requirements:

KoxyG commented 11 hours ago

Hi @bitfalt @evgongora,

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

Background and Relevant Experience

My name is Koxy, a blockchain Rust developer and Stellar ecosystem contributor. I’m the creator of the YouTube series Let’s Get Soroban, where I delve into hands-on development with Rust and the Stellar platform.

With a strong background in open-source development and a deep familiarity with Stellar’s architecture, I’m well-positioned to undertake the migration of the Semaphore Groups contract to Soroban.

I’m excited to implement immediate solutions and collaborate with the team on long-term improvements to enhance the Semaphore protocol.

Approach to Tackling This Issue

To address this migration, I plan to:

  1. Implement a Trait for SemaphoreGroups: Develop a trait and implement it to create a compatible contract for the Soroban platform.

  2. Thorough Testing: Write comprehensive tests that cover a wide range of scenarios, including edge cases. As i proposed here.

  3. Update Documentation: Revise CLI documentation and help messages to reflect the changes accurately.

  4. Submit PR: Create a detailed pull request with explanations of the changes and their rationale.

  5. Collaborate and Iterate: Work closely with maintainers to incorporate feedback and refine the solution as necessary.

This is a sample contract written in soroban.


Thank you for your consideration. Looking forward to contributing!