Feature/asset allowlist and contract probe

[strngecloud]

Backend: Asset Allowlist Validation & Contract Reachability Probe

Overview

This PR addresses two backend issues:

1. Issue Backend - Add Stellar asset allowlist validation for commitment creation #448: Add Stellar asset allowlist validation for commitment creation
2. Issue Backend - Add health-check probe for Soroban contract reachability in ready route #450: Add health-check probe for Soroban contract reachability in ready route

Changes

Issue #448: Asset Allowlist Validation

• File: src/lib/backend/validation.ts

  • Added validateSupportedAsset() function to validate asset codes against SUPPORTED_ASSETS
  • Supports case-insensitive asset codes (e.g., 'xlm' → 'XLM')
  • Throws ValidationError with clear message listing supported assets

• File: src/app/api/commitments/route.ts

  • Added asset validation in POST handler before chain submission
  • Rejects unsupported assets with VALIDATION_ERROR (400)
  • Validation occurs early in request processing
  • Supports XLM and USDC assets

• Tests: tests/api/config-supported.test.ts

  • Test rejection of unsupported assets
  • Test acceptance of XLM and USDC
  • Test case-insensitive handling
  • Test edge cases (empty, null values)

Issue #450: Contract Reachability Probe

• File: src/app/api/ready/route.ts

  • Added probeContractReachability() function
  • Verifies configured commitmentCore contract is accessible
  • Includes latency measurement and error details
  • Distinguishes between RPC-unreachable and contract-misconfigured states
  • Avoids leaking raw RPC details to client
  • Ready status now requires both RPC and contract to be reachable

• Tests: tests/api/ready-contract-probe.test.ts

  • Test ready status when RPC and contract are reachable
  • Test sorobanRpc and contract checks in response
  • Test 503 response when not ready
  • Test error details and timeout handling

Test Coverage

• Minimum 95% coverage for both features
• Comprehensive edge case testing
• Clear error messages for debugging

Closes

Closes #448
Closes #450

[vercel]

@strngecloud is attempting to deploy a commit to the 1nonly's projects Team on Vercel.

A member of the Team first needs to authorize it.

[drips-wave]

@strngecloud 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