Releases: nessshon/token-access-control-bot
v0.1.0
v0.0.9
What's Changed
- string without a thousand separator by @inozemtsev-roman in #14
Full Changelog: v0.0.8...v0.0.9
v0.0.8
What's Changed
- Added Alembic for DB migrations.
- Added
decimalscolumn totokenstable for improved compatibility.
Note: To update, runalembic upgrade headto apply migrations.
Important: Remove old tokens and add new ones. - Updated aiogram-tonconnect: Replaced pythonconnect with tonutils Ton Connect library.
Full Changelog: v0.0.7...v0.0.8
v0.0.7
What's Changed
- Updated "Connect" image URL for improved visual presentation.
- Added
connect_wallet_rejectedtext for wallet rejection warning message. - Refactored codebase to integrate updated
aiogram-tonconnectandpytonapi, resolving long-standing connection issues and improving stability.
Full Changelog: v0.0.6...v0.0.7
v0.0.6
What's Changed
- Refactor: Improve handling of token holder checks to reduce potential errors.
- Add error handling to ignore TONAPI TONAPIInternalServerError (e.g., SQLSTATE 40001)
- Add logging level configuration for httpx.
Full Changelog: v0.0.5...v0.0.6
v0.0.5
v0.0.4
What's Changed
- Update aiogram-tonconnect version to
0.13.6.- Refactor middleware for private chat handling only.
- ValidationError: 1 validation error for ATCUser
language_code
- ValidationError: 1 validation error for ATCUser
- Refactor middleware for private chat handling only.
Full Changelog: v0.0.3...v0.0.4
v0.0.3
What's Changed
- Update pytonapi version to
0.3.1. - Update aiogram-newsletter version to
0.0.11. - Refactor middleware for private chat handling only.
- Fix AttributeError:
'NoneType' object has no attribute 'language_code'.
- Fix AttributeError:
Full Changelog: v0.0.2...v0.0.3
v0.0.2
What's Changed
-
Added wallet disconnection post successful connection:
Optimized and lightened load on the TON Connect bridge. It's no longer mandatory to request theTONAPI_TONCONNECT_KEYif you don't anticipate a load exceeding 1 user per second. -
Added DEX Provider Selection Feature:
Implemented the ability to select a DEX based on available liquidity on eitherdedustorstonfi. Depending on the chosen DEX, a link for viewing or purchasing the token will be generated.
To set your DEX, add the following line to your.envfile:DEX_NAME=dedustReplace
dedustwithstonfiif you prefer Stonfi as your DEX provider. -
Implemented TON Connect locale support (ru/en):
Contributed by inozemtsev-roman in PR #2. -
Other recent commits:
- Set
nano_to_amountprecision to 9 for holder balance. - Fixed typo in Getgems base URL.
- Set
New Contributors
- @inozemtsev-roman made their first contribution in PR #2.
v0.0.1
TON Token Access Control Bot v0.0.1 Release
We're excited to announce the release of the first version of TON Token Access Control Bot!
What is TON Token Access Control Bot?
TON Token Access Control Bot is a specialized bot designed to manage access to private Telegram chats using NFT tokens and/or Jettons. With this convenient solution, you can precisely control who has access to your groups and when, leveraging tokens as unique non-transferable identifiers for each participant.
Features
- Token Access Control: Enable access via NFT tokens and Jettons, with customizable token limits.
- Testnet and Mainnet Support: Flexible testing and deployment on both networks.
- TON-Connect Integration: Ensures a secure and user-friendly experience.
- User-Friendly Admin Panel: Built-in panel for easy administration.
- Multilingual Support: Available in both Russian and English for user interaction.
- Newsletters to All Users: Distribute newsletters to all users, including delayed scheduling.
Get Involved
We welcome your feedback and contributions to make TON Token Access Control Bot even better. Feel free to contribute or report issues.