Today, we announced that with @VisaCA, we ran the first stablecoin credit card settlement pilot in Canada.
Canadians deserve a dynamic and efficient payment system. And we're proud to be at the forefront of this work.
[x] milady's core product is larp with the goal of growing the cult, it's entirely inward-facing. the entirety of the lore is self-referential and the gap between self-ascribed importance and actual influence is vast. the philosophy hasn't traveled any serious distance [..]
Anchor v1.2.1 is out!
This is a mandatory upgrade for all users on prior versions due to a security fix. Please upgrade ASAP. Further details to follow.
If you are running Anchor alongside Lighthouse, please also update Lighthouse: https://t.co/UscSA0JiwP
Lighthouse v8.1.1 (Scary Terry) is out!
This is a mandatory upgrade for all users on prior versions due to a security fix. Please upgrade ASAP. Further details to follow.
Also fixes VC head monitor timeouts, DataColumnsByRange duplicate bug, and a slow memory leak.
https://t.co/oXesKeyjwI
@_prestwich@adietrichs The lagging nodes that caused the resource exhaustion on Prysm might have been any client including prysm. I don't understand how the issue here is having multiple clients
@0xUncleBill@dataalways I was talking about it from the CL perspective. With a series of invalid payloads, regardless of whether the proposer gets paid or not, at some point, we would have to circuit break to local block building to have some transaction liveness
@0xUncleBill@dataalways A bug in a major builder impl could lead to a series of invalid payloads. At that point, it wouldn't matter if bids are over builder api or gossip. All I'm saying is that local block building fallback won't go away with epbs
@dataalways@0xUncleBill afaiu, ptc only attests to availability of the payload, not its validity.
So we could get a series of invalid payloads. And there isn't a 1-1 correspondence from a builder rpc to the onchain builder index for us to cut off a specific builder rpc
Lighthouse v7.1.0 Fantabulous is out!
This is an exciting release packed with major improvements:
📉 Hierarchical state diffs are now in the hot DB - reducing disk I/O by 4x during normal ops and using 10x less space during non-finality.
⛽ Default gas limit bumped to 45M - following extensive analysis by core devs to safely raise L1 throughput.
🔦 Light client updates are now gossiped by sync committee validator nodes, boosting light client data availability.
Full release notes: https://t.co/IYWx094wjw
We have just published Lighthouse v7.0.0-beta.1
It is a hot-fix for Holesky users which rejects the invalid justified block.
Only for Holesky users. No action required for mainnet users.
We encourage all Holesky validators to assist with the recovery 🙏
@potuz_eth@OisinKyne Just noting that we currently don't have hard stats on any potential improvements with IDONTWANT.
We enabled it on lighthouse in our last release but we need more of the network to adopt it to see clear signs that it improves bandwidth consumption