Cast by cassie
Quoted cast is the first post from native FIDs on Hypersnap! 0.17.x tracks the first major set of divergences from Snapchain, in short: - community run validators - fully forked chain (starting from blocks 50,477,529; 51,161,786; 50,996,940; on shards 0, 1, 2, respectively) - native account onboarding/decoupling from OP contracts - relay service to synchronize compatible data between Snapchain and Hypersnap The fork wasn't as totally smooth as it could have been, however, it went reasonably well, all things considered for a rapid community mobilization in the face of having all comms cut off.
1 reply
From the fork onward, if you are using the Hypersnap stats dashboard, you will see data specific to users created before the fork, as well as Hypersnap native users created after the fork. This means, unless there is a surprise resurgence of churned fc users that exclusively pick the NSFC client, you should only expect to see NSFC client activity dwindle on the dashboard. Unlike NS, we do not hail circumstances that guarantee outcomes as successes. As for why this is the case: we no longer listen to the OP contracts. By signing up with the OP contracts, a user is giving money to NS, and they are doing so, _knowingly_. Given they were willing to excommunicate some of the most active users on platform with zero notice, making the subscriptions, channels, and other items purchased effectively dead with no refund, we will not honor people giving them money going further. If you want to migrate a Snapchain account created post-fork to Hypersnap, accounts on Hypersnap are free, but the migration effort is yours.
Speaking of numbers: Since the fork, 176 accounts were created on the OP contracts, starting from FID 3358530. By all means, review them – you may form your own opinion regarding the percentage that are authentic users. Of users present on both sides of the fork, 345 users have since burned their yes votes, meaning they are only visible to clients on snapchain that do not use fcxyz APIs. They were, of course, always visible to hypersnap clients. As for clients, we are still seeing more new clients and experiments popping up. @arfonzo is maintaining a list of publicly available clients, so if you would like to add yours, submit it to this repo: github.com/arf0nz0/hypersnap_stuff/tree/main/clients_and_apps Ten of the earliest hypersnap clients are already on this list, but to my awareness there are already more than triple this being worked on.
So now, looking forward: 0.18 will bring important primitives to the network: - native channels - native miniapps - snap compute Alongside 0.18 (indeed, before 0.18), client SDKs will be updated to provide support for: - E2EE direct messages and group chats (we will be publishing this today) - Experimental features (things created by client developers that have not yet been turned into standards by FIP), like sticker packs