Finish 0.3.0: prove Kraken scope, drop the futures claim, close three… - #21
Merged
Merged
Conversation
… netting and terminal bugs Kraken publishes GetApiKeyInfo, gated on no permission of its own, so trade access is proven rather than reported as unknown and a key that can place orders is refused at connect time. Four surfaces said the opposite. /binance advertised USD-M futures that verifyScope makes unreachable — the connector's own comment said so, and README said the opposite of the page. Three defects found by running the code rather than reading it: - assetOn's bridge guard sat behind `name === scoped`, so it never ran for ten bridged tickers. A contract calling itself GNO on Linea took the bare ticker, netting into the real holding and drawing its price. - A Hyperliquid builder dex could take a chain's name, putting `optimism:USDT` on the book — the same shape a bridged token gets. - whenLeaving registered a handler per caller, each re-raising after its own cleanup. Re-raising ends the process, so only the first mode registered was ever handed back. Also: non-JSON venue bodies no longer read as a bug in tula, a corrupt credentials.json names the way out instead of being emptied by the read path, a refused CoinGecko id is asked again rather than cached for the TTL, and `npm update -g` cannot cross a 0.x minor so the instruction is `npm install`. Venue facts re-checked against each venue's own docs: Aave removed stable-rate debt in v3.2 and the Safety Module is now Umbrella; Hyperliquid publishes the 95% trigger for portfolio margin only; Coinbase's perps are INTX. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
… netting and terminal bugs
Kraken publishes GetApiKeyInfo, gated on no permission of its own, so trade access is proven rather than reported as unknown and a key that can place orders is refused at connect time. Four surfaces said the opposite.
/binance advertised USD-M futures that verifyScope makes unreachable — the connector's own comment said so, and README said the opposite of the page.
Three defects found by running the code rather than reading it:
name === scoped, so it never ran for ten bridged tickers. A contract calling itself GNO on Linea took the bare ticker, netting into the real holding and drawing its price.optimism:USDTon the book — the same shape a bridged token gets.Also: non-JSON venue bodies no longer read as a bug in tula, a corrupt credentials.json names the way out instead of being emptied by the read path, a refused CoinGecko id is asked again rather than cached for the TTL, and
npm update -gcannot cross a 0.x minor so the instruction isnpm install.Venue facts re-checked against each venue's own docs: Aave removed stable-rate debt in v3.2 and the Safety Module is now Umbrella; Hyperliquid publishes the 95% trigger for portfolio margin only; Coinbase's perps are INTX.