[devJaja]

Summary

Fixes four related configuration/environment issues in one atomic change.

---

#980 — Require SOROBAN_RPC_TIMEOUT_MS to be less than SOROBAN_POLL_INTERVAL_MS

The schema comment already said to keep the RPC timeout below the poll interval, but nothing enforced it. A hung RPC call that spans multiple poll cycles silently blocks event ingestion.

• Added Joi.less(Joi.ref('SOROBAN_POLL_INTERVAL_MS')) to SOROBAN_RPC_TIMEOUT_MS
• Clear startup error message when the constraint is violated
• Tests: equal value → fail, greater value → fail, defaults (4000 < 5000) → pass

---

#979 — Validate AUTO_RELEASE_SOURCE_ADDRESS with the Stellar checksum

The previous /^G[A-Z2-7]{55}$/ regex accepted shape-valid but checksum-invalid keys. A typo with a bad checksum would boot fine and then fail on every auto-release attempt on chain.

• Replaced regex with stellarPublicKey.optional() — same helper used by ADMIN_ADDRESS
• Calls Keypair.fromPublicKey (checksum verified, not just shape matched)
• Tests: checksum-invalid key → rejected, secret key supplied → rejected, valid key → passes, omitted → passes

---

#976 — Make access token lifetime configurable via ACCESS_TOKEN_TTL

REFRESH_TOKEN_TTL was already a validated env var. The access token lifetime was a hard-coded constant JWT_EXPIRY_SECONDS = 3600, so operators could not shorten it for higher-security deployments.

• Added ACCESS_TOKEN_TTL to configValidationSchema (integer >= 1, default 3600)
• sep10.service.ts reads configService.get('ACCESS_TOKEN_TTL') instead of the constant
• Documented in .env.example
• Tests: default = 3600, custom value coerced, zero → rejected, non-numeric → rejected

---

#977 — Remove process.env bypasses inside the NestJS DI container

Values read directly from process.env inside DI-managed services skip Joi validation, coercion, and defaults. This affected three services:

Location	Variable(s)	Fix
PrismaService	QUERY_TIMEOUT_MS, SLOW_QUERY_THRESHOLD_MS	Accept ConfigService as optional second constructor arg; PrismaModule passes it in
CacheService	REDIS_URL fallback	Removed ?? process.env.REDIS_URL; relies on configService.get exclusively
JwtGuard	SEP10_JWT_SECRET fallback	Removed ?? process.env.SEP10_JWT_SECRET; fails closed when no ConfigService

process.env fallbacks are intentionally kept only for the DATABASE_URL constructor path in PrismaService (which is called before full DI is wired), consistent with the AGENTS.md note.

---

What was tested

• soroban-config.spec.ts — 4 new tests for the timeout cross-field rule (all pass)
• config.module.spec.ts — 9 new tests for AUTO_RELEASE_SOURCE_ADDRESS checksum and ACCESS_TOKEN_TTL (all pass)
• Full affected spec suite: 122 tests pass across both files

Closes #976
Closes #977
Closes #979
Closes #980

[drips-wave]

@devJaja Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits