Загрузка видео...

Не удалось загрузить видео

На главную

Introducing Fireblocks Flow. Flow is stablecoin acceptance infrastructure for PSPs and fintechs. Consumers can pay with any digital asset. Merchants settle the stablecoin they configure. If you process millions of payments across Africa, LatAm, or Southeast Asia, you know accepting stablecoins is messy. Now, it’s easy with one SDK...

15,036 просмотров • 4 месяцев назад •via X (Twitter)

Комментарии: 21

Фото профиля Dynamic
Dynamic4 месяцев назад

Accept any digital asset. Settle in any stablecoin. Here’s a demo of how crypto deposits work on mobile. You can try it yourself at

Фото профиля Dynamic
Dynamic4 месяцев назад

Ready to start accepting stablecoin payments? Read the docs for a full overview:

Фото профиля Snibby
Snibby3 месяцев назад

stablecoin rails quietly getting built everywhere now 👀

Фото профиля PunkXBT
PunkXBT1 месяц назад

stablecoin payments getting abstracted into one api is exactly how this stuff should work ngl

Фото профиля LI.FI
LI.FI4 месяцев назад

congrats on the launch! 👏

Фото профиля Dynamic
Dynamic4 месяцев назад

Thanks friends!!

Фото профиля meagan brown
meagan brown4 месяцев назад

BIGGG DAY!!!

Фото профиля Big Chirpy
Big Chirpy2 месяцев назад

putting conversion before settlement keeps token reconciliation out of the merchants back office

Фото профиля T_Khanh2026.eth
T_Khanh2026.eth3 месяцев назад

finally stablecoins made easy

Фото профиля 0xAvseenko
0xAvseenko2 месяцев назад

this turns stablecoin acceptance into an acquiring problem rather than a token adoption problem

Фото профиля TotalWorld
TotalWorld4 месяцев назад

Fireblocks Flow looks like a solid solution for stablecoin settlements in emerging markets.

Фото профиля ALTCRYPTO GEMS
ALTCRYPTO GEMS4 месяцев назад

Check your inbox 📨 please

Фото профиля 8lends
8lends4 месяцев назад

big money moving through digital assets quietly nothing to flex, just solid flows

Фото профиля TriDung.sol
TriDung.sol2 месяцев назад

infrastructure plays fr

Фото профиля Melissa Kang
Melissa Kang3 месяцев назад

Huge potential here. Would love to collaborate 🔥

Фото профиля Liya
Liya4 месяцев назад

step 1 — context analysis

Фото профиля Diana Crypto
Diana Crypto4 месяцев назад

Fantastic project delivering quality results and meaningful innovation Say hi 🌟

Фото профиля Dynamic
Dynamic4 месяцев назад

we are here to serve

Фото профиля The Lady Crypto
The Lady Crypto4 месяцев назад

Amazing project making a strong impact Open to future conversations 🚀

Фото профиля lvnbbs_bnb
lvnbbs_bnb1 месяц назад

This is the bridge for global commerce fr

Фото профиля Wiz⚡
Wiz⚡3 месяцев назад

lbranding already pops - can practically see it itching to jump off the screen in full motion 👀

Похожие видео

When I’m trying to improve the user experience of my applications, one of the most valuable things is being able to see an entire user flow as a storyboard. Not just one screen or screenshot at a time. This is something I love using the `/visual-plan` skill for. You can describe any flow you want, and the agent will look through your code and wireframe out a storyboard of what the flow looks like. Then you can visualize the steps in a simplified way and spot areas to improve. Recently, I found that in certain flows we were still asking for organizations, even though I thought I had gotten rid of that and made it automatic. A quick storyboard let me see all the different code paths in a simple, visual, intuitive way. Spot the areas of the flow I didn’t want. And have the agent fix it. Sign up, onboarding, and setup flows are usually some of the most important experiences in your app. And usually the least looked at. Especially because it can be hard to reproduce every flow, for every situation, for every user type, feature flag, or whatever else you have. The `/visual-plan` skill lets you visualize any part of your code. Either to understand the current state, plan out a new state, or recap updates that were made. I’m pretty addicted to this skill. I use it for a lot of other things too, so let me know if you want to see videos on those. And of course it’s all open source. You can grab it on my GitHub. I'll link to it in the thread. If you try it, let me know your feedback.

Steve (Builder.io)

148,886 просмотров • 3 месяцев назад

