@chumschat
Your project aims to create a comprehensive integration between Chums and the TRON blockchain.
So I want more clarity that was why I asked
How will the integration ensure seamless communication between chums messaging protocol and Tron Blockchain infrastructure.
Thank you for the clarification!
Chums integrates with the Matrix network and the TRON blockchain independently, which ensures smooth and uninterrupted functionality for users.
Chums has a built-in non-custodial wallet that allows users to interact directly with the TRON network and initiate transactions without involving the Matrix server.
For features like Web3 channels and NFT clubs, we developed special plugins for the Matrix server. In these cases, Chums securely transmits only the userâs wallet address to the Matrix server to enable these features, while the seed phrase always remains securely stored on the userâs device.
Thanks for the amazing clarification
thatâs great but i think it still gonna be hard to achieve once this goes massive against regulations because some countries want the access too within their territory, and identity focused. even tg got a lot of problems, and how about handling crimes situation?
because criminals love any tech system with privacy, it protects their identity
Thank you for raising this important point. The Matrix network operates as a federation of multiple independent servers, with each server owner responsible for moderating their own content, though this is inherently limited due to end-to-end encryption.
As a messenger, Chums serves as an interface to these Matrix servers but doesnât exert direct control over user content. We plan to administer only our home server, chums.chat, ensuring that it complies with applicable laws.
Other servers, including those focused on Web3, are independently managed by communities, companies, or individuals, who assume responsibility for their content and compliance.
Iâm sorry but your response doesnât fully address the core concern about regulatory pressure and criminal misuse of privacy-focused technologies. While itâs true that Matrix operates as a federated network, which allows independent servers to control their own content, this does not entirely eliminate the issue of regulatory scrutiny or the potential for illegal activities.
First, governments around the world are increasingly implementing regulations that demand access to user data, especially in the context of messaging platforms where end-to-end encryption is a key feature. Even if a service like Chums only manages one home server (chums.chat), it still plays a part in the broader Matrix ecosystem. That ecosystem, regardless of server independence, is likely to face pressures for data access, just as Telegram and other platforms have encountered.
@chumschat to make it simpler.
Will you share ip-address and phone-number to government ? you provide the interface, so you have this responsibility too.
Thank you for your questions. These are important matters that deserve discussion.
Regarding user information disclosure in the Matrix network, this is regulated by the Matrix Foundation. Their Law Enforcement Guidelines can be found here:
According to official information from the Matrix Foundation, âhomeserver administrators are unable to view data which is end-to-end encryptedâ. This is a core architectural feature of the protocol.
We intend to comply with requirements from government authorities and regulators. In our case, we can only provide:
â Username
â Userâs IP address
â Display name
â Avatar image
â Non-custodial wallet address
â Content from public unencrypted rooms (which are accessible to any user anyway)
Phone numbers are not used for user registration or authorization.
Other data can only be provided by the Matrix Foundation.
You mentioned the possibility of technical backdoors, but this is highly unlikely in an open-source platform.
A decentralized platform like Matrix, while adhering to guidelines, will not escape the crosshairs of regulatory bodies, especially if itâs seen as a haven for illicit activity.
You mentioned that technical backdoors are unlikely in an open-source platform, but history has shown otherwise. Even open-source platforms can be forced to implement backdoors or allow vulnerabilities, as seen with the FBIâs legal battles against encrypted messaging services. The open-source nature of Matrix does not guarantee immunity from government pressure. If countries demand access to encrypted content, platforms like Chums may still face legal consequences or be forced to shut down.
Now looking at this discussion make me realize, the concept of a blockchain messenger promoting both transparency and privacy is inherently contradictory and flawed. On one hand, these platforms advocate for user control and data ownership, claiming that encryption and decentralization protect user privacy. However, the reality is that governments around the world are increasingly demanding access to user data, including chat histories, for regulatory, security, and legal reasons.
and the fact that only basic metadata can be shared, this does not sufficiently address how such platforms will prevent criminal exploitation
Youâre right that communication platforms must engage with authorities to comply with legislation, and this obligation applies to all platforms storing user information, whether itâs cloud storage, email services, or VPN providers.
At the same time, itâs worth noting that end-to-end encryption is essential not only for protecting personal data of individual users but also for securing sensitive information of governments and large corporations.
For example, according to open sources, the Matrix protocol is used by the French public sector to ensure secure communication across government departments:
Similarly, itâs reported that Skype, with its wide range of corporate clients, employs the Signal Protocol for its private conversations.
Weakening encryption protocols or implementing backdoors would introduce significant risks to all users, including government agencies, critical infrastructure, and major businesses that rely on this technology for secure communication.
Itâs therefore reasonable to believe that open-source platforms like Matrix and Signal, which prioritize strong encryption, will continue to provide essential privacy protections while working within legal frameworks to address legitimate law enforcement concerns.
We value all feedback and understand your perspective, but we donât see a contradiction between providing a secure communication environment and facilitating access to Web3 features.
For Matrix users, weâve designed Chums to gently introduce them to Web3 without overwhelming them. They can move between servers, explore new possibilities, and interact with Web3 features in a straightforward and familiar interface, with just a couple of taps.
For Web3 enthusiasts, we offer a space to stay connected with your community and actively use your tokens and NFTs. Join private rooms based on NFT ownership, sending and receiving tokens directly in chats, or receive updates on changes in your DAO â all brought together in one convenient place.
Our focus is on reaching a wide audience, with no intention of facilitating any questionable activities.
Earlier in this thread, I started demonstrating the core mechanics of Chums and will continue doing so over the next few days. Hopefully, Iâll be able to change your perspective along the way 
Iâll demonstrate how NFT clubs work in Chums using an account on the venom.fan server, which was created for the Venom blockchain community.
1. Creating group rooms in Chums
In Chums, you can create group rooms with various options:
â Public (anyone can find and join) or private (entry by invitation only).
â The ability to enable or disable end-to-end encryption.
â A choice between standard access or NFT-based access.
If you select NFT-based access, youâll need to specify which collection will be used for entry.
The screenshot below shows the room settings and an example of a public room, âChums Support.â
2. Viewing NFT clubs
To explore rooms with NFT-based access, go to the âNFT clubâ tab.
For example, letâs tap on the âVenom Early Participant NFTâ room â a message saying âYou donât have NFTâ will appear.
Weâll check the Wallet section to confirm that the required NFT is missing.
3. Acquiring an NFT using the built-in browser
To acquire the NFT, weâll use the built-in browser and navigate to the Oasis Gallery marketplace.
Find the necessary collection, select the âBuy nowâ option, and choose a listing. A purchase confirmation window will appear; with two taps, your ticket to the NFT club is secured!
4. Checking the Wallet and accessing the club
Next, go to the Wallet section to confirm that the NFT is now in your possession. Now, access to the club is unlocked: tap on the roomâs name â and youâre in!
Hey everyone! I wrote a Medium post explaining what weâre up to in simple terms. Itâs great for those who are new to Web3 and secure communication. Feel free to share it with your friends
Hi! Why arenât you continuing to focus on the Venom blockchain? You explained a lot about matrix and chum connections, but what are the benefits for TRON here? As you mentioned interoperability. How many networks will you have? Whatâs your plan to make TRON the spotlight?
Is this development level similar to building other wallets to provide the TRON community with more access, without directly impacting transactions on the TRON blockchain?
Can you show us how sending and receiving tokens directly in chat works? I want to see the user experience, would it be complicated like on-chain gaming, or a simpler process?
I sI still donât see the main use of the application. If itâs a messaging app, there are already tons of blockchain messengers, with or without Matrix. Ultimately, it will be competing against giants like Telegram, which offers a free, popular, and trustworthy platform.
The feature for sending and receiving tokens directly in chats isnât appealing as well; it disrupts the current user experience. I prefer sending tokens through my trusted wallet and then sharing the transaction hash in the chat later. Most investors have already made purchases through Telegram and Discord, so why would we switch to Chums? It seems like thereâs still a lack of âmarket fit,â and it would require too many resources to reach the target market. This still doesnât address the need for easy business integration as you want to accomplish.
For private NFT clubs, itâs much easier for moderators to verify ownership on platforms like Discord and Telegram, especially since those already have established moderation systems.
Currently, I donât see any plans for building moderator management in your chat app either.
Hello! Thank you for your questions. Iâll try to answer them step by step
Weâre aiming to reach a broad audience, which we can divide into two main segments:
1. Current users of the Matrix protocol. Most of them are unfamiliar with blockchain technologies or have only a basic understanding. For this group, we strive to offer the best features from different supported blockchains in a friendly, all-in-one interface.
To achieve this, we are developing a multi-server architecture that allows seamless movement between Web3 servers. Just a swipe, and youâre exploring the ecosystem of another blockchain.
2. Web3 communities that can set up their own servers and customize them according to their specific needs. The key here is to create a comprehensive experience within the chosen blockchain ecosystem.
Let me provide an example.
Our first supported blockchain is Everscale, for which we configured a server with the most extensive Web3 features based on their needs:
1. Integrated non-custodial wallet based on EVER Wallet:
â Fungible tokens
â Non-fungible tokens (NFTs)
2. Integrated dApps:
â Tokstock (NFT marketplace):
â Evername (Decentralized name service):
â FlatQube (DEX):
â stEVER (Staking):
â Gravix (Trading)
â Ever DAO / ĐĄoming soon
3. Creation of specific NFT clubs for projects such as:
4. Native integration of Inscriptions in the user interface.
This setup allows Everscale users to communicate privately, transfer tokens, and interact with key dApps within a unified environment without leaving our messenger and their server. Just a couple of taps, and everything is at their fingertips.
All the listed features are currently active, except for the whitelist of dApps in the built-in browser, which will be available next week.
Weâve also received requests for:
These features will be developed if we see similar demand from other communities.
For the TRON integration, we have implemented the following basic features:
These features represent the minimum viable integration to showcase Chumsâ potential within the TRON ecosystem.
We aim for a win-win approach, where Chumsâ development within each blockchain ecosystem is driven by its community.
To maximize Chumsâ value for the TRON community, we plan to align our efforts with the needs of existing projects and TRON users. For example, we are interested in exploring potential collaborations with prominent projects in the TRON ecosystem, such as:
The integration of the TRON wallet in Chums enables both on-chain operations (such as token transfers in chats and interaction with dApps via the browser) and off-chain activities, like receiving real-time notifications from dApps, linking a Web3 domain to a Matrix account, or joining NFT clubs.
Which features to implement will be decided in collaboration with the community and projects within the TRON ecosystem.
Yes, of course.
To transfer tokens, simply open a chat with your friend, tap the âSend Tokensâ button, select the network and token, enter the amount (and an optional comment), and confirm the transaction with just one tap.
We recently tested this with @relate101
Now, sending tokens on the TRON blockchain is available on the chums.chat server:
Our goal is to make the user experience as friendly and straightforward as possible.
We donât see ourselves as competing with tech giants like Telegram â that would be unrealistic.
Instead, we focus on users who share our vision of a convenient and secure communication environment, integrated with modern technologies like Web3.
We emphasize the following key aspects:
Convenient communication: This includes not just text messaging but also voice, video, and conferencing capabilities.
Privacy: Your conversations are protected end-to-end by default, meaning they canât be read or reused by third parties (e.g., for targeted advertising). Full data synchronization across your devices is available, even with end-to-end encryption in place.
Decentralization: You have the freedom to choose your server, ensuring complete control over your data. This data wonât be accidentally leaked or suddenly deleted. Thereâs also no single point of failure or centralized control over the entire network.
Reliability: The platform is built on open-source technology, trusted and continuously audited by a large community of developers over time.
In terms of Web3, we address the needs of Web3 communities and remain flexible in our approach.
A key advantage is that weâre not limited to a single blockchain. By supporting multiple blockchains, we provide access to essential dApps across different ecosystems and facilitate the mixing of users from various networks, enabling richer interactions and experiences.
Our goal is to offer a simple and intuitive experience, making Web3 interactions easy and accessible.
Itâs genuinely difficult to find such a comprehensive combination of features in a single platform
We aim to create a simple and intuitive Web3 experience for a wider audience.
Many users find it challenging to navigate traditional methods involving separate wallets, transactions, and hashes.
Chums offers the ability to interact with a variety of dApps from different blockchain ecosystems, seamlessly integrated into familiar user flows, providing a more cohesive and native Web3 experience.
We recognize that thereâs still work ahead in refining our market fit. Our approach is to grow gradually, following a win-win strategy alongside various communities to ensure sustainable progress.
