Binance API return Error: Filter failure: LOT_SIZE

 The LOT_SIZE filter defines the quantity (aka "lots" in auction terms) rules for a symbol. There are 3 parts:

minQty defines the minimum quantity/icebergQty allowed.

maxQty defines the maximum quantity/icebergQty allowed.

stepSize defines the intervals that a quantity/icebergQty can be increased/decreased by.


In Binance, we use the API follow to get lot_size of symbol

GET /api/v3/exchangeInfo
(https://binance-docs.github.io/apidocs/spot/en/#exchange-information)

We can use the function below to make valid quantity:

const getValidQuantity = (floatNumber, lotSize) => {
const n = lotSize.split('.')[1]?.indexOf('1') + 1;
return toFixedWithoutRounding(floatNumber, n);
}

--

const toFixedWithoutRounding = (floatNumber, n) => {
const x = Math.pow(10, n);
return parseFloat(
(parseInt(floatNumber * x) / x).toFixed(n)
);
}

I hope this helpful for you!

Nhận xét

Đăng nhận xét

Bài đăng phổ biến từ blog này

TypeORM should using repository or query buider ?

TypeORM should using repository or query buider ? Both repository and query builder approaches can be used to query data in TypeORM, depending on the situation and your preference. The repository pattern in TypeORM provides a more intuitive and straightforward approach to interacting with the database. It allows you to define methods in the repository to perform CRUD (create, read, update, delete) operations on objects in the database. These methods can also be used to perform more complex queries, such as using JOIN or GROUP BY queries.  The repository pattern The repository pattern also allows you to focus on the object rather than the query. The query builder in TypeORM provides a more flexible approach to building database queries. It allows you to build complex queries by combining multiple statements and enables you to create more interactive queries with the database.  The query builder The query builder also allows you to have more control over creating queries and can optimize
Read more »

Type of children prop in React Typescript

Hình ảnh
Type of children prop in React Typescript In difference contexts, you can choose type of 'children' prop as following types: 1. Type JSX.Element: using only for single React Element  If 'children' is list React Element, we can define: children: JSX.Element | JSX.Element[]  export default ICustomPageContext; type Props = { title: string, children: JSX.Element, }; const Page = ({ title, children }: Props) => ( <div> <h1> { title } </h1> { children } </div> ); 2. Type ReactChild: using for single React Element, string, number If 'children' is list React Elements, list string, list number, we can define: children: ReactChild | ReactChild[]  type Props = { title: string; children?: | React.ReactChild | React.ReactChild[]; }; 3. Type ReactNode: using for multiple React Elements, strings, number. This is general type for 'children' If you cannot identify the specific type of 'children', you ju
Read more »

Why we should Avoid using UNSAFE componentWillMount, componentWillReceiveProps, componentWillUpdate

Hình ảnh
  Avoid using UNSAFE componentWillMount (UNSAFE_componentWillMount) Using componentWillMount for init state ? We can using `state initialization` or init state in constructor => we don't need using componentWillMount import React from " react "; class ExampleComponent extends React. Component { state = { currentColor: this . props . defaultColor , palette: " rgb " } ; } class ExampleComponent2 extends React. Component { constructor (props) { super (props); this . state = { currentColor: this . props . defaultColor , palette: " rgb " } ; } } Using componentWillMount for fetching external Data ? import React from " react "; class ExampleComponent extends React. Component { state = { externalData: null , } ; componentDidMount () { this . _asyncRequest = loadMyAsyncData (). then ( externalData => { this . _asyncRequest = null ; this . setState
Read more »