Bridge Behind a Cross-Chain Liquid Staking Protocol
Vested* (real name is NDA) is a decentralized crypto liquid staking project.
Users stake assets into the protocol and receive rewards for their tokens’ participation in the PoS network’s block validation. The protocol delegates these stakes across a distributed set of validators, algorithmically creating a pool of those that are reliable, always online, and provide the most attractive yield for the protocol’s users. As proof that the tokens are staked, users receive liquid staking tokens (LSTs), which they can still trade or use in DeFi while the underlying funds remain staked.
Alexander, the co-founder, wears three hats at once: developer, product lead, and infra coordinator.
He’s spent years around PoS networks, validators, and DeFi. Today he runs a distributed team of twelve and a long tail of partner investors and validators across several blockchain networks.
Half a year ago, they moved most of their day-to-day work into Bridge.
“Everything was somewhere. Nothing was together.” ©
Before Bridge, their operations looked scattered, mostly relying on Telegram – working channels with the core team, validators, and some early whales. Discord was (and is still) used to interact with the community and engage new users.
The team used Google Docs for governance drafts, investor memos, specs, and drafting marketing copy, Zoom and Teams for meeting. “For our core team tasks we tried Asana, Jira, Notion and Slack, but that only added to our headaches.”
Typical problems kept arising:
- Lost decisions.
The final call on a parameter change, validator offboarding, or new chain integration might be buried in a private chat or an old call recording. - Incident ping-pong.
When something happened, people spammed screenshots across multiple chats. There was no clear “single thread” for an incident. - Founder as router.
Everybody pinged him personally: devs, funds, community mods. If he was AFK and missed replying in Telegram, something important got stuck.
Moving to Bridge: “We needed a table where everyone could sit.” ©
Alexander: “I didn’t want another tool. I wanted one place where the work actually happens, where we have all our channels (or can plug them in) at once.”
When they tried Bridge, the model just snapped together like a finished construction set: “Slack + Telegram + Notion + Trello + AI agents wired into the same scene”— plus — updates for X/Discord, and gateways set up so that these updates can be easily published and tracked.
They started expanding it step by step:
- First step: internal team chat + incident channels.
- Then: task boards for integrations and validator management.
- Then: a “validator & partner hub” inside Bridge.
- Finally: AI agents for tracking, summaries, drafting, and posting.
Results So Far
All of Vested’s live validator databases and algorithmic tools had already been running for years as a standalone service. The team deployed Bridge on the same private server where the rest of the system lives, so it runs as a single, tightly integrated hub. This allowed them to build a sane workflow and incident-hygiene pipeline: now any issue that needs human intervention is immediately turned into a task card in Bridge, an owner is assigned, and the right specialists and agents are tagged in.
“There’s way less context switching and far fewer stupid regressions.”
A separate database of leads and partners is kept in Bridge and is overseen by an AI agent. Whenever there’s a new prospect update, someone either mentions the agent in chat or throws it a link to an external conversation (even a screenshot works!); it checks the context, extracts the key points, and updates the prospect record automatically.
The team also created an internal knowledge hub: all previous documentation — code reviews, whitepaper versions, investor presentations, incident post-mortems, and marketing materials — now lives in one structured space. This lets support team members, both humans and AI, quickly find the right solutions, factual information, and even proper phrasing.
“Before, everyone came to me. Now, by default, Bridge is the first place we look. Yes, it uses a lot of tokens for all the Copilot and agentic features we rely on, but it’s still much cheaper than what we were paying before. The hierarchy of work also became much clearer: integrations have their own boards and threads, and incidents have clear owners. It took me months to realise the name ‘Bridge’ wasn’t about APIs at all, but about the idea of captain’s bridge. I stay informed, but I no longer have to constantly run between the engine room and the steering wheel.”
