Johnny Ge

I love you all and God bless you :-)

[Johnny Ge @JohnnyGe6]

@GLOBECEX @bulltheleader Its @bulltheleader season.

[Johnny Ge @JohnnyGe6]

@Roboslap12 @Openpawsol I hope bingx. It is a good one.

[Ghost Room @GhostRoomSol]

$GRoom Update

Hi everyone,
We are pleased to announce that our new UI design is now completed. This is an important step toward elevating the overall user experience on GRoom.

While we believe the new UI is a major improvement, we are still continuously refining it because we know it can become even better. This update represents the beginning of a more polished, modern, and intuitive design direction for GRoom.

The updated UI will be implemented in the app next, as part of our ongoing commitment to deliver consistent upgrades and improvements for our community.

More updates coming soon.

[Nishat Crypto @NishatCrypt0]

@CryptoKaduna Bro, look at the timing... @GhostRoomSol

Android rollout starting, spaces in a few hours, Community heating up again.

$GROOM really pushing the pace lately.

[Nishat Crypto @NishatCrypt0]

@GordonGekko Check this one out $GROOM lining up the Play Store, and a full Spaces later tonight.

Quiet teams don't build like this. These guys stay moving while everyone else coasts.

[CryptoBoy1199 @CryptoBoy1199]

Hey Bro check $GROOM

GROOM is tightening its advance with clean precision

Every rollout hitting sharp and showing the team is moving with real intent

Offline payment rails gearing up to flip the next major switch

Device to device communication running stable with flawless consistency

Holder momentum building strong as the base locks in harder each day

Bro this pressure is loading heavy don’t lose focus

[Nishat Crypto @NishatCrypt0]

@TheCryptoKazi Bro this pace is rare on @GhostRoomSol, clear schedule, nonstop progress, community growing on its own.

No hype tricks just work if they keep this rythm, it's gonna get loud fast. $GROOM just getting started.

[Johnny Ge @JohnnyGe6]

@NishatCrypt0 @CryptoTony__ @GhostRoomSol Let go $GROOM

[Nishat Crypto @NishatCrypt0]

@CryptoTony__ Check this one @GhostRoomSol, the consistency is wild. They keep shipping even on weekends, now a full weekly roadmap on top. Easy to see why more people are showing up here. $GROOM not wasting the momentum.

[Nishat Crypto @NishatCrypt0]

@DegenKenn Worth paying attention here @GhostRoomSol the roadmap is stacked, delivery pace is real, and the community keeps growing.

Just progress, If you blink you'll miss half the updates. $GROOM is moving different.

[Ghost Room @GhostRoomSol]

You have a few design issues with AES: shared password-derived key for the whole group. Anyone with the password or the ability to get the password can decrypt everything past or present this also brings in the ability to use dict attacks or just phishing attacks. That makes it so your encryption is vulnerable. You should never reuse a the nonces. This is not "military grade encryption" at its core.

Thank you for the detailed feedback. We appreciate the security review.
On nonce reuse each message uses a unique random 12-byte IV so nonces are not reused.
On the shared password model this is intentional for group channels, but we recognize the trade offs. Password compromise does expose channel history, and we are evaluating forward secrecy and per message key derivation. PBKDF2 uses 100,000 iterations with channel name salt, but stronger mitigations are needed.
We’re prioritizing improvements to channel encryption security over time. Your input helps us strengthen the implementation.

No data trails should be phrased as "no persistent logs". There will always be data trails with the ledger, I get why you said it and the marketing behind it, but its misleading compared to the actual design.
Thanks for the feedback. We use "no data trails" to mean no identifiable or linkable data trails that can be used to track users or correlate activity.
On-chain, Solana/Bitcoin transactions are permanent, but without personal identifiers or metadata linking them to users. Wallets and identities stay local, so on-chain data can't be tied to specific individuals without additional context.
No persistent logs of contact lists, message content, wallet balances, or user metadata on our servers. Transit metadata IP, timestamps, routing headers exists during forwarding but isn't stored or correlated after delivery.

