As $GALA comes up on its staking requirement, a few community members have come to me asking for me to look into some of the bridging transactions. I have learned a couple things. Over the past week, a grand total of 302 users have bridged about 689m GALA into GalaChain, where it needs to be for the staking to work. Of those bridging more than 1m $GALA, there have been 48. One of those users was Gala Games' Reserve wallet, which bridged in 500,000,000 $GALA, meaning that 72.6% of all $GALA bridged in over the last week was Gala itself. While I will give every bridging person the benefit of the doubt (even if 171 of those bridging were moving less than 10k $GALA) that means that only 301 users have bridged in enough to run 189 nodes. Out of the currently 35k nodes online...there has been enough $GALA bridged in to run less than 1% of them. Even if we look at all $GALA on GalaChain (4.7b), it is only enough to run 4,700 nodes, or 13% of the network...but that is forgetting that 171k users hold that GALA. This isn't decentralization, the community of node operators doesn't want it, and its absolutely antithetical to everything that web3 and blockchain is supposed to be. I poured my heart and soul into Gala for four years, and to see this going down is...ugh...just so beyond gut-wrenching I can't stand it. I still believe this can be turned around. There is a path forward where the community can be respected, not disregarded. I’m calling on the team at Gala to stop making decisions that push people away. It’s time to listen, to take responsibility, and to come together in support of the very community that helped build this from the ground up. I’ve already sent an email to Gala sharing my concerns, but I haven’t received any response. At the same time, I hear from the community constantly. People are confused. They’re frustrated. They feel betrayed. I spent too much time building all of this with you to sit back and watch it burn to the ground through colossal unforced errors. Anyone who would like to inspect the transactions themselves can do so here: