BTC $83,786.67 +1.27%
ETH $2,703.41 +2.21%
BNB $763.11 +0.21%
XRP $1.50 +1.29%
SOL $119.28 +0.95%
TRX $0.3357 +0.50%
DOGE $0.0950 +2.43%
ADA $0.2526 +3.32%
BCH $310.83 +0.68%
LINK $15.30 +12.08%
HYPE $88.16 -1.16%
AAVE $167.03 +13.38%
SUI $1.14 -2.57%
XLM $0.2298 +8.75%
ZEC $1,414.68 -8.55%
AAPL $337.13 -1.05%
AMZN $246.83 -0.74%
GOOGL $341.91 +0.29%
MSFT $507.88 -1.12%
META $718.23 -1.27%
NVDA $230.38 +2.49%
TSLA $357.97 -2.94%
SNDK $1,725.21 +0.96%
INTC $115.61 -2.27%
SPCX $146.57 -1.54%
MU $1,066.85 +0.97%
AMD $610.16 -0.61%
BTC $83,786.67 +1.27%
ETH $2,703.41 +2.21%
BNB $763.11 +0.21%
XRP $1.50 +1.29%
SOL $119.28 +0.95%
TRX $0.3357 +0.50%
DOGE $0.0950 +2.43%
ADA $0.2526 +3.32%
BCH $310.83 +0.68%
LINK $15.30 +12.08%
HYPE $88.16 -1.16%
AAVE $167.03 +13.38%
SUI $1.14 -2.57%
XLM $0.2298 +8.75%
ZEC $1,414.68 -8.55%
AAPL $337.13 -1.05%
AMZN $246.83 -0.74%
GOOGL $341.91 +0.29%
MSFT $507.88 -1.12%
META $718.23 -1.27%
NVDA $230.38 +2.49%
TSLA $357.97 -2.94%
SNDK $1,725.21 +0.96%
INTC $115.61 -2.27%
SPCX $146.57 -1.54%
MU $1,066.85 +0.97%
AMD $610.16 -0.61%

cat

All
Article
Flash

first_img OpenAI: Safety justification should be submitted before cutting-edge reinforcement learning training

On September 28, 2026, OpenAI published a safety-related article, stating that before continuing any cutting-edge reinforcement learning training, structured safety documentation should be required. Ideally, such documentation should reach the evidence-based structured risk argument level used in safety-critical industries like aviation and nuclear power. OpenAI views this as a direction for effort while acknowledging the complexity arising from the emergence of AI capabilities, making it difficult to achieve the same level of rigor.The article focuses on cutting-edge reinforcement learning training and does not cover the broader alignment attributes required for internal and external deployments. The recommendations in the article reflect current practices, which are expected to continue evolving and are being implemented internally at OpenAI. Technical safeguards should cover model alignment, isolation, and monitoring, including avoiding speculative positive reinforcement rewards, offline alignment assessments and stress testing, preventing automated scorers from seeing thought chains, as well as multi-layer infrastructure security, sandbox red teaming, limiting high-bandwidth cross-sample communication, and immutable preservation of agent records.Operational guidelines include preemptive dissent across teams, approvals that can be vetoed by senior leadership, accountability of training leads for safety arguments and incident responses, as well as fail-safe pauses, internal oversight, audit access, and escalation by severity. In response to serious misalignment events, OpenAI proposes controlled access to original records, root cause analysis, operational and cultural reviews, and treating incident-derived assessments as regression tests; results of investigations should be made public, along with reviews and operational changes, and affected third parties should be notified as soon as possible.

first_img Chainlink released CCIP 2, allowing enterprises to customize cross-chain security verification

On Monday, the oracle network Chainlink released the cross-chain interoperability protocol CCIP 2, making significant upgrades to its communication and cross-chain bridge infrastructure. The new version allows enterprises to add their own security verification checks on top of Chainlink's default network of 16 independent node operators. Enterprises can run their own validators or hire external service providers such as Infosys and Nethermind. Chainlink stated that users should not be forced to become "cross-chain security infrastructure experts."This upgrade comes about five months after the Kelp DAO was hacked in April of this year. The attackers are reportedly linked to the North Korean Lazarus group, stealing approximately $292 million in rsETH by deceiving the single validator relied upon by the Kelp cross-chain bridge, which operates on LayerZero. LayerZero blamed Kelp for using only a single validator, while Kelp stated that LayerZero employees had reviewed its setup and raised no objections. Kelp subsequently announced that it would migrate rsETH to Chainlink.The upgrade also adjusts the security mechanism that Chainlink had previously heavily promoted; its risk management network will no longer operate as an independent review node, with such independent checks now provided by optional validators. This means that users who have not added any validators currently rely on a single validation network, whereas previously they relied on two. Existing Chainlink users have been automatically migrated to the new version, but the company has not disclosed which institutions are using the new validators, only stating that Aave and Maple have begun adopting other features of the upgrade.
app_icon
ChainCatcher Building the Web3 world with innovations.