I believe your mb signing keys got liked to the same twetch account - it's possible this happened if you switched current logged in mb accounts w/o first logging out of Twetch when we recently launched our new api
Post by twetch#4721
1 twetch account can have many signing keys. If you share w/ me a post that you think should have been from ecat, i can resolve the issue
What the chain says
- Block
- 623 384
- Time
- 2020-02-24T00:55:09Z
- Signer
- 1HVieydsEtNMX7JvhVwGt7hjyqoVNtwaot
- App
- twetch
- Type
- post
- Content type
- text/plain
- Name in tx
- twetch#4721
Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.
Signed by
1HVieydsEtNMX7JvhVwGt7hjyqoVNtwaot VerifiedReplies (12)
the start post is from ecat account.
this one is from this account.
fixed, try now
twetching with u/130
now ecat account twetches twice !
its getting fun!
they are different transaction hashes