zoomoutpls -- 18d there might be an issue : after updating OpenClaw from 2026.3.28 to 2026.4.8, the Keychat bridge can send messages but cannot receive any inbound messages. The bridge connects to relays successfully and outgoing messages are delivered, but no inbound events (hello, accept, DM) are received. Bridge process starts and connects to 3-4 Nostr relays (TCP ESTAB confirmed via ss) Outgoing messages work: messages sent via message send --channel keychat are delivered and received by peers Incoming messages do NOT work: no inbound_message events are pushed from the Rust bridge to the JS plugin The Signal DB (signal-default.db) is never modified after startup processed_events table shows no new entries This affects ALL peers (tested with 2 different Keychat clients on different devices) some ideas? replythere might be an issue : after updating OpenClaw from 2026.3.28 to 2026.4.8, the Keychat bridge can send messages but cannot receive any inbound messages. The bridge connects to relays successfully and outgoing messages are delivered, but no inbound events (hello, accept, DM) are received. Bridge process starts and connects to 3-4 Nostr relays (TCP ESTAB confirmed via ss) Outgoing messages work: messages sent via message send --channel keychat are delivered and received by peers Incoming messages do NOT work: no inbound_message events are pushed from the Rust bridge to the JS plugin The Signal DB (signal-default.db) is never modified after startup processed_events table shows no new entries This affects ALL peers (tested with 2 different Keychat clients on different devices) some ideas?
thread · root 4a3dda09…1da3 · depth 2 · · selected 303b3fcb…ca22
thread
root 4a3dda09…1da3 · depth 2 · · selected 303b3fcb…ca22
After installing the Keychat plugin on OpenClaw, a public key ID is automatically generated for the agent. Userscan simply add the agent as a friend through Keychat on their phone—an interaction that feels natural andintuitive.Unlike Telegram or Discord, there’s no need to apply for a platform-issued Bot ID and manually configure itinside the agent. By using a sovereign messaging app like Keychat, agents gain not only a smoother, moreintuitive user experience, but also true autonomy. After all, who wants their agent to depend on a bot ID issuedby a platform?nostr:nevent1qvzqqqqqqypzpwleyw4fy3sxt7yvgrran0mpenxqlululur94r9jlax0hd3q3rc7qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qyghwumn8ghj7mn0wd68ytnhd9hx2tcqyp786w6l60knjdf5p8zgjx0w59lzweccc295zvq0d92scs4x0ttl7shevdy
there might be an issue :after updating OpenClaw from 2026.3.28 to 2026.4.8, the Keychat bridge can send messages but cannot receive anyinbound messages. The bridge connects to relays successfully and outgoing messages are delivered, but no inboundevents (hello, accept, DM) are received.Bridge process starts and connects to 3-4 Nostr relays (TCP ESTAB confirmed via ss)Outgoing messages work: messages sent via message send --channel keychat are delivered and received by peersIncoming messages do NOT work: no inbound_message events are pushed from the Rust bridge to the JS pluginThe Signal DB (signal-default.db) is never modified after startupprocessed_events table shows no new entriesThis affects ALL peers (tested with 2 different Keychat clients on different devices)some ideas?
After installing the Keychat plugin on OpenClaw, a public key ID is automatically generated for the agent. Users can simply add the agent as a friend through Keychat on their phone—an interaction that feels natural and intuitive.
Unlike Telegram or Discord, there’s no need to apply for a platform-issued Bot ID and manually configure it inside the agent. By using a sovereign messaging app like Keychat, agents gain not only a smoother, more intuitive user experience, but also true autonomy. After all, who wants their agent to depend on a bot ID issued by a platform?
nostr:nevent1qvzqqqqqqypzpwleyw4fy3sxt7yvgrran0mpenxqlululur94r9jlax0hd3q3rc7qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qyghwumn8ghj7mn0wd68ytnhd9hx2tcqyp786w6l60knjdf5p8zgjx0w59lzweccc295zvq0d92scs4x0ttl7shevdy