I was proposing NOT to use other assets to pay referrers, but let the BTS be there (as is), and make use of it in your client software (you can show it as something else, not a "share"). Paying non-BTS assets to referrers is not possible with current design, and hard to change (not impossible though). Only BTS in pools, no other assets, so the system can't sell them automatically. Automatically borrowing is too risky for the system. Automatically buying smart coins from market is expensive due to illiquidity, unless you setup a huge sell wall there by yourself. You can also setup a service, so your users can exchange their BTS to other smart coins from you (you buy from market for them or whatever method).
I'm not going to set up a worker if only you need a feature.
I remember puppy is helping you with something. If you're not too familiar with how BitShares works, best ask puppy to join the discussion.
Thanks for the reply @abit . Since it will be difficult to pay in non-BTS assets, what about a feature to allow any user to pay for another user's membership? That doesn't seem as complicated. It will 1) allow businesses to have a roundabout way to pay referrals in non-BTS assets. 2) allow users to pay for other people's membership dues as gifts.
Do you have an estimate of the cost to implement a feature that enables users to pay membership dues for others? I can create a worker proposal and try to rally people or raise enough funds to implement this as long as it's not too complicated or expensive.
It's possible with multi-operation transactions + proposals in your
*CLIENT SOFTWARE*, not have to modify the block chain core code. It can also be done in core anyway. IMHO, since there is too few people working on the core right now, and relative more people can work on client software, it's better for you to have it done in client software.
You can use worker to fund it, or use other funds e.g. IPO to develop it first then sell it to the stake holders via worker when most completed.
For technical details, please ask a technician to join the discussion. I'm afraid that I can not explain it clearly enough to you, nor have enough experience on cost/time estimation of client software.