11:28:57 I am the person who posted the reddit post regarding using Monero tx's for communications and data storage on the Monero blockchain. At the moment I have a very basic prototype that I wrote in C++ , which allows users to decode and print messages. 11:29:27 My only issue is that I am having diffculties with making the monerocpp library work 11:30:25 so I am stuck with the part of automating the part that directly pulls/send data from/to the network 11:30:37 Right now I have to : 11:31:10 1. use get_transfers from the CLI ( this exports a csv into the same folder as the exe monero exe) 11:31:44 2. parse the amount column with the module that I wrote 11:31:58 anonyphi[m]: you can PM woodser[m], he wrote the monero-cpp lib 11:33:04 This pretty much sums the entire process of recieving encrypted messages via the chain ( there are some specific definitions I used in order to separate multiple messages one from the other 11:33:31 anonyphi: you can PM woodser, he wrote the monero-cpp library 11:34:15 I tried that, got a bunch of errors, I think its due to the fact im doing it on a win10 machine 11:36:22 anonyphi[m]: this sounds like a painful process, not using a library that already handles blockchain interactions 11:37:44 woodser[m]: Like I said, right now I use the built in CLI command "get_transfers" which exports a list of transfers into a csv file. parsing it is really simple, its less than 60 lines. 11:37:58 of code 11:41:59 Right now I am able to manually send each transaction ( a single character) one by one to the recipient's address, recipient can then decode with my module... Perhaps I should create a short video demonstrating how messages could be sent, as well as data storage ( technically its possible to save any type of data this way, from short sentences to entire bmp images) 11:42:59 even grayscale images are possible, though quiet expensive due to fees 11:48:33 Why not use something like Bitcoin Cash (it has big blocks and OP Return)? Or you can fork Monero and add your messenger TXs on that chain (e.g. via tx_extra)? 11:49:05 Privacy is the first reason 11:49:35 Encrypt it before you write it in OP return. 11:50:34 second reason is I am not trying to create something new here, almost everything that's required to do this - already exist. my only issue is automating and maximizing efficiency 11:50:59 Also, you really want multiple TB of private messages to be stored permanently (no deletion or edits possible) for decades on thousands of strangers' computers worldwide? 11:51:28 I don't want it, but if someone wants it, I want them to be able to 11:51:54 Then they can implement it themselves or simply use PGP and email, Signal, XMPP or any other non-blockchain solution. 11:53:41 They could also use visa and mastercard, which give you cashbacks unlike monero. Also, this method requires no single connection point between the parties involved 11:54:33 I simply want this to be possible for those who want it. In the end the fees for spamming the network are too high for this to become an issue 11:54:58 and even if this does happen - its simply more rewards for miners 11:55:51 Visa and MasterCard are inaccessible since they require government ID KYC to signup for the credit card. Whereas nothing stops you from downloading PGP, Signal, XMPP, etc. 11:56:13 I feel bad if this bloats the blockchain, increases fees for everyone else, and may harm fungibility. 11:56:19 can we haz emojis in xmr bloatchain please 11:56:45 But you can probably develop this on testnet first. 11:57:42 If you believe that using these things give you the level of security you get with using monero with its 3 GH/s and sending each tx to a different node, I am sorry to disappoint you 11:58:46 I wouldn't feel secure if my private conversations were stored permanently for decades on thousands of people's computers. 11:59:02 But feel free to develop this if you want, nothing stops you. 12:59:30 imho, anything other than using txns to advertise a public key to bootstrap a comms channel is unnecessary bloat 12:59:56 (in the messaging use case) 13:00:23 what townforge does makes sense, chat messages stay in the mempool and don't get mined 13:00:33 (that discussion would be better suited for #monero thought, again, imo :p ) 13:00:59 selsta: yeah that’s neat - to correct my stmt: txns included in blocks 13:56:40 yeah, using the monero p2p network as a relay network independent of storage in the blockchain could be an area of interesting development 13:57:13 especially with the ability to use mine-for-service, or rpc-pay 16:49:43 .merges 16:49:43 -xmr-pr- 7886 7911 7917 16:50:36 Any comments remaining regarding #7891 (zmq changes)? Otherwise I will add it to the merge queue in the next days. 16:52:08 vtnerd: ^ 17:18:34 selsta ping me when you add it, I'll create PR for the release-v0.17 branch too 17:58:35 I've reviewed it, nothing else to say 17:59:00 is that appropriate for 0.17 branch? its an added feature not a bug fix 17:59:06 although the next release will be a while I guess 18:00:03 having it in the official release will make p2pool use easier. Right now I have to bundle it with custom monerod binary 18:48:09 yes, it will take a while to branch from master, it makes sense to PR it against release 22:02:54 are we doing 0.17.3.0 then?