I have been trying to withdraw a balance of around 1.2M GBP from Bitstamp for the last month. 

It has repeatedly failed.  They keep sending me in circles and fobbing me off.  I have raised several support tickets, and on Friday I raised a complaint via their complaints email address.  In my last support enquiry, I told them that I would have to treat the funds as stolen, if they tried to fob me off again.  But, they tried to fob me off, with some supporttard telling me to clear cookies and cache (classic fobbing-off technique), and closing the ticket.  So I do now have to treat the funds as stolen.

Although their domicile has always been unclear to me (elements apparently in UK, EU, US, and customer relationship apparently being moved between "entities"), it has always seemed to have a UK presence.  Therefore, I intend to raise a complaint with the FCA, and with the Serious Fraud Office in London.

My suspicion is that this is similar to when other exchanges in the past have started failing to execute withdrawals: that their client money account(s) do not match their client balances, or put more simply, that they have stolen client money.

The exact pattern has been: I enter my GBP bank account details as per the form, with IBAN etc.  I submit the withdrawal request.  I get an email saying it failed, and for GBP I must enter account number in IBAN / account number field, and sort code in SWIFT/BIC field.  I then try to do this, but their form won't accept it.  When I enter the six digits without dashes, form validation fails in one way.  When I enter it with dashes, it fails in a similar but slightly different way.  I then raise the issue with them, they fob me off / incorrectly tell me it's fixed, and I go through the cycle again.

I am going to assemble an exact timeline, screenshots, ticket text, etc, ready for submitting the complaints, and will update this thread with more details in due course.

The broadcast is of a fake rendering.

and entering prices manually for the subsequent 3 days, and running again, gives:

a: 0.00270063443633625
b: 0.574351659178193
predicted y: 10.7881510974019
predicted price: 48443
ln(todays price): 9.81465633882951
beti: -0.973

I make BETI -0.977 as of 2020-11-20, using gox then kraken daily data, with cutoff date of 2013-10-06, and filling in gaps (only a few days in each of gox and kraken) by assuming the price stays the same during the gap.

a: 0.00270185020127701
b: 0.572820201440624
predicted y: 10.7831121120664
predicted price: 48199
ln(todays price): 9.80587472366913
beti: -0.977

It doesn't work like that.  It would converge on a stagnant price, because it's using a best-fit to a model.

Output of a hacky script to do this today gives this:

<pre>
a: 0.00270185020127701
b: 0.572820201440624
predicted y: 10.7831121120664
predicted price: 48199
</pre>

They're not "adjusted".  They just are what they are, based on the regression fit.

How has it done against CHF over the time period?  That's the benchmark for stable value; loses roughly 1% a year.  Rule of thumb for shitcurrencies like those listed ITT is 5-7%, ignoring official stats.

They are determined on-the-fly by a regression fit, no?  Otherwise it's not BETI as defined by this thread.

any chance of an up-to-date BETI graph?

how about trimming back to 20 instead of 100?

I downloaded Electrum-3.3.4.tar.gz, unpacked, and ran ./run_electrum.

I get:

  File "./run_electrum", line 53
    sys.exit(f"Error: {str(e)}. Try 'sudo python3 -m pip install '")
                                                                               ^
SyntaxError: invalid syntax

I didn't want to "update", but my balance-monitoring using 2.9.3 stopped working at some, it's just perpetual "Synchronizing".

So shoddy all round.  Not an ongoing solution to anything, will find new solution for monitoring address balances.

Number of days exceeding half of top day: 20.

Number of days exceeding half of top day: 20.

Previous value: 17 for 2017-12-12.

Number of days exceeding half of top day: 17.

Number of days exceeding half of top day: 20.

Number of days exceeding half of top day: 22.

Number of days exceeding half of top day: 24.

Number of days exceeding half of top day: 35.

Number of days exceeding half of top day: 43.

Number of days exceeding half of top day: 46.