Security in pump

[certifirm]

As you said in your README, pump-dump are scam.

I think that may be useful add another parameter to test how much percent has grow the coin 5 or 10 seconds ago, or compare with the media of the previous day, or something like this. Sorry, but I am not a trader

May be, the script buys at 300% of the "normal" price.

[TTB82]

I think this question is a very useful suggestion.

From my point of view, it could be useful to have 2 checks before entering the pump, which can be set in the settings. For example (functional code): checkpoint1 = now() - 2 minutes checkpoint2 = now() - 30 minutes checkpointmaxdiff1and2 = 10 percent checkpointmaxdiff1andnow = 50 percent

if difference between (checkpoint1.value and checkpoint2.value) > checkpointmaxdiff1and2 OR if difference between (checkpoint1.value and now() ) > checkpointmaxdiff1andnow exit ELSE continue

Thank you for sharing your script. @BinaryDevil

UPDATE (3-14-2021): I was experimenting this feature and created a part of it; but point is, these requests take some time which you loose regarding the buying process. So this idea might not be that good as I (and @certifirm) thought.

UPDATE (3-22-2021): After timing the check, it doesn't really matter and takes less time than expected. I've added it anyway in my version. Furthermore, I want to experiment also with the price value based on 5 minutes before the pump, to take that as a base line for the values in the config. For example: when the pump is already on going, and the first buy has been done, the PEAK_TAKE_PROFIT_THRESHOLD is based on that price value. I think I want to change this into the value of 5 minutes ago. Maybe I will provide this solution later on in a fork of this project.

[ekog66]

I think this question is a very useful suggestion.

From my point of view, it could be useful to have 2 checks before entering the pump, which can be set in the settings. For example (functional code): checkpoint1 = now() - 2 minutes checkpoint2 = now() - 30 minutes checkpointmaxdiff1and2 = 10 percent checkpointmaxdiff1andnow = 50 percent

if difference between (checkpoint1.value and checkpoint2.value) > checkpointmaxdiff1and2 OR if difference between (checkpoint1.value and now() ) > checkpointmaxdiff1andnow exit ELSE continue

Thank you for sharing your script. @BinaryDevil

UPDATE (3-14-2021): I was experimenting this feature and created a part of it; but point is, these requests take some time which you loose regarding the buying process. So this idea might not be that good as I (and @certifirm) thought.

how can i add these ? i think its needed security over losses..

[TTB82]

I think this question is a very useful suggestion. From my point of view, it could be useful to have 2 checks before entering the pump, which can be set in the settings. For example (functional code): checkpoint1 = now() - 2 minutes checkpoint2 = now() - 30 minutes checkpointmaxdiff1and2 = 10 percent checkpointmaxdiff1andnow = 50 percent if difference between (checkpoint1.value and checkpoint2.value) > checkpointmaxdiff1and2 OR if difference between (checkpoint1.value and now() ) > checkpointmaxdiff1andnow exit ELSE continue Thank you for sharing your script. @BinaryDevil UPDATE (3-14-2021): I was experimenting this feature and created a part of it; but point is, these requests take some time which you loose regarding the buying process. So this idea might not be that good as I (and @certifirm) thought.

how can i add these ? i think its needed security over losses..

You can add it yourself or wait till someone (BinaryDevil.... or me) uploads a newer version. Maybe it should be tested first properly and this takes time. No one is holding you back to try to fix it yourself.

[C4rne]

I think this question is a very useful suggestion.

From my point of view, it could be useful to have 2 checks before entering the pump, which can be set in the settings. For example (functional code): checkpoint1 = now() - 2 minutes checkpoint2 = now() - 30 minutes checkpointmaxdiff1and2 = 10 percent checkpointmaxdiff1andnow = 50 percent

if difference between (checkpoint1.value and checkpoint2.value) > checkpointmaxdiff1and2 OR if difference between (checkpoint1.value and now() ) > checkpointmaxdiff1andnow exit ELSE continue

Thank you for sharing your script. @BinaryDevil

UPDATE (3-14-2021): I was experimenting this feature and created a part of it; but point is, these requests take some time which you loose regarding the buying process. So this idea might not be that good as I (and @certifirm) thought.

