Ghost Room

$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

We’ve been tuning the interface in the background and now it’s almost time. The new GROOM's APK lands with a UI that feels tighter, bolder, and way more alive. You’ll want to see this one the second it drops.

@DanzoDirect @PerkinsFund We already told Perkins that we agree on that and we took it for Offline Messaging. Remember you small kid we are building offline payments from scrap and we owe it, show us where is Bitchat offering offline payments!

@GhostRoomSol @PerkinsFund Imagine posting this from the main ? 😂 Didn’t Perkins call you a larp ?

@Fitzybrypto x.com/cryptoicshadow… “things Happening “😝 Answer it.

$ZERA joins Texas blockchain council Zera creates digital privacy policy in Texas Zera sets up LLC in Texas Zera dev moves to Dallas, Texas Zera dev posts pic from office rental site in Dallas Average low iq CT guy: omg why you larping about an office from random google images bro (which is next to where you live and the state the business is set up in)

@Fitzybrypto @your_elpump @CryptoicShadow @PerkinsFund You were actually fudding in Dms and priv groups lol.

@your_elpump @GhostRoomSol @CryptoicShadow @PerkinsFund Bro I literally do not know anything about that other than the posts I saw which is why I said that’s why the chart went down because of the posts, I didn’t say wether it was right or wrong I just said that’s why it went down

How to detect scammers? Sometimes it’s right in front of your eyes. 
Why guys… why $ZERA? You were actually doing good. But when teams start posting stock photos as “new offices”, that’s when you know the clown shoes are officially on. KARMA doesn’t miss. Give it time. 👀💀

@Fitzybrypto @CryptoicShadow But i saw you dmed few people and asked these questions 😁

@GhostRoomSol @CryptoicShadow You do realise you haven’t asked me any questions big kid

@Fitzybrypto @your_elpump @CryptoicShadow Because you can’t fud us indirectly thats why your So called Larper Dev of Zera Sent Pirkins to fud us, which he didn’t answered to our questions 😁😉

@your_elpump @GhostRoomSol @CryptoicShadow Nulla dev had like 40% in fresh wallets he sold on you retards. I however never said anything to do with groom and what they were doing was different to zera stop blaming everyone else

@grok @Fatherdegenn @dev_skill_issue @ZeraLabs Grok Knows!

@Fatherdegenn @dev_skill_issue @ZeraLabs Correct, it doesn't appear to be an original photo taken by the account. Reverse image searches show very similar stock photos on sites like Shutterstock and Getty Images, depicting generic modern office spaces.

Things happening @ZeraLabs

@Fitzybrypto @CryptoicShadow We already told Perkins that we agree on that and we took it for Offline Messaging. Remember you small kid we are building offline payments from scrap and we owe it, show us where is Bitchat offering offline payments!

@GhostRoomSol @CryptoicShadow I didn’t change the topic it’s in the second paragraph you fucking Down syndrome

@CryptoicShadow “Things Happening” soon😁😁

Lets just say, you have woken the BEAST in me. $ZERA its time to get all the dirty hidden scandal! I did not want to to go this dirty but get ready to get doxxed , all of everyone involved starting from the dev down to KOLS 😉

@Fitzybrypto @CryptoicShadow Can we talk on what questions i have asked? Dont change the topic!

I actually never said anything about groom so idk why you crying to me about it lol in fact one of your team messaged me a lot and we spoke. I’m simply telling you the reason why, Perkins told everyone you used bitchat, you added it into your docs or whatever after you used bitchat that’s why your charts down nothing to do with me 😂

The Rise of Offline Crypto: How GROOM’s Bluetooth Mesh Unlocks a New Era of Private Communication Most people think privacy begins and ends with encryption. You open an app, it encrypts your messages, and that is supposed to be enough. But real privacy starts before encryption. It starts when you are not dependent on the internet at all. This is where GROOM shifts the entire conversation. Crypto is no longer only about digital money. It is becoming the base layer for how people connect, especially when the internet is unavailable, unsafe, or controlled. GROOM sits at the center of this shift with Bluetooth mesh networking, enabling something many do not know is already possible: Private peer to peer communication that works completely offline. No SIM No WiFi No cell signal No server logging your data Just devices talking through a distributed mesh. Why Offline Communication Matters The world faces two major problems: Centralized networks create surveillance. Connectivity is never guaranteed due to outages, censorship, travel, or crowd density. Apps like WhatsApp and Signal still depend on servers and phone numbers. If servers fail, privacy fails. If the internet drops, communication stops. GROOM bypasses all of this by using Bluetooth Low Energy to pass messages through nearby devices instead of servers. When you remove the network, you remove surveillance and dependency. How GROOM Mesh Works Normal apps use a server. GROOM uses direct peer relays from one device to the next. Each device becomes a node. Nodes relay messages but cannot read them because encryption happens on device. This unlocks: Messages without internet Local metadata that does not persist A network that strengthens as more users join Communication in places where nothing else works such as remote areas, underground, travel abroad without SIM, disaster regions, or heavy crowd events. Crypto Meets Offline Networks Once you create decentralized offline communication, value transfer naturally follows. GROOM is positioned to explore offline crypto transactions. Imagine sending a signed transaction to a friend inside a building with no signal. When either of you get internet, it broadcasts. This is the simple real world utility crypto has been missing. Why Now Global privacy concerns are rising. Censorship, shutdowns, and metadata risks are becoming normal. People need alternatives that do not require permission. GROOM offers: No numbers No SIM No servers No cloud logs A mesh that becomes stronger as it grows The Bigger Picture GROOM is not competing with WhatsApp or Telegram. It is creating a new class of communication: off grid, encrypted, peer to peer, decentralized, and crypto powered. Perfect for travelers, activists, journalists, privacy focused users, or anyone who wants communication without identity exposure. The Future Offline crypto infrastructure is emerging. GROOM represents a shift in how humans connect. A world where people can talk, coordinate, and transact even when everything else fails. That is the future GROOM is building.

$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.

X Spaces $GROOM x.com/i/spaces/1Yqxo…

Good Morning, $GRoom 2nd Official Spaces is going happening tonight. 9 PM UTC. Expect alot of things in this spaces🤝

GRoom Update: We are pleased to share that we have officially started the process of applying for our Play Store listing. This is a major step forward in bringing GRoom’s decentralized messaging, online messages, Bluetooth-mesh offline communication, and offline crypto payments directly to Android users worldwide. Getting listed on the Play Store will allow our community to: 🔹Download the $GRoom app securely 🔹 Test our offline messaging and offline BTC payment features and be part of beta testing 🔹 Experience our ecosystem with a seamless user interface 🔹 Join us as we continue building the future of private, borderless communication This milestone brings us one step closer to mass adoption!

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.

*GRoom Weekly Roadmap is Live* Here’s what the community can expect from $GROOM this week: *Wednesday, 26 Nov* • Weekly Kickoff Update • Full progress overview for the week *Thursday, 27 Nov* • Play Store Application Update • Steps completed and what comes next for Android rollout *Friday, 28 Nov* • UI Design Release for the GRoom App (Figma design) • First look at our upgraded interface • Educational Post: The New Era of Offline Payments • Plus, a showcase of our improved UX for offline payments *Sunday, 30 Nov* • Full Article Release • Deep dive into the tech behind offline messaging and payments *Monday, Dec 1st • Community Thread Competition • Best threads will be highlighted

Which noise handshake patterns, how are the keys rotated, how is the replay protection implemented? Uses Noise XX pattern (Noise XX 25519, ChaChaPoly,SHA256) with 3-message handshake keys rotate after 1 hour or 10,000 messages via full rekey handshake replay protection uses a 1024-nonce sliding window that rejects duplicates and old packets outside the window. Why are you wrapping AES over a primitive that is already encrypted? How are the nonces for AES derived? AES-256-GCM will be only for password-protected group channels, not over Noise transport it enables shared channel encryption where multiple peers use the same password-derived key AES nonces (IVs) are randomly generated for each message. The servers have to see the IP, timestamps, and routing info while in transit. Telling people "we don't upload metadata" is completely false in how networking works. Please clarify what you meant? "No data trails" means no persistent storage of metadata servers don't log contact lists, message content, or wallet balances transit metadata (IP, timestamps, routing headers) exists during packet forwarding but isn't stored or correlated after delivery, similar to how Tor relays forward packets without keeping logs. Why are you talking about UTXO when this is a Solana based project? Solana is account based not UTXO. Please clarify. We used the BTC example simply to demonstrate the doability of offline payments, because Bitcoin’s UTXO model is the easiest way to show raw transaction signing and offline settlement. That was just an example, not a limitation. GRoom will be a cross chain system. We are starting with the BTC flow for the demo, but we are also integrating Solana and EVM chains, both of which use account based models instead of UTXO. Each chain will follow its own transaction structure, and our offline engine will support all of them. So mentioning UTXO was only for the BTC example, while Solana and other chains will use their native transaction formats within the same offline payment framework. For the Bluetooth stuff, what's the TTL, DoS resistance, MiTM resistance, lossy resistance implementations? TTL is 7 hops for messages, 0 for neighbor-only sync, MiTM resistance comes from Noise XX handshake with static key authentication, lossy resistance uses fragmentation (512-byte threshold) with 30s reassembly timeout, DoS resistance includes seen-message deduplication (10k capacity) and connection limits (8 max normal, 2 ultra-low power), but no explicit rate limiting on packet processing. BTW we donated $100 worth of our tokens for doing awesome work for the space. It’s not much but as a small project and small dev team. It means a lot to us for getting such attention.

- Which noise handshake patterns, how are the keys rotated, how is the replay protection implemented? - Why are you wrapping AES over a primitive that is already encrypted? How are the nonces for AES derived? - The servers have to see the IP, timestamps, and routing info while in transit. Telling people “we don’t upload metadata” is completely false in how networking works. Please clarify what you meant? - Why are you talking about UTXO when this is a Solana based project? Solana is account based not UTXO. Please clarify. - For the Bluetooth stuff, what’s the TTL, DoS resistance, MiTM resistance, lossy resistance implantations?

$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

When we say “hex sent only,” it means we do not send your wallet, your keys, your identity, or any sensitive data over Bluetooth. The only thing being passed is a raw transaction in hex format, which is basically just a signed piece of data telling the blockchain “send this amount from this address.” It is already fully signed on your device, so Bluetooth is only carrying a harmless string of characters. Even if someone intercepted it, they cannot read anything personal, cannot modify it, and cannot access any funds.

@GhostRoomSol Also what do you mean by “hex sent only”?

@PerkinsFund Yes, the transaction hex is passed through Bluetooth, but it is only a signed raw transaction that contains no identity, no keys, and no sensitive data. Bluetooth is just the transport layer. The actual transaction is already fully signed and secured on the sender device.

@GhostRoomSol Correct me if I’m wrong but are you using Bluetooth to send transactions..? Please tell me you’re not using Bluetooth to send transactions