00:00:15 If you must use the same seed with multiple wallet-rpc instances, i'd use subaccounts instead of subaddresses 00:01:15 ^ subaccounts (except account 0 that has main address at index 0) logically limit how mixing addresses work, and that lets you have multiple deposit/change addresses per user 00:02:03 note subaccounts or subaddresses within the subaccount are limited to uint32 on current implementation 00:02:20 uint32+uint32. This is relevant if you want to have many users. 00:42:27 given uint32+uint32 index space, what operational ceilings have you seen (wallet cache size / scan time) for accounts × subaddresses before it gets painful? 00:47:55 also, DataHoarder, if I run multiple wallet-rpc instances from the same seed, is the recommended pattern to restore into separate wallet files and give each instance a disjoint account (major) range to avoid overlap in change/spend selection? 00:48:54 I have implemented view wallets directly (from a programming perspective) and the wallet scan is more or less, viewkey lookup per tx, then checks a hashmap 00:49:10 the hashmap has all tracked subaddresses 00:49:23 that allows you to get the account/offset index 00:49:35 different seeds require repeating this process anew 00:49:57 yes, re multiple wallet files with same seed but different accounts 00:50:24 each account will have its own change/spend selection, yes 00:50:39 but dont need a new wallet-rpc for each account 00:50:53 You can just pass the account in the json req 00:51:54 1 wallet-rpc would be fine unless you need to send more than like, 1tps 00:51:57 the hashmap is composed of 32 bytes for the key, and 8 (4+4 bytes for the account/offset) value 00:52:54 you can probably have a low lookahead per user (then programmatically increase it as needed) 00:53:27 But if you are using multiple wallet rpcs, make sure they are designated to only touch certain accounts. Meaning wallet-rpc 1 only touches account 1-9999, wallet-rpc2 only touches account 10000-19999 erc 00:53:59 monero does the same > std::unordered_map subaddresses; 00:54:15 @datahoarder, if users are creating new addresses manually, then you shouldnt need the lookahead at all 00:54:21 exactly 00:54:32 same for accounts, it's effectively increased 00:54:38 with that, you can establish a lower bound in requirements in loaded indices ^ 00:54:50 (32+8 00:55:13 (32+8) * (number of users * average subaddresses per user) bytes 00:56:46 even considering all users (uint32) are used, with one subaddress each, that's 160 GiB of data 00:57:38 map overhead will make it go above that, ofc 01:01:49 thanks guys, appreciate the guidance 15:34:02 Test 15:36:15 What DEXes you suggest for swapping Monero?.. I use Fixed float 15:37:07 ERROR: not development related; Try [#monero:monero.social](https://matrix.to/#/%23monero:monero.social) 17:17:54 Please don't continue using FF. They are know to retain customer funds pending an onerous KYC process. They are rated BAD in kycnot.me and not even listed in Orangefren.com. Find another option from orangefren.com or use trocador.app to choose a better rated exchange 17:18:06 Please don't continue using FF. They are known to retain customer funds pending an onerous KYC process. They are rated BAD in kycnot.me and not even listed in Orangefren.com. Find another option from orangefren.com or use trocador.app to choose a better rated exchange 17:29:51 Please dont continue to use this room 17:30:29 and a correction: they are, in fact, listed in orangefren and trocador 20:33:21 Apologies if this is not the right place 20:33:58 Not in orangefren. I just checked once again. Fixed float is not listed 22:32:23 when monerod tx-proxy=tor,... do separate transactions go to different peers over different tor circuits? 22:35:42 No 22:36:16 There is ofc a more complete amswer than that, but in short: no, stream isolation per tx is not used 23:25:27 is there a way to enable it? restarting tor after every transaction is an option but why... 23:25:46 is there a way to enable it? restarting tor before every transaction is an option but why... 23:29:44 how long lived are the connections monerod forms to other peers? tor circuits have a 15 minute lifetime by default but if the connection it kept open the circuit lives indefinitely and there isn't an easy way to kill it without restarting tor. 23:43:35 Hey everyone. I'm having some trouble with my monero cold storage wallet. I was trying to sign a transaction offline and broadcast it from a view only wallet and i seem to have messed something up. I got an error about a double spend and now when i restore my wallet with the private spend key vs a watching only wallet there is a 20xmr difference in balance. I think this has to do 23:43:35 with my key image marking my outputs as spent when they aren't? On the full spend key wallet its not showing 2 of the incoming transactions that i am able to see on my view only wallet. If anyone is able to help me fix this id really appreciate it. Ive been trying for a couple days 23:48:34 Cuprate may have it