We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I'm not so sure how we can make the following logs much beautify, but here is what I'm proposing:
On New Announcement
Current:
New announcement detected: API3
New:
release time
releaseDate
timestamp
Bot <> Telegram Bot API
NEW: API3 Platform: KuCoin Release: Fri Jan 21 2022 06:28:04 Timestamp: Fri Jan 21 2022 06:28:13
starting buy placeorder with : announcementcoin='API3' | globals.pairing='USDT' | volume=33.0 | amount=6.623845845042151 x price='4.982' | side = buy | status='cancelled'
='%s'
total
amount
price
at
Bot <> Trading Platform
Coin: API3 Action: BUY Status: Cancelled Pair: USDT Volume: 33.0 Amount: 6.623845845042151 Price: 4.982 Total: {Amount x Price} At: Fri Jan 21 2022 06:28:10 Timestamp: Fri Jan 21 2022 06:28:13
sold API3 with -1.534 profit | -3.031% PNL
%
profit
sold price
Coin: API3 Action: SOLD Price: 4.877 Profit: 3.245 USDT (-1.534%) PNL: -3.031% At: Fri Jan 21 2022 06:28:10 Timestamp: Fri Jan 21 2022 06:33:24
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I'm not so sure how we can make the following logs much beautify, but here is what I'm proposing:
On New Announcement
Current:
New:
release time
: Binance or KuCoinreleaseDate
timestamp fieldtimestamp
: there is a time-window betweenBot <> Telegram Bot API
until message dropped to channelCurrent:
New:
='%s'
wrappingstotal
price:amount
timesprice
timestamp
: see aboveat
: there is a time-window betweenBot <> Trading Platform
. We should storetimestamp
before sending buy order to provider though APICurrent:
New:
%
toprofit
sold price
timestamp
: see aboveat
: see aboveThe text was updated successfully, but these errors were encountered: