Hallo zusammen,

Ich suche eine Auflistung von allen Forks, AirDrops, Rewards über alle Crypto Coins der Vergangenheit. kennt jemand eine Webseite dazu ?

Also um zu verdeutlichen was ich meine:

ca. 25.07.2016 --> ETH 1:1 ETC
ca. 13.10.2016 --> NXT 1:1 ARDR
ca. 30.04.2017 --> ZCL 1:1 ZEC
ca. 01.08.2017 --> BTC 1:1 BCH (bzw. BCC)
...

Was auch noch interessant wäre: Welche Börse denn Split, Fork, etc mitgemacht hat... und zu welchem Zeitpunkt das war.

Yay okay. As you said, there are different ways of implenting stuff on the client side. Synchronous calls, sending a request and waiting for
the response. and so on. Sending the request and asynchronously waiting for the response. So far we do agree Just different styles
of implementation. Indeed all the exchange API's I know so far are implementing simple request/response pattern. But thats a different topic
and not the point where the discussion started.

@deisik brought up this BTer async thing And I do not plan to implement BTer so I don't care about the behaviour that much. have
some thoughts on my own, but that is just speculating how they implemented their API.

PS: lost 3hours I could spend in coding 

I've never have seen a 202 response code either.

And maybe I pushed the discussion to the wrong side: the client-side.
For me the more interesting part is the BTer server-side
and the behaviour @deisik described. Still thinking about what he said

PS: Despite all a nice discussion so far

To come back to the topic  

Yes, I tried several bots in the past and this made me the decisson the implement my own trading platform. I'm not talking
of a "bot" anymore.

Each bot I tried, had its issues and parts I wanted to improve: different strategies, faster execution, diving into new technologies etc.
Here's a list of bots I tried:
- C.A.T.  
- SpreadBot (a German project)
- leoArdo
- poloniexlendingbot
- currently having a close look how gunbot is performing
- and some github open source projects I forgot


 

hm.... might mixing things up of the transport layer, the protocol layer and how an exchange API is implemented.
For sure there is a connection established when I want to invoke the API. But the http requests and responses do not have
to be synchronous.

There are tons of simple examples of working with REST Api's in a asynchronous way, e.g.:

Future<Response> response1 = client.target("https://bittrex.com/api/v1.1/market/cancel")
                               .request()
                               .async().get(Response.class);

Future<Response> response2 = client.target("https://bter.com/api/1/private/cancelorder")
                               .request()
                               .async().get(Response.class);

// now you can do other stuff or sit and wait till you have both responses.

You are totally right and same in java. I'm doing my stuff in exactly the same way

I think there was a lot of misunderstanding in the last couple of posts from both sides

The same point I didn't get: How do you know, if bter is internally working async or sync. This is not visible to a client. And  I don't care how they work internaly, as long as they are
fast and reliable. You already said it... If bter accepts a request with a higher nonce before a lower nonce . something ist not working as it should in my opinion.

@deisik but it is an interesting way, to work with the bter private  API. thanks for the hint. besides that, nearly every exchange has some undocumented stuff hidden in their API.

hmmm.... you may be mixing things up. But I dunno want to start a new discussion.
People might have different definitions of sync, async, threads, callbacks ,etc.

The point is,  that some steps in order execution must be done in a sequence, and other steps could be
done asynchron and parallel. It's all about optimization. (order execution is a sub-optimal example)

Most API's do have a roundtrip of about 500ms to 1s or even more.  e.g. If you now want to check e.g. market summaries of 150 altcoins hat polo,
you can do this in a loop and your done in about max 150s. Or you can fire 150 requests in parallel with some kind of client side rate limiting to not
exceed 6 req/sec. (no im not doing it in that way just an example)  and subscribe to the results. The rate limiter is aware of backpreassure
so, between firing the request and the response might be a long time. you won't block any thread. but in the total you have all the results in a
much shorter time.

And your are totally right with "good programming practise makes you decide about what to use". agree to that.

To answer your question what my program is doing: Crunching and analyzing a shit load of data

the way I do it: Sending a request to the exchange and async subscribing to the response.
You might read about reactive programming... or event driven architecture, or or or or as you are in an java environment, keywords are:
vert.x, akka, RXJava just to name some frameworks...

The only thing "deisik" wanted to clarify, is that RESTful endpoints are not synchronous by definition, as you said in one of your posts. You are using
them in a synchronous way, and thats okay. no problem with that.

No, definitely not... I hate blocking threads and waiting 2 seconds for a response from the exchange ...
sure, I need the result of my request at some point, but not in a sync 

A RESTful endpoint can be either synchronous or asynchronous.
As the C.A.T. bot is implemented in Java, you might have a look into JAX-RS 2 specification.

The limitation to send more than one request at a time, is at most exchanges the "nonce".

Edit:
@Sampey: Here is one explaining async REST Services implemented in Java:
https://dzone.com/articles/jax-rs-20-asynchronous-server-and-client

But the whole discussion is a little bit cherry-picking into details....

Sowas manuell zu machen, loht nicht wirklich. Der Ertrag steht in keinem Verhältnis zum Aufwand. Wenn du dir nen Bot dafür programmierst, der das dann automatisiert macht,
könnte evtl was rum kommen. Vor paar Wochen war Stella Lumen ne zeitlang auf bis zu 5 % (pro Tag) und das sogar für nen längeren Zeitraum. Da hatte ich spontan BTC gegen
STR getauscht und diese verliehen. Der Kurs von STR ist dann zwar nach untern gesackt, aber hat sich inzwischen wieder erholt. Hatte auch zwischen durch dann meine Zinsgewinne
wieder veräussert.

Was man halt generell sagen kann, wenn die Interest Rate nach oben schiesst, passiert das ja nicht ohne Grund. Im Prinzip bedeutet es dass Leute "short" gehen, d.h. auf
fallende Kurse spekulieren...

Arbitrage ist durchaus möglich. Aber glaub nicht dass du da alleine bist. Das machen schon sehr sehr viele und das auch schon seit sehr langer Zeit.
siehe auch https://bitcointalk.org/index.php?topic=1746734.0 zu dem Thema.
Kann man auf beliebige andere Exchanges übertragen. Wenn alles so einfach wäre, dann würde es die low-hanging-fruits nicht mehr geben

so geschätzt würde ich mal sagen, dass auf bitcoin.de zwischen 5 und 10 Bots unterwegs sind, die alle Arbitrage machen.

hast auf deiner Liste den SpreadBot vergessen:

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

Und hier zum Forum:
https://forum.spreadbot.de/index.php/topic,302.0.html


Mit Bot's ist halt so ne Sache... Glaub da steckt man zu viel Hoffnung rein... Und was viele nicht bedenken:
so ein "fertiger" Bot kann auch durchaus Minus erwirtschaften kann.

Wenn du mit was simplem Starten möchtest, dann kann auch durch aus der PoloniexLendingBot was für dich sein.
Im Schnitt 0,02% am Tag momentan.

Und zum Thema Arbitrage gab es erst vor paar tagen einen Thread, in dem es @Serpens66 ganz gut erklärt hat.
https://bitcointalk.org/index.php?topic=1746734.0

und wenn du manuell noch nie getradet haben sollest. dann denke erstmal nicht mehr über Bot's nach. Die nehmen dir
das denken nicht ab, sondern unterstützen nur dein Trading.
Die Performance der Bots hängt enorm von der Konfiguration ab, und wenn man da nicht weiss was man macht, fährt
man schön sauber Verluste ein