Read the latest Pulse

Tokyo edition

News checked through

Published 10 Oct, 23:21 UTC

You are reading a saved edition, not live news. News window: 9 Oct, 23:15 UTC to 10 Oct, 23:15 UTC. Labelled ongoing and upcoming items retain their own dates.

The catch-up

News from the last 24 hours, plus clearly dated ongoing developments and upcoming events.

Worth watching, unconfirmed

Solana's first full 200ms epoch averaged 218.3ms, one tracker says

Solana Compass, an independent site that runs a Solana validator, said epoch 1053 averaged 218.3 milliseconds per slot and lasted 26.2 hours. A slot is the window in which one validator can produce a block. The target is 200 milliseconds. Compass put the epoch from 14:40 UTC on 9 October to 16:52 UTC on 10 October, and said the average is that length divided by 432,000 slots. That is about 9% over the target, a similar millisecond gap to earlier steps. Solana's own upgrade page does not publish this average, Compass said. @bw_solana wrote the same day that slot times look reasonable and skip rates look good, without numbers. One epoch does not show how many slots were skipped. This desk did not recompute it.

Read story

Robinhood

1 development

Robinhood Chain dashboards still disagree, at 5.6 million and 8.47 million

Robinhood Chain is Robinhood's Ethereum layer-2. CoinDesk reported an average of 6.2 million transactions a day from 2 to 8 October, 42% below 10.8 million in mid-September. It said daily active addresses fell 31%, weekly spot volume fell 21% to $7.45 billion, deposits stayed above $1 billion, and perpetual-futures volume rose 26%. It also said Robinhood is still paying network fees on wallet swaps over 50 cents through 31 December. growthepie's chain page, updated 10 October at 05:35 UTC, now shows 5.6 million daily transactions, down 21.1% on the week, and about 265,600 active addresses, down about 22%. A growthepie page dated 10 October, and another dated 9 October, still list about 8.47 million daily transactions. This desk did not rebuild the series.

Why it matters Someone judging whether activity is really slowing cannot use one chart. The latest chain page moved toward CoinDesk's slowdown, while another growthepie page still shows a much busier day. Fee subsidies run through 31 December, so these counts are not yet what users do when they pay.

Read the context

Robinhood Chain is the blockchain Robinhood opened for tokenized stocks and other onchain markets. It is an Ethereum layer-2: transactions are batched and settled back to Ethereum, and fees are paid in ETH. A lot of the visible trading is on exchanges and launchpads, not only in the Robinhood app. A transaction count, an active-address count and a volume figure answer different questions. Cheap or repeated actions can inflate a count, one person can use many addresses, and a single day is not a multi-day average. CoinDesk's 6.2 million is an average for 2 to 8 October. The growthepie chain page is a latest-day snapshot. Its explainer pages can refresh on another schedule, which is one reason the same site can show 5.6 million and 8.47 million at the same time. No cited page publishes a trade-by-trade rebuild that would close the gap. Robinhood is also covering the network fee on some wallet swaps, which can make activity look stronger than it would if every user paid.

Link to this story

Solana

3 developments

Solana's first full 200ms epoch averaged 218.3ms, one tracker says

Solana Compass, an independent site that runs a Solana validator, said epoch 1053 averaged 218.3 milliseconds per slot and lasted 26.2 hours. A slot is the window in which one validator can produce a block. The target is 200 milliseconds. Compass put the epoch from 14:40 UTC on 9 October to 16:52 UTC on 10 October, and said the average is that length divided by 432,000 slots. That is about 9% over the target, a similar millisecond gap to earlier steps. Solana's own upgrade page does not publish this average, Compass said. @bw_solana wrote the same day that slot times look reasonable and skip rates look good, without numbers. One epoch does not show how many slots were skipped. This desk did not recompute it.

Why it matters The 200 millisecond switch is no longer only a target. The first finished epoch ran long enough to add about two hours to a day, if this clock is right. Apps that assume a blockhash lasts a fixed number of slots, or that an epoch is exactly 24 hours, can check the next epoch against this baseline.

