Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - MarkoPaasila

Pages: [1] 2 3 4 5 6
1
Technical Support / Re: How is Matching works?
« on: March 21, 2018, 08:08:43 pm »
Have a look at BSIP 33 - 35. They describe order matching pretty well. https://github.com/bitshares/bsips

2
This would of course concern only the reference client?

3
hey Marko, thanks for the updates. fully support @taconator in the escrow, i think one of the problems this worker had at first is that it was lacking some older and well known community members.
anyways, any help i can provide to synergy the active workers please let me know, need new api call from the core ? need to understand how the core works in a certain area ? etc. whatever ... just ask :)

Awesome! I will keep this in mind.

4
UPDATE

Since Crypto Kong was removed from the 3/5 multisig account controlling the WP funds, we need a new member. We have agreed to propose the addition of @taconator as the fifth member. The change will take place after one week, in order to give the community time to voice any concerns.

5
https://docs.google.com/document/d/1z2rMlMiMufHdZEirc8x9lKuqSHvLAsVDOYK3xr4AfYE/edit#heading=h.jr7hdxt73vut

In the above document, it says "The received funds will be held in escrow by the Bitshares Foundation, and released at successful delivery of milestones." but in the original post in this thread it states "The received funds will be held in escrow in a 3 of 5 multisig account controlled by @MarkoPaasila, @cryptokong, @Permie, @Kimchiking, and @Cryptick The escrow will exchange the funds to bitUSD and return all excess BTS to the pool, as explained in http://www.bitshares.foundation/worker/ (Under Escrow Worker Model)."

@MarkoPaasila any clarification on this?  Perhaps this is a reason why it's not voted in along with the high 6600/bts a day being asked for even if it is returned to the system later on.

The BitShares Foundation didn't have enough time, so we decided to proceed with an independent multisig. However Xeroc from the foundation has done due diligence on part of his proxy role before voting for the WP. The document you linked is the first draft of the WP.

6
Quote
We ask for a daily budget of $660. Since the payment is in BTS, we ask for 6600 BTS per day, which should suffice even if the BTS price temporarily falls to $0.10

The proposal says it is for 6600 BTS / day.  At an average price of 0.50 that would be $3600/day conservatively.

The project says the term runs for a full year.

Let's say we're frozen at a BTS price of 0.50 USD,   that's $1.2 million dollars to create an open source trading bot.

They claim that unused funds will be returned.

I'd like to see this proposal re-voted in on a monthly basis  (and not yearly) so we can re-vote as it progresses. 

I don't think it should take $1.2 million dollars to fund a market creation bot.  That's quite high.


The community will entrust us with 6600 BTS per day and to return all in excess of $660 per day. I have tried to make it very clear, but it's hard.

The project will run at most for a year, but our intention is to get it done in much less time. Also the WP can be terminated any day by the voters, which I really don't want to happen.

We will buy $660 from the market and return the rest. But yes, it's still some $220,000 if it lasts for the full 11 months that is left.

To begin with we can little more than give promises (claims). But our reputation is on line, and I wouldn't reck my own for a few thousand dollars. Soon we will be able to return some BTS to the pool, and we will post proof to the community.

It was suggested that we make a new proposal every month, but there's little point in it as the existing one can be unvoted any time. I also hate the politics of getting a WP approved. It's much more fun to do actual work and provide something of value  :)

7
Just saw this.

Generally it's a good thing to see development on top of BitShares. Market making does add value to the ecosystem.

My main concern about this worker proposal, is that I don't know you nor anyone in your escrow team, there is no introduction, no product in the document. It would be better if you have something done first before starting the worker. Also better if the members of escrow team are better-known in the community, e.g. bitshares foundation, committee members, witnesses, proxies, devs, etc.

Very valid concern. The funny thing is that none of us in the multisig know each other either other than from the chats and forums. It was me who chose the members, and I picked ones who were positive, objective and constructive, who seemed trustworthy, and who appeared to be strong BitShares proponents.

I also personally think misusing community trust to waste or steal funds would be a most idiotic thing to do, especially  using my real name. The WP could be unvoted in a day, and I would never get back the lost trust. Of course people still do stupid things, but I very much try not to. We can't do magic, but we will deliver. If we don't, it will be only right if the WP is unvoted.

8
still don't know from OP which one's the real one? please make it clear, and add an image from the wallet view if you want votings

Sorry for the unclarity. The duplicate WP appeared after OP here.

The right WP to vote for is the one with "($660/d)" and currently more votes:

DEXBot - User Friendly BitShares Market Making Bots ($660/d)

not this one:
DEXBot - User Friendly BitShares Market Making Software

9
Sounds like an interesting proposal, I'd like to see support for additional price feed sources - BTSBOTS was overly reliant on Poloniex for price feed stats.

