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.
Message
Cancel
Creating...
Broadcasting...
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).
Message
Cancel
Creating...
Broadcasting...
There can be more advanced schemes such as ECIES as used in BitMessages, but I believe we can start from something more simple.
Message
Cancel
Creating...
Broadcasting...
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.
Message
Cancel
Creating...
Broadcasting...
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.
Message
Cancel
Creating...
Broadcasting...
@DashCunning-banned maybe you can tell about MountMemo initiative on that Reddit thread as well? I don’t have an account there.
Message
Cancel
Creating...
Broadcasting...
#MountMemo⛰ with organized transactions towards eatBCH/eatBCH-SS is a better way to stress test bitcoin cash
Message
Cancel
Creating...
Broadcasting...
The shared secret can be hashed for additional security (like in BIP47 protocol).
Message
Cancel
Creating...
Broadcasting...
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.
Message
Cancel
Creating...
Broadcasting...
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.
Message
Cancel
Creating...
Broadcasting...
@modulus, yeah repeat that both of us don’t understand that idea again please. Like YOU TWO DONT UNDERSTAND, NEITHER OF YOU UNDERSTOOD etc.
Message
Cancel
Creating...
Broadcasting...
@modulus, doesn’t matter how complicated the actual condition is. It’s just a bad practice imo.
Message
Cancel
Creating...
Broadcasting...
Also, can we please disable “send by pressing return” and switch it to ctrl/cmd+return. Posting to blockchain is a bit different scenarios than instant messaging.
Message
Cancel
Creating...
Broadcasting...
@modulus if replies and reposts are the same action, you need to evaluate conditions to distinguish them
Message
Cancel
Creating...
Broadcasting...
@modulus if replies and reposts are
Message
Cancel
Creating...
Broadcasting...
@modulus, easy and straightforward to implement if replies and reposts have different prefixes
Message
Cancel
Creating...
Broadcasting...
@modulus, in microblogging it’s often useful to hide replies that are towards people you do not follow as well
Message
Cancel
Creating...
Broadcasting...
What’s wrong with the idea of a separate action to indicate reposts, afterwards?
Message
Cancel
Creating...
Broadcasting...
@modulus Treating specific “replies” as “reposts” is an “exception” to definition of a “reply”. Why creating some strange logical constructions if there is a straightforward solution?
Message
Cancel
Creating...
Broadcasting...
I have Private key from BlockPress to export but how do I transfer the funds to MEMO? This is why people are not into Crypto its so FUCKING complicated.
1. Import you Block Press Private Key into Electron Cash wallet, 2. Copy your Memo address. 3. From Electron Cash, make a transaction to your Memo address
Message
Cancel
Creating...
Broadcasting...
@modulus of course it does, or otherwise how would implementations know it is a repost and not an original post?
Message
Cancel
Creating...
Broadcasting...
My "name" is unique. It contains Cyrillic characters. Unique names is not a way to prevent such scams
That said, you name is only unique in terms of unicode. We can very easily create a framework that will help in distinguishing "perceived uniqueness".
Message
Cancel
Creating...
Broadcasting...