This article assumes that you understand the basics of trading with cryptocurrency exchanges. As the user does multiple trades, buying and selling, the exchange will store records. In general, these records are provided for download and are useful for accounting or tax purposes.
The format for these records is not standardized. Therefore, it’s up to the exchange to decide about the format and its structure. Throughout the following sections, you will follow the steps to understand how one particular exchange has organized its trade history using a CSV file.
Our goal is to understand the file structure, and then we…
What matters is that I was using Markdown already. Markdown is the well-known lightweight markup language designed to be easily converted to HTML. Developers know that, but if you don’t know, now you know. …
This article is based in a prior article entitled Using Binance API to get the user’s trades data. Here, however, our goal will be to fetch the data for the user’s margin account. It turns out that Binance uses different API endpoints depending on the kind of account (spot account, margin account for example).
The following explanation is based in the following sample:
Let’s go through the code which is very simple and straightforward:
/* Notice that node-binance-api was replaced
with a local version *
*///const Binance = require('node-binance-api');
In this project, we are interested in the user’s records related to the user’s previous trades. Why would one need to fetch the user’s record of trades? To help with accounting or analysis, for example. Keep in mind that this is not a complete example of what one would want to do with the data — it’s the starting point.
Many developers are struggling with problems when Mongo Express tries to connect with Mongo database using Docker-compose.
The general problem relates to the fact that Mongo Express needs to wait for Mongo database to be up. It turns out that Mongo Express developers provided a solution to this problem. Within Mongo Express Docker image comes a shell script (docker-entrypoint.sh) that tries to connect with Mongo database multiple times.
Consider the following situation with two containers. One, mongo.service, which is to be the datbase. And another, the client, named mongo-express.service.
I will provide a walk through of a situation where a market trade operation, initiated by an user B (a buyer), resulted in a limit order from an user A (a seller) to be executed.
At moment 1, user A places a limit-sell order. It’s a commitment to sell an amount of bitcoin at a given price. This is an order that won’t be automatically executed. It’s a price P which user A asks for a volume V of bitcoins. The following structure lists the main attributes of this limit-sell order. I kept a few numbers listed to better illustrate:
With a container-based infrastructure (Docker in this case) you will likely have separated containers — one for the database, another for your application, and perhaps another being a database administration container.
Your application needs to know when the database is ready so that you can connect. In a prototype phase, you may think about starting up the database service before your application service. This idea may work if you can manually start each service — if you are manually waiting for it.
But as you move to the docker-compose (or another orchestration system), you will need to find another way…
DISCLAIMER: THIS IS A DRAFT ESSAY INITIALLY PRODUCED BY MARCIO S GALLI. THIS WORK IS BASED WITHIN THE BLITZSCALING/05 TALK WITH JOHN LILLY (GREYLOCK) AND ALLEN BLUE (LINKED IN). THE GOAL OF THIS ARTICLE IS TO COLLABORATION. YOU CAN OPT IN TO HELP IN ANYWAY YOU CAN, BECOME A COAUTHOR OR SIMPLY ASK ME TO WORK ON IT BETTER. [Related https://medium.com/@taboca/challenging-the-status-quo-of-your-product-market-fit-eeff077318f0]
ON AUDIENCE: This is aimed at entrepreneurs and startup teams that are interested in the early stage of growth for their startups. This may also apply to startups working with customers (B2C) that already have customers and believe that…
In this example, when you follow the link it is supposed to jump to 31min and 59s when Reid explains his “theory of small gifts”:
By now our online space is full of social networks that serves for different purposes. Facebook is for social identity interactions, like photo sharing. Twitter is for what are you doing now; Linkedin for the job shifting potential and it goes on.
I will naively suggest that most of these are for general interaction around the people that are not so close to you. Thus, they are mostly intended to manage acquaintances and not friends interaction. And that may be the very reason that they grew so much and became so influential to our lives. Exactly, they give motivation for…