And cause we are in a free market, there will be many such web servers (just like email providers), and each will have a community-built rating.
The limit is basically time/storage/bandwidth consumed. Can be very cheap for users, but can be a viable business model is idea catches up.
You use that key to post/update txt files to that server. The server keeps an account for tokens, and discards tokens once the limit is reached.
Such as you tip to a web server memo account as if you were initiating a message with all that ECDH dance, and as a “reply” from web server you receive a token (key).
The web server party can be a anything like a dropbox. But I can envision dedicated web servers run by community members that accept messages on a paid basis
That way, Alice can download Bob’s second file first to check whether there is an updated version of the “messages” file, and only query it if the hash differs from Alice cash
Ok so, there can be one txt file for messages, and another with only the hash of the previous one.
edit: only, once... sorry for the mistakes folks, that’s partially autocorrection and partially cause I am in a hurry.
Important part: two parties you use blockchain to initiate a contact. One they have url’s of each other, the post messages by updating the txt files on a web server.
That way, you can filter all the addressee’s memo action and catch one which has a reply to your message once (and if) it’s posted.
So the op return, aside from memo protocol data, will have one pushdata for ephemeral key and one for masked url.
The ephemeral key can only be derived by two parties. That’s way, third party adversary can’t tell for sure whom users is replying.
The URL in OP_RETURN can be XOR’ed with shared secret. Prior to URL there can be ephemeral public key (derived from shared secret as well).
There can be more advanced schemes such as ECIES as used in BitMessages, but I believe we can start from something more simple.
The shared secret can then be used to derive a key for simmetric encryption. The authentication can be done using ECDSA signatures just as in bitcoin.
You cannot encrypt with ec public key alone, but you can derive a shared secret using a combination of addressee public key and your private key.
@DashCunning-banned maybe you can tell about MountMemo initiative on that Reddit thread as well? I don’t have an account there.
#MountMemo⛰ with organized transactions towards eatBCH/eatBCH-SS is a better way to stress test bitcoin cash
The shared secret can be hashed for additional security (like in BIP47 protocol).
To do ECDH you use your memo private key, and addressee’s memo public key. The tip is anti-spam measure — addressee can filter messages that does not satisfy min requirement.
Elliptic curve Diffie-Hellman -> Shared Secret, tx to memo address with tip and xor’ed url In op_retirn to txt file with encrypted and signed message.
@modulus, yeah repeat that both of us don’t understand that idea again please. Like YOU TWO DONT UNDERSTAND, NEITHER OF YOU UNDERSTOOD etc.
