Downloading...
Download

Integration

Create No Code Auto Trading Bot with Tradingview and OKXHello Everyone, In this tutorial, we learn about how to create simple auto trading bot using tradingview alerts and OKX exchange built in integration mechanism. Few exchanges have come up with this kind of direct integration from tradingview alerts to exchanges and as part of this tutorial, we are exploring the interface provided by OKX. In this session, we have discussed 🎲 Preparation Steps Preparing tradingview account Webhooks are only available for essential plans and plus. Enable 2FA in your tradingview account. Preparing your OKX account Create OKX account, and we prefer you do the initial tests under demo account before moving to active trading account. Bots created in demo account will not appear in the active trading account. Hence, when switching to active account, you need to create all the setup again. 🎲 OKX Tradingview Interface Features What is supported Auto trading based on strategy signal Custom signals - Enter Long, Exit Long, Enter Short, Exit Short What is not supported: Stop/Limit orders Bracket orders/ Complex execution templates 🎲 Weighing Pros and Cons of Using Direct Interface rather than Third party integration tools Pros Latency is minimal as per our observation Easy Integration with Tradingview and Pinescript Strategy Framework and no coding required You save cost on third parties and also avoid one hop. More secure as your data is shared between less number of parties. Cons No native support for Stop/Limit orders
Education
by Trendoscope
15
Re-Integration By Parts (near-term FB)This type of scenario/projection requires you to use your imagination a bit - align that with some solid math and some extrapolation and what we have is a very possible near-term scenario: - Imagine FB never gapped last earnings, what would the price action look like. Is it possible it was forming the final part of its distribution phase that would have decreased in volatility s.t. it took the shape of a triangle pattern, and instead the earnings report accelerated the mark down? What we can do is extrapolate by cloning the current trendlines across the highs and lows post-gap down (blue lines) and populating where the range left off pre-gap. To properly complete the distribution phase might require a retest of the bottom range, and rejection before really tanking it/discounting it (by that I mean it will likely end up sub 170 (shaded red rectangle area) mid-term -- that would be a proper discounting before the next long-term bullish impulse wave can begin. - Now, introduce some conventional techniques to see if there is a plausible path to test for rejection... recent (minor) bullish wolfe-wave 1-4 EPA @ ETA says yes, indeed, and by May 21st - nearly exactly when that pre-gap support line intersects the 1-4 EPA @ ETA!! - Finally, is there a setup that would make such a near-term run actually bearish s.t. it would get rejected and complete markdown going into the summer? Indeed, Bearish Deep Crab Harmonic. In summary: ~ Near-Term long to 258 ~ Mid-term short back to 170ish IF rejected after near-term pop ~ Long-term Bullish but will have to re-analyze and update along the way. There are more details to how/why I drew the path projection the way that I did, it is not random - pop pre-earning (i.e. before next week), small gap down post earnings next week, explosive bounce from that smaller gap to fill said gap and that momentum will take it to near-term target. If you're interested in how I determined this and you are familiar with stochastic analysis/Ito Calculus then we should talk. Otherwise just trust my word the math is gucci. This would be kinda crazy if it all plays out lmao, but worth bringing up as a perspective on "meta" or whatever; not financial advice or whatnot. Bless your souls, The Alpinist
FLong
by JerryManders
5
How to capture chart snapshot in tradingview-telegram alert botHello traders, In the last video we learnt How to create simple web-hook to send alerts to telegram . In this tutorial, we will try to build a bit more on it and to also include chart snapshots along with plain alert messages. Webhook code is updated in the replit repository here: replit.com Once, setup, run the repl and capture base URL ⬜ Webhook API Webhook post request URL format below: https:///webhook?jsonRequest=&tblfmt;=&chart;=&loginRequired;= jsonRequest - true/false. Set it to true only if you are sending alerts in the form of json. If set to true and the alert message is not in json format, it will throw error tblfmt - Values taken from python library tabulate . Defines how to display the json message in tabular format. Applicable only if jsonRequest is true chart - Chart URL from tradingview for which snapshot need to be captured loginRequired - true/false. Use this only if you are using a private non shared chart for snapshot or if your chart contains invite only scripts which needs to be shown in the chart snapshot. ⬜ Capturing Chart URL Note: Make sure you create different chart for different instruments which you are trying to get alert. Also make sure your chart is saved and all the indicators are in palce. ⬜ Testing on postman ⬜ Creating the alert
Education
by Trendoscope
68
Ledger Hardware Wallet - Monero integration : some news #4 Been tracking progress on the ledger integration. Think it will bring in allot of investors who are waiting for a hardware wallet to dip their toe into Monero www.reddit.com "Hi all Just performed a new push, here are the news: Status The wallet private key is now inited with the device seed. It do not use the 24 words mnemonic of Monero but the seed device from path: /0x8000002C/0x80000080/0x80000000/0x00000000/0x00000000 aka /44'/128'/account'/0/0 To make short the scheme is the following, assuming S is the seed from given path: a = keccak(S) a &= 0xF8; a = (a & 0x7F) | 0x40; b = keccak(a) b &= 0xF8; b = (b & 0x7F) | 0x40; The --generate-from-device seems to be fully functional. It retrieves the public keys (A,B) from the device and restore the wallet from them. If it exists any funds on the block chain associated with, they are retrieved. Note that scanning the whole blockchain is long, very long as all block as to be decode by the device. Transfer are now required to be validated on-screen: destinations amounts and fees have to be validated by user. Ok, I need to finish the check on the client side to abort tx is user reject it. Don't blame me for not doing it in this push :) Next So what next? Reference doc has to be updated! On device side, I have to add the hash-state machine to ensure the integrity of the whole process and avoid data modification between destination/amount validation and final signature. On client side all error code returned by device has to be checked and TX has to be aborted if needed. And then? Prepare a Push Request on 0.11.0 branch :). This will start the code review by the core team and I expect by others. During that, I will start a merge on master branch and work on the sub-address feature from kenshi84. I will also provide linux cli binary for those who want to test various scenario on testnet."
Long
by Emperor_Penguin