01:26:03 <m-relay> <a​mmortel:monero.social> So everyone gets to spy on everyone ?
09:32:35 <m-relay> <t​sjk:bitcoinist.org> Yes, it is possible, but this has to be explicitly allowed. This goes under the name of "watch tower".
09:43:15 <m-relay> <j​s:nil.im> You only need a watch tower if you want someone else to do the slashing for you while you're offline.
09:45:35 <m-relay> <j​s:nil.im> No, you need to publish that you have a newer state, not the contents
15:27:52 <m-relay> <j​ivan:opaline.uk> To clarify, whenever state changes in a lightning channel, the new commitment transaction (the partially signed transaction that reflects the new channel state) has consists of a HTLC whose time-lock unlocks in less time (say duration t_new) than that of the older commitment transaction (which would unlock after duration t_old, so we have t_new < t_old). If someone broadcasts an o<clipped message>
15:27:53 <m-relay> <j​ivan:opaline.uk> ld state, then in order for the new state to be claimed, it has to be broadcast within an amount of time equal to the difference in the time-lock durations (i.e. t_old – t_new).
15:27:55 <m-relay> <j​ivan:opaline.uk> Anyone who has a copy of the new commitment transaction can do this. In practice, that will be the channel peers, and any watchtowers they're using. The only data in commitment transactions is channel state (how many coins each channel peer has), so someone who has knowledge of all the past commitment transactions can see the flows of money that are happening between the channel p<clipped message>
15:27:57 <m-relay> <j​ivan:opaline.uk> eers, but doesn't know anything else (such as whether the peers were directly involved in the transaction or just hops along a longer payment route, or what the transaction was for, etc.).
15:27:59 <m-relay> <j​ivan:opaline.uk> Random third parties should never see any commitment transactions, because the channel peers should share them with each other and any watchtowers using encryption.
18:51:27 <m-relay> <a​mmortel:monero.social> Thank you very much for your excellent explanation. So my guess is that if a peer doesn't share states with a watchtower or others, old states of his channels can be maliciously claimed while he's offline
19:09:56 <m-relay> <j​ivan:opaline.uk> Yes, that's correct.
21:14:50 <Core2528> hey guys, is there some service to pay for hosting a containerized service ?
21:31:09 <kemosabe> Core2528: have you heard of AWS before? 
21:31:46 <m-relay> <j​ivan:opaline.uk> Most of the big public cloud providers offer this kind of service, e.g. AWS EKS, GCP Kubernetes/Docker, DigitalOcean and Linode have similar services
21:37:49 <m-relay> <s​yntheticbird:monero.social> I think Core2528 was more asking about service accepting XMR...
22:41:02 <boldsuck> maybe servers.guru or rantech/buyVM, both accept XMR
22:42:01 <boldsuck> frantech
22:43:52 <m-relay> <s​yntheticbird:monero.social> Kyun.host was suppose to launch a container service since 6 months now