Hi

Need help in understanding the status of Integrated Addresses after the recent upgrade

Same as before.

But the monero-wallet-cli is not recognising the transactions anymore

moneromooo: also not able to decode outputs on xmrchain.net with the Integrated Address

moneromooo: only able to decode the inputs (that too using the base address)

Give more info,

like?

Like what you did. Any error there is.

this is an incoming transaction to the integrated Address (4Eb1kaMM1eNWJ5NBsEj2R77ZBEgDa3fEe9GLpSf2FRmhexPvfYDUAB7EXX1Hdb3aMQ9FLqdJ56yaAhiXoRsceGJCdCtbqid7ngX2sCm3QW)

The base address for this is (437yDDiyKnAcxiBQo9LVF6jgcZ3q9AmFjDvrp2STC7Z9YirRiNFfn93YWaNhKSr7r8dMkjQszcdA9ZVEPvBhiNhgEB5HQ55)

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

But this time, I am able to decode the inputs ONLY with the base address

also this transaction is not being recognised into the monero-wallet-cli daemon

Oh, it's your code, not monero's ?

Explain what you mean by "I am able to decode the inputs ONLY with the base address".

when queried, receiving the response "Transaction not found."

ie, what do you do, and what does the wallet say in return.

(if anything)

{

"jsonrpc": "1.0",

"id": "curltest",

"method": "get_transfer_by_txid",

"params": {"txid": "16d6d6a87bfa6639c55e89bc71f5cbd76f21d096d4c67ef1f535788e5ac54945"}

}

I query the wallet instance with RPC command

{

"error": {

"code": -8,

"message": "Transaction not found."

},

"id": "curltest",

"jsonrpc": "2.0"

}

Paste large stuff elsewhere please.

This is the response I see

Is that related ?

But if I query the node daemon that the wallet-daemon refers to - pastebin.com/7aK1M8ha

Oh, nvm, it's a wallet RPC. Ignore my last question.

Somehow, the Integrated Addresses seems to be broken

Has the wallet refreshed past that tx yet ?

yes, the wallet daemon height is the latest

OK. I'll try here.

Is there any update in the transaction or addresses formatting?

No relevant one.

Works for me.

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.

Is your refresh-from-block-height set correctly ? See "set"

where is this flag?

See "set"

I tried the refresh RPC from 0 block height

It did not help

How did you create your wallet ?

Using the monero-wallet-cli tool

But what is the issue with xmrchain.net?

I am not able to decode them on their UI also

I don't know.

Are you sure you're using the right wallet ?

yes, the wallet was deployed like about 5 months ago

running till now

has done like 100s of transactions till yesterday

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.

rescan_bc ??

You can do this on a copy of the wallet cache.

Also, are you really sure you sent to that address ?

yes

Does this happen just for this tx, or also other txes ?

a couple of others also

Does at least one work ?

not after they stopped being recognised

Can you tell whether this point was (1) when you updated monero-wallet-cli, (2) when the fork happened, (3) something else ?

After I have upgraded the monero-wallet-cli, no issues

After the fork happened (assuming on 30th Nov), no issues

Issue started like from yesterday night

about 12-15 hours back

But the issue is also on the xmrchain.net

Did you run rescan_bc yet ?

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

I guess us as a whole. What are you good at, and what do you prefer doing ?

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

kind of things i think my skills would be applicable to.

We use python only for tests I think (tests/functional_tests). Trezor code is C++, ph4r05 is the one maintaining it.

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.

There's also the monero GUI, which is in QML and javascript, I'm sure it could use some mobile improvements.

About integration, easier integration with tor and i2p would be great too if you fancy that.

are all of these projects housed at github.com/monero-project?tab=repositories

No. There's github.com/monero-ecosystem also, and others.

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.

One other interesting project since we're talking about third party ones: repo.getmonero.org/selene/primo (QML/javascript/C++).

I'm sure there are other projects around, that's the only links I have though.

vtnerd: your noise PR says: Added support for "noise" over I1P/Tor to mask Tx transmission.

However, I'm getting a load of flood messages and I'm not using I2P nor Tor. Is this expected ?

I'm not using any --tx-proxy or other related switches.

"flood" as in tx relay messages from the flood code.

moneromooo: thanks for the resources, I'll have a look & see if I find anything interesting for me

Sounds good, thanks and welcome :)

<woodser> @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

monero-wallet-rpc, but I want to support a fully client-side wallet from monero-project via webassembly. [1] wallet mockups: github.com/woodser/xmr-sample-app/tree/master/wallet_mockups [2] sample web application: github.com/woodser/xmr-sample-app

luigi1111: v0.15.0.1 CLI release notes paste.debian.net/hidden/2d9f235f

maybe you can add downloads and set it as latest release

are there downloads?

ah wait

you added them to GUI

these are CLI notes

I’ll send you GUI notes later once we have binaries

oh I see

I'm blind

I deleted

there we go

luigi1111w: I forgot about hashes in the paste above paste.debian.net/hidden/d39e021b

kovri-slack2: yeah those mockups look pretty straightforward. that could be a nice fit for me.

For clarity, kovri-slack2 is a relay, woodser was writing.

where do you hang woodser? some slack i assume?

<woodser> yes I connect through slack

which slack?

There's more than one ? I thought it was a centralized company.

you have to join a specific slack though?

<woodser> I believe it’s the kovri.slack.com workspace

<woodser> yeah

are you the only one there? mebbe move elsewhere?

<woodser> heh I could be

oh lol woodser i thought kovri-slack was your username

<woodser> :P

woodser what's the best way to contact you about those projects?

<woodser> are you able to dm at this username?

woodser just sent one to <kovri-slack2>

which is what it says your username is

<woodser> keybase?

is it just woodser on keybase?

<woodser> yes

did i add you or is it an imposter woodser?

<woodser> it is the real woodser

👌

<woodser> @matix-io feel free to DM me on keybase at @woodser. I’d be happy to chat further

moneromooo : I don't follow on your flood question. the txes are still using the same "flood" method thats always been used

it sends a never been seen tx to every connection except the one it was received on

Oh, right the existing systen is just going through that new file, I see now. OK, that makes sense.