DApp connection to Lace Beta complains about versions

Technical Questions
1

Hi!

I am trying to use the DApp connector api to interact with the user’s approved actions.

Whenever I try to use any action besides the wallet state it will complain about the version of the proofs I am sending.
I am running DApp Version 3.0, Wallet-Api and Wallet v5 and Zcash as v4, all of them being the latest.

Tried downgrading to version 3.0.0 across the board but that did not change the error.

I am trying the normal balance → prove → submit flow but nothing seems to work with the DApp connector api. I would expect to be popped up a Lace Beta approval modal such as the one we’ve received when syncing the wallet with my application.

Has Lace Beta not implemented these actions or am I too far in the versioning?

I would expect it to work seamlessly as that was the point of the api itself. If you wonder what I try to send, it’s an empty Transaction with 0 tDUST (created via nativeToken() flow) with a 0 value, basically just querrying the network itself before moving into more complex actions.

Hope I can get some help.

Kind regards.

image
image1715×144 17.1 KB

2

Would probably makes sense if you show your package.json file as well your running proof server version exactly.

3

@sergeykisel Hi and thanks for the pervious answer.

This is what is midnight related in my package.json:

“@midnight-ntwrk/dapp-connector-api”: “3.0.0”,
“@midnight-ntwrk/wallet”: “5.0.0”,
“@midnight-ntwrk/wallet-api”: “5.0.0”,
“@midnight-ntwrk/zswap”: “4.0.0”

For the proof-server I am running 4.0.0 flat.

I checked the compatibility matrix and all versions tick.

Is there anything which I am missing that could cause this issue?

4

The picture from above is for when trying to erase proofs and it complains about version 0 when max is 4.
Without trying to erase proof, it complains about version 11 when max is 4.
Do we have any guideline for this?
Proof-server version does not seem to impact this.

5

Why would you call eraseProofs()? what is the use case actually? I think youre trying to do something which is on the lower-level API which is not really exposed to the user by midnight-js, could be that you’re bypassing some of the safety checks which in the end fails on the wasm level..

1 Like