Algorithmic trader & OSS developer. 12+ years in trading systems & exchange APIs. Building VESTROS.
Joined September 2026
- Tweets383
- Following60
- Followers49
- Likes307
Tiago retweeted
New release: @siebly/hyperliquid-api v1.0.3 for Node.js and TypeScript. Adds perpetual trailing stop orders for @HyperliquidX.
github.com/sieblyio/hyperliq…
Tiago retweeted
With just under 2 months left in 2026, our crypto API JavaScript SDKs have reached 4.87 million lifetime downloads (4,866,802 to be exact)!
Incredible to see the impact on our community building with them. Time to update that number on siebly.io 😅
Tiago retweeted
With the recent wave of vulnerability disclosures, it’s a good time to take a closer look at your own code.
Turn your coding agent into a team of security auditors with the open-source skill that seeded Cloudflare’s vulnerability discovery harness.
The 6 phase approach:
1. Map the codebase
2. Hunt for vulnerabilities
3. Challenge each candidate
4. Record the findings
5. Verify the findings
6. Report what’s confirmed, rejected, or still needs validation
Start your hunt here:
github.com/cloudflare/securi…
Tiago retweeted
If you're going to read only one article today, this is it. Attacks are only getting more sophisticated. Read through the chain of incidents, learn from them, stay safe out there.
Tiago retweeted
New release: @siebly/hyperliquid-api v1.0.0 for Node.js and TypeScript. One RestClient for the @HyperliquidX REST APIs, a promise-driven WebsocketAPIClient, typed requests and responses, and WebSockets that reconnect and resubscribe automatically.
github.com/sieblyio/hyperliq…
Tiago retweeted
Introducing our very own JavaScript & Node.js SDK for Hyperliquid’s REST APIs and WebSockets, with TypeScript support and the same familiar architecture as our other Siebly SDKs!
Check it out on GitHub: github.com/sieblyio/hyperliq…
We’ve included convenient wrapper methods for common workflows: market orders, limit orders, closing positions, checking balances, and more. There’s also a WebSocket API client for sending orders and other commands using the same methods as the REST client.
To get started, check out our tutorial with examples of the key workflows: siebly.io/sdk/hyperliquid/ja…
Building a trading bot, dashboard, or another Hyperliquid integration? Give it a try and let us know how you get on. Feature requests, feedback, and issues are all welcome. We’d love to see what you build.
Enjoy!
Tiago retweeted
Cloudflare has deployed default web application firewall (WAF) protections for newly disclosed PHP vulnerabilities before public disclosure. The rules use request and response signals to stop exploit attempts and prevent exposed data from reaching attackers. cfl.re/488w8dc
Tiago retweeted
🚨 THE INTERNET BROKE TODAY 🚨
Oct 21, 2026 will go down in history
1. eMudhra : Private key was literally "4". 8 keys forged ANY website for 17 months. 60M+ certs at risk.
2. SBI CONFIRMED. 3,897 customers' mobile, DOB, address + loan data found on dark web.
3. Rajasthan Police 🇮🇳ALLEGED hack. Group claims 70,000 identity records + 59,460 numbers for sale. Unverified.
4. php2shell [9.2] Unauth RCE in PHP. 70% of the web. WordPress, Drupal, Laravel. CISA: Patch or GO OFFLINE.
5. GitLab [10.0/10] PERFECT SCORE. Unauth RCE, no login needed.
6. Node.js [CVE-2026-111497] Brotli decoder RCE + TLS bypass. 10 CVEs patched today. Also blocked eMudhra.
7. Railway BREACHED TODAY. Env variables decrypted. Your API keys & DB passwords exposed. Rotate all.
8. OpenCode BREACHED. OpenAI, Anthropic, Google API keys exposed for Console users. Distillation attack. Bills run up in $$$$.
9. LiteLLM PyPI v1.107.0 was MALWARE today morning. Steals credentials + backdoor.
10. Plex2Shell ACTIVELY EXPLOITED. Hackers installing cryptominers LIVE. CISA KEV, deadline Oct 23.
AI found the bugs. AI is exploiting them. Humans can't patch fast enough.
Patch. Rotate. Revoke. Update.
RT to save someone's server ♻️
#CyberSecurity #DataBreach #India #php2shell
Tiago retweeted
Whether you're into algorithmic trading, from low to high frequency trading, building a platform, or just diving into the crypto dev world, accelerate your integration with our modern Node.js & TypeScript SDKs for the leading cryptocurrency exchanges.
siebly.io
Find all SDKs on GitHub: github.com/sieblyio
- Bybit
- Binance
- OKX
- Bitget
- Gate
- Kraken
- Coinbase
- Kucoin
- HTX
Tiago retweeted
The NCSC is encouraging UK organisations to prepare for immediate updating of systems using PHP. Where immediate remediation is not feasible, organisations should consider taking the system offline until it can be fully mitigated.
For more⬇️
ncsc.gov.uk/news/critical-se…
Tiago retweeted
Same TypeScript-first patterns across Binance, Bybit, OKX, Gate, Bitget, KuCoin, Coinbase, Kraken, HTX, Hyperliquid.
siebly.io/sdk
siebly.io/examples
github.com/sieblyio
Tiago retweeted
If you’re using Cursor / Claude Code / Codex against exchange APIs, start them on the map instead of random GitHub READMEs:
siebly.io/ai
siebly.io/llms.txt
Typed REST + WebSocket clients for 10 venues, plus examples and agent skills.
Tiago retweeted
The Siebly SDK includes Javascript examples for Binance WebSocket streams, with a dedicated Demo section for exploring different WebSocket workflows.
It’s a useful starting point when you know you need Binance WebSockets but haven’t decided which specific example or stream to use yet. You can browse the available Node.js examples and choose the one that best fits your setup.
The Javascript SDK examples and docs are available on Siebly.
Tiago retweeted
You wanted a KuCoin price feed. Somehow you're writing code to fetch connection tokens before you can even open a WebSocket.
KuCoin's Classic feeds need that extra setup. With kucoin-api, our JavaScript/TypeScript SDK handles it when you subscribe, along with heartbeats, reconnects and resubscriptions.
A lot of the value of a mature crypto exchange SDK is the code you never had to write. Or pay your coding agent to debug.
KuCoin REST API + WebSocket tutorial:
siebly.io/sdk/kucoin/javascr…
Tiago retweeted
Your trading bot can get an HTTP 200 and still have its order rejected.
Bybit reports API-level errors in the response body's retCode. A successful HTTP request doesn't necessarily mean the crypto exchange accepted what you asked it to do.
Our bybit-api SDK has a useful option for this: set throwExceptions: true on RestClientV5.
Non-zero retCode responses then throw, so your normal try/catch can handle them instead of your code happily carrying on.
One less API quirk for you or your coding agent to trip over.
Bybit REST API in JavaScript/TypeScript:
siebly.io/sdk/bybit/javascri…
Tiago retweeted
Working with Coinbase App private endpoints in Node.js is a lot easier when you have a clear example to start from. Siebly’s Javascript SDK example shows how the authenticated Coinbase App REST flow is put together in a simple script, with the docs there to help you along the way.
You can find the example here: siebly.io/examples/Coinbase/…
Tiago retweeted
Your trading bot crashing doesn't cancel the orders it left on a crypto exchange.
Kraken has a "dead man's switch" for that. Your bot periodically refreshes a timer. If those refreshes stop, Kraken cancels the open orders when the timer expires.
The useful bit: that timer lives at Kraken, not inside the process that just crashed.
Our Kraken JavaScript/TypeScript SDK exposes this as cancelAllOrdersAfter. Your app chooses the timeout and schedules the refreshes, without another hand-written API integration.
It cancels orders, not positions. On Spot, the scope is all open orders on the account, so don't assume it only affects one bot.
siebly.io/sdk/kraken/javascr…
Tiago retweeted
Your real balance is an expensive debugging tool.
Our OKX JavaScript/TypeScript SDK supports demo trading across REST, WebSocket streams and WebSocket API commands.
Use separate demo API keys and enable demo mode. The SDK handles the required headers and connection endpoints.
Now test whether your bot places, tracks and cancels orders correctly, whether you wrote it yourself or your coding agent did.
Demo fills won't prove your strategy is profitable. But finding integration bugs without involving your actual funds seems sensible.
Working examples in the OKX crypto exchange API tutorial:
siebly.io/sdk/okx/javascript…