Makes sense with the UTO, but your public material specifically states Solana there is no other talk about it (unless I missed it?

We’ve planned to expand step by step, developing and integrating more chains as the project grows. Our public materials haven’t fully caught up yet, and we still need to update the marketing content accordingly plus we want to keep some of it as a future catalyst.

The Bluetooth is plausible. I actually really like the idea, I'm curious how you are doing re-fragmentation/ reassembly on the other end with packet loss and in the presence of DoS like peers?
Reassembly uses a fragmentID-based map, each fragment set gets a random 8-byte ID, and fragments are stored by index until all are received. If fragments are lost, incomplete sets are cleaned up after 30 seconds, preventing memory buildup.
Duplicate detection via SecurityManager with a 10k message capacity, connection limits (8 max normal, 2 ultra-low power), and periodic cleanup of stale fragments for DoS mitigations. Fragments are validated before storage, and fragmentID randomness prevents predictable attacks, and currently no automatic retransmission, missing fragments cause reassembly to time out after 30 seconds. This is acceptable for lossy BLE, but we're evaluating selective retransmission for critical messages for packet loss. The 30-second timeout balances memory use and tolerance for transient loss.
We appreciate the feedback and are refining these mechanisms as we scale.

As a side note, we reviewed your main page post. Could you show us where it says we cannot use open-source code, and what exactly the concern is? Also, please point to any place where we stated that we don’t use open-source components.

Since you’re raising technical questions, can you also show us where in BitChat’s code the transaction is generated within the app, and where the hex is verified internally? Also show us where they implemented offline payments.

[Johnny Ge @JohnnyGe6]

@Can280420 @Fityeth One Word $GROOM

[CIM @Can280420]

@Fityeth Check out before thanksgiving

$GROOM offline payment layer is shaping up to drive the next big move. Device-to-device messaging remains solid with smooth and reliable performance signalling that big momentum is coming as community confidence is being raised.

[🧠 investor 🦖 @moneymancalls]

All eyes on $GHOST next leg up seems close. 👀

[Ghost Room @GhostRoomSol]

@PerkinsFund #Ref 2

[Ghost Room @GhostRoomSol]

@PerkinsFund #Ref 1

[Ghost Room @GhostRoomSol]

$GRoom “Game Changer Demo Preview”

The demo you’re seeing isn’t just a feature…
It’s proof that GRoom is years ahead of the entire market.

In this demo:

✔️ Offline Messaging (Bluetooth Mesh)
Devices communicate with zero internet, zero SIM, zero identity. Fully operational inside our Android app.

✔️ Offline Raw Transaction Generation
A Bitcoin transaction is created completely offline by the sender.

✔️ Hex Sent Through Offline Messaging
The raw hex is delivered to the receiver through Bluetooth only.

Online Execution by Receiver
Once anyone gets internet, the receiver broadcasts the hex and the BTC transaction goes live on-chain.

This means:

✔️ You can communicate in a blackout.
✔️ You can move value in a blackout.
✔️ You can transact without towers, WiFi, or visibility.
✔️ You can stay sovereign, private, and connected anywhere on Earth.

This is not a concept.
This is working, integrated, and live inside our Android app right now shown in demo.

$GRoom is officially building what others are only tweeting about.
This is the future of private communication and payments.

$Privacy $GRoom $Payments

[John Klein @Jonnklein]

I wouldn’t be surprised if we see $GROOM reach over a $10M market cap soon. Its utility is unique and already working.

GuETJT65ZdWSJbr3JHJYkqmrn7EtoskAfTN9sDUYpump

@GhostRoomSol

#GROOM

[Johnny Ge @JohnnyGe6]

@moneymancalls @avici Please help me, can you bring me back to groom telegram please and ask admin to unban me please. My tg Name @johnnygefunk

[Johnny Ge @JohnnyGe6]

@Jonnklein @GhostRoomSol Can you ask admin from groom telegram to unban me please @johnnygefunk
I dont know how to contact them