-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spend transactions to sub-account not shown in the mdw and explorer. #131
Comments
@mradkov can you please expand more on this? |
hi there, could you give an example of what you were expecting to see? I don't really understand from this what this issue is about? |
Steps to reproduce: create a keypair, derive second public key and send a spendtx from the main account to the sub-account. Main account [at index 0 according to the derivation path] Sends transaction to Sub-Account [at index 1 according to the derivation path] === Tx is not visible for neither of those. It is persisted on-chain and can be found here: https://testnet.explorer.aepps.com/#/tx/th_dAEWH1hZ637xpkpmYcFxbw2pEpxT1od5tGpUr1422xh8B9557 Expected behaviour: Tx to be present at both pubkeys in the explorer/mdw. |
OK I don't understand why but this one was not in the DB--when I made it load the tx again, it went in. Do you have other missing transactions? |
Loads are missing! Looks like a wider problem. I am manually reloading all blocks into the testnet mdw right now which should correct the issue until I can make a better fix. |
Not sure how long ago this originates, but I assume there might also be other stuff missing/affected. It will be good if there is a way to verify everything after reloading this into the mdw. |
I have sent 2 ae in two transactions from ak_2swhLkgBPeeADxVTAVCJnZLY5NZtCFiM93JxsEaMuC59euuFRQ to ak_212Jw6LJGMCKB5yRo8E3esazSDdC1ZyDcbzenh8PfkAXHJKvFV. But |
do you know when this will be addressed/resolved? |
Okay, will check it now. |
Spend transactions sent from pubkey0 to pubkey1 and so on are not present in the middleware's history nor in the explorers relying on the middleware.
The text was updated successfully, but these errors were encountered: