Does yield on a bitAsset purchase come from the interest paid by the short on the other side of the trade - and therefore stop being paid when that short covers?

I'm trying to write a script to regularly withdraw pay from my delegate into an account not hosted on my server, for security reasons.

When I do wallet_account_balance I get 0.01 BTS, so I presume the delegate pay isn't listed this way?

wallet_delegate_withdraw_pay requires an amount, but there doesn't appear to be any way to know what the total is. What am I missing?

Is it possible to get a delegate projects board added to the forum?

There could be a separate sub-board for each project so that we can share ideas and so interested parties can follow our development progress.

For example, there has been a fair amount of talk about web-wallets / mobile wallets recently, it would be great to have a place just to hash out the associated ideas/problems/requirements with the other developers, so we can share work and not re-invent each other's wheels, so to speak

I have tried everything, but all I get is a gateway timeout error trying to authenticate with the JSON RPC API server. The HTTP one works, but not the JSON one.

Any example of this working?

Hi all,

This is the MetaExchange 100% pay rate delegate voting campaign. Delegate name: dev-metaexchange.monsterer

What is MetaExchange?

MetaExchange is a website designed to lower the barrier to entry of owning and trading Bitshares to zero. It will do this by:

* Providing peer to peer on-ramps for BTS, bitUSD and the other major Bitshares assets.

* Acting as a web-wallet, allowing people to get started with Bitshares, without having to download the client and wait hours for it to sync just to see what all the fuss is about.

* Providing a slick trading interface and market view which will be familiar to forex/bitcoin traders

Who are we?

monsterer:

My name is Paul Firth, I have been a professional c++ software developer for 10 years. On this project, I am partnering with Shentist who is helping me shape the vision for MetaExchange and also providing the funding for my delegate registration.

I also run a blog about software development: http://wildbunny.co.uk/blog and a limited company (Wildbunny) based in the UK.

shentist:

My name is Frank Ahrens, I am in software support. I am happy that Paul and I could find common ground to combine our visions to produce something that we think will help BitShares as a whole greatly. On this project I'm helping with the vision and handling the legal and business side.

What is the planned release schedule?

* Release 1 will be a Bitshares market viewer, allowing users to browse markets and assets in a setting familiar to any trader who might have used a bitcoin exchange

* Release 2 will add the peer-to-peer on-ramp system, which will allow users to post bid/asks for trading BTS and the major Bitshares assets for bitcoin. In this system, MetaExchange will act as a escrow agent to facilitate safe peer to peer exchange of assets for bitcoin.

* Release 3 will be web-wallet and Fiat on-ramps adding to the peer-to-peer exchange, possibly by cooperation with Fidor Bank AG.

Peer-to-peer exchange has a number of great advantages, like providing an easy way for Bitshares users to get large quantities of BTS or assets without directly moving the market. We also won't hold any private keys, because we believe strongly in security of our user's funds.

How far through development are you?

MetaExchange has been in part-time development for a little while now, but it's tough to get enough free time to work on it actively, which is why we're campaigning for a 100% delegate. I estimate that we're about 50% of the way into release 1.

What is the delegate name?

dev-metaexchange.monsterer

In closing, we literally can't do this project without your support. We need your vote! Thank you for your consideration.

Paul aka monster / Frank aka Shentist.

Github repo

https://github.com/wildbunny/metaexchange

P.s. here are some screen-shots of the development build to whet your appetite:

I can't find anything in the docs describing the format of a transfer transaction. I'm trying to work out if its possible to chain two 0 confirmation transactions together, so they either both get confirmed, or both not?

The current bitasset pegging system is so fantastically complex because the assets are traded on a free market, which can be manipulated by any other market participants.

A neolithically simple alternative way to peg a bit asset to an external price would be to remove the other participants from the equation.

Create a different class of asset, which can only be bought and sold by the issuer. The issuer maintains a buy and sell price with a spread which takes into account adverse selection costs.

Issues:

100% trust is required of the issuer. Trust that they don't sell you the asset and then raise their buy price to $1M USD. Trust that they have enough liquidity to cope with adverse selection costs, so they're able to buy back the assets they sold you after the price goes up.

Now, take that idea and make the blockchain the issuer.

You then gain 100% transparency on the algorithm controlling the prices. You'd be able to see the 'balance' of the blockchain in advance to be sure it has liquidity reserves.

In addition, bitshares is ideally placed to implement this idea, since the necessary price feeds are already a fundamental component.

The only real remaining issue is designing the algorithm to set the bid/ask prices - perhaps something like the kalman filter (http://www.r-bloggers.com/the-kalman-filter-for-financial-time-series/) could be used over the feed data.

Thoughts?

Preparing my delegate, I'm at a bit of a loss for how to launch the bitshares client, unlock the wallet and set the unlock time to something decent via the command line.

I need to nohup the process in order for it to keep running when the bash session ends, but if I do that I cannot type any commands in, and there appears to be a very limited set of command line parameters which the client reads as it starts up?