A Successful Call Can Still Return Zero
In a $BNB Chain forum post, a contributor using the name Zealynx pointed to the sample helper in section 4.5 of BEP-706. The author said a Foundry test returned zero without reverting when 0x70 was empty.
The helper makes a low-level staticcall, checks only whether it succeeded, then converts the returned bytes using uint64(uint256(bytes32(data))). Solidity’s documentation confirms that low-level calls to nonexistent contracts can succeed; its conversion rules say shorter byte arrays are padded with zeros. An empty response therefore becomes zero rather than causing this helper to revert.
The forum analysis warns that an expiry check such as nowMs <= quote.expiry would then pass even for an expired quote. An empty 0x70 without an active precompile, as on BSC before activation, is one way to get that successful but empty response. The same concern would apply on another chain if the call there succeeded with no data. The post identifies neither an affected deployed contract nor an exploit.
The author recommends checking data.length == 32 or using abi.decode, which rejects empty data. The BEP’s sample contains neither safeguard. Even after activation, the timestamp remains validator-supplied within consensus limits: BEP-706 says finer precision provides no stronger timing guarantee than block.timestamp.
Payment Capacity and Token Support
Jenner also introduces Payment Lane, reserving 5% of block gas by default for eligible payments. Its payment-contract list starts empty, with entries added through governance; eligible bare $BNB transfers can qualify without a listing. The reservation does not guarantee inclusion for an individual payment.
The fork also installs CAS20, a protocol-native token standard with transfer policies and mint, burn and seizure controls. Installing that support does not open token creation: the release notes say a governance-appointed administrator must activate creation separately.

