You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our main goal is to build a Beam Chain client, in the time being as the Beam Chain spec won't be released until December 2025 we are building a Beacon Chain client for a few reasons
The Beacon and Beam chain should have a lot of infrastructure overlap
We want to build PoC's of the state transition function and benchmark the performance of running this code in ZKvm's
participating in Beacon to Beam network transition testnets
participating in the Beacon to Beam network transition on mainnet?
Provide better UX to our users on the transition
Onboard users before the Beam transition to get a lead in market share.
Without participating partially in the Beacon Chain, we will likely be a struggle to onboard users to our client since their is a lot of competition. Securing market share before the network transition in 5 years will be vital for growing our place in the market and building trust with stakers.
We strive for
The best User Experience
The best performance
The best developer experience
Lets go to the moon and build the best client possible 😁
The text was updated successfully, but these errors were encountered:
Our main goal is to build a Beam Chain client, in the time being as the Beam Chain spec won't be released until December 2025 we are building a Beacon Chain client for a few reasons
Without participating partially in the Beacon Chain, we will likely be a struggle to onboard users to our client since their is a lot of competition. Securing market share before the network transition in 5 years will be vital for growing our place in the market and building trust with stakers.
We strive for
Lets go to the moon and build the best client possible 😁
The text was updated successfully, but these errors were encountered: