contract state with iface fungible strange
Matrix-Zhang opened this issue · comments
when we get contract state with iface.fungible(), it return wrong assertOwner
the asset was issued at seal: a0ea0a6b4f9e52d2b12a1f7872c66f6576edfe5b2d88ad158f1d33835068a040:1
then we transfer someone others, the new seal is 41563b544dc1018162fae1e63c471a0693514aeeda4bc96307f5bdcb5933f97f:0
but when we fetch the contract state with iface.fungible(), it just rerturn a0ea0a6b4f9e52d2b12a1f7872c66f6576edfe5b2d88ad158f1d33835068a040:1
the attachment is the stock.dat
i peek it with hex editor, i can found 41563b544dc1018162fae1e63c471a0693514aeeda4bc96307f5bdcb5933f97f
Do you use v0.11.0-beta.5 from crates.io?
Do you use v0.11.0-beta.5 from crates.io?
yes, the version is beta.5
but when we fetch the contract state with iface.fungible(), it just rerturn
on sender or receiver?
The attached stock is whose?
but when we fetch the contract state with iface.fungible(), it just rerturn
on sender or receiver?
The attached stock is whose?
sender, the assert's first beneficiary
I am pretty sure the issue is closed in one of PRs we had in may. Can you pls check that now the system works correctly?