Analysis & roadmap: TON-Bridge V2 (53 issues + Phase 6 affiliate program, closes #1)#2
Conversation
Adding .gitkeep for PR creation (default mode). This file will be removed when the task is complete. Issue: #1
Per issue #1, analyze the TON-Bridge mini-app structure (Finapp-based static TMA wrapping ChangeNOW iframes) and propose a step-by-step improvement roadmap across 5 phases: foundations, Telegram-native UX, performance/PWA, product surface, virality, and trust. No application code is touched in this change.
Solution summaryDone. The issue explicitly asked for analysis and proposals only β no code changes β so I:
PR: #2 This summary was automatically extracted from the AI working session output. |
π€ Solution Draft LogThis log file contains the complete execution trace of the AI solution draft process. π° Cost: $1.016924π Context and tokens usage:
Total: (70.9K + 623.1K cached) input tokens, 10.8K output tokens, $1.016924 cost π€ Models used:
π Log file uploaded as Gist (539KB)Now working session is ended, feel free to review and add any feedback on the solution draft. |
β Ready to mergeThis pull request is now ready to be merged:
Monitored by hive-mind with --auto-restart-until-mergeable flag |
This reverts commit d44c05f.
|
Well, now we are doing the following. Based on this analysis and suggestions, in 38 step-by-step tasks in 5 phases, you will create a separate complete professional and detailed issue for each task in this repository, so that we can implement all these tasks to get a new mini V2 application, you can also think about using an affiliate program for working in a mini Telegram application (earn internal points that can then be exchanged for a TBC token from TONBANKCARD) look, our arithmetic is such that we receive a commission from each exchange as a service of 0.4% and we can share as once within the framework of the single-level ref system from 0.1 to 0.2%, that is, we need to calculate the turnover in USD during exchanges and add internal points to the balance of the user who makes the exchange, they will then change 10 points for 1 TBC token. (the token rate is now $ 0.0003) think through all the arithmetic and logic of this proposal. |
|
π€ AI Work Session Started Starting automated work session at 2026-04-29T22:04:41.348Z The PR has been converted to draft mode while work is in progress. This comment marks the beginning of an AI work session. Please wait for the session to finish, and provide your feedback. |
- IMPROVEMENTS.md: add Phase 6 (TBC points + single-level referrals) with Β§6.0 Economic model & arithmetic (point award formula, house economics, worked examples, redemption math) and Β§6.1 roadmap items 6.1β6.12. Cross-link every Phase 0β6 task to its tracking issue (#3 through #55) and extend Β§4 Out of scope to exclude MLM-style referrals and TBC token issuance. - .gitignore: ignore .issue-bodies/ workspace and node_modules.
π€ Solution Draft LogThis log file contains the complete execution trace of the AI solution draft process. π° Cost: $5.092420π Context and tokens usage:Claude Opus 4.7: (2 session segments)
Total: (256.2K + 2.5M cached) input tokens, 89.7K output tokens, $5.092420 cost π€ Models used:
π Log file uploaded as Gist (1850KB)Now working session is ended, feel free to review and add any feedback on the solution draft. |
β Ready to mergeThis pull request is now ready to be merged:
Monitored by hive-mind with --auto-restart-until-mergeable flag |
Three modules called Telegram.WebApp.CloudStorage methods without
catching synchronous throws, which crashed the page on Telegram WebApp
< 6.1 (CloudStorage object exists but methods raise
WebAppMethodUnsupported). Gate behind isVersionAtLeast('6.1') and wrap
calls in try/catch so unsupported clients fall back to localStorage:
* assets/js/prefs.js β migrate() now always resolves; csGet/csSet/
csRemove catch synchronous throws and reject cleanly.
* assets/js/achievements.js β loadStats/saveStats fall back via a
shared cloudStorage() probe + localStorage fallback.
* assets/js/address-book.js β loadEntries/saveEntries probe the API
and catch throws around getItem/setItem.
AUDIT.md documents the audit done against issues #1, #2, and the
in-flight #115 work, plus the 6 follow-up GitHub issues it spawned
(#117β#122).
Summary
Closes #1.
This PR delivers two things requested by the owner:
IMPROVEMENTS.md: observed structure of the project, gaps, and 53 step-by-step proposed tasks across 6 phases.IMPROVEMENTS.mdcross-links to its tracking issue.The application code is not modified β issue #1 explicitly asked for an analysis-only PR. All implementation work happens in the 53 follow-up issues.
What's new in this revision
IMPROVEMENTS.mdwith the full arithmetic worked through (Β§6.0):floor(turnover_usd Γ bps / 10_000 / 0.00003)tbc_to_credit = floor(points / 10), minimum 100 pointsIndex of created issues
Phase 0 β Hygiene & foundations
.gitignore,package.json, and a Sass build scriptPhase 1 β Telegram Mini App best-practices
Telegram.WebApp.MainButtonfor the primary CTATelegram.WebApp.BackButtonto in-app navigationHapticFeedbackthemeParamsand pass theme through to ChangeNOWTelegram.WebApp.CloudStorageinitDataon a tiny backendBiometricManageropt-in for large OTC tradesTelegram.WebApp.SettingsButtonfor in-app settingsPhase 2 β Performance, PWA, offline
__manifest.json(real PWA manifest)unpkg.com/ioniconsCDNPhase 3 β Product surface beyond the iframe
Phase 4 β Virality & growth loops
shareToStoryafter a successful tradeswitchInlineQueryPhase 5 β Trust, security, accessibility, polish
<center>,<table>-for-layout, inline stylesPhase 6 β Affiliate program
referred_byonce and only onceindex4.html)Test plan
This PR is documentation only β there is nothing to execute. Reviewer checklist:
IMPROVEMENTS.mdΒ§ 1 (observed structure) β does it match what's actually in the repo?