Feature: chained transfer / 3rd party approved transfer

[abitmore]

Inspired by #462, we can have "UI for approving transfers for assets that require it", via proposal, like another feature proposed in #866.

Assume A wants to transfer some asset X to another user C, and B is the issuer of asset X which requires issuer's approval for transferring, steps to do an approved transfer:

1. A create a proposal which contains 2 operations:
   • A transfer amount M of X to B
   • B transfer amount M of X to C
2. A approve the proposal
3. B approve the proposal

The 2 transfers will either both pass or both fail (atomic).

On the transfer page, we can have an option like:

• transfer via _____

We can pre-fill the text box with known agents, or the asset issuer, or a value saved by the user, or show a list, etc.

Note: since funds from A is not locked, this feature is not actually an escrow.

[wmbutler]

Needs UX

[degraffenried]

We are going to need this soon. Is anybody working on this? I would like to take a look at working on it.

[degraffenried]

A few nice things to have with this is that if the token being sent is set to transfer_restricted, then automatically assume that it needs to go through a proposal to the issuer, and then also check if a whitelist is set, and then only allow the receiver to be on that whitelist, then automatically sign the proposal from the sender after it's created. Then the only person left to sign it would be the issuer of the token, where they can either do it manually or with a bot that may check other KYC/AMI information before signing and approving.

[abitmore]

then automatically sign the proposal from the sender after it's created

This automation is a bit hard since bitshares/bitshares-core#138 hasn't been implemented.

[clockworkgr]

@sschiessl-bcp can the barter w/escrow UI be modified to cover this case?

[sschiessl-bcp]

@degraffenried

What is your use case for this feature?