View source for Talk:Np1sec/incremental consistency

Return to "Np1sec/incremental consistency" page.

[View source↑]
[History↑]

Thread title	Replies	Last modified
Using blockchain for ack	1	13:11, 12 September 2014
Sequence number to float decimal	1	13:10, 12 September 2014

Using blockchain for ack

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:

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).

Return to Thread:Talk:MpOTR/incremental consistency/Using blockchain for ack.

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

infinity0 (talk)‎

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)‎

Which sequence number are you referring to?

infinity0 (talk)‎

Last modified 11 years ago

View source for Talk:Np1sec/incremental consistency

Contents

Using blockchain for ack

Sequence number to float decimal

learn.equalit.ie