13:04:13 Hi 13:04:31 Need help in understanding the status of Integrated Addresses after the recent upgrade 13:09:48 Same as before. 13:13:21 But the monero-wallet-cli is not recognising the transactions anymore 13:13:45 moneromooo: also not able to decode outputs on xmrchain.net with the Integrated Address 13:14:04 moneromooo: only able to decode the inputs (that too using the base address) 13:14:07 Give more info, 13:14:18 like? 13:14:34 Like what you did. Any error there is. 13:14:46 https://xmrchain.net/search?value=16d6d6a87bfa6639c55e89bc71f5cbd76f21d096d4c67ef1f535788e5ac54945 13:15:07 this is an incoming transaction to the integrated Address (4Eb1kaMM1eNWJ5NBsEj2R77ZBEgDa3fEe9GLpSf2FRmhexPvfYDUAB7EXX1Hdb3aMQ9FLqdJ56yaAhiXoRsceGJCdCtbqid7ngX2sCm3QW) 13:15:23 The base address for this is (437yDDiyKnAcxiBQo9LVF6jgcZ3q9AmFjDvrp2STC7Z9YirRiNFfn93YWaNhKSr7r8dMkjQszcdA9ZVEPvBhiNhgEB5HQ55) 13:15:50 Now I am not able to decode the transaction with the Integrated Address as I used to do with a lot of incoming transactions earlier 13:16:12 But this time, I am able to decode the inputs ONLY with the base address 13:16:39 also this transaction is not being recognised into the monero-wallet-cli daemon 13:16:42 Oh, it's your code, not monero's ? 13:17:05 Explain what you mean by "I am able to decode the inputs ONLY with the base address". 13:17:07 when queried, receiving the response "Transaction not found." 13:17:21 ie, what do you do, and what does the wallet say in return. 13:17:25 (if anything) 13:17:54 { 13:17:54 "jsonrpc": "1.0", 13:17:54 "id": "curltest", 13:17:56 "method": "get_transfer_by_txid", 13:17:58 "params": {"txid": "16d6d6a87bfa6639c55e89bc71f5cbd76f21d096d4c67ef1f535788e5ac54945"} 13:18:00 } 13:18:02 I query the wallet instance with RPC command 13:18:09 { 13:18:09 "error": { 13:18:09 "code": -8, 13:18:11 "message": "Transaction not found." 13:18:13 }, 13:18:15 "id": "curltest", 13:18:17 "jsonrpc": "2.0" 13:18:19 } 13:18:21 Paste large stuff elsewhere please. 13:18:21 This is the response I see 13:19:29 Is that related ? 13:19:36 But if I query the node daemon that the wallet-daemon refers to - https://pastebin.com/7aK1M8ha 13:20:07 Oh, nvm, it's a wallet RPC. Ignore my last question. 13:20:11 Somehow, the Integrated Addresses seems to be broken 13:20:23 Has the wallet refreshed past that tx yet ? 13:20:52 yes, the wallet daemon height is the latest 13:21:06 OK. I'll try here. 13:23:20 Is there any update in the transaction or addresses formatting? 13:23:50 No relevant one. 13:41:59 Works for me. 13:42:46 I created two new wallets, mined to one, created an integrated address in the other, sent from the mining one to the other, the other sees the tx, and get_transfer_by_txid works with that tx. 13:43:20 Is your refresh-from-block-height set correctly ? See "set" 13:43:58 where is this flag? 13:44:08 See "set" 13:44:25 I tried the refresh RPC from 0 block height 13:44:30 It did not help 13:45:07 How did you create your wallet ? 13:45:44 Using the monero-wallet-cli tool 13:45:56 But what is the issue with xmrchain.net? 13:46:08 I am not able to decode them on their UI also 13:46:58 I don't know. 13:47:22 Are you sure you're using the right wallet ? 13:48:20 yes, the wallet was deployed like about 5 months ago 13:48:25 running till now 13:48:34 has done like 100s of transactions till yesterday 13:49:13 Then rescan_bc with log level 2, and see if it says anything different when it goes over that particular tx. Any error, mention of being skipped, etc. 13:50:45 rescan_bc ?? 13:51:14 You can do this on a copy of the wallet cache. 13:52:26 Also, are you really sure you sent to that address ? 13:59:47 yes 14:05:15 Does this happen just for this tx, or also other txes ? 14:11:13 a couple of others also 14:12:15 Does at least one work ? 14:13:21 not after they stopped being recognised 14:19:55 Can you tell whether this point was (1) when you updated monero-wallet-cli, (2) when the fork happened, (3) something else ? 14:27:14 After I have upgraded the monero-wallet-cli, no issues 14:27:32 After the fork happened (assuming on 30th Nov), no issues 14:27:43 Issue started like from yesterday night 14:27:52 about 12-15 hours back 14:30:53 But the issue is also on the xmrchain.net 15:23:23 Did you run rescan_bc yet ? 15:32:59 hey guys, i'd love to get involved working on monero in some capacity. who has a pretty global knowledge of projects going on related to Monero? would be great to chat to see where my skills might be applicable 15:34:17 I guess us as a whole. What are you good at, and what do you prefer doing ? 15:48:24 my normal work life involves lots of web & mobile app development. if these skills are useful anywhere in the monero ecosystem i'll elaborate. i generally enjoy programming in most languages, but python is probably a favorite and pure-functional languages like Haskell cause me problems. i just looked at the roadmap and noticed Trezor Hardware Wallets Support as an item. integrations like that are the 15:48:26 kind of things i think my skills would be applicable to. 15:51:17 We use python only for tests I think (tests/functional_tests). Trezor code is C++, ph4r05 is the one maintaining it. 15:52:29 Web stuff, woodser maintains a javascript lib for monero, and has a mostly working monero wallet building with emscripten. I'd like to get a build script for emscripten in tree (including dependencies), maybe you'd want to help with with. 15:52:57 There's also the monero GUI, which is in QML and javascript, I'm sure it could use some mobile improvements. 15:53:38 About integration, easier integration with tor and i2p would be great too if you fancy that. 15:55:37 are all of these projects housed at https://github.com/monero-project?tab=repositories 15:56:14 No. There's https://github.com/monero-ecosystem also, and others. 15:57:03 What you linked is what's maintained by the monero core team and contributors. The one I linked is a collection of projects from other people who decided to put their stuff in one place. 15:58:27 One other interesting project since we're talking about third party ones: https://repo.getmonero.org/selene/primo (QML/javascript/C++). 15:59:28 I'm sure there are other projects around, that's the only links I have though. 16:01:51 vtnerd: your noise PR says: Added support for "noise" over I1P/Tor to mask Tx transmission. 16:02:18 However, I'm getting a load of flood messages and I'm not using I2P nor Tor. Is this expected ? 16:02:40 I'm not using any --tx-proxy or other related switches. 16:03:13 "flood" as in tx relay messages from the flood code. 16:05:56 moneromooo: thanks for the resources, I'll have a look & see if I find anything interesting for me 16:06:18 Sounds good, thanks and welcome :) 16:24:15 @matix-io I’ve been looking for a web developer’s help building two possible web applications using monero-javascript in the monero-ecosystem. Specifically I had in mind a simple wallet application [1] and a stress testing tool that might one day be used to stress test the network. There’s a sample web application [2] which uses the library to demonstrate integration. It currently depends on 16:24:16 monero-wallet-rpc, but I want to support a fully client-side wallet from monero-project via webassembly. [1] wallet mockups: https://github.com/woodser/xmr-sample-app/tree/master/wallet_mockups [2] sample web application: https://github.com/woodser/xmr-sample-app 17:41:23 luigi1111: v0.15.0.1 CLI release notes http://paste.debian.net/hidden/2d9f235f/ 17:41:35 maybe you can add downloads and set it as latest release 17:42:38 are there downloads? 17:42:49 ah wait 17:42:52 you added them to GUI 17:42:56 these are CLI notes 17:43:19 I’ll send you GUI notes later once we have binaries 17:43:42 oh I see 17:43:50 I'm blind 17:43:54 I deleted 17:44:27 there we go 17:51:21 luigi1111w: I forgot about hashes in the paste above http://paste.debian.net/hidden/d39e021b/ 17:51:42 kovri-slack2: yeah those mockups look pretty straightforward. that could be a nice fit for me. 17:58:23 For clarity, kovri-slack2 is a relay, woodser was writing. 17:59:29 where do you hang woodser? some slack i assume? 17:59:44 yes I connect through slack 18:00:52 which slack? 18:01:55 There's more than one ? I thought it was a centralized company. 18:02:34 you have to join a specific slack though? 18:02:58 I believe it’s the kovri.slack.com workspace 18:03:29 yeah 18:04:00 are you the only one there? mebbe move elsewhere? 18:04:18 heh I could be 18:18:12 oh lol woodser i thought kovri-slack was your username 18:18:26 :P 18:20:46 woodser what's the best way to contact you about those projects? 18:21:47 are you able to dm at this username? 18:24:07 woodser just sent one to 18:24:13 which is what it says your username is 18:36:10 keybase? 18:37:44 is it just woodser on keybase? 18:37:50 yes 18:44:34 did i add you or is it an imposter woodser? 18:46:03 it is the real woodser 18:46:47 👌 19:27:17 @matix-io feel free to DM me on keybase at @woodser. I’d be happy to chat further 19:36:53 moneromooo : I don't follow on your flood question. the txes are still using the same "flood" method thats always been used 19:37:37 it sends a never been seen tx to every connection except the one it was received on 19:41:45 Oh, right the existing systen is just going through that new file, I see now. OK, that makes sense.