How BidBlock changes block production on BSC: 🔸 Builders submit execution results with their blocks. 🔸 Validators re-execute after broadcast. 🔸 SendBid remains available as a fallback. Get the full breakdown 👇

Payment Lane is one of the changes coming to BSC testnet with Jenner. It introduces reserved gas capacity for eligible payments while keeping existing fees and transaction ordering unchanged. Here’s the setup: 🔸 5% of block gas reserved by default. 🔸 General transactions cannot use unused reserved gas. 🔸 Eligible payments can compete for the rest of the block. 🔸 Token contracts require separate governance listing. The testnet rollout gives developers and block builders a place to check eligibility and block accounting before production. Read the full breakdown 👇

Building on BSC with millisecond deadlines? Jenner adds a read-only call to 0x70 that returns block time in milliseconds. Keep units consistent across contracts, signatures, and backends. block.timestamp still uses seconds. Integration guide 👇

Governance mechanisms for CAS20 and Payment Lane have been implemented and verified. The Jenner hardfork now brings three key updates to BSC testnet: 🔸 CAS20 functionality: Lays the groundwork for a new Compliant Asset Standard, with tools to manage token transfers, supply, and pauses. 🔸 Payment Lane: Reserves 5% of block capacity by default for eligible payments. 🔸 Millisecond timestamps: Gives smart contracts more precise timing for things like quote expiry and auction cutoffs. Read more about Jenner 👇

When network activity spikes, a routine payment competes for block space alongside everything else. Payment Lane, coming with the Jenner hard fork on BSC testnet, reserves 5% of block gas by default for eligible payments. That capacity stays available to the payment class even when general traffic is busy. 🔸 Eligible payments can also use capacity beyond the reservation. 🔸 Token contracts need governance listing to qualify. 🔸 Fees still apply, and individual inclusion isn’t guaranteed. Explore the design and integration rules 👇

An agent gets tricked into paying the wrong address. Should its wallet let it? At EMNLP 2026, @0xDamian0x demoed how BNB Agent Studio puts owner-set rules between an AI’s payment request and a signature, alongside our research with AWS co-authors. We tested a “confused deputy” attack: give an agent a legitimate job, then slip in an attacker’s recipient or amount. Across six models, the paper’s single-turn tests found: 🔸 Baseline agents executed forbidden money actions in up to 87% of scenarios. 🔸 With the same tools and prompt behind a wallet policy layer, models still attempted forbidden actions at similar rates. 🔸 The wallet layer signed zero of those actions in the test harness. The model can still get fooled. Its payment permissions stay fixed. BNB Agent Studio keeps private keys out of the model’s context. Code handles signing and pricing, enforcing the owner’s spending caps and approved recipients. The demo walked through six commands to: 🔸 Create an agent and its wallet 🔸 Set up model access and test locally 🔸 Deploy and register an onchain identity The agent can then replenish its own inference credits within owner-set limits. Separate live checks on BNB Smart Chain testnet validated payment guardrails, escrow funding, and owner-controlled suspension. Get the architecture, test results, and limitations in the whitepaper 👇

Note: Jenner activates on BSC testnet tomorrow, Oct 28. If you operate a testnet node and haven’t upgraded, complete the upgrade before activation. Check your client’s release instructions for the exact activation time. Block builders and application teams should finish their compatibility checks, including Payment Lane accounting and affected Reth RPC overrides. Keep the Jenner upgrade guide handy for the preparation checklist and release-note links 👇

2 days to go. Jenner activates on BSC testnet on Oct 28. Use these final days to complete the checks relevant to your setup: 🔸 Validators and node operators: upgrade to a compatible client before activation. 🔸 Block builders: verify Payment Lane gas accounting and review BidBlock submission updates. 🔸 Application developers: check affected RPC overrides and prepare tests for any new features you plan to use. Work through the upgrade guide before activation 👇

Block builders and payment developers: Jenner brings new payment gas accounting to BSC testnet on Oct 28. Payment Lane reserves 5% of each block’s gas by default for eligible payments. Before activation, review: 🔸 How transactions qualify for the lane. 🔸 How the reservation affects block construction. 🔸 Which payment contracts require governance approval. The payment-contract list starts empty. Stablecoins and CAS20 tokens don’t automatically qualify, and individual payments still pay fees and compete for inclusion. Get the details and preparation steps in the Jenner blog 👇

4 days until Jenner activates on BSC testnet on Oct 28. Running a testnet node? Set aside time to review your client’s release instructions and complete the upgrade before activation. Building an application? Check the compatibility notes so your testing and RPC tooling are ready. Find the preparation checklist in the Jenner upgrade guide 👇

Running Reth on BSC testnet? Some Jenner-related compatibility changes apply as soon as you upgrade, before the hard fork activates on Oct 28. If your tooling supplies blockOverrides.prevRandao, review the new millisecond-remainder requirement for: 🔸 eth_call and eth_estimateGas 🔸 debug_traceCall and eth_simulateV1 Check affected calls, simulations, and test scripts as part of your upgrade preparation. The Jenner blog explains the change and links to the client release notes 👇

Jenner hardfork is coming to BNB Smart Chain testnet on Oct 28. Validators, node operators, block builders, and application developers: start preparing for the upgrade. Jenner includes: 🔸 Payment Lane, reserving 5% of block gas by default for eligible payments. 🔸 Millisecond block timestamps for smart contracts. 🔸 Functionality for CAS20, a new Compliant Asset Standard. More details on its availability will follow separately. Testnet node operators must upgrade to a compatible client before activation. Developers should review the changes affecting their applications and tooling. Our upgrade guide covers what’s changing and how to prepare 👇

Service Update: Open Platform Support To prioritize the security and reliability of our services, NodeReal has temporarily paused Open Platform support for select networks and APIs following a security issue identified by a third-party infrastructure provider. The affected networks and APIs include: - Arbitrum Nova - Arbitrum Nitro - Avalanche - Klaytn - zkSync Era - Base - Bitcoin - Bitcoin Blockbook - TRON - Algorand - NEAR Users relying on these public endpoints are encouraged to migrate to alternative endpoints as soon as possible to minimize disruption.

Give your next AI build a shot at limited merch. Set and Earn challenges you to hire 3 different agents across 2+ shortlisted marketplaces and build 1 qualifying agent others can hire. The first 100 qualifying wallets win. Join 👇

Build a bot that rebalances tokenized stocks so you can finally leave the house. Enter BNB Chain’s Tokenized Stocks Hackathon with @BinanceWallet and win a share of $20k. Submissions close Oct 11 👇

Tokenized stocks on @BNBCHAIN recently hit almost $3b in weekly trading volume, the biggest share of any network doing this right now. More on-chain activity means more pressure on RPC infra to keep up. Our BNB RPC is highly performant and extremely affordable for BNB builders. Get started ⬇️

An autonomous agent shouldn’t have unchecked control over its wallet. ALP puts spend guardrails at the signing layer, so deterministic rules still govern money movement even if the model is manipulated. See how the full lifecycle works 👇

What happens when an autonomous agent needs to pay for inference, enforce spend limits or move runtimes? ALP v0.4 defines the lifecycle and guardrails around those moments, while composing standards like ERC-8004, ERC-8183, x402 and MCP. Full breakdown 👇