Feel free to contribute to the document where we are collecting thoughts about different strategies: https://docs.google.com/document/d/1hOPhow3WBwQmeNkL0JrIufvfE2TvsORD1OK0Xg3JnVg/edit#

10
please note you have 2 active worker proposals that are actually the same(http://bitshares-explorer.io/#/workers)

http://bitshares-explorer.io/#/objects/1.14.73/
and
http://bitshares-explorer.io/#/objects/1.14.74/

need to make clear everywhere to the stakeholders for what to vote as they can't be deleted or updated!

Yes thanks for pointing that out. What apparently happened was this:
  • We made a multisig account
  • I proposed a WP to the multisig account using my own LTM account
  • We all signed the proposed transaction
  • There was some problem, and the WP didn't get included in the chain. There was some message about missing translation. We probably should have taken note and made a Github issue.
  • We gave the account full permissions back, and made a new WP
  • Got a message that can't propose worker without LTM.
  • Upgraded to LTM
  • Made proposal again, and it succeeded. This is 1.14.73
  • The earlier WP was included in the chain as a surprise. This is 1.14.74
  • We changed the account back to multisig

So it appears that a multisig account can create a WP but if it doesn't have LTM the error message won't indicate that. Maybe I should create an issue of this?

11
Many users would also feel more comfortable using this if a BitShares dev peer reviewed the code.  That would also help iron out any bugs and speed development.  Perhaps Alfredo or Abit could help with this?
yea, no problem, if it gets accepted i will help them in what i can. did not readed fully yet but good luck!

Thanks Alfredo! I  think we will mostly be using the stakemachine python code, but we hope the core developers at least have a look at the code for the sake of safety.

12
The Worker Proposal is now live. Further discussions in this thread: https://bitsharestalk.org/index.php/topic,25615.0.html

13
Introduction
Market making can be a very profitable and rewarding enterprise.. For the uninitiated, market makers provide liquidity by placing limit orders on both sides of the books anticipating to earn a small profit thanks to the spread (or difference of the bid and ask) on any given trade. On the Bitshares DEX, while all markets could use more liquidity (which is provided by such market makers), there are also many dead or illiquid markets. This not only presents a problem for traders and businesses wanting to place large orders, on the DEX but presents a massive financial opportunity for people to become market makers.

At the moment it appears the DEX already has a few major market makers using their own private software. There are also a few open source projects on GitHub in mostly bare-bones, unfinished states. One project on GitHub, created by a long standing member of the community, is no longer available. This project was called BTSBots. It worked, was freely available to everyone and there was an Android app. This trading bot was not in a finished form, nor was it easy to use, in part due to the language barrier with the developer, many people still made a lot of money and helped add  liquidity to our markets before it went offline.

The importance of BTSBots to the Bitshares ecosystem is demonstrated by the sharp drop in “Daily Orders Created”, a measure of liquidity, by over 85% to a recent low of just ~53k in the course of just 2-3 days (right after public BTSBots access was revoked).

Quote
Revision, 12/16: “aperson” has has forked BTSBots and launched “Bitsharesbot” to the public. Limit orders measure has since slowly started to recover.
Link: https://steemit.com/bitsharesbot/@aperson/bitsharesbot-is-now-stable-reduced-fee-and-public-price-feed-available-tonight-feed

This damaging event has caused the BTS community to spring to action to build a more suitable, open-source, “official” baseline for community use moving forward. Even before now, several  community members got together and created a Telegram group with the purpose of discussing market making strategies and methodologies to profit while improving  liquidity on the DEX. We have discussed advanced theoretical strategies, written guides, helped people set up bots, and taught various manual staggered orders approaches. In doing so, we have built the foundation of a very diverse community of journeymen to highly advanced market makers. There are now over 100 people in our room, now without  their main weapon (BTSbots).

It is our belief that Bitshares markets should be different to markets of the past in which just a handful of market operators  pull the strings behind the curtain. We want to provide the tools for everyone to become a market maker - whether a basic one or with the freedom to progress beyond using the framework we’ve developed. The more market makers we have the greater the competition for profits, lowering costs for users.

We have been in contact with Bitspark and they have advised us of their plans to provide bots as well. We don’t want to be stepping on each others toes but rather work together in order to provide as much liquidity as possible. Since the loss of BTSBots and speaking to Bitspark, we now believe our first goal is to provide a replacement or alternative (if it ever comes back online) to BTSBots. The new bot will be far more user friendly and free for everyone to install and use on their own computers.

This Worker will implement several strategies, one by one, with user-friendly interfaces. BitShares will provide the community these tools, free of charge, in order to keep its markets liquid, competitive, and far more transparent than it’s centralised competitors.

The Goals
The BitShares community will have the necessary tools to provide liquid markets in a decentralised way, without the any single point of failure. The software provided will have all the necessary strategies for providing liquidity and real-world prices, and all possible strategies that add actual value to the markets in the DEX. These are mostly market making strategies.

Details of such are further detailed in our supporting document: https://docs.google.com/document/d/1hOPhow3WBwQmeNkL0JrIufvfE2TvsORD1OK0Xg3JnVg/edit#

The necessary elements to providing liquid markets are immediate liquidity, market depth, and prices close to those of other exchanges. There are a several different strategies that can be used to reach these objectives. The exact strategies to be implemented first are the ones we identify as lowest hanging fruit. We will make the decisions transparently throughout development, utilizing community input.

The provided open source software will function as a good basis for developing custom solutions and custom strategies. For example, remittance services can customize the software to meet their specific needs, and provide it as a user friendly package to their communities. The creators of User Issued MPA’s can customize the software to support their own markets. Thus, this Worker will support many future efforts to provide value to the ecosystem.

The specific strategies with details will be discussed elsewhere, such as in the above link, and we will discuss them openly with the community before and during implementation. The most up-to-date information will be in the Telegram Chat (see below). This document is an overview of the proposal.

Developers
In practice, the Worker will be a community escrow which aims to allocate the funds to maximize the value provided to the community as a whole. We have secured developers for the job, but will also pay bounties to freelancers and possibly acquire more developers to speed up development.

The developers are employed by the software company Codaone Oy, registered in Finland.

Mika Koivistoinen as main developer.
Vesa Toivonen as Designer
Juhani Haapala as Python developer.

BitShares representatives
Marko Paasila. Bitshares proponent since 2014. Experience in product development, project management and cryptocurrencies. I will communicate the community's needs and priorities to the developers and ensure good quality.
StatDude - Bitshares enthusiast, experienced market maker, trading bot architect.

Schedule
The worker will begin on Monday 2018-01-01 and end on 2018-12-30. The Worker can be terminated earlier by the community. The coders will begin work as soon as possible during the beginning of January. The development speed will be up to the team. Funds in escrow will be released at each completed milestone. Development will be done in 2 week sprints, with release on monday’s for ensuring better response time and support. Each new feature will be tested and made user friendly before proceeding to the next one.

A target list of features and milestones will be provided and mapped to progress on our living Strategy document.

The initial roadmap is:
Milestone 1: Basic/Relative orders bot with GUI, user defined price and spread, and a simple interface. Installable package. (Single pair)
Milestone 2 Staggered orders bot supporting multiple market pairs (Management page - multiple pairs)
Milestone 3: Manage several bot instances (accounts) within the same interface (Management page - multiple accounts)
Milestone 4: Reporting, full trade history export / Performance monitoring graphs
Milestone 5: Streamline bot creation, funding, cloning and deletion
Milestone 6: Support use and custom weighting of feeds to DEX from some other exchange
Milestone 7: Addition of social features (chat / leaderboards)
Milestone 8 and forward. More features based on community input.

The schedule and priorities will be adjusted constantly based on realities and community input.

Payment
We ask for a daily budget of $660. Since the payment is in BTS, we ask for 6600 BTS per day, which should suffice even if the BTS price temporarily falls to $0.10. The BTS will be sold for BitUSD at market price. At the end of Worker period, all excess funds will be returned to the treasury.

The received funds will be held in escrow in a 3 of 5 multisig account controlled by @MarkoPaasila, @cryptokong, @Permie, @Kimchiking, and @Cryptick The escrow will exchange the funds to bitUSD and return all excess BTS to the pool, as explained in http://www.bitshares.foundation/worker/ (Under Escrow Worker Model).

Payments will be made on successful milestones. Development costs can only be estimated beforehand, but the developer takes the risk. The escrow multisig is responsible for evaluating the quality of the released software. All payments will be made public and accounted for transparently.

Miscellaneous
The software will be provided under the MIT-licence, just like bitshares-core and bitshares-ui.

There will be a website to represent the software with introductions to different strategies and guides for getting started.

We will provide weekly updates on the progress.

The key metric to follow is either liquidity or market depth. We will design a suitable KPI and update it weekly.

Because the software is funded by the community, it will not contain strategies that don’t add value to the whole. These are Technical Analysis Trading strategies and any other strategies that reduce liquidity without increasing it somewhere else.

Contacts
Project Coordination:    Marko Paasila (@MarkoPaasila)
Telegram Rooms:          https://t.me/BTSLiquidityBotWorkerProposal
                                                     https://t.me/DEXLIQUIDITYBTS
Reports and Information:    MarkoPaasila[/member]/]https://steemit.com/@MarkoPaasila/
               