UPDATE (3-22-2021): After timing the check, it doesn't really matter and takes less time than expected. I've added it anyway in my version. Furthermore, I want to experiment also with the price value based on 5 minutes before the pump, to take that as a base line for the values in the config. For example: when the pump is already on going, and the first buy has been done, the PEAK_TAKE_PROFIT_THRESHOLD is based on that price value. I think I want to change this into the value of 5 minutes ago. Maybe I will provide this solution later on in a fork of this project.

hi TTB82, i would like to share some ideas with you and then try to turn into code (im not a developer)., is there a way i can contact you ? maybe an email ?

[TTB82]

I think this question is a very useful suggestion. From my point of view, it could be useful to have 2 checks before entering the pump, which can be set in the settings. For example (functional code): checkpoint1 = now() - 2 minutes checkpoint2 = now() - 30 minutes checkpointmaxdiff1and2 = 10 percent checkpointmaxdiff1andnow = 50 percent if difference between (checkpoint1.value and checkpoint2.value) > checkpointmaxdiff1and2 OR if difference between (checkpoint1.value and now() ) > checkpointmaxdiff1andnow exit ELSE continue Thank you for sharing your script. @BinaryDevil UPDATE (3-14-2021): I was experimenting this feature and created a part of it; but point is, these requests take some time which you loose regarding the buying process. So this idea might not be that good as I (and @certifirm) thought. UPDATE (3-22-2021): After timing the check, it doesn't really matter and takes less time than expected. I've added it anyway in my version. Furthermore, I want to experiment also with the price value based on 5 minutes before the pump, to take that as a base line for the values in the config. For example: when the pump is already on going, and the first buy has been done, the PEAK_TAKE_PROFIT_THRESHOLD is based on that price value. I think I want to change this into the value of 5 minutes ago. Maybe I will provide this solution later on in a fork of this project.

hi TTB82, i would like to share some ideas with you and then try to turn into code (im not a developer)., is there a way i can contact you ? maybe an email ?

Why don't you share your idea right here? Please take note that @BinaryDevil is the initiator of this script, and good idea's are probably welcome on his address ...

[C4rne]

Why don't you share your idea right here? Please take note that @BinaryDevil is the initiator of this script, and good idea's are probably welcome on his address ...

Sure i already wrote him in order to analize first of all the feasibility and estimate the effort.. basically the idea is not so far from what certifirm said at the beginning of post: avoid to buy at highest position (fulfilling sell orders of who entered in the very first seconds of the pump) and maybe find a way to predict the pair that is going to be pumped by observing all the xxx/btc pairs..

[BinaryDevil]

In my opinion security is all about choosing the right group, as in these events 1 second can result in a lot of price change, if your pump is pre-pumped probably you will not stand a chance no matter how.

Currently you can disable initial buy in the config. But your thoughts are welcome and any PR is very welcome, as I have a lot of work in daily life and might not have sufficient time to enhance this script. (and I don't participate p&ds any more)

[C4rne]

In my opinion security is all about choosing the right group, as in these events 1 second can result in a lot of price change, if your pump is pre-pumped probably you will not stand a chance no matter how.

Currently you can disable initial buy in the config. But your thoughts are welcome and any PR is very welcome, as I have a lot of work in daily life and might not have sufficient time to enhance this script. (and I don't participate p&ds any more)

You right, but even with the right group moving lot of volume (1400 BTC according to the last pump on 28th march) the chance of getting profit for "outsiders" like us are getting smaller every pump.. in order to automatically select the pair in order to enter from the beginnig, in config i would set 3 const like:

• pump time (hhmmss when the pump should start );
• % growth (of the pair) from the beginning of the day (as you said they are always prepumped)
• % growth on the first second after the pump time. if real time data ara >= the % growth preset as const in config then select that pair to apply the rest of the code.

the problem is to analyze all the xxx/btc Pair simultaneously and get those kind of data.. i don't know if those are available from API

Also a check on traded volumes would be very helpfull but again i don't know how to get those info...

More than one pair may have a % growth from the beginning of the day >= of what we preset in config, but only one have an additional peack on the first second after the pump event time (we set) becouse we now the time when the bolt hit the ground..

i see that those kind of implementation are not an easy deal but they may woth it ... let me know what you think about !

[C4rne]

Is there anybody that know how to turn this idea (if feasible) into a project maybe involving other developer here on github?