01:57:49 Are you sure that they are actually connected to each other? 01:58:41 Because if not, a node that is supposed to be online but has 0 connections, and hasn't yet connected to a node will return "busy" errors 06:26:24 yes. when I type "status" in both they show 1 in and 1 out 07:03:20 Is is a mode which has any checkpoints ? If so, that will happen and you need to remove checkpoints. 07:03:54 You said testnet so unlikely if you mean actual testnet, but I've seen that happen before. 07:05:22 Oh, testnet does seem to have checkpoints (src/checkpoints). 07:08:17 not sure if related: checkpoints for fast sync in testnet require this change https://github.com/spackle-xmr/monero/pull/35/files#diff-3dcea545b20bc1145f2766e64ca91d4e547d6072462970fd67830e1be6cdf793 09:08:09 how can i check the balance of a subaddress of monero publicly if i have the view key? 12:21:22 I have removed checkpoints from src/checkpoints. Is the "SYNCHRONIZED OK" suppossed to appear after 100/100 synced? I'm not seeing the OK. 12:26:47 Setup a third node 12:27:34 A > B, B > C, C > A 12:28:13 make sure `--allow-local-ip --max-connections-per-ip=3` is set 12:31:15 Testing now.. 12:32:42 and you're following this guide? https://github.com/moneroexamples/private-testnet 12:40:58 Yes, it is supposed to appear. 12:41:43 I've seen it fail to show up from time to time, there is likely a bug somewhere. 14:44:57 https://x.com/silentlink1/status/1833153070940741890 14:45:12 does subaddress-lookahead not do what it's supposed to? 14:48:24 open source their backend and someone can take a look or offer a bounty for help 14:50:23 Or tell them to fix their matrix or come here 14:50:32 Twitter is the best support platform 14:52:17 or is this the related issue: https://github.com/monero-project/monero/issues/8980 14:52:28 pretty sure they are using the command wrong 14:52:32 yeah I was wondering if it isn't related to an open issue 14:52:48 my expectation is that they've created a ton of subaddresses - one for every new invoice 14:52:58 and so they have to lookahead past unpaid invoices 14:53:03 which might number in the thousands 14:53:44 Given that they are a merchant, 1000 seems a bit little? 14:53:57 Especially if they use one address per invoice/payment 14:55:05 I mean they know internally how many are unpaid, no clue 14:55:06 Are they using cli or rpc? 14:55:16 definitely RPC - their payments are automated 14:55:34 Twit says cli, but that seems strange 14:55:51 If they are looking for a specific payment, then maybe they would have to re-scan the blockchain after resetting the lookahead value. Also, should subaccount lookahead really be zero? Probably it is ok, but a non-zero value could rule out more problems. 14:57:24 They should try tunning it with startup flags instead of `set` and see if that has any diff behavior 14:57:45 Meantime ill see abt getting the interactive flag fixed / investigated 15:01:42 By default there are 50x200 address lookahead. Thats 10000 addresses. Probably easier to use 200 then switch accounts 15:03:36 They should try tunning it with startup flags instead of `set` and see if that has any diff behavior << nvm this doesnt work with an existing wallet 15:18:05 When i create a wallet with --subaddress-lookahead 50:500, it works 15:18:53 Seems that the `set` method may be broken. Will try that now 15:23:32 Yeah. `set` method is bogus 15:23:57 Tried 3 nodes, no difference 15:25:05 There are no errors connecting nodes to each other, they sync, the OK message doesn't appear but that's it. 15:25:06 Connecting CLI wallet to one of the nodes gives: 15:25:08 ```[127.0.0.1:59276 cb82f094-f991-4e67-bdf6-ebca88add4fd INC] NEW CONNECTION 15:25:10 2024-09-09 15:24:15.288 D connection type 2 127.0.0.1:1235 <--> 127.0.0.1:59276 (via 127.0.0.1:59276) 15:25:12 2024-09-09 15:24:15.349 E [127.0.0.1:59276 INC] Signature mismatch, connection will be closed``` 15:25:14 There are no errors connecting nodes to each other, they sync, the OK message doesn't appear but that's it. 15:25:16 Connecting CLI wallet to one of the nodes gives: 15:25:18 `[127.0.0.1:59276 cb82f094-f991-4e67-bdf6-ebca88add4fd INC] NEW CONNECTION 15:25:20 2024-09-09 15:24:15.288 D connection type 2 127.0.0.1:1235 <--> 127.0.0.1:59276 (via 127.0.0.1:59276) 15:25:22 2024-09-09 15:24:15.349 E [127.0.0.1:59276 INC] Signature mismatch, connection will be closed` 15:25:44 start_mining still doesn't work because daemon is "busy" 15:31:57 delete lmdb and try again? 15:34:28 Doesn't fix it 15:34:46 SYNCHRONIZATION started 15:34:48 Synced 99/99 15:35:03 SYNCHRONIZATION started 15:35:04 Synced 99/99 15:35:06 Daemon is busy can't use start_mining 15:35:17 no idea why 16:04:48 How did you sync to 99 without mining 16:14:02 I mined on one node using --offline then the other nodes synced the offline mined blocks when added as exclusive peers 16:16:52 Why --offline? 16:19:00 https://github.com/moneroexamples/private-testnet 16:19:00 follow guide here for "start first node" 16:42:24 hello friends 17:09:16 hello, john_alan 19:23:15 I can build v0.18.3.4 on macos by applying PR 9462, but I'm still getting this error building monero-cpp, when importing cryptonote_basic/account.h: 19:23:16 In file included from /Users/woodser/git/monero-ts/external/monero-cpp/src/wallet/monero_wallet_keys.h:56: 19:23:18 In file included from /Users/woodser/git/monero-ts/external/monero-cpp/external/monero-project/src/cryptonote_basic/account.h:33: 19:23:20 In file included from /Users/woodser/git/monero-ts/external/monero-cpp/external/monero-project/src/cryptonote_basic/cryptonote_basic.h:41: 19:23:22 In file included from /Users/woodser/git/monero-ts/external/monero-cpp/external/monero-project/src/serialization/binary_archive.h:43: 19:23:24 /Users/woodser/git/monero-ts/external/monero-cpp/external/monero-project/contrib/epee/include/span.h:165:5: error: static assertion failed due to requirement 'std::is_trivially_copyable>>()': type must be trivially copyable 19:23:26 static_assert(std::is_trivially_copyable(), "type must be trivially copyable"); 19:23:28 any ideas? 19:51:29 found by fix, by adding `rct::sk2rct` around keys 22:17:13 because i can't mine any other way, offline worked but when connecting nodes to each other mining says daemon is busy error 22:17:50 I followed the guide you linked but it doesn't work. Thats how i got the daemon busy error 22:18:06 Did you follow the guide exactly as written? 22:18:28 Ill try to reproduce 22:19:24 Do it with a new private chain and mine some blocks with peers connected see if it works or regtest 22:27:39 Working fine here.. 22:27:45 Monero Support 22:28:18 Have you tried with an empty chain and mine a few blocks? 22:28:32 Yes 22:28:45 Thats exactly what im doing atm 22:28:52 In offline or not? 22:29:03 No 22:29:18 Monero Support 22:29:50 Have you removed checkpoints? 22:30:12 Monero Support please 22:32:28 Passing this off to my associate ofrnxmr:xmr.mx