05:12:25 <tarkdools[m]> <plowsof[m]> "Is that all xmrsale is? Just a..." <- basically. Also has a woocommerce store though which means I could start up a online wordpress tore and sell things for XMR
05:14:12 <anarkiocrypto[m4> Looks like Monero Integrations already has a WooCommerce plugin: https://monerointegrations.com/
06:46:01 <ajs_[m]> Hydrogen Lab #2 Live DJ Set with RYIT spinning 'Cyber Technology' themed Psytrance this Saturday @ 7PM PDT (02:00 UTC) on XMR.radio
07:54:36 <dEBRUYNE> plowsof[m]: lol :D
13:09:25 <sethsimmons> First mainnet atomic swap completed 👀:
13:09:26 <sethsimmons> https://twitter.com/sethforprivacy/status/1427615531130105856?s=20
13:29:35 <vikrantCake[m]> > <@sethsimmons:monero.social> First mainnet atomic swap completed 👀:
13:29:35 <vikrantCake[m]> > 
13:29:35 <vikrantCake[m]> > https://twitter.com/sethforprivacy/status/1427615531130105856?s=20
13:29:35 <vikrantCake[m]> sweet!
13:30:06 <vikrantCake[m]> Hey all.. Cake version 4.2.5 is out.  The big feature is batching of multiple transactions (for xmr and btc).  I feel its a game changer on mobile as you don't have to do one by one transaction and wait 20 mins between each. Please update now and let me know what you think.
13:31:29 <vikrantCake[m]>  * Hey all.. Cake version 4.2.5 is out.  The big feature is batching of multiple transactions (for xmr and btc).  I feel its a game changer on mobile as you don't have to do one by one transactions and wait 20 mins between each. Please update now and let me know what you think.
13:34:57 <carrington[m]> vikrantCake[m]: Awesome! If only minko was still running to play with this
13:35:49 <vikrantCake[m]> carrington[m]: haha.. it wouldve been perfect for that
13:37:06 <carrington[m]> Regarding the discarding old blocks completely idea, could transactions be constructed in a way such that after X amount of time they will perform a self-send? Thus keeping the transactions "fresh" and allowing the deletion of historic bloating data
13:37:53 <carrington[m]> I imagine some combination of multisig and time locks would be needed but I don't know enough about the XMR implementation of either to know if it is possible
13:41:45 <carrington[m]> I am thinking that "self refreshing" needs to be within the structure of the transaction itself, because leaving it to wallet implementation still requires periodic user interaction
13:53:19 <BusyBoredom[m]> My biggest concern with that idea is how it might affect privacy, because (from my primitive understanding) we'd be treating real outputs differently from decoys. I don't really know what I'm talking about though.