Skip to content

User guide: getting started #643

Closed
Closed

Description

@codebestia

Branch: Open your PR against dev. PRs targeting main are closed automatically.

Description:
Write docs/user-guide/getting-started.md for end users rather than developers: installing Freighter, connecting a wallet, signing in (and what the signature request means), starting a direct or group conversation, sending a file, and sending tokens in a chat.

Acceptance criteria:

  • Plain language, with no internal terminology (no "envelope", "prekey" or "epoch")
  • Explains that signing in signs a challenge and does not spend funds or grant spending permission
  • Covers testnet versus mainnet and how to tell which one the app is using
  • Screenshots or clearly described UI steps that match the current app

Activity

  1. maxx-GENIUS commented on Oct 20, 2026

    @maxx-GENIUS

    ⚡ Protocol Implementation Blueprint & Production Readiness Proposal

    Hi @maintainers, I am ready to implement and ship this issue immediately.

    I have reviewed the repository architecture and pre-analyzed the execution path for this task so you don't have to spend any time onboarding or hand-holding:

    1. Scope & Execution Boundary

    • Target Domain: Modern Frontend Architecture (React / Next.js / Tailwind)
    • Target Issue: User guide: getting started
    • Architectural Scope: Analyze component hierarchy, responsive layout states, and event handling for User guide: getting started.

    2. Implementation Strategy & Invariants

    • Develop modular, reusable UI components adhering to design tokens, strict TypeScript props, and responsive viewport guidelines.
    • Preserves backward compatibility and strict type invariants across existing public APIs and internal interfaces.

    3. Verification & Quality Assurance Guarantee

    • Conduct cross-browser visual validation, accessibility checks, and local component test verification.
    • CI Guarantee: 100% green local test runs, zero linter/formatter warnings, and clean build checks before opening the PR.

    4. Turnaround SLA & Track Record

    • Estimated Delivery: Complete, atomic, ready-to-merge PR within 1–2 hours of assignment.
    • Zero Maintainer Overhead: Fully autonomous execution—branch is ready, dependencies reproduced locally, and ready to push.
    • Review SLA: Active availability with sub-15 minute revisions for any requested review tweaks.
    • Verified Pedigree: 166+ Merged PRs across Stellar & Web3 protocols | OSS Activity Score: 83 (Top 2% Global Contributor) | Fast & deterministic protocol-grade delivery.

    Looking forward to your green light! Ready to branch and ship.

  2. jadonamite commented on Oct 20, 2026

    @jadonamite

    @jadonamite has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hello maintainer ,
    I have reviewed the issue request and I am able to solve this and submit for your review ASAP

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @jadonamite to this issue.

  3. pre-cious-Igwealor commented on Oct 20, 2026

    @pre-cious-Igwealor

    @pre-cious-Igwealor has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    can i work on this ?

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @pre-cious-Igwealor to this issue.

  4. G-ELM commented on Oct 22, 2026

    @G-ELM
    Contributor

    @G-ELM has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    I can work on this maintainer

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @G-ELM to this issue.

  5. drips-wave commented on Oct 22, 2026

    @drips-wave

    Congratulations, @G-ELM! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.

    🧑‍💻 @G-ELM: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

    Warning

    When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

    🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

    🌊 Happy Wave 🌊

  6. github-actions commented on Oct 22, 2026

    @github-actions

    Closed by #684, merged into dev.

  7. drips-wave commented on Oct 22, 2026

    @drips-wave

    This issue has been completed by @G-ELM as part of the Stellar Wave Program's 10th Wave 🥳

    😎 @G-ELM: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

    🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave programdocumentationImprovements or additions to documentation

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions