[Feature Request]: bitchat bridge mode

[EthnTuttle]

Platform

Cross-Platform

Description

https://github.com/permissionlesstech/bitchat/blob/main/WHITEPAPER.md

BitChat is a decentralized, peer-to-peer messaging application designed for secure, private, and censorship-resistant communication over ephemeral, ad-hoc networks. This whitepaper details the BitChat Protocol Stack, a layered architecture that combines a modern cryptographic foundation with a flexible application protocol. At its core, BitChat leverages the Noise Protocol Framework (specifically, the XX pattern) to establish mutually authenticated, end-to-end encrypted sessions between peers. This document provides a technical specification of the identity management, session lifecycle, message framing, and security considerations that underpin the BitChat network.

Bitchat seems aligned with meshtastic's architecture/principles and this feature request proposes a bridge mode be created. I'm not knowledgeable enough to understand the technical details, but I understand that most devices leverage BT to connect to a phone or other device for management. I propose leveraging those existing BT pathways to bridge between bitchat users and meshtastic, allowing messages to flow bi-directionally. This would extend bitchat's range and enable broader interoperability for meshtastic with adjacent protocols.

[KonnikPahoni]

That would be awesome! If meshtastic worked around the globe with missing connections covered by internet. E.g. if one of people in the local mesh net had access to the internet -- all should be able to utilize it so send international messages. Strong upvote!

[dzid26]

Except that he was talking about bluetooth....

[evansmj]

I wrote my first alpha draft of this here. I only tested with my rak4631. You wont be able to connect the meshtastic phone app with this firmware though. but it does forward bitchat messages over lora, and unwraps them on the other side. both meshtastic devices will need to be running this firmware.

https://github.com/evansmj/firmware-bitchat-plugin/tree/feature/bitchat-plugin

[dzid26]

I could not make it do anything useful.

• I could connect with meshtastic app, but I disconnected it for the test
• Nothing shows up on Bitchat #mesh,
• LOG - phone gets disconnected:

DEBUG | ??:??:?? 1208 BluetoothStatus CONNECTED INFO | ??:??:?? 1208 BitChat BLE: Peripheral connection established (handle=0) DEBUG | ??:??:?? 1208 BitChat Bridge: Created announcement with TLV payload (74 bytes) DEBUG | ??:??:?? 1208 BitChat: Serialized message 96 bytes (flags=0x00) DEBUG | ??:??:?? 1208 BitChat Bridge: Signed announcement with Ed25519 (packet bytes: 96, padded: 256, signature: 64) DEBUG | ??:??:?? 1208 BitChat Bridge: Signing data preview: 01 01 00 00 ... (total 256 bytes) DEBUG | ??:??:?? 1208 BitChat Bridge: Signature preview: c7 47 0c 52 ... INFO | ??:??:?? 1208 BitChat Bridge: Sending peer announcement (ID: 0x8bc9999f, TTL: 7, payload: 74 bytes) DEBUG | ??:??:?? 1208 BitChat: Serialized message 160 bytes (flags=0x02) DEBUG | ??:??:?? 1208 BitChat BLE: notify() returned false (client may not have enabled notifications yet), 160 bytes DEBUG | ??:??:?? 1208 BitChat BLE: nRF52 broadcasted message type=0x01, 160 bytes DEBUG | ??:??:?? 1208 BitChat Bridge: Message broadcasted to BLE INFO | ??:??:?? 1208 BLE connection secured INFO | ??:??:?? 1209 BLE Disconnected, reason = 0x13 DEBUG | ??:??:?? 1209 PhoneAPI::close() DEBUG | ??:??:?? 1209 BluetoothStatus DISCONNECTED INFO | ??:??:?? 1209 BitChat BLE: Client disconnected (handle=0, reason=0x13) INFO | ??:??:?? 1209 BitChat BLE: Client disconnected 

[r41d]

He did write in the post that "You wont be able to connect the meshtastic phone app with this firmware" so it's no wonder the phone app doesn't work

[evansmj]

I could not make it do anything useful.

• I could connect with meshtastic app, but I disconnected it for the test
• Nothing shows up on Bitchat #mesh,
• LOG - phone gets disconnected:

DEBUG | ??:??:?? 1208 BluetoothStatus CONNECTED INFO | ??:??:?? 1208 BitChat BLE: Peripheral connection established (handle=0) DEBUG | ??:??:?? 1208 BitChat Bridge: Created announcement with TLV payload (74 bytes) DEBUG | ??:??:?? 1208 BitChat: Serialized message 96 bytes (flags=0x00) DEBUG | ??:??:?? 1208 BitChat Bridge: Signed announcement with Ed25519 (packet bytes: 96, padded: 256, signature: 64) DEBUG | ??:??:?? 1208 BitChat Bridge: Signing data preview: 01 01 00 00 ... (total 256 bytes) DEBUG | ??:??:?? 1208 BitChat Bridge: Signature preview: c7 47 0c 52 ... INFO | ??:??:?? 1208 BitChat Bridge: Sending peer announcement (ID: 0x8bc9999f, TTL: 7, payload: 74 bytes) DEBUG | ??:??:?? 1208 BitChat: Serialized message 160 bytes (flags=0x02) DEBUG | ??:??:?? 1208 BitChat BLE: notify() returned false (client may not have enabled notifications yet), 160 bytes DEBUG | ??:??:?? 1208 BitChat BLE: nRF52 broadcasted message type=0x01, 160 bytes DEBUG | ??:??:?? 1208 BitChat Bridge: Message broadcasted to BLE INFO | ??:??:?? 1208 BLE connection secured INFO | ??:??:?? 1209 BLE Disconnected, reason = 0x13 DEBUG | ??:??:?? 1209 PhoneAPI::close() DEBUG | ??:??:?? 1209 BluetoothStatus DISCONNECTED INFO | ??:??:?? 1209 BitChat BLE: Client disconnected (handle=0, reason=0x13) INFO | ??:??:?? 1209 BitChat BLE: Client disconnected 

What device? For me my rak4631's appear as another bitchat peer. Sometimes i had to delete the existing meshtastic device from my bluetooth settings to get it to work, maybe thats whats going on so i'll have to figure that out

[dzid26]

Excellent, that worked! - Rak4631 as well.
This is cool. Will do more testing later.