View source for Talk:Np1sec/incremental consistency

Contents

Thread titleRepliesLast modified
Using blockchain for ack113:11, 12 September 2014
Sequence number to float decimal113:10, 12 September 2014

Using blockchain for ack

It is simpler to keep a block chain of all messages received in a session as follows:

(m_1, h(m_1), m_2, h(h(m_1), m_2), m_3, h(h(h(m_1),m_2),m_3,....)

And send hash of parent(m) with messages or heartbeat. This way it is very easy to look up into the blockchain to see if the hash of other participants matches the user. And it also allows for orders other than received order (lexi, etc).

Vmon (talk)07:15, 11 September 2014

How does this relate to what is written on either this page or the SenderKeys page?

infinity0 (talk)13:11, 12 September 2014
 

Sequence number to float decimal

I argue for float decimal number for the sequence number. In this way the transport can add a message out of order.

Vmon (talk)07:06, 11 September 2014

You do not have permission to edit this page, for the following reasons:

  • The action you have requested is limited to users in the group: Users.
  • You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.

You can view and copy the source of this page:

Return to Thread:Talk:MpOTR/incremental consistency/Sequence number to float decimal/reply.