Viktor Stanchev (@Vikstrous) header
Viktor Stanchev (@Vikstrous) profile picture

Founding Engineer @Anchorage

New York City
Joined June 2008
Photo by Viktor Stanchev (@Vikstrous)Photo by Viktor Stanchev (@Vikstrous)Photo by Viktor Stanchev (@Vikstrous)Photo by Viktor Stanchev (@Vikstrous)Photo by Viktor Stanchev (@Vikstrous)Photo by Viktor Stanchev (@Vikstrous)Photo by Viktor Stanchev (@Vikstrous)
Do you have agents researching trades? News? Do you have custom agent harnesses? Do you need access to more than one AI model family? Get in touch with us to try our new product and get $100 of credits.
Get a $100 inference credit for your research agents, funded by @BlockRunAI. Point your agents at trading research, from governance proposals to DeFi liquidity data. With Agentic Banking from Anchorage Digital Bank N.A., your agents don't hold the funds they spend.
30
When we started building support for AWS Nitro, I was surprised that the go library every tutorial recommended hadn't had any updates for 4 years at the time and wasn't going to meet the bar we set for ourselves at @Anchorage. When we had something that worked, we open sourced it and had AWS double, triple check our work too. It's more important than ever to have strong verifiable cryptographic proof of running what you expect to be running. Having gone deep in every TEE stack out there, I have to commend @awscloud for building the best experience with Nitro for developers to get started with because you get the full PCRs and attestation right off it. And @turnkeyhq's QuorumOS builds a very strong layer for apps on top of the foundation. We deliberately kept the dependencies limited to stdlib and cbor, and urfave for a nice CLI. Consequently, it trivially compiles to wasm for verifying nitro attestations outside of a CLI in even more constrained environments too.
1
2
1
16
711
A while back, the engineering team at @Anchorage was digging into Solana transaction parsing for institutional flows. The existing parsers in Rust brought a lot of dependencies for very little gain. Around the same time, Turnkey had written a lighter-weight parser — authored, of all people, by Omkar, who worked with us at Anchorage previously. Small world. Lean, understandable code. One problem: it wasn't usable as a library yet for what eventually became visualsign-parser. So I sent in an open-source fix to make it one, and Omkar and I started trading notes again on what else needed sharpening. Those conversations are what eventually turned into the Turnkey collaboration where we co-designed aspects of Turnkey Verifiable Cloud to deploy visualsign-parser. We have collaborated on improving Anchor IDL parsing functionality as well as strengthening the testing coverage in the parsers with ongoing work on Fuzzing and Property testing. While we were geeking out on the nuances of parsers, someone with better business sense on our side floated, "what if this is the path to real DeFi support on Solana for institutions?" From there it was: building a proprietary browser extension that lets institutions interact with the full Solana DeFi ecosystem from a Porto account. Swaps, program upgrades, yield, governance — all signed against infra that meets our institutional grade standard. Institutions have a safe, secure way to access Solana DeFi. @solana & @turnkey: Thanks for the great collab. Learn more about Solana DeFi at Anchorage Digital here: anchorage.com/insights/unloc…
3
5
2
17
1,496
I'm working on giving AI agents access to payment systems. It's incredible how much is being built in this space right now. Reach out to us at agentic@anchorage.com if you have agents that need access to make crypto and fiat payments and to manage money.
3
1
1
9
375
Out of everything I've read about software architecture, the most important thing is to have a "domain layer". It doesn't matter who your preferred software architecture guru is. They'll all tell you that you need one of these. viktorstanchev.com/posts/gua…
4
102
This is why you should care about the UIs of transaction signing devices. Full talk at: youtube.com/watch?v=Mjd3kFm2…
What you see is (supposed to be) what you sign. But let’s be real: most users see “0x8e…4b” and cross their fingers. Viktor Stanchev (@Vikstrous), Founding Engineer at Anchorage Digital and I dove into this at Eth Taipei.
1
4
424
Viktor Stanchev retweeted
[1/16] The real world is large, and we want our AI models to operate on the scale of reality. Over the past two years, my colleagues and I have developed fVDB, a deep learning framework for large-scale, high performance spatial intelligence. We finally announced this work at SIGGRAPH and have released the framework in early access. Here’s a small tour of what fVDB is, and what we’ve used it to do.
5
57
8
255
34,228
This is the project I've been working on lately. I can talk about now that it's public :)
1/ Introducing Atlas, the crypto settlement network by @Anchorage Digital, built for institutions to maximize capital efficiency. Buy/sell-side firms use Atlas to help avoid counterparty, delivery, and bankruptcy risks.
3
86
Viktor Stanchev retweeted
Let's play Unpopular Opinions! 🎸 @vikstrous thinks burritos are great meanwhile lobster is "arguably not food" 🌯🔝🦞 🎥 Explainer ~> youtu.be/eqfKFdVRJAE Do you agree? Vote and reply with your hot take! #golang #unpopularopinion
55%I agree with Viktor
45%I disagree with Victor
11 votes • Final results
1
809
Are you using @temporalio and writing workflows in Go using their #golang SDK? I created a type-safe wrapper around the Temporal Go SDK called tstemporal. It helps you avoid many common mistakes when working with Temporal workflows. viktorstanchev.com/posts/tst…
3
73
Viktor Stanchev retweeted
📢📢📢 Check out XCube, a generative model for very-high resolution 3D shapes and scenes! Project Page: tinyurl.com/ykex2wur Project Video: youtu.be/GX0lzwy8nUI Props to @xuanchi13 for leading this project!!!! [1/N]
5
63
6
294
42,608