-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement wallet connection for Stellar #52
Comments
@Marchand-Nicolas |
Please let me do this, sir. ETA 3 days |
Gm dev. I have thoroughly read the task and it's requirements and I can do this within the specified time frame if given the chance. I'm Pascal, and I'm already in the tg. I'll keep in touch |
Hi, I can solve this Let me handle this task |
@Marchand-Nicolas |
@Marchand-Nicolas |
Would love to take this on? |
Let me handle this issue! |
Hello @Marchand-Nicolas, I'm Josué Soto, from Dojo Coding How can I plan to solve it? Technical Solution:
interface WalletConnector {
connect(): Promise<string>; // Returns wallet address
disconnect(): Promise<void>;
}
class StellarWallet implements WalletConnector {
// Implementation using Stellar SDK
}
class StarknetWallet implements WalletConnector {
// Implementation using existing Starknet logic
}
const getWalletConnector = (chain: string): WalletConnector => {
switch (chain) {
case 'stellar':
return new StellarWallet();
case 'starknet':
return new StarknetWallet();
default:
throw new Error(`Unsupported chain: ${chain}`);
}
}; ETA 3 days Following Open Source Guidelines:
Regards |
Is it okay if I take this? |
Can I contribute to this one? |
Would love to tackle this! |
I’d love to work on this task. I’m a full-stack blockchain developer with over 3 years of experience working with Tailwind, React, TypeScript, and Solidity/Rust. I handle this issue? |
My backgroundI'm a software engineer and passionate about solving problems, I've been contributing to open source software for a few months and it's an experience that has taught me a lot and I really like to contribute to other projects. I am a member of the Dojo Coding community⛩️. I will dedicate all my effort to complete this issue in the best way. |
Holla i'm Vestor, I'm an experienced frontend developer and a smart contract developer and i would love to take on this issue. |
Holla i'm Martin, I'm a frontend developer who enjoys building smooth applications to pixel perfect and engaging websites using JavaScript, typescript and frameworks(React, nextjs, tailwindcss etc.) and i have contributed to other projects that have been merged. |
May I handle this issue? |
Can I work on this, please? |
Can I take this issue? |
Can I try solving this issue? |
Can I start working on this? |
On it |
Description 📹
Implement wallet connection for the Stellar chain in
pages/verify/[discordServerId]/[discordMemberId]/[customLink].tsx
. Add support for Stellar Testnet & Stellar Mainnet by showing a Stellar wallet connect popup if the expected network is Stellar. For other chains, show the Starknet wallet popup. Ensure the solution is clean and scalable to accommodate additional chains in the future.Proposed Actions 🛠️
Here’s a checklist of actions to follow for resolving this issue:
Fork the repository and create a new branch using the issue number:
Implement Changes:
Add Stellar Testnet and Stellar Mainnet to
configs/networks.json
with the new "chain" field:Update
pages/verify/[discordServerId]/[discordMemberId]/[customLink].tsx
to:networks.json
.chain
field for the current network."stellar"
, show the Stellar wallet connect popup."starknet"
, show the Starknet wallet connect popup.Create separate reusable functions/components for:
Ensure the code is clean and adheres to scalable design principles.
Run Tests and Commit Changes:
Make sure your changes don't break existing functionality and commit with a clear message:
git commit -m "Fix: Implement Stellar wallet connection with scalable multi-chain support"
Required 📋
To keep our workflow smooth, please make sure you follow these guidelines:
Thank you for your contribution 🙏
The text was updated successfully, but these errors were encountered: