You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Result of the stress testing of Matrix server revealed that with increasing number of participants in the channel message delivery time increases exponentially. That's a problem for our proposed broadcast channel where Balance Proofs are broadcasted and Monitoring servers actively listen for messages sent to the channel.
Ideas:
submit BP via direct message to MS. This would require some sort of MS discovery (can be done in a channel)
split broadcast channels and use naming schema i.e. <chain_id>_<token_network_address>
TODOS:
decide on how to avoid using broadcast rooms (use service discovery?)
create metrics for proposed protocol
decide which naming schema for the broadcast channels will be used
The text was updated successfully, but these errors were encountered:
Result of the stress testing of Matrix server revealed that with increasing number of participants in the channel message delivery time increases exponentially. That's a problem for our proposed broadcast channel where Balance Proofs are broadcasted and Monitoring servers actively listen for messages sent to the channel.
Ideas:
<chain_id>_<token_network_address>
TODOS:
The text was updated successfully, but these errors were encountered: