Firstly: it isn't called "attack". It is called "cross-exmination" and is one of the core percepts of adversarial system of justice in the USA. It is also commonly used while performing "due dilligence" in the USA.

Secondly: I questioned Gavin Andresen on him continuing to provide what appears like accounting advice, despite the following:

2a) he had closed his personal Bitcoin business (Clearcoin) before he was legally obliged to submit paperwork under the penalty of perjury.
2b) he continues to make implicit statements portraying bitcoin{d,-qt} as compliant with the GAAP (both for the USA and the rest of the Western world and its accounting tradition).

Moderators: I know this is a sore subject on this forum. Try maybe moving it to the appropriate place instead of simply deleting. Thanks.

Mr. shtylman had inadvertently disclosed that he is completely unfamiliar with how US banks operate in regards to account overdrafts. I'm suspect that he not only isn't a US resident but he also doesn't have a business nor personal nexus in the USA (meaning a short-term permanent or temporary resident with no family connections).

The business/residence photographs aren't really going to help. In the thread below Mr. shtylman is soliciting for the loans in the form of "rebates for liquidity provider". This is an activity that is regulated in the USA. The loans aren't paid interest in the TVM sense but are paid by a negative trading commission.

https://bitcointalk.org/index.php?topic=93632.0

I would recommend that people who are tempted to became the "liquidity provider" do the same due dilligence as those who became the liquidity providers for Bitcoinica. The regulations in the USA provide for the collateral security and rights of offset that are available to the "liquidity providers".

At the request of Gavin Andresen and shtylman couple of messages were deleted from the thread in "Development and Technical Discussion":

https://bitcointalk.org/index.php?topic=93502.0

In one of the deleted messages shtylman (the operator of BitFloor) had inadvertently disclosed that he isn't an US resident and doesn't reside on Manhattan where the exchange offices are allegedly located. I wish I saved those messages before posting, but I'm working from a borrowed laptop.

Anyway, be safe or be sorry. The choice is yours.

I know that you are trolling right now by pretending to be naive about how the bank works. I guess the real or feigned naivette about accounting is par for the Bitcoin course.


In a bank if you deposit X coins you can withdraw at most X.

Thank you very much for your work and your comment.

I actually don't have an ARM machine to play. I played a bit with a pre-release simulator for a device that incorporates an ARM core. And by "a bit" I mean "floating point only". Because of the pre-release status:

1) instruction timing could be inacurate
2) it could simulate a future version of the ARM core

Thanks again.

The ARM core on Kindle Fire has 128-bit registers in addition to the usual 32-bit registers. This could give a 2-4 times speedup, depending on the exact details of the core used.

There are many ways to use them:

http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dht0004a/CHDGDHIC.html
http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dht0002a/ch01s04s02.html

You could probably take a look and see how you can do on ARM things comparable to what pooler did on Intel.

The original code by pooler was an awesome example of using Intel SSE (and/or AVX) to achieve great speedups (about 4 times?) with the help of SIMD (Single Instruction Multiple Data).

Did you attempted to use SIMD on ARM (where it is called NEON)?

With NEON SIMD or without?

That sensitivity to the cosmic radiation that you keep reading about FPGA is about SEU (Single Event Upsets). Those are cured by the power cycle.

It is extremely unlikely that SEU would damage an FPGA. It would be something like SEU that causes input pin to reconfigure itself as output pin and then fry in the confrontation with the external driver for that pin.

Your FPGAs are much more likely to die from electromigration due to high temperatures than from aftereffects of a SEU.

http://www.altera.com/literature/wp/wp-01012.pdf

Just add to the requirements that in addition to decimal the numbers should be printed in tonal. Then Luke-Jr will do all your work for free and will contribute to the bounty.

I was trying to give you a clue: the oldest and shrewdest accountants couldn't figure out how the account feature operates. I hereby refund all the money you've paid to get this clue from me. I'm sorry you wasn't satisfied. I got an impression that you are trying to account for the transaction fees in bitcoind.

Please don't waste time on the "account" feature of the default wallet code. It is kind of a joke. If you need to do an accounting use the BerkeleyDB callbacks functions to record the changes to the wallet in your own separate database.

Maybe profits maybe losses. Now that the previosly secret algorithm is in the open traders could tune their strategies off-line with no capital layout. It isn't immediately obvious that there is no algorithm that could push the resurrected Bitcoinica into red.

I think that everyone here should first try to add margin and shorting priviledges to your regular stockbrokerage account. The forms you'll have to submit have a very detailed explanations for the collateral requirements and how that affects your allowable leverage. There also will be the explanation of charges you'll have to pay for the capital you've borrowed to execute your margin or short trade.

In an honest trading establishment even 1:1 leverage requires credit check for shorting. If the lever is more than 1:1 then by definition the customer didn't put enough capital up front.

I understand that you are French and the bucket shop moniker is very much rooted in the American tradition.

But the line of reasoning is really simple. You don't really have to disassembly any perpetuum mobile to say that it can't work.

1) Long trade has a range from unlimited gain and 100% loss.
2) Short trafe has a range from 100% gain to unlimited loss.
3) To honestly allow shorting you have to do a credit check on the customers.
4) Bitcoinica wasn't doing credit checks and didn't attempt to collect on loses.
5) From the above Bitcoinica was a gambling establishment.

Call it "bucket shop", "bunga-bunga shop", "spread betting", "contract for difference" or whatever else the gambling regulations allow throughout the world. The logical outcome is really simple.

I don't know the details either. From what little I understand his modified algorithm would sandbag the spreads in such a way that the loss was always on customer's side not on the house's side. The amount of sandbagging was somehow keyed with volatility.

I distinctly remember somebody somewhere posting a Python code to whipsaw bitcents from the original algorithm and then Zhoutong came up with a fix for that.

Ah, OK then. I was worried that you are going to waste your skill and time on doing the security audit on the cadaver.

Zhoutong's key invention was the secret semi-random pricing algorithm. I recall that somebody reverse-engineered his original pricing algorithm and posted a Python script to reliably scrape small profits (maybe that person was "macbookair"?). Then he added some randomness and it worked like catnip on all the gamblers here.

I would let other people do the necromancy and create Frankencoinica, Litecoinica, Solidcoinica and whatever else.

Actually it will probably be Биткоиница.

I'm not "Rails coder" and most of the people here aren't either. But we are all curious and capable of coding or at least reading code. I would suggest that your target audience shouldn't be a "Rails coder", but any curious hacker not afraid to code.

Since you've mentioned Mt.Gox API key I have another question: how difficult is to stub out the portion that queries Mt.Gox and instead plays back a stored ticker tape in the csv or any other spreadsheet-compatible format.

Many people are interested what the secret pricing algorithm did to the bid/ask spreads on Bitcoinica. This could probably be of paramount importance if any litigation comes to fuition.

And thank you for the Rubymine reference.

I would suggest that everyone runs their own clone localy.

Could you post what Mac IDE you were using in your original post as well as any other steps required to make it run on a freshly out-of-the-box Mac?

I think that way many more people would join you in reverse engineering.

From your post I gather that you have never worked, consulted or even repeatedly visited any large publicly-traded company. Neither you've served in armed forces of any country.

They are all completely nuts, exactly like that. Top-level security and armed guards at the front door, but an elephant door to the warehouse in the back secured with a piece of plastic.

http://en.wikipedia.org/wiki/Mathias_Rust
http://en.wikipedia.org/wiki/Buffalo_Soldiers_(film)