01:09:15 <m-relay> <k​ufecure:xmr.se> Hey folks. If I use Tor to connect to a Monero remote node and send a tx, what exactly does the Tor entry node see? Like, will the entry node,  act like an ISP on the clearnet, know my IP and figure out I’m making a Monero tx? Thanks!
01:18:30 <as2333> kufecure - the entry node knows your address (unless you connect to tor via another proxy). As to what the entry node can learn about you, there's no clear answer. It's certainly possible to guess to some degree what  you are doing by looking at traffic patterns.
01:21:18 <m-relay> <o​frnxmr:xmr.mx> Depends on if the node is an onion or tls, and what wallet you use
01:25:23 <as2333> even when connecting to hidden services, analysis of encrypted traffic patterns will give some information
01:28:31 <m-relay> <o​frnxmr:xmr.mx> If you dont use a wallet that supports cert pinning (or use an http node) then they can potentially strip the ssl
01:28:32 <m-relay> <o​frnxmr:xmr.mx> so yes, if using http, the entry node knows that your ip sent a specific tx
01:30:34 <m-relay> <o​frnxmr:xmr.mx> encrypted traffic patterns of a monero wallet are hard to follow, because every wallet is a bit different
01:34:54 <as2333> https://link.springer.com/chapter/10.1007/978-3-031-64954-7_11?error=cookies_not_supported&code=ea2a487b-9b61-444d-9351-119d9790810a
03:05:47 <m-relay> <k​ufecure:xmr.se> thanks.
06:13:07 <m-relay> <e​longated:matrix.org> List of such wallets ?
09:18:12 <m-relay> <o​frnxmr:xmr.mx> cli, maybe stack
12:39:42 <YUiNA> https://i.imgur.com/VnVHt2i.png
12:40:10 <YUiNA> why do i sometimes not get payouts when i have blocks in the pplns window when a share is found?
12:41:13 <m-relay> <a​nestheticbliss:kyun.host> You get paid when a block is found. When was the last block found?
12:41:37 <m-relay> <a​nestheticbliss:kyun.host> Last share 22 min ago is your share, it doesnt mean p2pool found a block
12:44:39 <YUiNA> ahh thank you
13:21:04 <m-relay> <s​yntheticbird:monero.social> a share is proposed solution with high enough difficulty that the pool can say "oh yeah you aren't fucking with me, you're really working"
13:21:12 <m-relay> <s​yntheticbird:monero.social> and will therefore reward you for it
13:21:50 <m-relay> <s​yntheticbird:monero.social> but this high enough difficulty is often very far from the required difficulty for actually mining the block
13:24:09 <m-relay> <o​frnxmr:xmr.mx> P2pool is a sidechain, no not quite the same as a normal pool that allows shares with ie 1000 difficulty
13:24:44 <m-relay> <o​frnxmr:xmr.mx> so* not quite
13:28:20 <m-relay> <a​nestheticbliss:kyun.host> Yeah but the concept is pretty similar
13:28:35 <m-relay> <a​nestheticbliss:kyun.host> Just that p2pool diff scales with the hashrate of the pool I guess
14:52:01 <ruidx> how do swap services implement monero? I mean, all funds are locked (unconfirmed) until transaction is done? So swap services maintain multiple wallets to serve multiple customers?  
14:52:18 <ruidx> or how does it work
15:00:30 <m-relay> <a​nestheticbliss:kyun.host> They dont need multiple wallets, multiple subaddresses is enough
15:00:44 <m-relay> <a​nestheticbliss:kyun.host> Since the wallets can know to which subaddress the funds came
15:02:27 <m-relay> <a​nestheticbliss:kyun.host> If you get N transactions, each transaction is locked for the next 10 blocks, independent of the rest, regardless of whether its one wallet and one address or multiple
15:02:53 <m-relay> <a​nestheticbliss:kyun.host> So all they have to do is show one different subaddress to each customer
15:05:27 <ruidx> alright, I can understand that wallet can use/spend from separated subaddresses, but AFAIK all funds from them are going into transaction - specified amount goes to specified destination and everything else (except fee) goes back to wallet of swap service
15:06:03 <ruidx> and what goes back to the wallet, to which subaddress? I don't understand this thing
15:06:37 <ruidx> some LLM tells me it goes to new created subaddress in the sequence, some tell me that it goes to primary subaddress with index 0
15:06:41 <ruidx> how to track where it goes?
15:08:57 <ruidx> I guess I better just test it myself and find out :)
15:09:54 <m-relay> <o​frnxmr:xmr.mx> ruidxchange sells 10ltc to 3 people who deposit 1 xmr each
15:10:34 <m-relay> <o​frnxmr:xmr.mx> ofrnxmr is person #4 and needs to swap 1btc for 1xmr. Ofrn sends btc, ruidx sends xmr
15:11:15 <m-relay> <o​frnxmr:xmr.mx> ruidx has 3 xmr, and can send 1 of them np. All of those subaddresses from the first 3 deposits all belong to the same wallet
15:16:20 <ruidx> ruidxchange that's how I will call my swap service thanks
15:18:22 <ruidx> in monero I can't choose `change output` yes? unlike in bitcoin
15:20:02 <ruidx> it's a privacy feature, so transactions can't be linked together using chosen `change output`, do I get it right?
15:20:43 <m-relay> <r​ucknium:monero.social> ruidx: You can perform coin control. Many "user-friendly" wallets don't support it, but the CLI and RPC wallets do.
15:27:48 <ruidx> yeah I think I understand, also I see a nice feature `subtract_fee_from_outputs`, I guess I can use it to construct a transaction to only my chosen outputs, I'll test it out, thanks
15:37:20 <m-relay> <o​frnxmr:xmr.mx> Feather, cake, monfluo all support coincontrol
15:37:46 <m-relay> <o​frnxmr:xmr.mx> I dont think cli and rpc support proper/full coin control (?)(spending specific outputs together)
15:42:15 <m-relay> <r​avfx:xmr.mx> afaik no
15:49:50 <m-relay> <r​ucknium:monero.social> monero-wallet-rpc can freeze and thaw specific outputs.
15:50:43 <m-relay> <o​frnxmr:xmr.mx> Yeah, but cant select which outputs to spend
15:50:56 <m-relay> <o​frnxmr:xmr.mx> Have to freeze all-but the ones you want to spend
15:51:44 <m-relay> <o​frnxmr:xmr.mx> Feather, cake, monfluo, allow you to select outputs w/o freezing others
15:52:20 <m-relay> <o​frnxmr:xmr.mx> I wonder if it will ever be upstreamed lol
15:52:40 <m-relay> <o​frnxmr:xmr.mx> They all run a patched monero lib afaik
16:09:38 <m-relay> <a​nestheticbliss:kyun.host> I don't understand...  The exchange can just show different subaddress to each customer.
16:09:39 <m-relay> <a​nestheticbliss:kyun.host> Customer A is shown 8AXXX
16:09:41 <m-relay> <a​nestheticbliss:kyun.host> Customer B is shown 8BXXX
16:09:43 <m-relay> <a​nestheticbliss:kyun.host> Customer C is shown 8CXXX
16:09:45 <m-relay> <a​nestheticbliss:kyun.host> Each of them deposit their xmr amounts to each account, at different times
16:09:47 <m-relay> <a​nestheticbliss:kyun.host> Each transaction is locked for a different amount of time. Maybe A releases at 10:00, B releases at 10:02 and C releases at 10:15. 
16:09:49 <m-relay> <a​nestheticbliss:kyun.host> Whenever each transaction releases, the exchange pays the customer
16:11:41 <m-relay> <a​nestheticbliss:kyun.host> The exchange knows how much was deposited to each account. So:
16:11:43 <m-relay> <a​nestheticbliss:kyun.host> Customer A was asked to send 1 XMR to 8AXXX
16:11:45 <m-relay> <a​nestheticbliss:kyun.host> Customer B was asked to send 1.5 XMR to 8BXXX
16:11:47 <m-relay> <a​nestheticbliss:kyun.host> Customer C was asked to send 2 XMR to 8CXXX
16:11:49 <m-relay> <a​nestheticbliss:kyun.host> To the exchange, it doesn't matter who sends funds to which address. As long as 8AXXX receives 1XMR, 8BXXX receives 1.5 XMR and 8CXXX receives 2 XMR, the exchange is happy and will pay them
16:12:02 <m-relay> <a​nestheticbliss:kyun.host> It doesn't need multiple wallets for any of this. Just one wallet and multiple subaddresses
16:13:12 <m-relay> <r​obbin_da_hood:matrix.org> What's the size of the BC these days guys? 250GB
16:14:03 <m-relay> <r​obbin_da_hood:matrix.org> I'm at around 60
16:15:05 <m-relay> <r​obbin_da_hood:matrix.org> 48 hours in
16:15:38 <m-relay> <a​nestheticbliss:kyun.host> Pruned, like 80 or 90GB I think. Non pruned like 225? 250?
16:16:42 <m-relay> <a​nestheticbliss:kyun.host> Are you downloading to an SSD or HDD? HDD can be hell
16:16:57 <m-relay> <r​obbin_da_hood:matrix.org> Yeah. Sounds about right. I'm going full, public node with --restricted-rpc. I'll hide behind Tor when it has caught-up.
16:17:13 <m-relay> <a​nestheticbliss:kyun.host> Yeah it will take a while 😅
16:17:17 <m-relay> <r​obbin_da_hood:matrix.org> External HD.
16:17:39 <m-relay> <a​nestheticbliss:kyun.host> Yes but whats the tech? Is it a magnetic spinning disk (HDD) or a solid state SSD
16:17:54 <m-relay> <a​nestheticbliss:kyun.host> HDD's are slow as hell and will take ages to sync
16:20:27 <m-relay> <r​obbin_da_hood:matrix.org> HDD I reckon. I can hear it whirring.
16:23:18 <m-relay> <a​nestheticbliss:kyun.host> Yeah then it will be very very slow
16:34:45 <ruidx> anestheticbliss: here is the thing, continuing your example, after customers A, B and C were asked to send the amounts, here comes customer D, he wants to get 2.6 XMR, and if using monero-wallet-rpc, all of the funds will be locked in the transactions, from all addresses of the clients, 8AXXX, 8BXXX and 8CXXX, and meanwhile swap service can't serve potential client E, even if there should be
16:34:48 <ruidx> available balance of 0.9 XMR, because if subaddress is used in a transaction, no matter if you want only a small portion of funds from it, anyways all of the funds from it will be locked in a transaction 
16:35:17 <ruidx> that's why I asked in the first place, but now I think there can be a workaround by splitting `change output`
16:37:12 <m-relay> <a​nestheticbliss:kyun.host> If those customers come and the wallet doesn't have unlocked funds, the customers will just wait 20 min for the funds to unlock
16:37:40 <m-relay> <a​nestheticbliss:kyun.host> Its the exchange's responsibility to have enough unlocked funds to have a good customer experience
16:38:06 <ruidx> yep here is the problem, swap service shouldn't have a long queue 
16:38:12 <ruidx> yeah that's true 
16:43:35 <m-relay> <e​verythingxmr:matrix.org> I think these no KYC exchanges can really afford to pay higher transaction fees
16:43:49 <m-relay> <e​verythingxmr:matrix.org> With the shit rates they have
17:01:47 <m-relay> <o​frnxmr:xmr.mx> Exch, for example, has this problem all the time
17:02:19 <m-relay> <o​frnxmr:xmr.mx> You'd be told "wait 7 blocks for your xmr to unlock" because reserves were low
17:04:08 <m-relay> <o​frnxmr:xmr.mx> If reserves arent low, and exchange has a lot of enotes to use, its not really a issue. Even large exchanges have "bankrun" issues, where their hot wallet is drained faster than replenished by deposits
17:24:13 <m-relay> <a​nestheticbliss:kyun.host> Fee is irrelevant to funds being locked
17:24:28 <m-relay> <a​nestheticbliss:kyun.host> Most of the times, fees don't make any difference in Monero
17:30:36 <m-relay> <e​verythingxmr:matrix.org> Funds get unlocked when the transaction gets to 10 confirms
17:30:49 <m-relay> <e​verythingxmr:matrix.org> Paying higher fees makes that faster
17:31:53 <m-relay> <a​nestheticbliss:kyun.host> 10 confirmations just means the blockchain increased by 10 blocks since you made that transaction
17:32:30 <m-relay> <a​nestheticbliss:kyun.host> Your fees do not make the chain grow faster, the chain regulates itself to grow at 1 block per 2 minutes
17:33:01 <m-relay> <e​verythingxmr:matrix.org> Oh lol
17:33:40 <m-relay> <a​nestheticbliss:kyun.host> The only thing higher fees do, is they make the miners prioritize your transaction if there is a high amount of transactions at that specific moment and they dont all fit in the blocks
17:34:03 <m-relay> <a​nestheticbliss:kyun.host> But this happens rarely, and it only happens for until you actually get inside a block. After that, its 10 blocks no matter what you do
19:19:01 <m-relay> <o​frnxmr:xmr.mx> I have xmrig-proxy running on one of my servers, and noticed 7 workers that arent mind :D lol
19:21:13 <m-relay> <o​frnxmr:xmr.mx> All of them are currently disconnected,  and its not running on the standard 3333 port. I wonder why they tried to mine there instead of my rpc