You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a long time the error [ERR] CORE: non-existent 42 wallet should exist has been around:
2024-05-03 02:41:07.927 [TRC] MUX: "POST http://127.0.0.3:5758/api/newwallet HTTP/1.1" from 127.0.0.1:47976 - 200 12B in 431.15313ms
2024-05-03 02:41:08.028 [TRC] CORE[dcr]: Fallback fees set at 20 atoms/byte
2024-05-03 02:41:08.028 [TRC] CORE[dcr]: Fees rate limit set at 100 atoms/byte
2024-05-03 02:41:08.028 [TRC] CORE[dcr]: Redeem conf target set to 1 blocks
2024-05-03 02:41:08.040 [TRC] CORE[dcr][TXHISTORYDB]: All 0 tables opened in 0s
2024-05-03 02:41:08.237 [DBG] CORE[dcr]: tip change: 0 (6bef82c645999585f7255cb02672921ac2f5492820090cd635fe3a59d16b4f87) => 669 (1cee355787ba89f92a5b8cfd4eeac921f587074f001daae9a99c80d1c97386d4)
2024-05-03 02:41:08.237 [TRC] CORE: Processing tip change for dcr
2024-05-03 02:41:08.237 [ERR] CORE: non-existent 42 wallet should exist
2024-05-03 02:41:08.311 [INF] CORE: Created dcr wallet. Balance available = 0 / locked = 0 / locked in contracts = 0, Deposit address = SssQ6ThpSrDXngZ8Zr3Znw5NYpExatAU7o7
2024-05-03 02:41:08.311 [TRC] MUX: "POST http://127.0.0.3:5758/api/newwallet HTTP/1.1" from 127.0.0.1:48004 - 200 12B in 815.218188ms
2024-05-03 02:41:09.949 [TRC] CORE[ltc][TXHISTORYDB]: All 0 tables opened in 0s
2024-05-03 02:41:09.951 [DBG] CORE[ltc][SPV]: Starting native LTC wallet...
It doesn't seem to have an effect on anything, so we should silence it at least. To reproduce just make a new simnet dexc and the error should be there. It may only happen for brand new clients.
The text was updated successfully, but these errors were encountered:
For a long time the error
[ERR] CORE: non-existent 42 wallet should exist
has been around:It doesn't seem to have an effect on anything, so we should silence it at least. To reproduce just make a new simnet dexc and the error should be there. It may only happen for brand new clients.
The text was updated successfully, but these errors were encountered: