Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

💬 We get asked If I launch two different strategies on my Vault, will they mess up each other's positions? ❕ Answer from a GT App Trader: They won’t. That was actually the biggest issue with running a Vault - everything used to mix into one messy pile. 🔸...

32,245 Aufrufe • vor 3 Monaten •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

Introducing Zest Protocol Stacks Vaults, Automated yield strategies for Bitcoin-native finance. Launching alongside the stacks.btc Bitcoin Staking upgrade. Stacks Vaults mark the evolution of Zest Protocol from a lending market into yield infrastructure. Until now, earning optimised yield on Stacks meant actively managing positions across markets, moving collateral, monitoring rates, and rebalancing by hand. Stacks Vaults changes that: deposit a single asset, select a strategy, and the vault handles the mechanics in the background. This is the yield toolkit for Stacks. Every yield source in the ecosystem becomes a strategy that can be automated and offered as a single-deposit product. The first vault is a levered Bitcoin Staking vault, built around the liquid staking Bitcoin token Stacking DAO launches with the Stacks Bitcoin Staking upgrade. How the levered Bitcoin Staking vault works: 🟠 One deposit, one position. Deposit BTC, sBTC, or stBTC directly into the vault. You hold a single position while the strategy runs itself. 🟠 Automated leverage. The vault uses your stBTC as collateral to borrow sBTC, stakes the borrowed sBTC into stBTC, and repeats the process. Target yield: 6 to 8%, purely derived from Bitcoin Staking on Stacks. 🟠 Non-custodial. The vault contract can only execute strategy actions on Zest Protocol's lending markets. It cannot move funds anywhere else, and only the user can withdraw their position. No one, including Zest Protocol, can access vault assets. 🟠 Built on live lending markets. The vault runs on Zest Protocol's existing markets: two years in production, over a thousand liquidations processed without bad debt. 🟠 Continuous monitoring. Zest Protocol manages the strategy and monitors the position automatically. No manual rebalancing, no juggling markets. 🟠 First of many strategies. The stBTC looping vault is the first, not the last. STX-based strategies, stablecoin and credit-based strategies, and structured yield products can all be built on the same foundation. External curators will be able to manage their own strategies on Stacks Vaults. Lending markets were the foundation. Vaults are what gets built on top. Stacks Vaults launch alongside stBTC, right before Stacks Bitcoin Staking goes live. Note: Stacks Vaults are separate from Bitcoin Collateral Vaults, Zest Protocol's upcoming flagship product that allows users to borrow against native BTC on any chain (e.g. Ethereum). More updates on Bitcoin Collateral Vaults follow shortly. Follow Zest Protocol on X or subscribe to our newsletter to be notified when levered Bitcoin Staking goes live.

Zest Protocol

28,549 Aufrufe • vor 1 Monat

🪴 GT Protocol Monthly Recap: May 2026 May focused on launching advanced trading infrastructure, introducing AI risk-management tools, and shipping major platform upgrades. 🚀 Hyperliquid Vaults Live Run multiple algorithmic strategies on a single Hyperliquid Vault inside GT App. Enjoy automated execution, auto-rebalancing, and protocol-level security. You can find Vault trading on the Hyperliquid exchange account connection page in the Trade on Vault section. Try it in GT App 👉 🤖 AI Hedge Fund Experiment Live An experimental AI Hedge Fund powered by 5 independent LLM models is live on Hyperliquid. Each model manages $10,000 to test different AI trading personalities and allocation strategies. Discover it now here 👉 📈 Isolated Margin & AI Risk Tools Isolated Margin is live across GT App for precise risk management. Enhanced with AI-powered logic, it assists with dynamic asset monitoring and smarter strategy deployment. Try it in GT App 👉 🔥 Top Strategy Performance Top trader strategies like "lebakien" achieved over +141% profit this month. Users can explore metrics and follow the strategies of top traders directly in the marketplace. Explore Marketplace 👉 🛠 Key Product Updates ⚙️ Strategy Discovery: enhanced demo trading flows and top trader strategy integration. ⚙️ AI Strategy Chat: demoed a flow to create, launch, and test strategies via natural language chat. ⚙️ Advanced Execution: added manual safety orders for granular control over active positions. ⚙️ Testing & Validation: optimized historical data validation for more accurate strategy testing. ⚙️ Knowledge Hub: launched GT Protocol Learn and a new Knowledge Base for streamlined support. ⚙️ Performance: upgraded website structure and improved overall page responsiveness. Find all the latest GT App updates Here 👉 Discover guides, insights, and resources in Learn 👉 and Knowledge Base 👉 📰 GT Protocol AI Digests 4 new AI Digest issues (No.89–92) are live on Medium, covering AI-native hardware, data privacy, and the evolution of AI agents. Read More 👉 May brought institutional-grade AI strategy management closer to every user.

