I don’t mean to bring any contention to this forum, or make this thread about ‘technical’ vs. ‘social’ paradigms.
I never implied price doesn’t matter, of course it does. I meant simply that there is a very important difference between intrinsic value and market valuation.
The ephemeral attention of an increasingly fickle crypto community often distorts the bigger picture. It’s easy to get swept up by price fluctuations and short-term hype, but in the long run, the most robust and innovative technologies will prevail. In my experience, the crypto community today tends to overlook what truly sustains a blockchain in the long run: the strength of its underlying technology.
Blockchains with robust consensus mechanisms, scalability, decentralization, and strong developer ecosystems will outlast the hype.
You actually make my point for me here with regards to measures of success. Do I equate rapid short-term growth to “success”? Thankfully, no.
Solana did some impressive things when building their blockchain and its PoH and Tx mechanisms. What the crypto community did with their blockchain is another story altogether.
What’s written to a blockchain today is just a prelude. The real story unfolds in the next five to ten years, when real-world use cases mature and the market weeds out projects that lack meaningful utility. Blockchain as a whole hasn’t even scratched the surface of its potential. This current era—dominated by speculative tokens and meme coins—is simply a phase. Whether Solana is going to be the blockchain equivalent of Netscape or Google remains to be seen, and only a fool would claim that they know otherwise.
@EovE7Kj is a zApp deployed to all sentinels? If this is the case how do you orchestrator which sentinel will run the SC code and which ones verifies it?
Or will a zApp developer host the zApp themself on their own sentinel (or maybe on a hosting provider’s sentinel)? Then that sentinel will pass the output to others to verify. If those other sentinels don’t host the zApp I assume the SC itself will have some way for other sentinels to verify the output of the zApp run on another sentinel.
I’m trying to create a simple thread on X and want to make sure I understand this correctly.
@EovE7Kj can you please elaborate on the “fee” mechanism to interact with SC on NoM. Which one of these statements is true (based on your latest design ideas)?
A SC user will pay a “fee” in the form of qas (a fraction of QSR) to interact with a Smart Contract. A “fee” in this case is a cost, like gas in ethereum. It will NOT be fused and returned. The qas will exchange from one party to another. Presumably from the user to the Sentinel that runs the zApp.
A SC user will pay a “fee” in the form of qas by fusing QSR. After the SC runs the qas will be returned to the party that fuses it.
We are getting confused by the word “fee”. This word appears in the WP (or a variation of it). I think the WP implies SC require a fee that is NOT fused and returned. But we are really not sure.