BJetton

What's BJetton

BJetton is a community Jetton token customized by Beecon for Telegram groups. Each group can have its own Jetton token minted by the group owner using the Beecon bot, which can be used to incentivize active participation among members of the community, enabling advertisers to purchase these tokens for ad placements within the community.

To achieve this goal and effect trivial changes for Jetton. We have decided to using TEP64 to store the information within the Telegram group. From the very beginning, BJetton is just storing the relevant info in an extra field named extends:

• protocol: identifier, bjt for BJetton, others for future resevation.
• id: Telegram group ID, int64. Since groups are identified by their unique group ID, the group id is to ensure no duplicate tokens for group. One BJetton for one group.
• owner: The user id of Telegram group owner. This field serves permission purpose. Considering that there should be access authorization for management, like token issuing, burning and transferring group to others, we decide to store the group owner to BJetton's metadata.
• extra: Data that no need to store onchain, which can any type. For us now, it's a link pointing to the group details.

extra is a link to a json file which updates by Beecon bot automatically. The file includes:

• group_name: The name of the telegram group.
• group_link: The group invitation link, we highly recommend to make the group public.
• member_count: Number of the group members.
• activity_score: A comprehensive score for community activity.
• tags: Community custom tags.

All these field are stored in the content Cell attributes extends with JSON format., which would not mess up Jetton's original metadata.

Here is an example of a BJetton content:

{
   "name":"Banknote Plane",
   "description":"Fly with banknote planes and journey to every corner of the planet.",
   "image":"ipfs://QmRBUx9UbfrMLAK75tXTvcFUqG2duLihVR4PWpVuBUSuPz",
   "symbol":"BNP",
   "decimals":"9",
   "extends":"{\"protocol\":\"bjt\",\"id\":\"-1001839662169\",\"owner\":\"6303440178\",\"extra\":\"ipfs://Qme2dWGPsFsd98opkPCnSUm375RkntHbRkd5qQke8RwSc8\"}"
}

Furthermore, it's kind disappointment that we can not use telegram to interact with TON directly. Therefore, we're exploring ways to combine Telegram and TON network, which may involve an oracle on TON to enable interaction with Telegram on TON network directly via smart contract. This would be our first step in making Telegram and TON work together.

Q: Why store this info on-chain not off-chain?

A: Since off-chain's data is very easy to corrupt and modified by some malicious attackers. On-chain data is more rubost than off-chain data. Meanwhile, there's certain limitations(see Telegram Limits) for this data, so it's reasonable for the trade-off with a higher storage rent fee for more reliable infomation.