Blockchain Context Bundle Laravel Package

Product Decisions This Supports

• Multi-chain crypto payment infrastructure: Enables seamless integration of TON (The Open Network) and EVM (Ethereum-compatible) chains (e.g., Ethereum, Polygon, BSC) into a Symfony application, reducing development time for cross-chain deposit detection, transaction building, and verification.
• Build vs. Buy: Buy—avoids reinventing blockchain SDK integration, RPC clients, and security layers (e.g., key encryption, signature verification). The bundle abstracts low-level complexity (e.g., EIP-1559 signing, TON Connect wallets) into reusable services.
• Roadmap priorities:
  • Phase 1: Launch a crypto payment gateway (e.g., fiat-to-crypto onramps) with TON + ETH/USDT support.
  • Phase 2: Extend to other EVM chains (e.g., Arbitrum, Avalanche) by leveraging the bundle’s tagged-iterator chain pattern (add new builders without DI refactoring).
  • Phase 3: Integrate with decentralized identity (e.g., verify signatures from TON Connect or MetaMask via SignatureVerifier).
• Use cases:
  • Crypto merchant services: Detect deposits (TON/Jetton/ERC20) and auto-credit user balances.
  • Cross-chain bridges: Build transactions for asset transfers between TON and EVM (e.g., USDT-Jetton ↔ USDT-ERC20).
  • Regulated compliance: Encrypt private keys at rest (AES-256-GCM) and log deposit evidence for audits (DepositEvidence).
  • Gas optimization: Fetch real-time gas prices per chain (EthGasFetcher, TonGasFetcher) to minimize fees.

When to Consider This Package

• Adopt if:

  • Your Symfony 7 app needs TON + EVM blockchain integration with minimal boilerplate (e.g., RPC clients, wallets, signature verification).
  • You require type-safe, autowired services (e.g., JsonRpcProviderInterface, ToncenterClientInterface) to avoid manual DI setup.
  • You want to support multiple chains (e.g., TON, Ethereum, Polygon) with a consistent API (extend via tagged services).
  • Security is critical: AES-256-GCM key encryption and EIP-191/Ed25519 signature verification are pre-built.
  • You’re building crypto payments, bridges, or DeFi infrastructure and need deposit detection (ChainDepositCheckChain) or transaction finality checks (FinalityVerifier).

• Look elsewhere if:

  • You need non-PHP languages (e.g., Node.js, Rust) or existing SDKs (e.g., Web3.js, Ethers.js).
  • Your stack isn’t Symfony 7 + PHP 8.3+ (e.g., Laravel, SvelteKit).
  • You require enterprise-grade support (package has 0 stars/dependents; evaluate risk).
  • You need Layer 2 solutions (e.g., Arbitrum, Optimism) beyond EVM/TON—extendability depends on community adoption.
  • You prioritize audited code over MIT-licensed open-source (no formal audits disclosed).

How to Pitch It (Stakeholders)

For Executives:

*"This bundle lets us launch crypto payments faster by eliminating the 3–6 months of engineering work typically required to integrate TON and EVM chains. It provides:

• Pre-built infrastructure for deposit detection (TON/Jetton/ERC20), transaction signing, and gas optimization—reducing dev time by 70%.
• Security out of the box: Private keys are encrypted with AES-256-GCM, and signatures are verified via EIP-191/Ed25519 (critical for compliance).
• Scalability: Add support for new chains (e.g., Polygon, Avalanche) by dropping in a new service—no DI refactoring needed.
• Cost savings: Avoids licensing fees for proprietary SDKs while maintaining MIT’s permissive license. For our crypto payment gateway, this means we can focus on UX and partnerships instead of reinventing blockchain plumbing."

For Engineering:

*"This is a Symfony-native blockchain toolkit that:

• Autowires typed RPC clients (JsonRpcProvider, ToncenterClient) and security services (SignatureVerifier, PrivKeyEncrypter)—no manual setup.
• Standardizes cross-chain logic (e.g., deposit checks, gas estimation) via tagged-iterator chains, so adding a new chain is a matter of implementing an interface.
• Handles edge cases we’d otherwise debug (e.g., TON finality polling, EIP-1559 transaction building).
• Integrates seamlessly with Symfony’s DI system—just inject EthRpcClient or TonWallet where needed. Tradeoff: Early-stage package (0 stars), but the code quality (PHPStan L9, CI/CD) and modular design make it production-ready for our use case. If we hit limits, we can fork or extend it."*