Wrong address as issuer in listasset directly after creating asset

Question

Hi,

I discovered the following problem.

(using beta2, single node)

- create an address (lets say it is ABC)

- grant permissions to this address

- create another address (XYZ(

- grant permissions to this address

- create an asset using issuefrom with XYZ

- directly query the asset just created using: listasset (with verbose = true)

-> the issuer is (sometimes) the address ABC and not XYZ

-> when you wait some seconds (maybe let the asset creation be mined?) the address of the issuer changes to the correct one (XYZ) I used with issuefrom

 

The problem occours in my automatic unit tests, so you have to fire the request very fast.

And also then the problem occours with probability of about 30 %.

 

I don't know if the mistake is on me here (but I have no idea where), or if this is the correct behavior or a bug?

 

I could not debug this directly on multichain with --debug  but sadly only the requests are logged, and not the rpc responses. So I would atleast see if the wrong response really comes from the multichain and is not e.g. an caching issue on my side..

 

Greetings,

Alex

Answer 1

Thanks for reporting this – it sounds like it could likely be a bug with MultiChain, because many querying APIs have separate logic for memory pool-based changes in state and blockchain-based changes in state. We'll look into this for the production release, and be in touch if we need any further information. I hope you're able to work around it for now.

Answer 2

We believe we've identified and fixed this problem, which occurs when there is more than one unconfirmed asset issuance in the memory pool. Please contact us if you'd like a hotfix for your testing, otherwise it will be in the final 1.0 release to come out shortly.

Comments

Great news. I'll wait for the 1.0.
Thank you for the information.