-
m-relay<blurt4949:matrix.org> Thanks moneromooo!
-
m-relay<blurt4949:matrix.org> rbrunner: I'm just curious to see how far it can be pushed. I'm not sure I'll be able to reach my 2^20 goal though since signing/verifying time is exponential...
-
m-relay<blurt4949:matrix.org> er- *quadratic
-
m-relay<aremor:matrix.org> Happen to know what commit broke it?
-
m-relay<keepemup:matrix.org> Is it possible to transfer/sweep multiple outputs across different account indexes?
-
m-relay<keepemup:matrix.org> I know you can use outputs from multiple subaddr indices (as long as the subadresses belong to the same account index),but are you limited to using outputs that are ultimately under just one account index per txn?
-
rbrunnerI think so, yes. The "walls" between the accounts are pretty hard, by design, to implement something like "wallets within wallets".
-
rbrunnerIt's no fundamental thing, however, as far as I know. You could build yourself a CLI wallet version which would allow such things, together maybe with some modifications in `wallet2`.
-
m-relay<xfedex:matrix.org> well yes, but actually no
-
m-relay<xfedex:matrix.org> that would work, but you wouldn't be able to "cancel the subscription" and stop future payments, since they are actually already done but not complete
-
m-relay<xfedex:matrix.org> also, iirc monero's timelock limit is 2 years
-
m-relay<snowman:tetaneutral.net> I think you can do longer with cli
-
rbrunnerThe field in the transaction to hold the `unlock_time` value allows for billions of years. The rest are deliberate software limits.
-
m-relay<keepemup:matrix.org> Rbrunner, thanks, will continue research
-
rbrunnerIt's understood that we will soon nuke that lock feature, right?
-
m-relay<j0j0xmr:monero.social> Can consensus been reached regarding tx_extra?
-
m-relay<j0j0xmr:monero.social> Has consensus been reached regarding tx_extra?