Send TP is a high-speed on-chain messaging protocol designed for transferring tokenized value between multiple blockchains. By combining low-fee execution with verifiable proofs, it enables liquidity providers and developers to coordinate transfers across ecosystems securely.
Unlike simple bridge mechanisms, Send TP focuses on intent-centric routing, allowing users to specify destination chains and price thresholds while smart contracts handle settlement and fraud detection automatically.
Protocol Architecture at a Glance
| Component | Role in Send TP | Security Model | Typical Finality |
|---|---|---|---|
| Intent Relayer | Broadcasts user transfer intent and matches liquidity | Signed intent receipts with non-repetition nonce | 1–3 seconds indexing |
| Proof Aggregator | Collects Merkle and state proofs from source and destination chains | Consensus-weighted validator set | 5–15 seconds aggregation |
| Router Contract | Enforces path rules and releases reserved liquidity | On-chain invariant checks with slashing conditions | Finality at destination block confirmation |
| Oracle Price Feed | Provides real-time exchange rates and slippage bounds | Decentralized signers with heartbeat monitoring | Sub-second price updates |
Cross-Chain Routing Logic
Send TP routes transfers by decomposing a user request into atomic steps across source, bridge, and destination chains. The protocol evaluates multiple routes in parallel, selecting paths that meet user-defined price targets while minimizing settlement time.
Each route is scored on expected cost, estimated latency, and historical reliability. Validators continuously update route rankings, ensuring that newly surfaced opportunities can be selected without manual intervention.
Security and Slashing Framework
Security in Send TP is enforced through bonded validators who stake native tokens and run light nodes for each supported chain. Misbehavior such as withholding proofs or submitting invalid state transitions triggers automatic slashing, which is then redistributed to honest relayers and liquidity providers.
The protocol also incorporates timelocked challenges, allowing third parties to submit evidence of faults. This design maintains integrity even when some validators are offline or compromised, while keeping challenge windows short to preserve user confidence.
Developer Integration Patterns
Developers integrate with Send TP using modular SDKs that expose intent submission, status tracking, and receipt verification. These libraries abstract low-level proof handling and provide hooks for wallets, dApps, and custodial services.
Advanced integrations can leverage custom routing plugins and fee-splitting contracts, enabling teams to build branded transfer experiences without rebuilding core infrastructure from scratch. Detailed documentation and reference implementations accelerate time-to-market for new cross-chain products.
Operational Best Practices and Key Takeaways
- Always review route price and latency scores before submitting large transfers.
- Keep wallet gas reserves sufficient for both source and destination chain fees.
- Monitor dispute windows and retain proof receipts for cross-chain settlements.
- Use official SDKs to benefit from ongoing security audits and updates.
- Engage with community governance to influence fee structures and supported assets.
FAQ
Reader questions
How does Send TP differ from traditional bridges?
Send TP uses intent-centric routing and on-chain proofs to match user transfers across multiple liquidity sources, while traditional bridges typically rely on locked-and-minted models with limited path optimization.
Can I set my own price impact limits when sending TP?
Yes, users define maximum slippage and acceptable price deviation directly in the transfer intent, and the protocol will only execute routes that satisfy those thresholds.
What happens if a validator submits a false proof during a TP send?
Bonded validators risk having their stakes slashed for invalid proofs, and disputed routes are challenged through a timelocked process that rewards whistleblowers with a portion of the slashed funds.
Which chains and tokens are currently supported by Send TP?
The protocol natively supports major L1 and L2 chains with ERC-20 and SPL token adapters, and new chains can be added through community governance proposals that adjust routing fees and security parameters.