Going offshore to escape the CFTC

TRADERSWAY PERFORMANCE ISSUES

I am running one TradersWay account in a pool of brokers,
and just noticed truly awful performance. Whereas the
Coinexx and FinPro accounts were executing in the range of
500-700 msecs, which I regard as fairly slow; the Tradersway
account was clocking up 2,000 - 20,000 - 60,000 msecs which
is so slow my system logic even has trouble dealing with that,
since copy-Slaves should refrain from copying a Master if the
latency in response to the Master is > 30 seconds or so…
since any price precision is lost…

Anyway… I’m just sayin’ that’s terrible, and I’ve advised that
the account be moved. All of the accounts are MT4.

hyperscalper

[EDIT] just check out this data where [TW] is the TradersWay
account.
[20181105-22:37:00.632(GMT)] OrderOp BUY Exception elapsed msecs: 99
[20181105-22:37:00.819(GMT)] OrderOp BUY Exception elapsed msecs: 298
[20181105-22:37:00.819(GMT)] OrderOp BUY Exception elapsed msecs: 298
[20181105-22:37:00.835(GMT)] OrderOp BUY Exception elapsed msecs: 313
[20181105-22:37:00.835(GMT)] OrderOp BUY Exception elapsed msecs: 302
[20181105-22:37:01.039(GMT)] Buy Market OrderOp elapsed: 516
[20181105-22:37:01.040(GMT)] Buy Market OrderOp elapsed: 518
[20181105-22:37:10.056(GMT)] Buy Market OrderOp elapsed: 9519 [TW]
[20181105-23:47:03.276(GMT)] OrderOp Buy Limit elapsed: 266
[20181106-00:08:53.130(GMT)] OrderOp BUY Exception elapsed msecs: 69
[20181106-00:08:53.158(GMT)] OrderOp BUY Exception elapsed msecs: 97
[20181106-00:08:53.177(GMT)] OrderOp BUY Exception elapsed msecs: 90
[20181106-00:08:53.186(GMT)] OrderOp BUY Exception elapsed msecs: 92
[20181106-00:08:53.346(GMT)] OrderOp BUY Exception elapsed msecs: 285
[20181106-00:08:53.376(GMT)] OrderOp BUY Exception elapsed msecs: 315
[20181106-00:08:53.392(GMT)] OrderOp BUY Exception elapsed msecs: 305
[20181106-00:08:53.392(GMT)] OrderOp BUY Exception elapsed msecs: 298
[20181106-00:08:53.502(GMT)] Buy Market OrderOp elapsed: 407
[20181106-00:08:53.502(GMT)] Buy Market OrderOp elapsed: 408
[20181106-00:08:53.680(GMT)] Buy Market OrderOp elapsed: 587
[20181106-02:26:52.662(GMT)] OrderOp Close Position elapsed: 130
[20181106-02:26:54.192(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: xxxx514 msecs: 450
[20181106-02:26:54.209(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: xxxx924 msecs: 468
[20181106-02:27:11.095(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: [TW] msecs: 17354
[20181106-04:19:53.081(GMT)] OrderOp Close Position elapsed: 223
[20181106-04:19:54.597(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: xxxx514 msecs: 530
[20181106-04:19:54.627(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: xxxx924 msecs: 560
[20181106-04:20:08.213(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: [TW] msecs: 14146
[20181106-06:32:28.134(GMT)] OrderOp BUY Exception elapsed msecs: 112
[20181106-06:32:28.150(GMT)] OrderOp BUY Exception elapsed msecs: 131
[20181106-06:32:28.165(GMT)] OrderOp BUY Exception elapsed msecs: 144
[20181106-06:32:28.184(GMT)] OrderOp BUY Exception elapsed msecs: 162
[20181106-06:32:28.385(GMT)] OrderOp BUY Exception elapsed msecs: 363
[20181106-06:32:28.400(GMT)] OrderOp BUY Exception elapsed msecs: 381
[20181106-06:32:28.462(GMT)] OrderOp BUY Exception elapsed msecs: 441
[20181106-06:32:28.478(GMT)] OrderOp BUY Exception elapsed msecs: 456
[20181106-06:32:28.540(GMT)] Buy Market OrderOp elapsed: 517
[20181106-06:32:28.555(GMT)] Buy Market OrderOp elapsed: 535
[20181106-06:33:25.462(GMT)] Buy Market OrderOp elapsed: 57439 [TW]
[20181106-06:43:09.492(GMT)] OrderOp BUY Exception elapsed msecs: 108
[20181106-06:43:09.508(GMT)] OrderOp BUY Exception elapsed msecs: 124
[20181106-06:43:09.524(GMT)] OrderOp BUY Exception elapsed msecs: 141
[20181106-06:43:09.555(GMT)] OrderOp BUY Exception elapsed msecs: 169
[20181106-06:43:09.743(GMT)] OrderOp BUY Exception elapsed msecs: 359
[20181106-06:43:09.758(GMT)] OrderOp BUY Exception elapsed msecs: 374
[20181106-06:43:09.774(GMT)] OrderOp BUY Exception elapsed msecs: 391
[20181106-06:43:09.852(GMT)] OrderOp BUY Exception elapsed msecs: 466
[20181106-06:43:09.899(GMT)] Buy Market OrderOp elapsed: 514
[20181106-06:43:09.930(GMT)] Buy Market OrderOp elapsed: 547
[20181106-06:43:10.275(GMT)] Buy Market OrderOp elapsed: 886
[20181106-12:15:20.425(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: xxxx924 msecs: 696
[20181106-12:15:20.426(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: xxxx514 msecs: 697
[20181106-12:15:29.971(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: xxxx503 msecs: 598
[20181106-12:15:30.001(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: xxxx514 msecs: 625
[20181106-12:15:30.002(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: xxxx518 msecs: 626
[20181106-12:15:30.002(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: xxxx523 msecs: 630
[20181106-12:15:30.109(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: xxxx924 msecs: 730
[20181106-12:16:14.778(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: [TW] msecs: 55048
[20181106-12:16:15.261(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: [TW] msecs: 45885
[20181106-12:16:15.265(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: [TW] msecs: 44683
[20181106-12:16:15.281(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: [TW] msecs: 43493
[20181106-12:16:56.774(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: xxxx503 msecs: 599
[20181106-12:17:09.985(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: xxxx519 msecs: 557
[20181106-12:29:56.077(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: xxxx514 msecs: 633
[20181106-12:29:56.093(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: xxxx924 msecs: 648
[20181106-12:29:56.260(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: [TW] msecs: 816
[20181106-12:35:11.421(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: xxxx514 msecs: 545
[20181106-12:35:11.439(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: xxxx924 msecs: 562
[20181106-12:35:33.350(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: [TW] msecs: 22473
[20181106-12:41:15.107(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: xxxx514 msecs: 564
[20181106-12:41:15.206(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: [TW] msecs: 663
[20181106-12:41:15.217(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: xxxx924 msecs: 674
[20181106-13:04:39.668(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: xxxx514 msecs: 532
[20181106-13:04:39.777(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: xxxx924 msecs: 641
[20181106-13:04:39.959(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: [TW] msecs: 823
[20181106-13:05:13.335(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: [TW] msecs: 504
[20181106-13:05:13.385(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: xxxx924 msecs: 554
[20181106-13:05:13.511(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: xxxx514 msecs: 680
[20181106-13:05:16.980(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: xxxx514 msecs: 541
[20181106-13:05:17.089(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: xxxx924 msecs: 651
[20181106-13:05:18.712(GMT)] SlaveCloseOrderTask OrderOp elapsed acct: [TW] msecs: 2274

come to think of it swap fees are so high on bitmex that i cant imagine coinexx having higher fees, id be surprised if so.

.075% taker fee for what you have in position, i.e., 20 bitcoin leveraged at 100 so your real amount is only 20% of a bitcoin, but you pay the fee for 20 bitcoin. It basically works out to starting off a position at a 7.5% loss. Needless to say I try to do maker fees on the other exchange i use, but the liquidity is poor and I get front ran badly by mm bots.

im attempting to make an account at hugos way if theyll approve it. it does say not directed at contrary jurisdiction yadda yadda so eh. I figure Ill give coinexx and hugos way an even chance, just feel like the kyc is more likely to get me my money back if and when giancarlo decides to pay them a visit to stop all the fun.

That is indeed bad. What did Trader’s Way say about it?
Was it definitely Trader’s Way, or points in between?
Either way, I am hoping it is just an anomaly. TW has built a good reputation over the years.
If it was their servers, it also is nice to know if they refund any funds lost because of it.

BTW: my foreign language experiment didn’t pan out. foreign broker referred me back to a broker in Luxembourg that doesn’t accept US clients, no matter what language the US client speaks.

I’m not going to the trouble to investigate one of a dozen broker
accounts and follow up. Direct comparison with other brokers
at the same time is enough for me… We run from highly tuned
dedicated servers in Amsterdam; not from some DSL modem in
my basement… LOL :slight_smile: TW’s MT4 backends I think are either
Amsterdam or London; not sure…

[EDIT] the MT4 instance journal says we are 1.92 milliseconds
from TW’s MT4 servers… So… we’re close enough

hyperscalper

i agree about KYC but hugosway have a bigger problem they are directly operating on U.S. soil

TW’s LPs rejecting your trades ?

I don’t have time to track what the problem is. These are Market
Orders and Market Closures, which are time-sensitive,
and all the other accounts respond instantly, so…

hyperscalper

COINEXX MAINTENANCE DEPOSIT DELAYS

I’ve been having some issues and delays moving initial
deposit funds into Coinexx accounts. It should be
an instant and automatic process but apparently
they are undergoing “maintenance” issues, so I’m
looking at an “8-10 hour” delay, according to their
support.

[EDIT] now 10 hours or so and waiting for Coinexx
to fix whatever their deposit problems are…

[EDIT2] … next morning… looks like the deposits
have been made at Coinexx… hoping they don’t have
any further probs…

[EDIT-final] I guess I forgive them since then sent me
this cute email apologizing:
"Dear ,
Apologies if you had any inconvenience from our end. I can confirm that payment has been successful updated in your account. Our deposit process is completely automated; all the deposits automatically get updated in the trading account once confirmed on the block-chain network. However due to some technical slag, these particular transactions were not credited in time due to the maintenance going on the client area, the concern has been raised to the technical department and they have been looking into it and will make sure nothing sort of this happens in future again

If you require any assistance or have any questions, please feel free to contact us any time via Live Chat, email ( [email protected] ) or 24/5 live chat."

APOLOGY ACCEPTED !!

hyperscalper

One of our members has sent me a file of email correspondence to and from Vload, regarding failed (declined) funds transfers. The problems began on or about October 19, and, as of today, have not been resolved by Vload.

I was asked for advice regarding this problem – advice which I can’t give, because I have no recent experience with Vload.

But, some of you have had recent dealings with Vload, and now have an opportunity to help a fellow member with a frustrating problem.

If you have used Vload for funds transfer since October 19, please weigh in here with details of the steps you took to complete the transfer, the time required from start to finish, and any snags which you hit along the way.

Specifically, did you get any sort of run-around concerning 3D-Secure authentication?

  • Is Vload screwed up?

  • Is Vload unwilling to admit that they are under attack by U.S. regulators?

  • Or, is this just a one-time snafu?

Let’s find out. Please help, if you can.

just got this message in my EPAYMENT account

" Financial consultants: exercise caution

Be aware. Some customers are being encouraged to register an ePayments account to transfer funds to financial investment schemes that are then not delivering on the promises made.

Please note, ePayments does not have any exclusive partnership with any investment institution or financial consultant. You should scrutinise the collaboration with such entities thoroughly before making any payment."

I made a fairly significant number of transfers using Vload on October 29 and October 30 to deposit funds into 2 different forex brokers, everything worked very smoothly without a hitch, the purchases showed as pending for about 1 minute then were ready, the deposit transfers to the brokers was instant. Prior to that I did have a credit card decline in an attempt to purchase Vload vouchers, but that was because my bank was blocking the transaction. I used a different card from a different bank and had no problems.

I made 2 purchases with Vload on 10/24/2018 and 10/25/2018. The first one was smooth, and the second one missed PIN,and Vload said they had tech issues, and would resend me PIN in 24 hours. The problem was resolved in 24 hours and I got my PIN.
The tranfers from Vload to coinexx were smooth.

FINPRO PERFORMANCE

Very consistent performance, finally getting some things ramped
up to volume trading… FinPro does have very consistent
performance, as you can see, and low commissions.

hyperscalper

[20181108-01:15:33.860(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 101
[20181108-01:28:02.892(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 119
[20181108-01:29:31.727(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 156
[20181108-01:29:31.837(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 266
[20181108-01:41:00.406(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 179
[20181108-01:41:00.530(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 304
[20181108-01:41:01.061(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 133
[20181108-01:44:39.467(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 137
[20181108-01:44:39.577(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 247
[20181108-02:24:55.450(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 103
[20181108-02:24:55.560(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 213
[20181108-03:47:21.502(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 153
[20181108-04:20:29.901(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 132
[20181108-04:20:30.006(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 237
[20181108-04:41:51.311(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 180
[20181108-05:29:14.498(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 127
[20181108-05:49:14.355(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 161
[20181108-06:07:26.909(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 142
[20181108-06:07:27.020(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 253
[20181108-06:07:27.565(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 94
[20181108-06:08:26.953(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 123
[20181108-06:30:54.799(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 165
[20181108-06:35:07.410(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 100
[20181108-06:40:05.192(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 121
[20181108-06:49:24.601(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 153
[20181108-06:49:33.006(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 144
[20181108-14:07:46.367(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 156
[20181108-14:07:47.331(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 413
[20181108-14:08:43.518(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 196
[20181108-14:15:54.723(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 148
[20181108-14:16:01.068(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 160
[20181108-14:27:50.833(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 897
[20181108-14:27:50.833(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 193
[20181108-14:27:51.002(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 362
[20181108-14:27:51.003(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 1067
[20181108-14:31:15.935(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 81
[20181108-14:33:40.842(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 137
[20181108-14:33:40.952(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 247
[20181108-14:33:41.499(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 93
[20181108-14:38:04.244(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 143
[20181108-14:38:04.368(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 267
[20181108-14:40:01.948(GMT)] SlaveCloseOrderTask elapsed acct: [FinPro] msecs: 156

1 Like

TURNKEYFOREX AND FINPROTRADING LEVERAGE

We are still seeing 400:1 leverage.

Are we anticipating that ESMA will drive that down?

I am leaning toward Coinexx to avoid jurisdictional leverage
restrictions, but maybe it’s too soon to worry?

[EDIT] or perhaps large minimum deposit levels will be used
to drive smaller traders away is the greater worry?

hyperscalper

1 Like

FXCHOICE FUNDS WIRE TRANSFER ISSUES

…from an email just now…

"Unfortunately, starting from November 12th, 2018 we will no longer be able to process payments (both Deposits and Withdrawals) that use the following two Intermediary/Correspondent banks:

Deutsche Bank AG, Frankfurt
Deutsche Bank Trust Companies Americas, New York
Any payments that are attempted using the above-mentioned Intermediary/Correspondent banks will be rejected and returned, minus the fees."

hyperscalper

Regarding large minimum deposits, have you heard something about it, or just thinking out loud?

Thanks.

ARTICLE ON ESMA IMPLICATIONS

Generally what I’ve read is that the regulators generally want
to kill small retail forex… anyway, we’ll see. One way to do
this is cut back on leverage, and raise minimum deposit.
This article talks about the projected impact areas. It’s
more “Nanny State” stuff, but Euro style !!

hyperscalper

My workaround for now is to have several high leverage, small, crypto currency denominated accounts with funds in reserve to compensate for any drawdown. That and being prepared to move quickly. Code strategies in R, Python, MQL4, and MQL5.

Is there any way we could petition for better legislation? I would be willing to take a training class and get certified in order to trade. Reading Hyperscalper’s posted article, ‘they’ claim to be worried about people squandering all their money. If I can get certified to carry a handgun, why can I not get certified to handle my own money as I choose?

1 Like

Yeah, it would be great if “real traders” could get an exception to
the Nanny State rules for the Masses… But that’s not gonna happen…

[EDIT] and why should I have to ask “the Nanny State” for permission
to have a perfectly legal business, in which “the Nanny State” should
not be involved in the first place… ? It’s a shame… But where there
is a demand, whether for Drugs or Services, someone will be able
to provide the service, and I’m talking about legal drugs of course !

hyperscalper