Read the context

Solana is a blockchain whose speed is set in part by slot time. The target was cut from 400 milliseconds to 200 in four steps, and the last step went live at epoch 1053 on 9 October. An epoch is 432,000 slots. At a perfect 200 milliseconds it would last 24 hours. Compass's 218.3 millisecond figure is the measured length of that epoch divided by 432,000, so slow or missing slots pull it up. It is one operator's clock, not a figure from Anza or the Solana Foundation, and the series does not include a skip rate. Earlier targets also landed about 15 to 19 milliseconds slow in Compass's data. @bw_solana is the chief executive of Anza, the team that builds the Agave validator software. His comment that slot times look reasonable is qualitative. The second 200 millisecond epoch was still in progress when Compass pulled the data at 19:20 UTC.

Link to this story

Anza's CEO proposes raising Solana's block compute cap back to 100 million

@bw_solana , chief executive of @anza_xyz , linked a Solana discussion that proposes raising the block compute cap from 50 million compute units to 100 million. A compute unit caps how much work one block may contain. The 200 millisecond slots that went live on 9 October cut that cap in proportion, so a block holds about half the work it held at 400 milliseconds. The post says skip rates look good and slot times are reasonable. It would climb in five gates, 60, 70, 80, 90 and 100 million, and would not raise the shred limit or the limit for a single account. It cites less room for work that must run in order, and uncertain network bandwidth. @jacobvcreech , of the Solana Foundation, replied that latency was halved and capacity should be doubled. No date or software release is given. This is a discussion, not a live change.

Why it matters Doubling the cap while slots stay at 200 milliseconds would raise how much work the network allows per second, which is what crowded apps actually feel. It is not scheduled. Validators and developers can read the proposal and the reasons it leaves account and bandwidth limits alone.

Read the context

Solana measures block capacity in compute units. The cap exists so a leader cannot pack more work than other validators can replay in time. Shortening slots from 400 to 200 milliseconds also cut the per-block cap from 100 million to 50 million, so the work required per second stayed about the same. Restoring a 100 million cap at the new speed would be a real capacity increase, not a return to the old pace. Watt's post would do that in steps. It would leave the single-account cap where it is, because ordered work on one account has less spare room, currently described as 20 million compute units in a 200 millisecond slot. It would also leave the shred limit, a cap on block data sent across the network, because bandwidth headroom is unclear. A GitHub discussion is an idea. It is not a finished improvement document, a validator vote, or a client release. Nothing in the post names an activation epoch.

Link to this story

Samsung Wallet still aims USDC transfers at US Galaxy phones in late October

@solana posted a video presenting its Samsung partnership as always-on payments. The Solana Foundation’s 7 October note says Samsung Wallet and Samsung Pay will support stablecoins on Solana, and that users in the United States will be able to send USDC across borders beginning the last week of October 2026. It says the feature is built into Samsung Wallet rather than a separate crypto app, will cover 82 million U.S. Galaxy devices at launch, and may add markets later subject to local rules. The video is promotional and does not add fees, eligibility screens or a start clock. This desk did not send a transfer. The U.S. feature is not described as live today.

Why it matters A phone-wallet remittance path would put Solana stablecoin transfers inside an app people already use for cards and IDs. The watch is whether the last-week-of-October U.S. start actually appears in Samsung Wallet, and in which form.

Read the context

Samsung Wallet is the preinstalled wallet on many Galaxy phones, used today for payment cards, boarding passes and IDs. The Solana Foundation says Solana would run behind that interface so a user would not have to open a separate crypto app to send USDC. USDC is Circle’s dollar stablecoin. The Foundation’s note is dated 7 October 2026 with no clock time on the page. It gives no country list beyond a U.S. start, no fee schedule, and no exact calendar day inside the last week of October. @solana ’s 10 October video repeats the partnership and quotes speed, cost and 24/7 uptime. It does not replace the Foundation schedule. Some news write-ups name Sui, Bastion and Coinbase as additional partners. Those names are not on the Solana Foundation page this desk read, so they are left out here. 82 million is Samsung’s count of compatible U.S. Galaxy devices, not a count of people who have turned the feature on. Until the wallet actually ships the flow, this remains a dated launch watch.