Appendix

Pays for Itself
A trading bot has the ability to greatly increase the number of transactions that take place. Current analysis indicates that about 80% of trading is already from bots. These heavy traders only represent 20% of the total traders. With a basic bot that can trade day and night even while investors sleep, it is not unrealistic to see a huge spike in activity. This activity will bring in more trading revenues. There will be more lifetime memberships, more transaction fees generated and more market makers holding assets such as bitUSD, open.btc or bridge.btc benefiting our gateways too.

A Bot for the Common Investors
Highly advanced bot development may be an area for specialized traders, however building a basic bot is about creating the tools and environment that can allow every single member of the community a way to participate, control risk and position themselves for success. This gives them a way to increase participation in the markets and the community by helping to reduce risk and cost to others. Communities often spend public money in building roads, railroads and airports. A basic bot,providing liquidity, is akin to this infrastructure so development funded by the communal funds is warranted. A simple interface that allows every person tools to automate basic strategies is the first goal. All bitshares participants will benefit from a trading bot whether they use it directly via trading or indirectly through greater liquidity.

Market Makers Community
We have already started building our base and anyone is free to join, there is so much potential here already waiting to pump liquidity into our markets, we just need the tools. We already have guides on how to add liquidity by means of manual trading but to contribute meaningfully that would be very time consuming.