GT Protocol

32,904 Aufrufe • vor 3 Monaten

Transformer by hand ✍️ ~ 6 steps walkthrough below Open the hood of a transformer and the parts list is overwhelming: embeddings, positional encoding, attention weighting, self-attention, cross-attention, multi-head attention, layer norm, skip connections, softmax, linear, Nx, shifted right, query, key, value, masking. Which of those actually make the car run? Two of them. Attention weighting and the feed-forward network. Everything else is an enhancement to make it run faster and longer, which is how we got from a car to a truck, and to the word "large" in large language model. So I drew and calculated those two parts entirely by hand. Goal: push five features through one transformer block, filling in every cell yourself. 1. Given Five positions of input features, arriving from the previous block. 2. Attention matrix Let us feed all five features to a query-key module (QK) and read back an attention weight matrix, A. The details of that module are a post of their own. 3. Attention weighting We multiply the input features by A to get the attention weighted features, Z. Still five positions. The effect is to combine features *across positions*, horizontally: X1 becomes X1 + X2, X2 becomes X2 + X3, and so on. 4. First layer Let us feed all five weighted features into the first layer of the FFN. Multiply by the weights and biases. This time the combining happens *across feature dimensions*, vertically, and each feature grows from 3 numbers to 4. Note that every position goes through the same weight matrix. That is what "position-wise" means. 5. ReLU We cross out the negatives. They become zeros. 6. Second layer Let us bring it back down: 4 dimensions to 3. The output feeds the next block, which has a completely separate set of parameters, and the whole thing runs again. You have just calculated a transformer block by hand. ✍️ The takeaway: the two parts are doing two different jobs, and neither one alone is enough. Attention mixes *across positions*, so a feature can see its neighbours. The FFN mixes *across feature dimensions*, so each position can think about itself. Horizontal, then vertical. Then that pattern repeats N times, each block with its own separate set of weights. That is the Nx from the list up top, and that is what makes the transformer run. 💾 Save this post! #AIbyHand #Transformers #DeepLearning

Tom Yeh

26,089 Aufrufe • vor 2 Monaten

I just built a Meta Ads diagnostic in Claude Code that tells you WHY your account broke, not just what changed 🤯 It spins up a team of agents that each investigate a different reason performance dropped, then argue against each other to kill the wrong answer before it ever reaches you. All inside Claude Code. Perfect for DTC brands and agencies who panic-kill creative the second CPA spikes. If you've watched ROAS fall off a cliff and opened Ads Manager with ten tabs going, you already know what happens next. Your gut says "creative fatigue." You kill your best-performing ad. A week later performance is still broken, because that was never the problem. Guessing wrong is the most expensive move in paid social. This workflow ends the guessing: → One agent investigates each competing theory — creative fatigue, budget and delivery changes, traffic quality, offer and seasonality → Each one is blind to the others, reasoning only from its own slice of the data so they can't bias each other → A refuter agent then attacks every surviving theory and tries to kill it → A theory only stands if the data can't disprove it → You get a ranked diagnosis: the real cause, the evidence for and against it, and the one move to make this week No anchoring on the first obvious answer. No killing winning creative on a hunch. No "here's what happened" reports that never tell you why. What you get: → Every theory tested in parallel instead of one biased guess → An adversarial pass that kills the wrong answer before you act on it → A ranked diagnosis with confidence levels and evidence both ways → A reusable workflow you drop next month's export into and re-run Built 100% in Claude Code with the new dynamic workflows. The first account I ran it on looked like textbook creative fatigue. The workflow disagreed, and traced the real cause to a budget change that had doubled spend and flooded delivery with junk traffic. I put together a full playbook with the exact workflow, the prompt, and how to run it on your own account. Want it for free? > Like this post > Comment "META" And I'll send it over (must be following so I can DM)

Mike Futia

12,861 Aufrufe • vor 3 Monaten