Cross-Contract Authorization Setup

[Mkalbani]

Description

Implement the cross-contract authorization pattern so that settlement can call escrow.release() and registry.record_contribution() securely. Contract addresses must be set at deploy time and enforced at runtime.

Acceptance Criteria

• Each contract stores the address of its authorized caller in persistent storage at initialization
• Runtime checks verify env.invoker() matches stored authorized address
• Admin can update authorized addresses post-deploy via a guarded function
• Tests simulate cross-contract calls using soroban-sdk test environment
• Document the deploy order and address wiring in scripts/deploy.sh

Technical Notes

• Soroban cross-contract calls use ContractClient generated types
• Refer to [Soroban auth model](https://soroban.stellar.org/docs/fundamentals-and-concepts/authorization) for require_auth() patterns

[2411015047-afk]

Hi! I can implement the cross-contract authorization pattern for your mesh-contract project.

I have experience with:

• Soroban contract-to-contract authorization patterns
• Persistent storage for contract address management
• Secure runtime checks with env.invoker()

This is a well-defined task. Would you like to hire this out? I can deliver a clean implementation with tests.