Link to this story

Base

2 developments

Base says 19 new Coinbase stock tokens are live, naming SONYc, NOKc and SAPc

@base said 19 new Coinbase tokenized stocks are now live on Base, including SONYc, NOKc and SAPc. On 9 October at 19:59 UTC the same account posted that more tokenized stocks were ready for the weekend, and a reply said they are only available in eligible places outside the United States. These tokens are onchain stand-ins for shares, issued through Coinbase and traded on Base, Coinbase's Ethereum layer-2. The Saturday post also said tokenized-stock trading volume on Base reached $500 million last week. The post text does not list the other 16 tickers. This desk did not buy one or match the tickers to shares.

Why it matters The stock-token shelf on Base is widening past the first US names, on Base's own count. A reader can look up SONYc, NOKc and SAPc and the eligibility warning. A US account should not assume it can trade them.

Read the context

Coinbase tokenized stocks are tokens on Base meant to give eligible customers outside the United States exposure to shares. Base is Coinbase's Ethereum layer-2. The tokens can trade when stock exchanges are closed, and other Base apps can plug them in, but access depends on jurisdiction and on Coinbase's rules. Base's Saturday note gives a count of 19 and three tickers. It does not, in the text, name the other 16 or say when each contract was created. The Friday post announced more stock tokens for the weekend without that count. The US exclusion is in Base's reply, not in the Saturday roundup. That roundup also repeats older items, including a Latin American stablecoin plan and Aerodrome volume, which are separate from this listing. This desk did not open a wallet or check the backing.

Link to this story

Aero posts 1:1 AERO and ~0.044 VELO rates for a 21 October launch

@aeroxyz opened an upgrade hub for Aero, which would combine Aerodrome, Base's main decentralized exchange, and Velodrome into one liquidity layer. The hub says the Aero app, new AERO emissions and upgrade portals go live at 8:00 p.m. EDT on 21 October 2026, which is 00:00 UTC on 22 October. 1 AERO becomes 1 new AERO. 1 VELO becomes about 0.044 new AERO, because Velodrome holders are assigned 5.5% of the new supply and Aerodrome holders 94.5%. Launch chains listed are Base, Ethereum, OP Mainnet, Arc, Ink, Robinhood Chain and Arbitrum. Old emissions stop at launch. The date is announced, not guaranteed. This desk did not upgrade tokens.

Why it matters Holders of AERO, VELO and the locked versions have a published rate and a clock, plus nearer chores on 15 and 20 October. The merge reaches Base, Circle's Arc and Robinhood Chain, so liquidity would no longer sit only on Base and Optimism. Missing the prep steps can leave tokens on the wrong chain when the portals open.

Read the context

Aerodrome is the main decentralized exchange on Base. Velodrome is its sister exchange, associated with Optimism. Aero is the plan to merge them into one liquidity layer and one token, so holders convert instead of keeping two reward systems. The hub's rate is about 0.044 new AERO per VELO because Velodrome holders get 5.5 percent of the new supply and Aerodrome holders 94.5 percent. The hub says xVELO held on chains other than OP Mainnet and Ink should be bridged back to OP Mainnet by 15 October, and veNFTs should be withdrawn from relays or other vaults by 20 October. Launch remains 8:00 p.m. EDT on 21 October 2026, which is 00:00 UTC on 22 October. Those dates are what the hub says, not a guarantee. Named launch chains include Base, Ethereum, OP Mainnet, Arc, Ink, Robinhood Chain and Arbitrum. Arc is Circle's blockchain. Robinhood Chain is Robinhood's layer-2. Old emissions stop at launch. The hub says a conversion cannot be reversed. This desk did not upgrade a token.

Link to this story

Arc

1 development

Extended sets a 22 October 12:00 UTC move of its perp DEX onto Arc

@extendedapp , a perpetual DEX that now settles on Starknet, said it will move settlement to Circle’s @arc . Its 8 October post told holders of more than $1 of USDT or wBTC in a sub-account to convert or withdraw by 12:00 UTC on 19 October, with migration in the week of 19 October. The documentation page, which Extended said prevails, now lists a conversion deadline of 21 October 2026 at 12:00 UTC and a migration start of 22 October 2026 at 12:00 UTC. USDT and wBTC are not available on Arc. In-app conversion is 1:1 into USDC or cirBTC, with a 0.50% premium paid by Extended. Missing the deadline can restrict the account and close those positions. Trading is supposed to continue. @arc replied on the announcement. The move is announced, not guaranteed.

Why it matters Anyone using Extended with Tether or wrapped bitcoin collateral has a dated choice: convert, withdraw, or risk a forced close. For Arc it would be a live trading venue moving onto Circle’s chain, with gas in USDC.

Read the context

Extended is a perpetual-futures exchange built by a former Revolut team. It currently settles on Starknet. Arc is Circle’s layer-1 blockchain, live since 16 September 2026, with fees paid in USDC. Extended says most accounts migrate automatically: same wallet, keys, positions, orders, points and history. USDC is meant to move as native USDC through Circle’s Cross-Chain Transfer Protocol. ETH is meant to become wETH 1:1. Vault and XVS balances are supposed to be preserved. USDT and wBTC deposits were disabled from 16:00 UTC on 8 October. Users who authorise conversion can still withdraw until migration begins. If they miss the deadline and still hold more than $1 of either asset in a sub-account, Extended says it will restrict the whole account for up to 30 minutes, cancel orders, close those positions at mark with no fee, and return the unsupported assets to the login wallet. EVM wallets would get the assets on Ethereum plus $5 in ETH for gas; Starknet wallets would get them on Starknet. Deposits and withdrawals may pause for up to two hours during the move; sub-account transfers are supposed to keep working. cirBTC is Circle’s bitcoin-backed token. Extended currently expects it to keep wBTC’s 90% collateral ratio. Extended warned it will never send a migration link. Timing may change. This desk did not convert funds.

Link to this story

Elsewhere in crypto

1 development

XRP Ledger discloses a bug that could have minted spendable XRP

The XRP Ledger published a vulnerability report dated 9 October 2026, with no clock time on the page. It says a payment-engine overflow, present since about 2015, could create spendable XRP beyond the ledger’s intended supply. An attacker would place hundreds of specially priced offers and consume them in one payment. Each offer owner would be credited in full, while the buyer paid only a wrapped-around total. The same wrap hid the new XRP from the check that is supposed to stop XRP from being created. The cost described is a few hundred XRP in reserves, later recoverable, plus fees. The fix shipped in xrpld 3.4.1 on 25 September and applied as servers upgraded. The report says there is no evidence it was used on a public network. A separate Batch-wrapper bug was closed by the fixBatchV1_2 amendment, which the report says activated on 9 October, also with no clock time. CoinDesk’s account was published at 04:20 UTC on 10 October. This desk did not reproduce the bug.

Why it matters A payment that can create spendable XRP breaks the assumption that ordinary transactions cannot inflate the supply. The patch is already in the 25 September release, and the project says it found no public exploit, but exchanges, wallets and anyone still running an older server can read which payments the fix rejects. The Batch amendment also changes which grouped transactions the ledger accepts.

Read the context

The XRP Ledger is the network behind XRP. Its payment engine can fill a payment by walking through offers on its built-in exchange. XRP balances are integers, and this bug was an unchecked 64-bit sum across many offers. The report says normal payments do not reach numbers that large, because the offers have to be priced far worse than real markets. Protocol changes usually wait for validators to enable an amendment. This overflow fix skipped that wait so the bug would not stay exploitable for weeks after the patch was public. The report calls that the first such transaction-processing change since the amendment system began, and says validators on the default list upgraded quickly. The Batch feature lets one account submit up to eight inner transactions together. It was not active on mainnet when the wrapper bug was found.

Link to this story