Topic: Windows Desktop Bitcoin Lending Bot for Poloniex - page 12. (Read 15268 times)

Looks nice man. But I've always wonder what would happen if someone takes your loan and ends up losing all the money from your loan. What would happen in that case?

Hi All,

I just posted a new build. There's no critical fixes in it so don't feel that you have to upgrade. I apologize for the quick turn between builds. There were some features I felt were needed for new users and I wanted to get them in there. If you want to upgrade please go over to the website to see updates regarding the UI, Max Loan Amounts, and manual offering loans, as well as cancelling them through the UI.

The short version:
The UI is now in percent - ie 0.1234% rather than 0.00143400. I initially released it with the 0.00143400 format as that's the internal format that Poloniex uses and it was helpful for me to see exactly what was going to the API for debugging. This also fixes a bug where rates without a decimal point showed bad data. I also added some tool tip data over the controls.

Max Loan Amount - This allows you to cap the maximum amount to lend in a single loan. IE, if you have 10 BTC in your account and want to issue small loans and you set this to 0.5 it would offer one offer at a time for 0.5, ultimately resulting in 20 loans for 0.5 rather than 1 loan for 10. Remember, though, Pololen attempts to only have one loan open at a time so this will take a while. I don't recommend using this all the time and I don't recommend using it at all if you are manually lending at higher than market rates. It's very likely if you use it in that situation that only a portion of your funds will be leant at a time. There is also an increased chance of Pololen not being able to close offers that it opens if there is a problem with the server when using this functionality so if you are using it you should keep an eye on the loan offers you have out there.

Loan Offers are now visible - In part because of the above issue with offers being orphaned if Poloniex is overloaded or having a DDOS attack I went ahead and added a tab to show open offers. This will update each minute and has a cancel button so offers can be cancelled from here.

Loan Offers can be created manually - In part because I created a way to see open offers I figured the user should be able to create offers from here as well. Bear in mind that Pololen by default attempts to lend out all your funds so you'll need to use the bank function to keep some available in your account to be manually leant, should you choose to do so.

Version check - Pololen now checks every 12 hours to see if there is an update available and puts an unobtrusive note above the recommended rate on the lower left if there is a new version available.

Again my apologies for the short period between builds. This upgrade is only needed if the above sound like something you need.

Hi All,

I've posted a new version - 1.0.1.2. I recommend this version for all users as it has a couple of changes that I consider critical. I'm no longer linking downloads here - so please go over to the website at http://poloniexbitcoinlendingbot.com for the download link and instructions. Instructions for upgrading are in the FAQ. It's pretty easy, just a couple of files to move, but make sure you have a full backup of your folder in case you need it.

Changes:
Critical:
Changed order of operations in lending cycle to minimize the time between a loan being cancelled and a loan being offered.
Changed order of operations in history cycle to prioritize credit checks. There was a situation that if the Poloniex history retrieval failed then the credit check for new credits wouldn't happen until the next cycle.

Important:
Added manual overrides to make the app work more like a traditional bot, with a defined minimum rate and a defined duration, should the user want to go that route.
Changed the text on the API tab to better match the Poloniex website.
Updated handling of the BTC price retrieval. In prior versions if the API didn't return for some reason it set the price to 0. Now if we fail to retrieve a price we will use the last price retrieved until we are able to refresh it.

I am going to be fairly unavailable today so if you don't hear from me often don't worry I will be back.

I realy appreciate your effort to make PoloLen better. Thank you for that.

It is always the Dev's effort what makes things great.

Unfortunately I have no idea how much work it is for you. So I blindly ask for additional functions. Take them as brainstorm ideas, they may fit in your project or not. Maybe you already had that function and you have learned, it's useless... ;-)

About the graphs lenght, would be nice to be sure the "Market" graph is 60 days. If thats the case, don't mind about my question for longer graphs, it's already there ;-)

I would like to set, how much of the offered BTC I would like to ignore, say "60BTC". To override this big low offers of 40-200 BTC, which pop up every now and then.

