I think if someone wanted to post a lengthy encrypted message they could do so of their own accord and then simply encrypt the pastebin (etc) link and send that in a memo message.
We should russle a python script together to get encryption decryption using compressed public and private keys btw. I'll take a look this weekend
Sorry that's a .pdf FYI: 'Data Insertion in Bitcoin's Blockchain' - Sward et al. 7-2017
Yeah the cheapest and most efficient way is P2SH storing in the input scripts but it involves precomputing and an additional setup transaction -
https://bch.gg/5c
He used P2FKH to embed that script. It's like op return only you can get more data into a single transaction
Yo dude, ye I meant output scripts! Although it is possible to embed data in the input scripts also. correct horse battery staple brainwallet being the most notorious culprit 😂
See post number five in this thread and try send me a message to wake up to and decipher! httpstcointalk.org/index.php?topic=1239463.0
Google it's hash if you fancy falling down a spooky rabbit hole before bed 👻
Did you ever see the password generator embedded in the input scripts of tx: ba92e66f5469ed5551c3ea4391f09dfcc34b78b66946183e80b8636843a34940? Something tells me its VERY important.
I hadn't even gotten that far, wouldn't put it past them corrupting that repo to be honest this sort of stuff is the intelligence communities worst nightmare.
Public Key (compressed, 66 characters [0-9A-F]): 022952F74E7A53DE7D41EC70E26EB80F1034DE35CC0BBD27FCF101FC5DF12611E5
Nice one! So we could just publish our public keys here and send each other super cool encrypted messages with all the establishment's secrets containing openssl passphrases etc?
Yes a simple new protocol feature: "Set Encryption Public Key";Prefix=0x6d15;Value=35 Char PubKeyHash -> Displayed on profile! Of course the encryption & decryption happens offline.
I will look at that BIP thanks
Yes but we could do uncensorable & untamperable secure asymmetric elliptic curve communications *onchain* with a simple feature to tie a 2nd (cold) address to our accounts 👍🏼
And certainly not use and derive symmetric keys from 3rd party compromisable key servers (memo) or compromisable internet connected android phones (for example) 👍🏼
I do understand, it's just that if you want to do secure communications *onchain* you need to be able to burn keys!!!🔥🔑🔑
The problem with symmetric encryption is that both parties are a security vulnerability; So if either are compromised of the shared key it's GAME OVER so
https://bch.gg/ramer Shoup?
*with off-memo private keys and onchain public addresses
But sure, your ECDH and message hosting is also 3rd party! I just am wary of using memo hosted private keys to do encryption 😐 Maybe we could implement onchain ECDH handshake? *
Well a simple PGP key OPReturn header to associate a MIT key with am account is a good start, no?
The Google captcha is particularly good at identifying via browser fingerprint which device is proceeding to solve the captcha. Check out
https://amiunique.org
Regarding point number 2: Neat, I did not know that! It could be enforced by the 3rd party application. Who shall build it? Will I try?!
