Rancho Stake

🌵 Rancho Stake 🤠
Node operator collective | Colectivo de operadores de nodos
Promoting decentralization in LatAm | Impulsando la descentralización en AL

[Casa Blanca @casaweb3]

Nuevo workshop junto a @RanchoStake

¿Cómo funcionan realmente ETH y SOL?

🗓 Viernes, 20 de Febrero
🇲🇽 15:00 🇨🇴 16:00 🇻🇪 17:00 🇦🇷 18:00 🇪🇸 22:00

Nos vemos en Discord 👇

[Phase Delegation @PhaseDelegation]

Meet Aero, a stake pool designed to empower and uplift Solana ecosystem contributors.

Here's everything you need to know. 🧵

[Rancho Stake @RanchoStake]

Ahora puedes hacer staking de SOL en @RanchoStake directo desde @phantom 🤠🥩

Staking hecho en México 🫡

[Rancho Stake @RanchoStake]

Lanzamos el validador de Rancho Stake en @solana mainnet hace apenas 15 días…

y ya superamos los 10,000 SOL delegados 🤠🔥

Gracias a todos los que están impulsando un validador construido por mexicanos, desde México.

Apenas empieza el viaje, súmate!

[Rancho Stake @RanchoStake]

@EduxEdu_ @solana 🤠🤝

[Rancho Stake @RanchoStake]

Lanzamos el validador de Rancho Stake en @solana mainnet hace apenas 15 días…

y ya superamos los 10,000 SOL delegados 🤠🔥

Gracias a todos los que están impulsando un validador construido por mexicanos, desde México.

Apenas empieza el viaje, súmate!

[Rancho Stake @RanchoStake]

@DontRunImAsian @solana Incoming!

[Rancho Stake @RanchoStake]

Fusaka upgrade in @ethereum, Testnet restart for @solana 🫡🫡

Just a normal day at the Rancho 🤠🥩

[Rancho Stake @RanchoStake]

@omarespejel @henrlihenrli

[MarioVega.eth 🦇🔊 @elbuenmayini]

Fusaka has finalized on Ethereum Mainnet!

On top of that, we have successfully concluded our Mainnet testing round of all Fusaka EL functionality!

Check out the report with details of the tests for each EIP here:

https://t.co/h6Trh4Ef9P

[Rancho Stake @RanchoStake]

@cripto_nita_ The right leadership.

[Rancho Stake @RanchoStake]

@LuLuDiscord @discord_support @discord_support you gotta be seriously retarded to suspend the account of one of your most respected security agents... get your shit together clowns!

[Rancho Stake @RanchoStake]

@oyealmond @baselatam Pistachio Man 🥋

[Rancho Stake @RanchoStake]

Decentralization doesn't matter until it does!

Support geographic diversity in public infrastructure 🌎🌍🌏

[Martin Fernandez @Forkland93]

The main vision I had when I founded @Senseinode was for us to be outside the clouds — to pursue the decentralization of data centers. Seeing what happened with AWS today, I know I was right.

[Rancho Stake @RanchoStake]

A great thread on how EVM nodes run in @dappnode <3

[Dappnode @dappnode]

Do you know how Ethereum validation works on your Dappnode?
Here is a technical breakdown of the validator, Web3Signer, beacon & execution clients, the backup node (new feature), and the red-line boundary. 🧵👇

[Shipyard MX @ShipyardMX]

Camino hacia el @solana Cypherpunk Hackathon 🇲🇽🚀
Un solo proyecto.
Tres etapas.
Tres oportunidades para ganar.

🏆Premios locales: hasta $1,500 USD
🏆Mini-retos junto a @fruteroclub: hasta $150 USD
🏆Hackathon global Cypherpunk @colosseum: hasta $2.5M USD en premios

Construye, presenta y compite desde México y LATAM para el mundo.

Más info y registro en el primer comentario. 👇

[Dappnode @dappnode]

We are joining forces with Meta Pool to decentralize NEAR Protocol

And YOU can be a part of it.

Together, we’re onboarding 25 new validators powered by Dappnode, no devops skills required

[ethPandaOps @ethPandaOps]

With Fusaka rolling out on Testnets and preparing for Mainnet, we've had a lot of questions about how node requirements change... 🧵 (1/8)

[Rancho Stake @RanchoStake]

If you are a home staker, you should get as much information as you can about PeerDAS. Fusaka is around the corner!

[vitalik.eth @VitalikButerin]

Fusaka will fix this.

But also, safety first is of the utmost importance for Fusaka. The core feature, PeerDAS, is trying to do something pretty unprecedented: have a live blockchain that does not require any single node to download the full data.

The way PeerDAS works is that each node only asks for a small number of "chunks", as a way of probabilistically verifying that more than 50% of chunks are available. If more than 50% of chunks are available, then the node theoretically can download those chunks, and use erasure coding to recover the rest.

In the first version, there are two cases where the full data of a block still needs to exist in one place: (i) initial broadcasting, (ii) reconstruction, in case a publisher publishes 50% <= p < 100% of a block. But these roles are untrusted: we only need one honest actor to do them, if there are also 100 dishonest actors the protocol simply bypasses them. And different nodes can perform this task for different blocks. In the future, cell-level messaging and distributed block building will allow even these two functions to be distributed.

This is all new technology, and the core devs are wise to be super cautious on testing, even after they have been working on this for years. This is also why the blob count will increase conservatively at first, and then become more aggressive over time. But it is the key to L2 scaling (and eventually L1 scaling, once the L1 gas limit goes high enough that we have to put L1 exec data into blobs)

[Ente @enteio]

You can't change our mind

[Rancho Stake @RanchoStake]

🤠🥩🥩🥩🥩

[Koen @Koenmtb1]

There's only 1 @aztecnetwork node running in 🇲🇽 Mexico right now. Is that you @dappnode ? 👀