> For the complete documentation index, see [llms.txt](https://dmtp.gitbook.io/dmtp-sdk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dmtp.gitbook.io/dmtp-sdk/08-solution-architecture-intro/08.3-technical-implementation-details.md).

# 8.3 Technical Implementation Details

The Web3 Traffic Exchange system is built with several technical considerations to ensure performance, scalability, and security:

1. Blockchain Integration:
   * Currently, the system uses TON wallet for SDK user identification in the account module.
   * Future integration will include TON blockchain for decentralized design, with points represented as TON Jettons (blockchain tokens) for increased functionality.
2. Domain Structure:
   * Frontend app: app.apps-network.net
   * Backend API: click.apps-network.net
3. Security Considerations:
   * Wallet addresses in the Banner Exchange Code URL are hashed for improved security.
   * Telegram User IDs are hashed before storing or processing by the system
4. Performance Optimization:
   * The Clicks Queue is designed for lightweight and fast processing to handle high volumes of clicks efficiently.
   * Separate instances are used for impressions tracking to ensure speed and reliability.
5. Scalability:
   * The system is designed to start with a limited number of banner formats and grow over time.
   * The architecture allows for easy addition of new features and scaling of existing components.