Ton Cell Php Laravel Package

Product Decisions This Supports

• Build vs. Buy: Buy – Eliminates the need to maintain a custom TON cell/BOC implementation or rely on Node.js interop (e.g., shelling out to tonos-cli or @ton/core). Reduces technical debt and aligns with @ton/core v15’s canonical format.
• Feature Expansion: Enables native PHP support for TON smart contract interactions (e.g., Jetton transfers, NFT minting, or custom contract messages) without leaving the PHP ecosystem.
• Roadmap Priorities:
  • Wallet-as-a-Service (WaaS): Integrate with amashukov/ton-wallet-php to build PHP-based TON wallets (e.g., for e-commerce, DeFi, or gaming).
  • Blockchain Backend Services: Power PHP microservices for TON (e.g., payment processing, oracle feeds, or DAO voting).
  • Interoperability: Bridge PHP apps with TON via canonical BOC serialization, ensuring compatibility with TON Indexer, TonCenter, or other TON tools.
• Use Cases:
  • Jetton/NFT Transfers: Build PHP APIs for token movements (e.g., transferJetton messages).
  • Contract Deployment: Generate and sign BOCs for deploying TON smart contracts from PHP.
  • Off-Chain Data: Parse TLB-encoded data (e.g., contract events) in PHP without Node.js dependencies.
  • Hybrid Apps: Use alongside toncenter-client-php for a full-stack PHP/TON solution.

When to Consider This Package

• Adopt if:

  • Your PHP app interacts with TON (e.g., wallets, DeFi, NFTs) and you want to avoid Node.js interop (e.g., no exec() calls to tonos-cli or @ton/core).
  • You need byte-exact parity with @ton/core v15 for BOC serialization (critical for contract compatibility).
  • Your team lacks TypeScript/Python expertise but needs to work with TON’s TLB format.
  • You’re building a PHP-first blockchain service (e.g., a TON payment processor or oracle) and want to minimize dependencies.

• Look elsewhere if:

  • You’re using Python/TypeScript/Java and already have @ton/core or pytonlib support.
  • Your use case is read-only (e.g., querying TON via JSON-RPC), and you don’t need to construct or sign BOCs.
  • You require active maintenance (package has 0 stars/dependents; vet for long-term viability).
  • Your PHP version is <8.3 (requires ext-gmp).
  • You need full wallet functionality (pair with amashukov/ton-wallet-php or use a higher-level SDK like ton-php).

How to Pitch It (Stakeholders)

For Executives:

"This package lets us build TON smart contract interactions natively in PHP, eliminating the need for Node.js sidecars or custom implementations. By using a byte-exact replica of @ton/core, we ensure our BOCs (TON’s binary format) are compatible with the entire ecosystem—wallets, explorers, and other contracts. This reduces latency, simplifies deployment, and opens doors for PHP-based TON services like wallets, payment processors, or DeFi integrations. The MIT license and modular design make it a low-risk addition to our stack."

For Engineering:

*"Problem: PHP apps interacting with TON either shell out to Node.js (slow, fragile) or reinvent the TLB cell/BOC wheel (error-prone, non-canonical). Solution: amashukov/ton-cell-php gives us:

• Fluent builders/slices for constructing/parsing TLB data (e.g., Jetton transfers, contract messages).
• Canonical BOC serialization (matches @ton/core v15, no compatibility issues).
• Bigint support via ext-gmp (handles TON’s large integers like coins).
• No dependencies, just PHP 8.3+ and ext-gmp. Use Cases:
• Build PHP APIs for TON transactions (e.g., transferJetton).
• Sign BOCs for contract deployment without Node.js.
• Parse TLB-encoded events in PHP. Tradeoffs:
• Early-stage package (0 stars, but PHPStan L9 + parity tests).
• Requires ext-gmp (common in PHP blockchain stacks). Next Steps: Pair with ton-wallet-php for wallets or toncenter-client-php for RPC. Vet for long-term maintenance needs."*

Key Ask: "Should we prototype this for [specific use case, e.g., Jetton payments] and evaluate against alternatives like Node.js interop?"