Everyone's building AI agents that run on someone else's server, store memory in someone else's database, and can be shut down by someone else's terms of service. I built one that can't be. FlowClaw is an AI agent that runs on a decentralized distributed computer. Your agent, your conversations, your memory, your tools — all stored onchain on Flow, a distributed network of validator nodes across the world. Not a centralized cloud. Not someone's S3 bucket. A blockchain that functions as censorship-resistant compute and storage for your AI. This isn't a wrapper. Your agent is a Resource — a first-class programmable object in Cadence (Flow's smart contract language) that physically lives in your account's on-chain storage. It can't be duplicated, seized, or deleted by anyone except you. Your encrypted messages, your cognitive memory, your scheduled tasks — they persist on a global distributed ledger that no single entity controls. It's an alpha build. It will break. But it works today on mainnet and I want people to push it this weekend. What it does: You go to authenticate with a passkey (Face ID, Touch ID), and you have a blockchain account in seconds. No wallet. No seed phrase. No tokens needed — gas is sponsored. You're immediately chatting with an AI agent that has real tool execution: live web data, token prices, on-chain balances, Cadence script execution, FLOW transfers. Every message is encrypted client-side before it touches the chain. The agent has a cognitive memory system — it doesn't just remember your last message, it builds molecular memory clusters where related knowledge bonds together for contextual retrieval across sessions. You can spawn sub-agents from a visual canvas to run parallel research. The memory tab shows you exactly what your agent knows. Everything is transparent and everything is yours. 11 smart contracts. No external dependencies. No keeper networks. No account abstraction hacks. Here's the part that matters for the censorship-resistance crowd: FlowClaw supports BYOK — bring your own key. You can plug in any LLM provider. But pair it with Venice and you get the full stack: a censorship-resistant AI model running inference with no content filtering, connected to an agent whose state lives on a decentralized network that no company can shut down, with end-to-end encrypted conversations that nobody can read — not the relay operator, not the LLM provider, not the blockchain validators. Venice doesn't log prompts. Flow can't read your encrypted storage. The relay never sees your plaintext. That's not a privacy policy. That's architecture. You can also use OpenAI, Anthropic, or any OpenAI-compatible provider. The agent platform doesn't care — it's model-agnostic. But the Venice pairing is the one that closes every gap in the stack. For the people tinkering with OpenClaw and the broader open-source agent ecosystem — FlowClaw is exploring what happens when you take the agent off the cloud entirely. Not just open-sourcing the code (though it is), but putting the actual runtime state on a distributed computer. Your agent's memory isn't in a SQLite file on your laptop or a Pinecone index on someone's cluster. It's on-chain, encrypted, and replicated across every validator node on Flow. You own it the way you own a private key — mathematically, not contractually. The blockchain here isn't a gimmick bolted onto an agent for token speculation. It's functioning as the infrastructure layer that replaces AWS. Flow accounts are programmable containers with their own storage, keys, and security capabilities. Passkey authentication works natively because Flow supports P-256 keys at the protocol level — the same curve your phone uses for biometrics. Gas sponsorship works natively because Flow transactions have separate proposer, authorizer, and payer roles built into the protocol. No proxy contracts. No relayers. No ERC-4337. Now here's the part that interests me economically. Every FlowClaw interaction is an on-chain transaction. Every message stored, every memory committed, every session created, every sub-agent spawned. An active user might generate dozens of transactions in a single conversation. Scale that and FlowClaw becomes a real contributor to Flow's transaction volume. Flow.com becomes deflationary at 250 TPS. Applications like FlowClaw that generate high-frequency, storage-heavy transactions are exactly what moves the needle. Every encrypted message uses account storage, which requires FLOW balance to back it. Every transaction burns fees. The more agents running, the more demand for $FLOW — not because of a tokenomics gimmick, but because the protocol literally requires it for compute and storage. FlowClaw doesn't have its own token. The token is $FLOW. The entire platform runs natively on the network — using Flow storage, paying Flow transaction fees, backed by Flow account balances. If FlowClaw succeeds, FLOW captures that value directly. I'm sharing this early because the AI agent space is moving fast and I think the decentralized infrastructure angle is underexplored. Most "crypto AI" projects are tokens with a chatbot attached. FlowClaw is the opposite — it's an agent platform that happens to use a blockchain because the blockchain solves real engineering problems that centralized infrastructure can't. Try it: Github: Create an agent, ask it something, spawn a sub-agent, check your memory tab, pair it with Venice for the full censorship-resistant stack. Break it and tell me what broke. If you think this direction matters, the best thing you can do is use it and give feedback. Your AI agent should be yours. Not your provider's. Not your platform's. Yours.

doodlifts

12,210 просмотров • 7 месяцев назад