Would be nice to be able to put a % value in "Bank" ...

What about making a mask for the "operation" log, preferably with correct numbers. For example "Recommended Rate: 0.00176200", that looks a bit strange, even it works ;-)

While watching PoloLen for hours till my head fell on the table, I noticed, that about a third of the time, the PoloLen offer is just 0.0001 too high, just sitting on a price together with a big offer. I would take off 0.0001% in general from your "Recommended Rate". Or have a tick box, where I can mark "-0.0001".


The "Deviation Calculations" window shows me, that you spent a lot of time with this problem. You're brain is so much tuned to that, that a new brain struggles to follow you, because you already built your own way of thinking.
This window looks like it's made by Spok from Starship Enterprise, sure it is correct, but ....  :-)


PS: ...if you can make a hot girl popping up after every profit, and telling me I'm the biggest and the best ;-)

Hi Brobbel,

It's good to hear from you. In terms your question I don't have a plan for it short term. One of the things I'd probably have to sacrifice would be speed. Poloniex limits the amount of inbound connections to the API from a single IP address to 6 connections per second. If I were to set up a website I'd either have to run it quite slow to support multiple users or I'd need to have a way to spawn additional server instances per small group of users so that I could maintain the speed and Poloniex wouldn't be taking in more than 6 connections per second. For that I would need to increase rates quite a bit. Even the rate increase, though, may not be enough. The other problem is that payments tend to be micro payments and transaction fees are so high currently that I'd lose a good portion of the fee to the miners when I try to sell it to pay for the server.

This may all completely change if Segwit activates but at this moment in time I suspect that the rates I'd have to charge to get enough funds after transaction fees are taken into consideration would be higher than the percentage that the user could reasonably expect to gain from using the service.

That's a weird one - 200000% is a bit higher than I would expect It was flying for a while there, though. I might have a bug where there is a missing decimal point and it should be 2.00000. Let me know if you see it with any other ones.

The short loans, though, happen all the time at high percentages. Pololen will try to lend them, of course, at a super high rate. My record is 1.8% which lasted, maybe, 8 seconds. As soon as there are lower loan rates available I *think* Poloniex will close the existing ones and give the trader lower rates. That's only a guess though. I know that they can find lower rate loans for traders under certain circumstances, but I don't know what those circumstances are.

Or it could be the trader saw the loan rate and immediately closed their position. I know I would

Hi,

Now you've a website created with information, are you planning to create the possibility to work online instead of locally (like some other bots did/do)?
It should be nice to use it online, because normally my computer isn't 24/7 working - but now it does because of this really nice program!

Wow, what a Dev !!!

Did you read my brain ? ;-)

I'm sure you are very experienced in Polo lending, and you got even a better insight with your tool too.

I'm lending quite well between 0.2 an 0.37 and would like to keep it up there, till I know it better ;-)

Why can I see a booking in my "recent closings", where I lent 0.01 BTC for 11 seconds at 200000% ...........  don't forget to blink ;-)
Where does that come from ?

Looking forward for the new release, thanks mate :-)

I have to agree in terms the math. It's pretty convoluted

Profit wise my findings are that I make better returns lending consistently letting the loans break up into smaller chunks with variable duration without a hard minimum. The step down rate dropping is also a big reason why I myself don't use a minimum rate at all. BUT - I hear you. I thought about it and while the current build doesn't have manual settings I am going to add them. The coding, in fact, is done. I just need to get the build on my box to test it.

So within the next day or two I'll have a new build with a tab for "Manual Overrides". If you select that you'll be able to set a duration between 2 and 60 days and set the minimum rate. The system will still try to get you a better than minimum rate if the market is higher than your minimum, but it won't go below the minimum rate you set.

This more or less will eliminate the mean and deviation logic in the bot and have it function like other bots have in the past. Again, I think using the mean and deviation does yield a higher return but if you're having good results with a minimum setting I'm more than happy to provide it.

