-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add SubscribeAssociationChanges #238
base: main
Are you sure you want to change the base?
Conversation
// Request to subscribe to association changes, triggered by Identity Updates | ||
message SubscribeAssociationChangesRequest {} | ||
|
||
message SubscribeAssociationChangesResponse { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there any world where this can just be a stream of identity updates, with the parsing of the stream done client-side? Would be simpler/more compatible with decentralization/requiring less server trust
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm hoping in a decentralized world we can create a subgraph that does that aggregation by reading events from the blockchain and running our code. Then we can slice and dice the data any way we want.
But for now, it's a big ask for clients to run libxmtp
from whatever language/framework they are using and correctly store previous association states and apply updates.
@neekolas is this still relevant? |
@mkysel Yes. Waiting on feedback from a partner before I merge it |
tl;dr
Issues
xmtp/xmtp-node-go#410