🔥🔥【MONITOR】 🔥🔥 Dracoix's Moonshot Pump Monitor

[dealung]

I bought this kind of thing, but it did not work well and beyond my expectations and I was disappointed.

I'm interested, but is there a trial version of it?

[dracoix]

I bought this kind of thing, but it did not work well and beyond my expectations and I was disappointed.

I'm interested, but is there a trial version of it?

PM sent.

Well that's the beauty of it, I promise nothing. I just use it for weekly coin picks and a few moon rides because I HODL long-term for days on end. Also, build 1089 really doesn't signal much (I'm now calling it a bug), but the Conf is still correct.

[parakacha]

I'm getting this error:


        at DracoixMoonAlert.json.JSONObject.getJSONArray(JSONObject.java:698)
        at DracoixMoonAlert.market.update(market.java:255)
        at DracoixMoonAlert.market.check(market.java:287)
        at DracoixMoonAlert.DracoixMoonAlert.loop(DracoixMoonAlert.java:135)
        at DracoixMoonAlert.DracoixMoonAlert.main(DracoixMoonAlert.java:110)
Press any key to continue . . .

What could it be?

[dracoix]

I'm getting this error:


        at DracoixMoonAlert.json.JSONObject.getJSONArray(JSONObject.java:698)
        at DracoixMoonAlert.market.update(market.java:255)
        at DracoixMoonAlert.market.check(market.java:287)
        at DracoixMoonAlert.DracoixMoonAlert.loop(DracoixMoonAlert.java:135)
        at DracoixMoonAlert.DracoixMoonAlert.main(DracoixMoonAlert.java:110)
Press any key to continue . . .

What could it be?

You cut off the good part of the error, so I have no idea other than I'm guessing Bittrex didn't send the data and gave a 503 instead.

[parakacha]

I'm getting this error:


        at DracoixMoonAlert.json.JSONObject.getJSONArray(JSONObject.java:698)
        at DracoixMoonAlert.market.update(market.java:255)
        at DracoixMoonAlert.market.check(market.java:287)
        at DracoixMoonAlert.DracoixMoonAlert.loop(DracoixMoonAlert.java:135)
        at DracoixMoonAlert.DracoixMoonAlert.main(DracoixMoonAlert.java:110)
Press any key to continue . . .

What could it be?

You cut off the good part of the error, so I have no idea other than I'm guessing Bittrex didn't send the data and gave a 503 instead.

Here is the top part after account confirmation:

Loading Markets...
0.38%
0.75%
20.00%
20.38%
20.75%
40.00%
40.38%
40.75%
60.00%
60.38%
60.75%
80.00%
80.38%
80.75%
Done...

24HR Market Health: -2.00%

Crunching to find pumpers...

ANN: Data is gathered in bulk, price is not as important as volume data points.
ANN: Candlestick data is gathered from the 5min dataset and as much as Bittrex a
llows to send.
ANN: Data requests are internally throttled to prevent Bittrex from throttling o
r banning.
INFO: V/MED is last Volume over (Filtered) Median Volume.
INFO: V/AVG is last Volume over (Filtered) Average Volume.
INFO: High values of previous mean big movement.
INFO: PCA is the percent of change from the price average of the entire download
ed candlestick data.
INFO: PCA's Simplified Formula: 100 * ((Last - Avg) / Avg)
INFO: Confidence is arbitrary signaling. 100 * (1 - (MED / V)) * (1 - (AVG / V))

INFO: ACT is the probability of *growth* activity within the next 5 minutes.
INFO: If there is a 'Moon Alert' take the risk with every precaution.

It may take several seconds before any markets are shown, please wait.

Exception in thread "main" DracoixMoonAlert.json.JSONException: JSONObject["resu
lt"] is not a JSONArray.
        at DracoixMoonAlert.json.JSONObject.getJSONArray(JSONObject.java:698)
        at DracoixMoonAlert.market.update(market.java:255)
        at DracoixMoonAlert.market.check(market.java:287)
        at DracoixMoonAlert.DracoixMoonAlert.loop(DracoixMoonAlert.java:135)
        at DracoixMoonAlert.DracoixMoonAlert.main(DracoixMoonAlert.java:110)
Press any key to continue . . .

[dracoix]

Okay so after the fact that I was getting it now too, and the long delay in my reply (sorry, was finding the problem), I have found the cause.

I have found the bug (it's on bittrex side, because they didn't updated their api data feed.)

"BTC-ANS", "BTC-SEC", "ETH-ANS", "ETH-SEC" are no longer a valid markets, even though they are listed as a valid market in the GetSummaries dump; how I list all existing coins to scan.

Unfortunately my v1.0's source has been butchered into version 1.1 that I was planning to release sometime this week. I'll have to step that up. If anyone is really desperate for a hotfix, pm me with your TxID and I'll give you a link to the hotfix that includes inactive future coding for version 1.1. It's basically 1.0 but with hidden debug code for 1.1, so your account.conf will still work... for now.

I'm now posting this stating that the problem has been acknowledged, a solution has been found, a hotfix has been made (for Moon Alert), but it should be cleared up in 24 hours because other api users are going to have the same problem lol.

tl;dr: IT SHOULD CLEAR UP SOON <24HR, BITTREX FORGOT TO REMOVE "ANS" AND "SEC", THEY ARE NOW "NEO" AND "SAFEX" Their GetSummaries api function include the old market names. :p

Also if you want the weekly coin picks, it's the least I can do while I was debugging:

Code:

Good Weekly Picks:
BTC-ARK   | +0.0008%    | After 24HR: +0.23%
BTC-GLD   | +0.0009%    | After 24HR: +0.26%
BTC-QWARK | +0.0013%    | After 24HR: +0.37%
BTC-OK    | +0.0017%    | After 24HR: +0.48%
BTC-ANT   | +0.0034%    | After 24HR: +0.98%
BTC-ADT   | +0.0070%    | After 24HR: +2.04%
BTC-XEM   | +0.0071%    | After 24HR: +2.08%
BTC-NLG   | +0.0114%    | After 24HR: +3.34%
BTC-OMG   | +0.0222%    | After 24HR: +6.60%

Bad Weekly Picks:
ETH-BCC   | -0.0692%    | After 24HR: -18.06%
BTC-XVG   | -0.0686%    | After 24HR: -17.92%
BTC-BCC   | -0.0389%    | After 24HR: -10.59%
BTC-DGB   | -0.0289%    | After 24HR: -7.99%
BTC-BTS   | -0.0280%    | After 24HR: -7.76%
BTC-XRP   | -0.0222%    | After 24HR: -6.20%
BTC-NXT   | -0.0217%    | After 24HR: -6.06%
BTC-XLM   | -0.0204%    | After 24HR: -5.71%
BTC-ARDR  | -0.0204%    | After 24HR: -5.71%

Take them with a 49% grain of salt. No seriously, that's pretty much how it works. lol

[parakacha]

Okay so after the fact that I was getting it now too, and the long delay in my reply (sorry, was finding the problem), I have found the cause.

I have found the bug (it's on bittrex side, because they didn't updated their api data feed.)

"BTC-ANS", "BTC-SEC", "ETH-ANS", "ETH-SEC" are no longer a valid markets, even though they are listed as a valid market in the GetSummaries dump; how I list all existing coins to scan.

Unfortunately my v1.0's source has been butchered into version 1.1 that I was planning to release sometime this week. I'll have to step that up. If anyone is really desperate for a hotfix, pm me with your TxID and I'll give you a link to the hotfix that includes inactive future coding for version 1.1. It's basically 1.0 but with hidden debug code for 1.1, so your account.conf will still work... for now.

I'm now posting this stating that the problem has been acknowledged, a solution has been found, a hotfix has been made (for Moon Alert), but it should be cleared up in 24 hours because other api users are going to have the same problem lol.

tl;dr: IT SHOULD CLEAR UP SOON <24HR, BITTREX FORGOT TO REMOVE "ANS" AND "SEC", THEY ARE NOW "NEO" AND "SAFEX" Their GetSummaries api function include the old market names. :p

Also if you want the weekly coin picks, it's the least I can do while I was debugging:

Thanks for the reply. I'm in no hurry to use it today. I will wait.

[dracoix]

They didn't fix it. So I fixed mine instead. Build 1171 is up. I removed the version 1.1 test code to keep prying eyes away from my Moonshot keygen testing.

[dracoix]

First alpha screenshot of Moonshot released.

[dracoix]

New Moonshot alpha screenshot showing $RISE shooting to the moon by sheer confidence triggering alone.

[dracoix]

And people wonder why I'm not releasing the alpha yet. $SWIFT broke the damn thing. https://i.imgur.com/gUWSK5j.png

Somehow it gave a value in a calculation that should have a value be less than 1, be greater than 1. The cruncher died and failed to signal a Moonshot, but the Conf is still an awesome arbitrary backup.

[le_hunnybear]

Hello dracoix!

I have downloaded and tested your software the last days and would like to give a short review of my experience so far:

User experience
The software does what it is supposed to do - a simple black prompt window where generated info is displayed. Nothing more or less. Downloading and start is quiet easy. Although I have to admit I did not test the "buy" part of the tool so far ...  

Signals and data usage
I ran the tool from 12.08.17 20:00 CEST - 14.08.17 16:00 CEST.
In total the following signals were generated:

Sell signals	3111
Late signals	2051
Buy signals	28

In average this tool used 0,92 GB data per hour.

Personal opinion
I think the idea of this tool is great and I am really looking forward to see your new planned tool However I would strongly suggest the following things:

• Add a time stamp and the current asset's value to every generated signal. Especially in break-out trading timing and the entry point is everything. Unfortunately it is impossible to assess the generated signals retrospectively without that info.  
• I am thinking of using your signals in an automated (maybe self written) trading tool. Therefore it would be great to get easy access to your generated signals so they can be processed automatically. Implementing the possibility to log signals to a text file would help a lot (especially in your new graphical Moonshot tool)

Keep on with your great work, I really appreciate.

In the end a question: Will the generated signals of your "simple" tool and your "graphic" moonshot monitor be the same?

[dracoix]

Hello dracoix!

I have downloaded and tested your software the last days and would like to give a short review of my experience so far:

User experience
The software does what it is supposed to do - a simple black prompt window where generated info is displayed. Nothing more or less. Downloading and start is quiet easy. Although I have to admit I did not test the "buy" part of the tool so far ...  

Signals and data usage
I ran the tool from 12.08.17 20:00 CEST - 14.08.17 16:00 CEST.
In total the following signals were generated:

Sell signals	3111
Late signals	2051
Buy signals	28

In average this tool used 0,92 GB data per hour.

Personal opinion
I think the idea of this tool is great and I am really looking forward to see your new planned tool However I would strongly suggest the following things:

• Add a time stamp and the current asset's value to every generated signal. Especially in break-out trading timing and the entry point is everything. Unfortunately it is impossible to assess the generated signals retrospectively without that info.  
• I am thinking of using your signals in an automated (maybe self written) trading tool. Therefore it would be great to get easy access to your generated signals so they can be processed automatically. Implementing the possibility to log signals to a text file would help a lot (especially in your new graphical Moonshot tool)

Keep on with your great work, I really appreciate.

In the end a question: Will the generated signals of your "simple" tool and your "graphic" moonshot monitor be the same?

Thanks for the constructive criticism!

Yes I'll add timestamps and price for 1.1.

1GB per hour is insanely high if it's network usage. I'll look into that.

As I stated before, the signals are a little (more) unreliable and restrictive since 1089 when I implemented Time-Of-Day relative activity and traditional statistics.

The signals should be the same and are arbitrary to tuning. Classic uses simple Conf and PCA (5min percentage change relative to the mean of all 5min changes). But recently I've been using the fill order book in conjunction with in/out pool volume. When the pool is negative and there's more sell fills than buy fills, that's obviously a SELL signal, the reverse BUY, and when it's stable up spree (bandwagon) it's a moon alert. It's more visual on the candlestick chart and there's a start and end to the display. The current problem is HODLers, oh my god the HODLers, they buy and never sell even when their bags drop to oblivion. Just one more thing to tune. When that's accurate to my liking, it'll be thrown into the new version of Classic. I also noticed on both Poloniex and Bittrex, for weeks now, on Bear days there's a massive human bias bandwagon for top 24hr% so much so that I'm almost profiting from them, that too will be added feature. I'm a newb when it comes to financial tendencies, but math is math, data is data, and I follow it where it takes me.

The most accurate thing in classic are the weekly coin picks (they are based strictly on statistical behavior), the Conf (Confidence there's anomalous activity), TV (Time-of-day average volume), and TC (Time-of-day average price change). I made so much coinage off weekly picks, it's not even funny, almost gained back half my losses from the June crash. When I was using Classic, I didn't even use the BUY/SELL/LATE signals personally anymore, just Conf and coin picks. I'm personally scared of changing the code of coin picks for this reason. But I will have to add to it for Moonshot.

Thank you. Few instance I get feedback, a lot of trial keys were passed out in the hopes for more ideas. I don't see your username in my pms, so if you bought yours, pm me your ETH address so I can put you in the queue. If you brute/spoofed it, all the same, you're getting a fancy keycode soon.

Now back to coding! I got progression screenshot to grab.

[2Block]

I would be interested, would def need to trial first. Let me know if that is available. Sounds like a great tool! Thanks

[easwil]

A very interesting tool I don't know if it will work well but I would love to try it out.

[dracoix]

New screenshot: https://i.imgur.com/kF0UkAA.png

Sorry for the delay, I've been doing other things.

It's been a bloodbath day for altcoins, best day to debug and code. Moonshot highlights (cyan-colored volumes) only use past data, when I start making coins off them (simulated at least) that's when they'll be finalized. PSUM (not to be mistaken for p-value) is equal to (last 6 candles volume) / (entire two-week data volume), basicly anything over 1% is true moonshot/bandwagon activity; right now much of those numbers are debug info for myself. Oh, and I added USDT markets.

I thank you all for patiently waiting for a beta version to drop. I'm hoping sometime this weekend.

Bonus screenshot: https://i.imgur.com/HzrPKW5.png - let me know how this one goes.

[tiiim]

Hi, i bought just to give it a try.

What is up with this message;?

Please Enter the CONFIRMED Transaction Hash (TxHash):0x#####################################

TRANSACTION DOESNT MATCH!
Incorrect sending address!
Press any key to continue . . .

[dracoix]

Hi, i bought just to give it a try.

What is up with this message;?

Please Enter the CONFIRMED Transaction Hash (TxHash):0x#####################################

TRANSACTION DOESNT MATCH!
Incorrect sending address!
Press any key to continue . . .

I've had 4 instances so far of people using a mixed-case (upper and lower case lettering) in their address. I'm not sure what wallet does that, but I never expected a wallet to spit out non-standard base16, my assumption is now a bug. I have to manually recreate a new keycode for each issue.

[soothaa]

This looks interesting but I am a little confused as to what it does.. is this doing technical analysis or is it watching sudden volume and price changes on coins?

[dracoix]

This looks interesting but I am a little confused as to what it does.. is this doing technical analysis or is it watching sudden volume and price changes on coins?

Mostly anomalous volume changes. It won't track common fluctuations from daily activity, so if the coin price skyrockets from normal volume activity, it might be completely ignored. It will detect first instances of bandwagoning and huge single-instance dumps/pumps though.