[Docs] ARCHITECTURE.md documents wrong backend env var name (STREAMING_CONTRACT_ADDRESS vs STREAM_CONTRACT_ID)

[grantfox-oss]

Telegram (ask questions / claim the issue here first): https://t.me/+DOylgFv1jyJlNzM0

Why this matters

docs/ARCHITECTURE.md (Required Environment Variables, ~line 224) lists STREAMING_CONTRACT_ADDRESS as the deployed contract ID var, but the code only ever reads STREAM_CONTRACT_ID (soroban-event-worker.ts:87, sorobanService.ts:5, soroban-indexer.service.ts:30, health.routes.ts:62) - there is no STREAMING_CONTRACT_ADDRESS anywhere in backend/src. Following the doc silently leaves the indexer disabled. Same table also writes STELLAR_NETWORK values as TESTNET/MAINNET uppercase while code uses lowercase testnet.

Acceptance criteria

• Rename STREAMING_CONTRACT_ADDRESS to STREAM_CONTRACT_ID in docs/ARCHITECTURE.md and match backend/.env.example
• Use the lowercase STELLAR_NETWORK casing (testnet/mainnet) consistent with the code
• Cross-check the table against backend/.env.example so var names match what the code reads

Files to touch

• docs/ARCHITECTURE.md
• backend/.env.example
• backend/src/workers/soroban-event-worker.ts

Out of scope

• Frontend NEXT_PUBLIC_* var documentation (separate issue)

[OluRemiFour]

I've reviewed the task and have a clear implementation plan. Looking forward to contributing with a quality PR.

[Dennis-Ritchie1]

@Dennis-Ritchie1 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi maintainers, I'd like to work on this issue.

I'm a Full Stack Developer with experience across the entire stack — from pixel-accurate frontend UIs to scalable backend APIs and database design. I've shipped production-ready features using Next.js/React + Tailwind on the frontend, and Node.js/Express, PostgreSQL, and REST/GraphQL APIs on the backend.

What I'll deliver

• Component/feature implemented to match the design/spec
• Responsive behavior (mobile + desktop), no layout breakage
• Hover/focus states + accessible semantics
• Clean, reusable components and consistent styling
• RESTful or GraphQL API endpoints (if applicable)
• Database schema design or migrations (if applicable)
• Authentication, authorization, and data validation where needed

Approach

1. Review the design/spec, existing code patterns, and any relevant API contracts
2. Build the UI + interactions on the frontend
3. Implement or update backend logic, routes, and data models as needed
4. Write unit/integration tests for critical paths
5. QA on multiple breakpoints + open a PR with screenshots/video and a summary of backend changes

Stack
Frontend: Next.js · React · TypeScript · Tailwind CSS
Backend: Node.js · Express · PostgreSQL · Prisma / Drizzle
Infra: REST · GraphQL · JWT Auth · Docker · Vercel / Railway

If assigned, I'll start immediately and share progress updates in the PR.

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

[DeePrincipal-dev-lang]

@DeePrincipal-dev-lang has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi, I'd like to work on this issue. I'm a prompt engineer, detail-oriented, reliable, and comfortable delivering quality work on time. I've reviewed the issue and I'm confident I can handle it. Please assign it to me, I'm ready to get started.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @DeePrincipal-dev-lang to this issue.

[Kenisank]

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

Hi maintainer, I would like to work on this issue.

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

[dinahmaccodes]

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

Hello maintainer, my name is Dinah and I am a solid developer.
I can work on this and solve the problem easily.
Can I be assigned this issue??

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

[grantfox-oss]

🦊 GrantFox — @dinahmaccodes has been assigned to this issue!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #900)
2. Your PR will be reviewed by the LabsCrypt maintainers

Good luck! Track your progress on GrantFox.

[drips-wave]

Congratulations, @dinahmaccodes! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @dinahmaccodes: 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 🌊

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@dinahmaccodes's PR #909 was approved and merged by @ogazboiz.

🏆 @dinahmaccodes: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (83 total points). Track your full progress on GrantFox.

👏 Great work, @dinahmaccodes! Keep contributing to LabsCrypt.

[drips-wave]

This issue has been completed by @dinahmaccodes as part of the Stellar Wave Program's 6th Wave 🥳

😎 @dinahmaccodes: You earned 200 Points for completing this issue! After the current Wave ends, 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.