two kraken entries, one checklist — what am i missing?

Just finished reading the Kraken Futures setup guide here and I want to think out loud a bit, because the part that stuck with me isn't the connection steps, it's the failure modes. The guide is clear that spot and futures are two entirely separate platforms, separate hosts, separate keys, separate signing. Fine. But that means most of us will end up with two entries sitting next to each other in the connections list with almost the same name. And I've watched enough people fat-finger things to know that "two nearly identical labels" is a risk in itself, not just a cosmetic annoyance. So my questions, in checklist order, because that's how my brain works: 1. Naming. Does anyone rename their connections to something unmissable? I'm inclined to make the futures one shout at me, since a leveraged perp fill is a very different animal to a spot fill of the same size. 2. Key hygiene. The guide says a spot key won't work on futures and vice versa, which is honestly a nice safety property — the wrong key just fails rather than doing something clever. But has anyone confirmed what the failure actually looks like on the app side? A clear rejection, or a silent nothing? Silent nothing is the one that scares me, because you sit there thinking your order is working. 3. Symbols. The mapping table shows you can type the friendly ticker and it gets translated to the PF_ product code. My worry is the opposite direction: if I have alerts and notes saved against the friendly name, do I ever end up looking at a spot chart while an order is queued against the perp? I'd rather train myself to type the PF_ code every time so there's no ambiguity about what instrument I'm actually on. 4. Permissions. The guide notes market data needs no key at all, only orders do. That suggests a sensible staging: connect data first, watch it for a while, record, and only add a key once you're bored of watching. Anyone actually do it in that order, or does everyone just wire up the key on day one? Not trying to be the person who turns a ten-minute setup into a two-week audit. But perps are the place where a routing mistake costs you the most, so I'd rather ask the boring questions before rather than after. What did you all trip over?
R
RiskFirstRita
16 posts · 0 followers
+ Follow

Related reading

4 replies

G
GapHunterMike· Aug 2026 ago
renamed mine ages ago. spot is lowercase, futures is in caps. sounds dumb, works. and yes type the PF_ code. friendly tickers are how you end up long the wrong thing.
L
LurkerLee· Aug 2026 ago
On point 4 — if data works without a key, can you paper/record the perp for a week before any key exists at all?
H
HalfKelly· Aug 2026 ago
Rita, your staging idea is the one I'd underline. The thing that changes when you move from spot to perps isn't the symbol, it's that your notional stops being bounded by your cash. A sizing sheet built for spot will quietly hand you a much larger position on the futures side for the same "one unit" input, and that mismatch is invisible until it isn't. So before the key goes anywhere near the account, I'd rewrite the sizing rule in terms of contract exposure rather than spend, and check what a stop actually costs you in the units the futures platform reports. The connection stuff is a half hour. The sizing translation took me considerably longer than I expected.
M
MomoQueen· Aug 2026 ago
YES to renaming!! I have mine flagged so obviously I can't miss it, learned that lesson the annoying way once. Also the two-keys-can't-cross-over thing is genuinely reassuring, one less way to blow yourself up!
Sign in to reply →
← All brokers & apis