I'm hoping to have the new build out within 36 hours or so. I'll make a post when it's ready for download.

THANK YOU VERY MUCH !!!

...for your quick and detailed answer.

After reading twice, I got headache. So I called my mate over, usually a clever IT pro. He could'nt figure it out either.
Sorry mate, I have to ask you in a different way:

What setting keeps my offers at the highest level, with very slow decreasing. So hat PoloLend only makes high offers (above 0.3%).
If the rate stays down at 0.13 for 3 days, I don't mind have no active loans.

(I'm worried that PoloLend lends all my 8btc in the first few minutes or hours, while tomorow we get better offers.)

sorry for asking again ;-)

THX

Hi GoogleBit,

The minimum is essentially how low you'll post a loan offer from the average rate. I added it before I added the step down settings, so to be honest I set mine very low (which is a high setting in the drop down) and rely on the step down. As you change this the text underneath for minimum rate will show the lowest rate it'll offer the loan for.

The deviation bit is a tough nut to crack - hopefully this helps. If this doesn't sound like what you were expecting feel free to let me know what you're thinking - here or via PM. You're absolutely right about the average data. Right now it's off the mean by about .05%. The problem is the market changes so often that the starting data will never be perfect.

When I initially started testing this I used real numbers to extend the loans based on my observation of the market. IE I added 1 day if the rate was over .2%, 2 days if over .3%, etc. When I proved to myself I had higher returns over time that's when I took the time to add the heavier math and additional settings. Long story short the only difference between adding loan duration based on a real number such as .2%, .3%, etc. and using deviations is that with deviations the system adjusts to the market whereas using a real value, like .2, .3, etc may not be meaningful at all if the market changes.

In terms an easy example for a deviation, it's a tough one. To be honest I really can't think of a simple example but hopefully this makes sense. Deviations give us an idea of how far a typical loan rate is from the average rate. IE, if the average rate is .15 and the market rate is .2 we can easily see that the market rate is higher than average and that is meaningful. However, we don't really know how meaningful it is. There could be a situation where the historical rates are .1, .2, .1, .2 which would also give us an average of .15, but that would mean the .2 isn't unusual at all - it's happening every other time we check. The idea of deviations is it gives us a way to create an average range rather than a single average number. We create that range as basically (average - deviation) on the low side and (average + deviation) on the high side. Anything falling in that range is nothing special. It also gives us a way to get an idea of how different the rate is that we're checking. The idea is the majority of your rates will fall within the average range, then a smaller amount will be within 1 deviation, and an even smaller amount will be within 2 deviations. As the rate becomes more deviations higher from the average range the likelihood of seeing it becomes less and less and it's value to the lender becomes more and more.

Here's some heavier math:
Deviations are a way to measure how far a given value is from the mean (or average). To generate it first we find the average (we add all the points from the last two weeks together and divide by the amount of points). Then, to find the average deviation we measure the distance of all the points from the average to the point's own value (and this is the absolute value, so even if the result is a negative number we make it positive). IE if we have five points that are 3, 8, 7, 9, 5 our average is 6.4. Then to find the deviation we do this:
6.4 - 3 = 3.4
6.4 - 8 = 1.6
6.4 - 7 = .6
6.4 - 9 = 2.6
6.4 - 5 = 1.4

Then we average those results and our deviation is 1.92. That allows us to set a range that we can consider average, in this case it would be 4.48 through 8.32. That means that anything outside that range is unusual. If it's lower than the range then as lenders we don't want it, but we still may want to take it for as short a time as possible. If it's higher than that range then we definitely want it and should treat it better than we would an average point. That's where adding days comes in.

....aaaah, I'm sure the bloody thing will do what I'm expecting, but I still fight with the settings ;-)

One reason might be, I installed yesterday and may have not enough history in db.

But...

Minimum Loan Duration 2-60 Days
Minimum Loan Rate: -0.1 to -5.0 Deviation
Add 1-10 Day Per: 0.1 - 10 Deviation

