# No Transaction Occuring \[SOLVED\] **URL:** \ **Category:** Technical\ **Created:** [June 21, 2018, 1:47pm UTC](https://community.blockcerts.org/t/no-transaction-occuring-solved/1142 "2018-06-21T13:47:38Z")\ **Posts on this page:** 7\ **Page:** 2
**Author:** ![dev](https://avatars.discourse-cdn.com/v4/letter/d/e8c25b/32.png) [@dev](https://community.blockcerts.org/u/dev)\ **Post date:** [June 22, 2018, 3:00am UTC](https://community.blockcerts.org/t/no-transaction-occuring-solved/1142/21 "2018-06-22T03:00:28Z")
Meanwhile, @Palash-A > Check this out. This was the supposed fix it seems (for windows and mac machines). And, I think you are not using docker, so this might be the fix you are looking for. Try importing as \_pysha3 and check? ---
**Author:** ![aronning](https://avatars.discourse-cdn.com/v4/letter/a/47e85d/32.png) [@aronning](https://community.blockcerts.org/u/aronning)\ **Post date:** [June 22, 2018, 3:29am UTC](https://community.blockcerts.org/t/no-transaction-occuring-solved/1142/22 "2018-06-22T03:29:14Z")
Yup! You have that correct. If you check the signed json file, you’ll see that the recipient address is in there. ---
**Author:** ![Palash-A](https://sea2.discourse-cdn.com/flex016/user_avatar/community.blockcerts.org/palash-a/32/384_2.png) [@Palash-A](https://community.blockcerts.org/u/Palash-A)\ **Post date:** [June 22, 2018, 12:28pm UTC](https://community.blockcerts.org/t/no-transaction-occuring-solved/1142/23 "2018-06-22T12:28:21Z")
Yes I know I can’t do that. My point was to check whether the other imports were working in the file or not and whether `keccak_224` was used by cert-issuer. I wanted to see if `sha_224` would be used instead. ---
**Author:** ![Palash-A](https://sea2.discourse-cdn.com/flex016/user_avatar/community.blockcerts.org/palash-a/32/384_2.png) [@Palash-A](https://community.blockcerts.org/u/Palash-A)\ **Post date:** [June 22, 2018, 12:32pm UTC](https://community.blockcerts.org/t/no-transaction-occuring-solved/1142/24 "2018-06-22T12:32:58Z")
Yup. I got my certificates to issue on Python 3.5 I did change the requirements of `pysha3` in `/lib/python3.5/site-packages/merkletools-1.0.2-py3.5.egg/EGG-INFO/requires.txt` from `pysha3==1.0b1` to `pysha>=1.0.2` though. ---
**Author:** ![Palash-A](https://sea2.discourse-cdn.com/flex016/user_avatar/community.blockcerts.org/palash-a/32/384_2.png) [@Palash-A](https://community.blockcerts.org/u/Palash-A)\ **Post date:** [June 22, 2018, 1:29pm UTC](https://community.blockcerts.org/t/no-transaction-occuring-solved/1142/25 "2018-06-22T13:29:40Z")
Hey @aronning I changed my issuing address and its private key to a new account and got my certificates to issue [[tx](https://ropsten.etherscan.io/tx/0xf34f3cc497c5df4913588c5ce55ca71c46dc18863b3ba8a911bde12541612241)]. However, I also changed the `pysha3` requirements of `merkeltools-1.0.2` at the same time like an idiot and hence, don’t know which fixed the issue. Although, my guess is changing `pysha3` requirement did the trick. Did you update at your end as well @dev? One thing I did notice was that the `signed-certificates` directory (work directory and otherwise) is always empty. Is that supposed to happen? If so, why ask us to create one? ---
**Author:** ![aronning](https://avatars.discourse-cdn.com/v4/letter/a/47e85d/32.png) [@aronning](https://community.blockcerts.org/u/aronning)\ **Post date:** [June 22, 2018, 1:44pm UTC](https://community.blockcerts.org/t/no-transaction-occuring-solved/1142/26 "2018-06-22T13:44:47Z")
Another user brought that up recently. I think that might be a typo somewhere, it should be in the `blockchain_certificates` when ready. ---
**Author:** ![dev](https://avatars.discourse-cdn.com/v4/letter/d/e8c25b/32.png) [@dev](https://community.blockcerts.org/u/dev)\ **Post date:** [June 22, 2018, 2:29pm UTC](https://community.blockcerts.org/t/no-transaction-occuring-solved/1142/27 "2018-06-22T14:29:32Z")
@Palash-A Great! I didn’t have an issue with pysha3. So didn’t update that. My issue was mismatch between public and private keys. After fixing that, we were able to issue the certificates. [Previous page](https://community.blockcerts.org/t/no-transaction-occuring-solved/1142.md?page=1)