Today, we are launching Harbor, a Layer 1 network with native asset vaults capable of custodying diverse assets, such as Bitcoin and its UTXO variants (Litecoin, Zcash), Ethereum and its respective L2s, Solana, and more. Harbor’s first application is a cross-chain order book, providing fast and efficient spot trading to service the burgeoning market of cross-chain swaps. The network employs a dual-actor marketplace to ensure fair pricing and execution for cross-chain swaps. Existing solutions are susceptible to the flaws of solver-based designs, where an “all-or-nothing” approach incentivizes solvers to price quotes ever-higher in the hopes of earning business, but are free to execute wherever they please within a wallet’s price tolerance (usually 3%). Harbor solves this problem by having two separate entities that are naturally opposed to one another: the central limit order book (CLOB) and a smart order router. The CLOB represents the interest of market makers: performant, programmatic trading APIs allow extremely tight pricing, usually within a single tick of the market’s best bid or ask, at meaningful size. The smart order router represents the interests of swappers: placing limit orders at exactly the quoted amount, allowing market makers to compete to fill at that price, or regressing the order down the book until it fills or refunds due to price tolerance. This design ensures that no single market maker is responsible for the execution quality of a swap. The swap is worked through the order book, ensuring the best possible pricing, utilizing liquidity provided by multiple makers, while preventing quotes higher than fillable orders. We believe Harbor’s design— a hybrid DEX securing custody through threshold signature vaults and a decentralized validator set, paired with a high performance matching engine for speed and execution, along with the ability to support other purpose built “subnets” utilizing its vaults— positions Harbor as the best L1 design capable of delivering neutral, efficient, decentralized, native asset rails. Follow us for more details about our upcoming plans, intro blog post, whitepaper and more.

1/ Blockworks has acquired Messari. We’re bringing together crypto’s two largest data and market intelligence platforms.

Figure taught two robots to make a bed together - fully autonomous Honestly, they’re better at it than most humans

Per-customer deposit addresses are live on Tempo. On most chains, giving every customer a unique deposit address means initializing, monitoring, and sweeping a real onchain wallet for each. With virtual addresses, funds credit directly to a master wallet at the protocol layer.

Here's a brief @THORChain 101, from someone who was deep in that codebase for 4 years. THORChain has 95 active validators, which are organized into 5 different “asgard” vaults. Asgard vaults are simple EOAs that are operated by their validator membership (19 nodes per vault) via threshold signatures. Here’s the actual endpoints to hit to see the live membership/vaults: nodes: gateway.liquify.com/chain/th… vaults: gateway.liquify.com/chain/th… THORChain “churns” every 3 days, some validators leave, some enter, new vaults are generated via keygen, and funds rotate from old to new. A swap happens through 3 basic stages: Observation, Execution, and Outbound signing. Observation In order for a swap to happen on THORChain, a supermajority of ALL validators need to observe, sign, and agree on the inbound tx to one of the vaults. This means with today’s active set effectively 64/95 validators need to observe and sign off on the inbound. This inbound tx on ETH or BTC contains a memo instructing the network on what to do with it. Execution Once an inbound reaches consensus, the network begins executing the swap based on the instructions encoded in the memo. The memo contains the desired output asset, limit, and destination address. The swap occurs on THORChains AMM, and once complete, an outbound is scheduled to one of the 5 asgard vaults. Outbound signing The vault that is assigned to send the outbound goes through the keysign ceremony: each member validator signs the same onchain tx via TSS, and once a supermajority of that vault has signed the tx, it is broadcasted on chain (effectively a 13/19 threshold signature). So, basically, 64/95 validators need to agree to process a transaction, need to agree on the execution/outbound, and 13/19 actually sign it out. If 32/95 validators refused to process an inbound it would be black-holed onto the vault EOA, the network would have no record of it, and nothing would happen with those funds without further intervention.

when you say "nodes", are all of those "validators" (actively effectuating transactions?) at one time I was told the number of validators might be as few as 3, in which case it's hard to distinguish from a multisig type situation, but could be total bullshit, I don't know

Introducing Claude Design by Anthropic Labs: make prototypes, slides, and one-pagers by talking to Claude. Powered by Claude Opus 4.7, our most capable vision model. Available in research preview on the Pro, Max, Team, and Enterprise plans, rolling out throughout the day.

Swaps are accelerating at @Harbor_DEX 🚢 - bigger swap size available - more wallet integrations - 10% all time volume in the past 24h - excellent and transparent swap execution See it in action on Thorswap. Currently supported assets: BTC, ETH & USDT.

Harbor has demonstrated the first Tempo USDT -> native Bitcoin swap. Call a smart contract on @tempo, receive native $BTC, with a single transaction. @LayerZero_Core handles the @USDT0_to bridge. Harbor handles the Bitcoin swap. Coming soon to a wallet near you.