I would love to read more about trading part. For now I see one simple scheme.

1. Multisig borrow USD and send to worker.2. next day worker make sell order 5% above feed at USD:BTS3. Multisig fill worker orders and send USD to worker again.5.Repeat

If this is the case, why 5%?

It is going to be exactly like [member=5080]Geneko[/member] described it.The only thing that is not yet clear to me from the procedure, is* Should a collective account be used to borrow bitUSD instead of spreading shareholder-owned collateral to multiple accounts?* Should the account's permissions be set to be committee owned after the expiration, or should it be re-useable?

I personally, prefer to send BTS to a separate account that holds the collateral position and sends back the bitUSD. This makes accounting easier but requires another multisig group to organize and maintain the collateral.

We also support this worker proposal. I am looking forward to creating more dev tools for the community. Please also add an extended documentation to the tool so that new devs can get started easily.

Short question:

- How much time will you dedicate for this worker and BitShares?4,000 euro a month sounds like a full-time worker for 3 months.

- Are you also working on further steemit related projects?

Thanks for the support, chris!The worker is based on milestones. So you get all milestones fulfilled for 3 months * 4000$/mth =12k$The amount of time I need to put into it depends on how fast I can bring it on and how many problems I run into it.In the end, this way is in favor for BTS holders and makes it more risky for me .. but I am pretty confident I can deliver in time

I also have commitments with some Steem projects. No commitments so far for Steemit Inc.

Actually, there is no need to put 2.5x collateral. If there are no offers between feed and SQP price, borrow bitUSD with minimum (1.75x) collateral and let it be margin called as soon as an offer appears between feed and SQP.

Depends. Margin Calls can force you to pay up to 10% above the feed while if you maintain collateral, you can just to partially close your position at lower premium.Given that the shareholders (on paper) pay with more dilution for this worker already, I don't think it's fair to also ask them to pay for margin calls. Hence, 2.5x collateral.Makes sense?

It is going to be exactly like [member=5080]Geneko[/member] described it.The only thing that is not yet clear to me from the procedure, is* Should a collective account be used to borrow bitUSD instead of spreading shareholder-owned collateral to multiple accounts?* Should the account's permissions be set to be committee owned after the expiration, or should it be re-useable?

I personally, prefer to send BTS to a separate account that holds the collateral position and sends back the bitUSD. This makes accounting easier but requires another multisig group to organize and maintain the collateral.

I see one flaw. Collective account income isn't specified. Are they working for free? I would give them 10% of savings that they made, or better to say: if. Fair offer. Your idea is amazing btw.

I see one flaw. Collective account income isn't specified. Are they working for free? I would give them 10% of savings that they made, or better to say: if. Fair offer. Your idea is amazing btw.

The original plan was to get the BitShares foundation bootstrapped by offering this as a service for a fee. But due to some time-delaying issues they couldn't make it til now. Hoping to find a way to do this for a subsequent worker.

Actually, there is no need to put 2.5x collateral. If there are no offers between feed and SQP price, borrow bitUSD with minimum (1.75x) collateral and let it be margin called as soon as an offer appears between feed and SQP.

Depends. Margin Calls can force you to pay up to 10% above the feed while if you maintain collateral, you can just to partially close your position at lower premium.Given that the shareholders (on paper) pay with more dilution for this worker already, I don't think it's fair to also ask them to pay for margin calls. Hence, 2.5x collateral.Makes sense?

Yes, it does. I guess, this whole process could be automated with a simple bot, can it?

Yes, it does. I guess, this whole process could be automated with a simple bot, can it?

Yes it can .. more of less .. everything that involves the worker account needs to be approved by the multisig group tho ..But you can concatenate multiple operations into a single transaction/proposal so that they only need to approve once ..

Morning everyone. I am still looking for some support for my worker proposal. Please consider voting so that we can improve the python tools and libraries that other devs can then use to build their apps and improve the ecosystem. Examples are the faucet (tapin) or a market making bot (stakemachine) but even more is possible like tipping bots, trading bots and any kind of automation of your account (like donations of some tokens to new accounts as done on the testnet).

Is Python good enough to start a very simple community based sidechain? By saying sidechain I mean bunch of bots operating as multisig account in minimum 2 blockchains (e.g. steem <=> bitshares). Bots read data from blockchain's apis, voting on transactions and store data about it. Is that sidechain? Workers, pegged assets, custom dividend schemes, mining... All done with python bots, flexible UIA's and multisig groups - with possibility to upgrade to faster language if business model generate enough income to hire devs. Every time I see fractals like that I'm super exited. Is this a way how Graphene blockchain is supposed to scale or my uneducated imagination led me to false conclusions?

Absolutely .. in fact, I actually NEED this kind of code to run this worker and get paid (due to the multisig nature of the escrow service for bitUSD payments).Building bots will be very easy. You can see the same code base in action on STEEM called pysteem (pytsteem.com). It's a very popular library for python devs.

PyBitShares will simplify using the BitShares blockchain and build businesses around BitShares and I am not just talking about faucets or mm bots. Any kind of buisness that wants to run on top of BitShares could build a MVP in python very quickly and move over to custom libs/code while they grow their user base. Or they stick with pybitshares which is build with scalability in mind.

As I am making significant progress with both, pybitshares library and uptick, I would like to request input from you as to what features you would like to have in the library and the command line tool uptick in an upcoming public first release candidate.