-
m-relay<kiersten5821:matrix.org> in what circumstances will a transfer have to be split into multiple tx? can't find in the docs
-
m-relay<ofrnxmr:xmr.mx> if its a sweep, of you use transfer_split on wallet-rpc and the tx is greater than 100kb
-
m-relay<ofrnxmr:xmr.mx> I dont remember if `transfer` on cli == `transfer_split` behavior
-
m-relay<kiersten5821:matrix.org> yeah it does say "this will be split in 2 tx" when i send to more than 15 outputs (16 or above causes split)
-
m-relay<kiersten5821:matrix.org> i saw tx with more than 100 inputs on block explorer before though
-
m-relay<kiersten5821:matrix.org> so wonder if there are any specifics on the cause
-
m-relay<ofrnxmr:xmr.mx> that too. If you send to > 15 outputs it will split into more txs (max is 16 out, so 15 + change)
-
m-relay<ofrnxmr:xmr.mx> Max inputs is only limited by size, (100kb)
-
m-relay<kiersten5821:matrix.org> thanks, so just the 16 output limit and 100 kb size limit? is there any reason why it's 16 outputs max?
-
m-relay<ofrnxmr:xmr.mx> I think its just a number thats been there for a long time (forever?)
-
m-relay<kiersten5821:matrix.org> it would be good to write this in the docs instead of having it stored just in brains and code
-
m-relay<ofrnxmr:xmr.mx> the 100kb size limit is actually 150kb by consensus
-
m-relay<ofrnxmr:xmr.mx> 100kb is just the way reference wallet software constructs them. There have recently been some txs on chain that someone constructed with different software that use closer to 150kb