@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.