# Best practice for adding a new Ed25519 threshold-schnorr signer branch?

**URL:** <https://forum.dfinity.org/t/best-practice-for-adding-a-new-ed25519-threshold-schnorr-signer-branch/46972>\
**Category:** Rust\
**Created:** [May 6, 2025, 7:38am UTC](https://forum.dfinity.org/t/best-practice-for-adding-a-new-ed25519-threshold-schnorr-signer-branch/46972 "2025-05-06T07:38:43Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![rohansingh4](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/rohansingh4/32/19970_2.png) [@rohansingh4](https://forum.dfinity.org/u/rohansingh4)\
**Post date:** [May 6, 2025, 7:38am UTC](https://forum.dfinity.org/t/best-practice-for-adding-a-new-ed25519-threshold-schnorr-signer-branch/46972/1 "2025-05-06T07:38:43Z")

</div>

Hello everyone,  
I’m preparing my first open-source contribution to the DFINITY SDK and would love your guidance on the workflow:

- I have a working Ed25519 threshold-schnorr signer implementation for Stellar and Solana.
- I’ll soon finish support for Hedera and SUI.

Should I simply create a new feature branch (e.g. `threshold-schnorr-ed25519`) off the main repo and open a pull request there, or is there a preferred branching strategy or repository layout I should follow?

Thank you in advance for any pointers or contribution guidelines!