Author Topic: Important and urgent appeal to the witnesses and members of the Committee!!!  (Read 807 times)

0 Members and 1 Guest are viewing this topic.

Offline seyseich66

And so people have to lose money because of their random mistakes?

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 3428
    • View Profile
    • Steemit Blog
  • BitShares: abit
  • GitHub: abitmore
Technically, the bitUSD asset type is owned by committee-account, and the permission "asset owner can transfer asset back to himself" is not disabled, so it's possible for the committee to transfer some amount of bitUSD from one account to another account, e.g. transfer back the bitUSD from the old account to your new account.

However, we've never done so in the past because it's controversial and can lead to scamming. Also it may put the committee or certain committee members to unexpected liabilities.

In this case, if the lost bitUSD is really important for you, I'd recommend that you start a some sort of charity fundraiser asks for donation.

Should this be turned off?

I noticed a quite a few posts highting that a new stable coin had this feature and was therefore a sign it is not a real cryptocurrency.

I can imagine cases where it might be desirable to transfer bitUSD back but should it really be a technical option? It feels like it goes against the whole idea of the DEX.
BitShares as a platform provides such features for asset owners who need it.

BitUSD as a special asset may or may not need it.
BTS account: abit
BTS committee member: abit
BTS witness: in.abit

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12694
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
This turns into a general question: Should the committee ever force-transfer (revert) wrong transfers even if they can be proven without any doubt?

If the question to that answer is "yes", there are a couple things that need to be done *BEFORE* actions can taken:
* 100% prove that the transfer was "wrong" and a reversal is legally and morally o.k.
* a procedure as to WHO does WHAT in case of a refersal (e.g. should the committee become intermediary of funds for a few weeks?)
* Fees need to be paid because it is a manual process - how much? who would get that fee? 50%+1 of committee need to agree still!

If the answer is "no", then we need to
* educate people more about the finality of transfers (i thin we do a good job at that already)
* should committee opt out of the "allow issuer to overwrite transfers"? permission to end this once and for all?
Give BitShares a try! Use the http://testnet.bitshares.eu provided by http://bitshares.eu powered by ChainSquad GmbH

Offline clockwork

  • Committee member
  • Full Member
  • *
  • Posts: 159
    • View Profile
  • BitShares: clockwork
This turns into a general question: Should the committee ever force-transfer (revert) wrong transfers even if they can be proven without any doubt?

If the question to that answer is "yes", there are a couple things that need to be done *BEFORE* actions can taken:
* 100% prove that the transfer was "wrong" and a reversal is legally and morally o.k.
* a procedure as to WHO does WHAT in case of a refersal (e.g. should the committee become intermediary of funds for a few weeks?)
* Fees need to be paid because it is a manual process - how much? who would get that fee? 50%+1 of committee need to agree still!

If the answer is "no", then we need to
* educate people more about the finality of transfers (i thin we do a good job at that already)
* should committee opt out of the "allow issuer to overwrite transfers"? permission to end this once and for all?

I'd opt for no.
Saying yes even once opens a big can of worms and means we'd have to evaluate every such request. Committee could be DDoS'd :D

If there is no real reason why "allow issuer to override transfers" has been left on (@abit?) i'd be in favour of disabling it.

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 3428
    • View Profile
    • Steemit Blog
  • BitShares: abit
  • GitHub: abitmore
If there is no real reason why "allow issuer to override transfers" has been left on (@abit?) i'd be in favour of disabling it.
I have no clue why it's there.
BTS account: abit
BTS committee member: abit
BTS witness: in.abit

Offline matle85

  • Jr. Member
  • **
  • Posts: 47
    • View Profile
My vote would be for disabling it. I don't think it would be ever used anyway and having the option there undermines it in the same way it does for Circles USD Coin (guess you guys have seen the same posts as me in recent days highlighting this owner feature allowing them to block accounts and transfer the asset back).

Offline Thom

And so people have to lose money because of their random mistakes?

Well, that's how people learn. It's a matter of being responsible for the decisions you make and the actions you take.

Sad they're necessary, but it's best for the safety of those who have already learned the hard lesson you're in the middle of.

I am also in favor of removing the "asset owner can transfer asset back to himself" permission on committee controlled bit assets like BitUSD, BitCNY, BitEUR etc. We call these "trustless assets", but it appears whoever set these assets up initially didn't set permissions according to a truly trustless model.

Best of luck to you in the future. Perhaps one day you'll understand the ramifications to others of what you're asking.
Injustice anywhere is a threat to justice everywhere - MLK |  Verbaltech2 Witness Reports: https://bitsharestalk.org/index.php/topic,23902.0.html

Offline pc

  • Hero Member
  • *****
  • Posts: 1397
    • View Profile
    • Bitcoin - Perspektive oder Risiko?
  • BitShares: cyrano
I'd opt for no.
Saying yes even once opens a big can of worms and means we'd have to evaluate every such request. Committee could be DDoS'd :D

If there is no real reason why "allow issuer to override transfers" has been left on (@abit?) i'd be in favour of disabling it.

+1
Bitcoin - Perspektive oder Risiko? ISBN 978-3-8442-6568-2 http://bitcoin.quisquis.de