future183

today i've been working on preparing the native iOS and Android apps for submission to the app stores hopefully i'll be able to give you early access through TestFlight or Android beta testing pretty soon, for anyone who wants to try them there are still some things i need to fix and adjust to meet the app store requirements, but i'm actively working on it also shipped the new desktop design today if you prefer the old one, i've added a button to switch back to the classic version. i'll keep improving the new design too work hasn't stopped for a single day i basically wake up, build, grab something to eat, sleep and get back to building been doing this for 10 days straight now the pace is actually crazy when you compare what Motion looked like in v1 to what we have now in v6 and i'm definitely not slowing down

gm everyone $MOTION is now listed on CoinGecko coingecko.com/en/coins/motio… back to building now 🧑‍🍳

fair point. i completely agree that security matters more than speed or any other feature, especially when people are trusting a platform with serious money. but i want to explain how motion is actually built, because the approach is quite different from most trading terminals. motion is non-custodial by design. your trading wallets’ keys are generated and stored locally in your browser, inside an isolated vault on a separate origin. the server only stores an encrypted backup that it cannot decrypt on its own. every trade is signed inside that vault, in your browser — never on our server. on robinhood, bnb and near your browser sends the signed transaction straight to the blockchain nodes; our server isn’t in that path at all. on solana a copy of the already-signed transaction also goes through our relay to a fast rpc for speed, but a signed transaction can’t be changed — the server can only pass it on. and this is exactly why i can’t offer features like copy trading or limit orders that execute while your browser is closed. it’s not a technical limitation i haven’t figured out yet. it’s a deliberate decision. i don’t want motion to have the ability to access your keys or sign transactions without you. the vault code is hash-pinned, with public hashes for every release. there’s already a page where you can verify it yourself, right in your browser, instead of taking my word for it: motion.gift/security-center. i’m expanding it into a full write-up of the architecture. of course, there’s a downside to this approach too. if you lose your browser storage and don’t have a usable backup, i can’t recover your wallets either. that’s why exporting your backup is important. now about audits. i understand why people want a reputable independent audit, and i agree it’s necessary. but there’s a real dilemma here. a proper top-tier audit costs tens of thousands of dollars. i could probably get a much cheaper audit from a less established firm, but would that actually make anyone feel safer? i doubt it. so instead of paying for a badge just to say we’re audited, i’m focusing on what i can actually do right now: continuous internal security reviews, testing attack scenarios, adversarial testing, and making as much of the architecture independently verifiable as possible. none of that replaces an independent audit, and i’m not going to pretend it does. i also want to introduce a public bug bounty and eventually get a proper top-tier audit when the budget allows. i know established terminals have years of history behind them, and motion doesn’t have that yet. i can’t create that track record overnight. but what i can do is build everything as transparently as possible, explain the tradeoffs, and give people the tools to verify things themselves. that’s the approach i’m taking.