Our vision is to have a thriving community of market makers spread all over the world, of all different sizes, using the tools provided to them by the community. With the more knowledgeable, experienced market makers helping the new guys get started. Good market makers could be given access to manage other people's accounts, earning from the transaction fees created by the bots if they referred them. This opens up a whole new revenue stream that many will have not even considered. A mentor and apprentice scheme where the better your apprentice is the more transaction fees you will benefit from over time.

We expect people will work together in teams to provide liquidity to their favourite coins and that this will get quite competitive in the beginning as the usual crypto tribalism sets in. This will result in other crypto communities depositing their coins on our gateways and borrowing assets such as bitUSD to make the market.

We imagine people not only creating their own tokens but having the tools available to create the required liquidity in order for people to instantly trade it too. You could have a fully functioning market up and running very quickly for an asset you had created providing you had the tools and funds to do so.



EDIT: There is a duplicate of the Worker Proposal. Please vote for the one with "($660/d)":

DEXBot - User Friendly BitShares Market Making Bots ($660/d)

Please remove your votes from this one:

DEXBot - User Friendly BitShares Market Making Software


14
Great news! I have one concern though. It is not clear from the proposal how decentralized will be your bots. Since you plan to use funding through WP, I would expect the resulting product to belong to community and server nodes to be easy to run by anybody. Btsbots is great, but it was ran in a centralized way, and wee see what happened.  Could you make any comments regarding this concern?

We will not provide servers for the purpose. Everyone has to run the bots on their own computers or servers. Many of the market making strategies are suitable for use on computers that aren't on all the time. So it will create a very redundant swarm of decentralized bots, where everyone holds their own keys, and many their own nodes.

So market making pro's can run this on a server, and normal people plus noobs can do it on a laptop. There will be a CLI version and an installable GUI version.

So do I understand correctly that your design does not need a dedicated server node (unlike btsbots)? Is this correct?

Correct. We think it's bad practice to give private keys to a third party. However, if the lack of a bot-as-a-service is a showstopper, we are ready to consider it.

No, with btsbots you don't need to give private keys to a third party, but it still has a server, where web page is hosted, bot config files for every account, price feed scripts etc. This is makes it very convenient to use, because you can run your bot on your private server, and control it from any device via btsbots.com web page, but this makes it non-trivial to fork. We can't just download the source code and run the bot, because it requires data from btsbots.com, which is down (which is very pity).

You are right. But having the keys in your browser means you need to keep the browser window open. The server can't update your strategy when your browser is closed. In that sense local software isn't much different. I think a server-browser model has it's merits, and we will consider all possibilities. Have you already joined the Telegram chat room? https://t.me/BTSLiquidityBotWorkerProposal, where we will be discussing such details? We would love to have your input there.

15
Great news! I have one concern though. It is not clear from the proposal how decentralized will be your bots. Since you plan to use funding through WP, I would expect the resulting product to belong to community and server nodes to be easy to run by anybody. Btsbots is great, but it was ran in a centralized way, and wee see what happened.  Could you make any comments regarding this concern?

We will not provide servers for the purpose. Everyone has to run the bots on their own computers or servers. Many of the market making strategies are suitable for use on computers that aren't on all the time. So it will create a very redundant swarm of decentralized bots, where everyone holds their own keys, and many their own nodes.

So market making pro's can run this on a server, and normal people plus noobs can do it on a laptop. There will be a CLI version and an installable GUI version.

So do I understand correctly that your design does not need a dedicated server node (unlike btsbots)? Is this correct?

Correct. We think it's bad practice to give private keys to a third party. However, if the lack of a bot-as-a-service is a showstopper, we are ready to consider it.

Pages: [1] 2 3 4 5 6