In the early days we imagined how Bitcoin will improve the world. Very few considered that as Bitcoin is a technology that reinvents money, it will expose a lot of shit from around the whole world.
C'mon folks, anybody interested in launching alternative Memo implementation utilising BlockPress codebase? Angular 5 and Ruby on Rails. Get in touch with me, it's perfect time now :)
Bitcoin is fucking awesome, op_return is fucking awesome, bitDB is fucking awesome, memo is fucking awesome, webtorrent is fucking awesome. I am in ecstasies over all these. We will rock the world.
Anyone experienced in Angular 5 / Ruby on Rails, wanna join some fascinating open source project? You know what I mean. Drop me a massage wanzou[a......t]pm.me
Imagine journalists 30 (300?) years from now digging blockchain to uncover us discussing the upcoming hashwar that precedes the epic iceberg flippening.
The more I fantasize about Memo as a global social network the more I think 0x6d won’t be a definitive code of the protocol. More like the first byte that defines a thematic branch.
In the rainbow 🌈 my wife and me
This music video and the song itself are going to be a worldwide hit soon. You can help this video to go viral! (Please don’t tip, I have nothing to do with it)
1mil sounds like another good denomination. 1mil == 1mBTC. It’s not milli-btc though, it’s million satoshis.
It’s very inefficient to use regular outputs to embed data into blockchain. Those utxo’s become forever unspendable.
BitcoinIsP2PC4$H >Did you ever see the password generator embedded in the input scripts of tx -> wtf do you mean? those are completely noraml ScriptSigs
Good idea. You can associate another public key with your account and make an announcement that you only use this key for encrypted communications.
The actual messaging will still be off-chain though, if we consider this protocol as viable.
>>if you want to do secure communications *onchain* >> the communication is off-chain. only initial signaling is on-chain.
Anyway, it is better than plain text emails...
Ok, then just do not use implementations of such a protocol - if it will ever be implemented - that rely on insecurely hosted keys.
To fetch a notification you must listen for all his actions (you anyway listen them if you follow) discarding all that does not include your unique ephemeral id
>The problem with symmetric encryption is that both parties are a security vulnerability -> every modern widely deployed scheme of encrypted communications is a hybrid encryption
If your addressee is interested in communicating with your, he/she extracts your public key -> ecdh -> shared secret (unmasks url) -> unique id (will be different) -> notify you.
-> where actual message encryption is done using symmetric keys
