
Your gateway to @flow_blockchain supercharged development. Interact, inspect, and build with Flowser
Flow blockchain 🌊
Joined February 2022
- Tweets205
- Following326
- Followers402
- Likes883
Pinned Tweet
Effortlessly interact with the @flow_blockchain like a pro, manage txn, and explore smart contracts. Unleash the full potential of the network whether you're a beginner or a seasoned enthusiast. Flowser - where simple design meets powerful functionality
Crescendo making big waves in the Flow ecosystem! 🌊
Our web tool was also updated to support Cadence v1.0, but we are still working on bringing new Cadence snippets to our apps, so that you can play around with the newest Flow features!
Stay toned for a new update soon!
The Flow Crescendo upgrade is unlocking the future of consumer web3 🌊
Crescendo, now live, is the biggest upgrade since the genesis of Flow. It removes complexities for developers and enables full interoperability with the broader Web3 ecosystem.
🔗 flow.com/post/flow-reaches-c…
We are also working on a little Easter egg in the next update 🥚👀
In the meanwhile, check out: interact.flowser.dev
Flowser retweeted
Coming in hot, Edgevana’s latest research report on FLOW just dropped 🔥🔥. Flow’s Crescendo update is ushering in an exciting new era for the chain. Check out all the details and links below. 1/4 👇
Crescendo update is flowing! 🌊
We are also working on rolling out updated versions of our tools soon!
See ya on the other side, fingers crossed🤞
🛠️ Flow Network Upgrade (Crescendo) 🛠️
The Flow network upgrade (Crescendo) will start in 1 hour, at 5am PT. The network will be in maintenance for ~6 hours.
We will provide updates on the upgrade via the Flow Twitter, Discord, and Status Page.
status.onflow.org/
Flowser retweeted
Yes! More of this, please!
There is a universe of ways to make blockchain apps more interesting (and fun!) that go beyond speculation.
If you dream (as I do) of seeing this tech blossoming to its fullest, you should encourage, follow, and support creators that want to try something!
I’m bored
Tired of speculating on which insider coin will pump the most
So I decided to start making a simple mass multiplayer crypto game. There is no NFT associated. It would function more as an event/experience, with qualifier rounds leading into the championship round
Let me know if you’d be interested in participating
I envision the championship round being 50-100 transactions per player, so eth mainnet is not an option
What chain would you like to see it on?
Ideally EVM compatible. Currently thinking Base, Flow, or Blast
Would appreciate if you shared 🫡
Our frens at @flow_blockchain just pulled a 200 IQ move - they're going full EVM!!
And guess who's riding that wave? Your boy @MoralisWeb3
We're about to flood Flow with our god-tier Nodes and Data APIs
Crescendo update = EVM equivalence = Moralis superpowers activated ✊
👀 Cadence is safe for managing your personal assets in a similar way as Rust is safe for managing your program memory!
💡And the key to this kind of safety for managing assets are Cadence resources: cadence-lang.org/docs/langua…
Flowser retweeted
the Flow CLI dependency mgr is like "npm" for your Flow contracts.
like on the npmjs website, you can NOW copy your dependency cli command in 1 click from CB!
shout out to @onflowser for the idea 🫶
Flowser retweeted
L2’s are not “same as ETH” like many pretend they are. They are being more centralized and less secure to be fast. To be the future of digital goods and services this is unacceptable. Web3 needs to fast, secure AND decentralized.
This is why we built @flow_blockchain
Replying to @LineaBuild
Most L2s, including Linea, still rely on centralized technical operations which can be leveraged to protect ecosystem participants. Linea's core value is a permissionless, censorship-resistant environment so it was not a decision we took lightly.
Flowser retweeted
100% necessary and possible on @flow_blockchain. One of many under-the-hood features that make FLOW the best platform for consumer web3
Flowser retweeted
#Crescendo is coming. 🌊
#EVMonFlow breaks down barriers for ETH builders on Flow and unleashes their potential to build for the mainstream.
Flowser retweeted
It was a big week at @EthereumDenver for the Flow Foundation!
We had a week-long hacker house that was stacked with activity. Including…
🗣️ Community podcasts, including one with @FR3NCHL0AF & @austin_flowty.
🤝 A panel with our friends at @StoryProtocol, @coinfund, @dapperlabs, & @doodles.
🏗️ A range of building & hacking from Flow scholars like @Noah_Overflow, @intangible_eth, @0xPearl and others.
⚒️ Workshops & demos from the likes of @flipsidecrypto, @LayerZero_Labs, @evaluatexyz, & @magnetiq_xyz!
🍻 Parties filled with socialising and networking
Keep an eye out for more details and content from the Hacker House soon 👀
Just spotted a bull warming up in the field, stretching those gains like it's prepping for a marathon 🏃💨 #StretchThoseProfits
Sean gave a really good explanation on Flow’s take on blockchain modularity 👀
Lots of hype around modular blockchains, but not a lot of people realise this.
I love modular blockchains because it breaks out of the blockchain trilemma (speed, security & decentralization)
There are 3 ways to achieve modularity from my view.
1. Writing code modules that enable developers to spin up chains with a select your own consensus feeling.
2. Layers that each independently operate as a blockchain themselves with changes that could help them preform their module better. (The pattern discussed in this thread.
3. Nodes each with a specified role to perform. (This is how @flow_blockchain works. )
I’ll zoom in on approach 2 and 3 here.
With approach 2:
➕many blockchains can attempt a diverse set of solutions at the same time.
➖each blockchain likely requires its own token to secure it
➖ it pushes complexities on to the developer and user to work across and understand the risks of each blockchain
➖ the full stack is only as secure as its weakest token or chain
With approach 3:
➕simplified developer experience using a single blockchain to build their app
➕simplified user experience enabling for them to no longer worry which DA layer is used for app A or execution layer for app B
➕single token and blockchain to secure
➖ puts a lot on the protocol developers to create this holistic platform aligning on the best decisions and directions for the community
IMO approach 2 is another solution that leads to sharding. Sharding state, networks or users while makes it easier on protocol engineers, pushes risks and complexities to developers and users. This is why the initial proposal for a sharded blockchain scaling pattern is something Ethereum moved away from years ago. This feels like that same discussion to me.
#onFlow we use option 3 with our multi-node architecture.
Consensus nodes provide sequencing and settlement.
Execution nodes provide execution.
Collection nodes serve as the data availability.
I believe modular blockchains are the way to scale and using node to achieve this are the way to make it usable for developer and users. 🌊
Attaching a gif that shows Flow in action.
uploads-ssl.webflow.com/5f73…



























