BitShares Forum
Main => Technical Support => Topic started by: codewookie on November 21, 2017, 12:38:34 am
-
We are working towards issuing an asset on BitShares and need to control who can hold and trade the asset due to regulatory restrictions. We have set the Whitelist option and also the Issuers Approve Transfers.
- The Issuers Approve Transfers blocks transfers at the client so the issuer does not have an opportunity to approve.
- When Whitelist is turned on an no one is whitelisted, buy and sell trades are still allowed.
We are using WookieCoin on the Testnet.
-
We are working towards issuing an asset on BitShares and need to control who can hold and trade the asset due to regulatory restrictions. We have set the Whitelist option and also the Issuers Approve Transfers.
- The Issuers Approve Transfers blocks transfers at the client so the issuer does not have an opportunity to approve.
" Issuers Approve Transfers" means the token can only be transferred to the issuer or from the issuer.
To archive your goal, you can use the proposal feature:
* Assume token holder A wants to transfer some token to B, need the approval of issuer C
* Build a proposal with two transfer operations inside, one is A->C and the other is C->B, so both operations will execute or none will execute.
* Then A approve the proposal, then C approve the proposal.
This can be done with the builder_transaction command set in cli_wallet.
- When Whitelist is turned on an no one is whitelisted, buy and sell trades are still allowed.
Whitelisting is two-layer setup. In asset options the issuer set authorities(admins), then the authorities(admins) set the real list. So, it's not "no one is whitelisted" but "no one is set as authority", in this case the flag doesn't take effect.