Author Topic: Asset ownership changed, now I can't issue anymore  (Read 276 times)

0 Members and 1 Guest are viewing this topic.

Offline tanselkaya

  • Newbie
  • *
  • Posts: 6
    • View Profile
  • BitShares: bzzrx
Asset ownership changed, now I can't issue anymore
« on: April 17, 2018, 02:04:01 pm »
I have created an asset named HEARTBIT under the bzzrx user,  and I have issued 770.000 tokens. I have transferred the ownership of the token to user tnsl-ky. Now when I try to issue new tokens, the operation hangs. I can still send existing tokens but I can't issue.

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 3297
    • View Profile
    • Steemit Blog
  • BitShares: abit
  • GitHub: abitmore
Re: Asset ownership changed, now I can't issue anymore
« Reply #1 on: April 17, 2018, 08:38:22 pm »
Only owner can issue.
BTS account: abit
BTS committee member: abit
BTS witness: in.abit

Offline tanselkaya

  • Newbie
  • *
  • Posts: 6
    • View Profile
  • BitShares: bzzrx
Re: Asset ownership changed, now I can't issue anymore
« Reply #2 on: April 20, 2018, 02:52:51 pm »
I have transferred the ownership of the token by paying BTS tokens. There is a new owner but this owner cannot issue tokens. Should I move the token to the old owner. I think the system has a bug, that should be addressed.

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 3297
    • View Profile
    • Steemit Blog
  • BitShares: abit
  • GitHub: abitmore
Re: Asset ownership changed, now I can't issue anymore
« Reply #3 on: April 20, 2018, 05:15:41 pm »
There was a bug in bitshares-ui 2.0.180402, which should have been fixed. Please try with the new version (2.0.180418b).

Related issues:
https://github.com/bitshares/bitshares-ui/issues/1424
https://github.com/bitshares/bitshares-ui/issues/1395
BTS account: abit
BTS committee member: abit
BTS witness: in.abit

Offline tanselkaya

  • Newbie
  • *
  • Posts: 6
    • View Profile
  • BitShares: bzzrx
Re: Asset ownership changed, now I can't issue anymore
« Reply #4 on: April 20, 2018, 05:41:21 pm »
Thank you very much. We have resolved the issue by updating to the latest version 180418b. Thank you for taking the time to review this.