Track B submission ⚡
Just connected my agent to Binance Agent OS via MCP and completed the full trading workflow:
✅ Spot trade executed
✅ Futures trade executed
✅ Margin / Convert trade executed
Setup:
• Agent connected through Binance MCP
• Dedicated Agentic sub-account
• Permissions scoped to trading only
• No withdrawal access (as designed)
This is exactly what Agent OS should feel like — market data in, decision out, trade executed inside user-defined limits.
Building the next layer next: automated signals + on-chain actions on the same agent.
We built Agent OS. Now let’s see what it can actually do.
#BinanceAgentOS @binance
Introducing the Binance Agent OS Mini Hackathon.
$60,000 USDC Prize Pool.
Just 7 days to build and submit your entry.
Two ways to win:
🛠️ Track A: Build an AI agent with Agent OS (20K USDC)
⚡ Track B: Connect your MCPs and trade (40K USDC)
Pick your track. Build your workflow.
You’ve got until Sept 8, 2026, at 23:59 UTC.
How to enter:
→ Follow @Binance & repost this post
→ Reply or quote repost with your submission (Track A only: video/demo + GitHub, if applicable)
→ Complete the survey: https://t.co/ciX8P7xFDZ
We built Agent OS. You build what's next. 🫡
Disclaimer: This is not an offer or solicitation to trade any financial product. Not available to users in jurisdictions including: US, UK, EEA, Hong Kong, Singapore, and the jurisdictions on Binance's prohibited list (see https://t.co/j87Pp5MLvd for details)
@DeepSafe_AI Deterministic unspendable internals from the policy is the right direction. Just don’t sell it as “simpler backups” unless the policy is backed up as carefully as the seed.
A draft posted to bitcoin-dev this month reworks one small piece of taproot backup. It sits in an individual fork, hasn't been assigned a BIP number, and is still in its earliest form.
The draft addresses backup for unspendable internal keys. One existing approach it cites as motivation is to choose a random r and retain it, so the internal key can be recomputed later.
The draft's mechanism derives a chain code from a tagged hash of a normalized wallet policy. That chain code, the fixed NUMS point H, and a selected derivation path together determine the internal key — in a step the draft describes as being done "without additional secret material."
Its Security considerations section states two things: "The policy and selected derivation are enough to reproduce the internal key," and, in the same section, "Seed backups alone do not reconstruct the policy."
Read narrowly, what the draft changes is which inputs are needed to reconstruct that internal key.
Draft: https://t.co/IiCRQuQPcv
Good Morning 🏖️
Waking up to a world that still has someone as gorgeous as you in it… yeah, that’s a pretty perfect start. Hope your day is as bright, soft, and impossible to look away from as you are. Have a beautiful morning 🫶🫶
🔥 Bitcoin at $86,461 after hitting 8-month high
+12% in 7 days | +45% in 90 days
ETF inflows + short squeeze fueling the move.
Holding above $86k. Next stop $88k–$90k?
#Bitcoin#BTC#cryptonewsdaily
@binance
Binance has paused all deposits, withdrawals, and internal transfers due to a platform upgrade that started at 06:00 UTC today.Official update says it should take about 1 hour. Multiple networks (BSC, ETH, SOL, TRX, etc.) currently show as https://t.co/z7WqdvCjQ7 should still work. Just wait before sending funds.
My SmartX trader type: “The Alpha Caller.”
“Three hours of research. Two-word thesis: send it.”
Find yours in 6 questions. Join the waitlist for up to 50% off fees and a share of 10,000 USDT in rewards.
https://t.co/pG1uRFg67t