-
m-relay<kiersten5821:matrix.org> what is the default behavior around output management in the wallet? does it target a certain number of outputs or something? if i have 1000 outputs and i'm making normal small transfers will it attempt to shrink the number of outputs i own? i have definitely had cases where i had very few outputs and the wallet was consolidating them anyway and reducing the number of outputs i ha<clipped message>
-
m-relay<kiersten5821:matrix.org> d afterwards. this doesn't seem well documented
-
m-relay<ofrnxmr:xmr.mx> Prefers 2 over 1
-
m-relay<ofrnxmr:xmr.mx> But the details are in fact not well documented and behavior not consistent
-
m-relay<kiersten5821:matrix.org> you mean prefers to use 2 inputs instead of 1 when building a tx?
-
m-relay<ofrnxmr:xmr.mx> example.. you could have outputs of 1, 3, 5. If spending 3.5xmr it will usually spend the 1 + 3. Why? If it spends the 5, it creates more small outputs which worsen privacy over time by creating a lot of small outputs that are later consolidated
-
m-relay<kiersten5821:matrix.org> got it, so by default it tends towards very few large outputs. how do i balance this with needing to have more smaller outputs to be able to make a lot of tx in a short period of time, assuming privacy is not extremely important? and if i have too many outputs then i'm not immediately able to send a large chunk of the balance due to the tx size limit. is there any guide to this? i<clipped message>
-
m-relay<kiersten5821:matrix.org> s this why exchanges are constantly having withdrawal issues on the coin?
-
m-relay<ofrnxmr:xmr.mx> mobile wallet (or feather) coin control
-
m-relay<ofrnxmr:xmr.mx> No, exchanges have withdrawal issues becuase they dont have the xmr :D
-
m-relay<ofrnxmr:xmr.mx> You dont close withdrawals for 30 days while trading xmr 10% below other exchanges _while accepting deposits_ and have a legit reason for doing so
-
m-relay<kiersten5821:matrix.org> i remember binance had delayed withdrawals for a few hours at a time back in the day and they were approximately the same price as everyone else during that time
-
m-relay<kiersten5821:matrix.org> is there any advice on how to balance the few outputs -> 20 minute lock on transfers with the many outputs -> max transfer size limited in a role similar to an exchange?
-
m-relay<kiersten5821:matrix.org> or will i just have to study everything and then do the freeze everything then spend trick in the wallet rpc to manually manage all the outputs
-
m-relay<kiersten5821:matrix.org> is there any advice on how to balance the (few outputs -> 20 minute lock on transfers downside) with the (many outputs -> max transfer size limited downside) in a role similar to an exchange?
-
m-relay<ofrnxmr:xmr.mx> There are a few very valid reasons.
-
m-relay<ofrnxmr:xmr.mx> 1. Spend wallet corrupt, needs resyncing. Wallets with a ton of outputs take longer to sync (explains hours to resync).
-
m-relay<ofrnxmr:xmr.mx> transfer_split gets around max transfer size
-
m-relay<ofrnxmr:xmr.mx> Also wallet maintenance gets around transfer split. Use sweep below to consolidate dust daily
-
m-relay<ofrnxmr:xmr.mx> Sweep_all with below_amount param
-
m-relay<ofrnxmr:xmr.mx> docs.getmonero.org/rpc-library/wallet-rpc/#sweep_all
-
m-relay<kiersten5821:matrix.org> what do you mean by wallet maintenance gets around transfer split
-
m-relay<ofrnxmr:xmr.mx> If you have outputs large enough to satisfy the withdrawals, you wont need to split a transfer
-
m-relay<ofrnxmr:xmr.mx> you can fit ~146 inputs into a tx. If your largest 146 inputs can satisfy the largest expected withdrawal request, you wont have an issue. You have issues when all of your inputs are 0.001xmr
-
m-relay<kiersten5821:matrix.org> oh. you mean regularly maintaining your outputs. i thought you meant there was some automatic process that bricked it somehow
-
m-relay<ofrnxmr:xmr.mx> Not necessarily manually though. Aitpmating a sweep below amount every day / week can deal with the dust on your behalf
-
m-relay<ofrnxmr:xmr.mx> If your exchange has like 20k xmr, and processes withdrawals over 500xmr, it would make sense to keep outputs of 100+xmr on hand
-
m-relay<kiersten5821:matrix.org> this all makes sense, thanks
5 hours ago