Can you give me an easy example which includes "Deviation". Here I struggle ;-(

An what is the "minimum Lending rate" in Operation Log?

thx

Hi Mario,

Good suggestions. In terms the chart holding a longer span, which chart and how much time are you thinking? When I first started it up I was using a 30 day period to generate the mean and deviations, but I found it was too much data and cut it down to 2 weeks. The deviations over a month just got too big and I wanted them tighter. That doesn't mean I couldn't show more data, though.

I've thought about referrals and I've held off at the moment due to transaction fees. Most payments in are micropayments and if I were to pay out a percentage with fees where they are I'd be in a situation where I'd have to spend 100% of the balance in to pay 10% of the balance back out. I'm hoping after the situation in late July passes we'll have some kind of consensus and the fees will be a lot lower and I'll revisit.

Hi Silvie_S,

I'm currently using 2 days per .4 deviations. Typically I lend for a max of 45 days, but with Segwit2X and BIP148 coming I want to make sure I'm not lending any coins when they activate, so right now I'm using 5 day max and will be turning off in the second week in July to start moving my coins to a safe "bunker" until the crisis is past.

Thanks GoogleBit,

I'll be posting a new download this weekend to correct the labels on the API tab so they make more sense with Poloniex's API page.

In terms the add x day per x deviations, first I just want to remind everyone that BIP 148, Segwit2X, and the Bitmain plan are all coming together in the last week of July. I highly recommend that no one be lending coins during this period. Poloniex has made very clear that if coins are on loan when a split occurs, the lender will not receive back coins on both chains. I'm planning on working my coins out of lending prior to BIP 148 and Segwit2X activation, just to make sure I have them on hand before any possible splits occur.

That said, the idea of adding duration based on deviations is to attempt to maximize profits by holding the loans longer. Based on observation, there's a sweet spot between the 1st deviation and the 15th in which loans often stay in force for longer periods (that's between, roughly, 0.18% and 0.45% in the current market, but will change as the market rises and falls.) I find with rates over that you may have a loan accepted but it won't necessarily stay in force. My highest loan ever was 1.8%, but I only had it for 6 seconds.

For reference I'm personally adding 2 days per .4 deviations and the current average rate is roughly 0.15%. I usually give loans a maximum duration of 45 days. Right now, due to the situation in the end of July, I'm only lending for 5 days. These settings start adding days while still in the "high average" range.

The theory behind it is fairly simple. Loans that are in the average range are the easiest to get. Therefore it makes sense to keep the duration for those short so you can both get the benefits of compound interest and have a chance at a higher loan. As the rates move higher than average the likely hood of getting that loan rate again at the same time you have funds available for lending is less, so we try to hold those loans longer.

You will not hold all those above average loans, but you will hold some, and they will add to your overall amount earned. There is always a possibility, though, that the market will completely take off and you'll have a situation where higher rates are available and your funds are lent out lower. In practice, though, when the market is really flying and rates are high, traders are changing positions and oftentimes your loans will get closed because the trader that has it is shifting his position to include whatever is new and flying at that moment. I've been running this for a few months now and I have not seen a situation where I thought I missed out on higher rates due to extended loans. In theory it can happen and at some point it may, but I have not seen it yet.

I hope this makes sense .

...a referral system and a chart who covers longer time span.
And a button to pause lending ;-)

Otherwise clever made, and looks very handy.

This app does not charge 5% by itself, you have to pay for by hand. So, quite secure !

barcodeguy , looks interesting.

May I have a setup of "deviation Calculations" for 8BTC available for one year ?  ...out of your experience ?  please ;-)

THX

Beautyful tool !!!

It did not work with a new generated API key in the first place.
By the way, the app is asking for API/API key instead of API key/secret.
I had to generate another new API key, again without trading and withdrawal, and off he goes :-)

Dev, can you give me a more detailed explanation of " add x day to x deviation ".
Because that looks like the most important part.

Exciting !!!!!  :-)

I'm the first one ?

I'll give it a try...  ;-)