Ton Php Laravel Package

Product Decisions This Supports

• Blockchain Integration Roadmap: Enables PHP-based applications to interact with The Open Network (TON) natively, reducing reliance on JavaScript/Node.js for blockchain operations. Ideal for:

  • DeFi platforms needing TON wallet support (e.g., token transfers, smart contract interactions).
  • Gaming/metaverse projects leveraging TON for in-game assets or NFTs.
  • Enterprise blockchain solutions requiring PHP backend compatibility with TON’s ecosystem.

• Build vs. Buy: Buy for teams lacking blockchain expertise or time to build a custom TON SDK. Build only if needing deep customization beyond this package’s scope (e.g., non-standard wallet versions).

• Use Cases:

  • Wallet-as-a-Service (WaaS): Integrate TON wallets into PHP apps (e.g., user authentication, micropayments).
  • Smart Contract Deployment: Interact with TON smart contracts via WalletV4R2 and InternalMessage.
  • TON Blockchain Explorer: Fetch/parse TON blockchain data using the typed toncenter client.
  • Cross-Chain Bridges: Combine with amashukov/eth-php for TON-Ethereum interoperability.

When to Consider This Package

Adopt if:

• Your PHP app needs direct TON blockchain interaction (e.g., wallets, contracts, transactions).
• You require canonical BOC encoding (byte-exact compatibility with @ton/core).
• Your team prefers pure PHP (no Node.js dependencies) and minimal external libraries (only gmp, sodium, bcmath).
• You’re using TON’s Wallet v4R2 or need a typed toncenter client.
• You want a single composer require for the full TON stack (cells, crypto, wallets, RPC).

Look elsewhere if:

• You need TON support in a non-PHP language (e.g., Python, Go).
• Your project requires legacy wallet versions (e.g., Wallet v3) not covered here.
• You’re constrained by PHP 8.3+ (or lack gmp/sodium extensions).
• You prioritize community adoption (this package has 0 stars; olifanton/ton is more mature but lacks canonical BOC).
• You need Symfony integration (use blockchain-context-bundle instead).

How to Pitch It (Stakeholders)

For Executives: "This package lets us integrate TON blockchain functionality into our PHP backend with a single dependency. It covers wallets, transactions, and smart contracts—enabling features like in-app TON payments or NFT minting without relying on external APIs or JavaScript. The canonical BOC encoder ensures compatibility with TON’s core libraries, and the typed toncenter client reduces integration risk. Given TON’s growing ecosystem (e.g., DeFi, gaming), this gives us a competitive edge in blockchain-native products."

For Engineering: *"We’re adding a pure-PHP TON SDK that bundles:

• Canonical BOC encoding (matches @ton/core byte-for-byte).
• Wallet v4R2 support with Ed25519 crypto and TON mnemonics.
• Typed toncenter client for reliable RPC interactions.
• Zero blockchain-library dependencies (only PHP extensions: gmp, sodium, bcmath).

This replaces ad-hoc TON integrations with a maintained, composable stack. Tradeoff: Early-stage package (0 stars), but PHPStan L9 and parity tests ensure quality. Alternative: olifanton/ton (more stars) but lacks canonical BOC. Recommend this for new TON projects or if we need strict BOC compatibility."*

For Developers: *"Need to interact with TON from PHP? This SDK gives you: ✅ Cells/BOC: Build/parse TON messages with @ton/core-compatible encoding. ✅ Wallets: Full WalletV4R2 support with Ed25519 signing and TON mnemonics. ✅ RPC: Typed toncenter client for seqno checks, transfers, etc. ✅ No Glue Code: ToncenterWalletRpc implements WalletRpcInterface—just plug it in.

Example workflow:

$wallet = new WalletV4R2($keyPair, $address);
$rpc = new ToncenterWalletRpc(new ToncenterClient($httpClient));
$wallet->setRpc($rpc); // Auto-fetches seqno, broadcasts signed txs.

Requirements: PHP 8.3+, gmp, sodium, bcmath. Pair with amashukov/http-client-php for HTTP."*