Hoang S.C.A.M FUD (❖,❖) (hoangstephen)

2,025 free Christmas NFTs are on the way for the Top 2,025 gift openers. Stay in the Top 2,025 when Season 1 ends to secure yours

• 0 replies
• 0 recasts
• 0 reactions

@cityprotocol.base.eth, join_base_city, I TRADE

• 0 replies
• 0 recasts
• 1 reaction

@cityonbase , join_base_city, I TRADE

• 0 replies
• 0 recasts
• 1 reaction

Day 3 with Siggy Teacher ! From Gas Markets to Compute Markets In Ritual’s framing, any decentralized compute system has two sides: *Users submit requests: transactions, proofs, AI inferences, oracle queries, batch jobs. *Nodes supply compute: validators, provers, oracle nodes, GPU operators, AI servers. For every request, there is a valuation – the maximum a user is willing to pay to have it processed. For every node, there is a cost the minimum it needs to be paid to execute work sustainably. A good protocol must decide two things: 1. Allocation which requests get served, and by which nodes, under all the technical constraints of the system. 2. Pricing & payment how much each user pays, and how much each node earns. Ritual sets three ambitious goals for this marketplace: *Maximize welfare choose allocations that generate the highest total economic value. *Zero protocol margin the protocol itself does not extract rent from the spread between what users pay and what nodes receive. *Individual rationality every user and node that participates is at least as well off as if they stayed out of the market. And it wants to achieve all of this while presenting simple, posted prices to users not gas auctions or bidding games .

• 5 replies
• 0 recasts
• 12 reactions

Day 4 with Siggy Teacher Resonance and Heterogeneous Compute Ritual’s block building and fee mechanism, Resonance, is already designed to handle heterogeneous compute: *Many different types of workloads (LLM calls, proofs, data queries, etc.). *Many different types of nodes with different capabilities and constraints. *Complex relationships between requests (conflicts, dependencies, batching, redundancy). The blog on Markets for Decentralized Computation takes this one step further. It generalizes Resonance into a posted-price mechanism that can, in principle, apply to any decentralized compute market not just AI inference on Ritual.

• 7 replies
• 1 recast
• 11 reactions

Day 5 with Siggy Teacher : Market Makers Instead of User Bidding Traditional gas markets ask users to bid. Whoever pays more gets priority. That’s bad UX, and it puts the burden of price discovery on the least informed participants. Ritual flips this. Instead of forcing users and nodes to bid directly, the system introduces a new class of actors: compute market-makers. These market-makers are sophisticated participants that: *Propose allocations how to route requests to nodes given all constraints. *Design pricing schemes what each user should pay and each node should receive. *Commit to tolerance ranges how much they’re willing to adjust prices up or down while still staying profitable. The protocol doesn’t try to “out-think” them. It simply runs a meta level rule to select the best proposal among competing market makers, based on clear improvement criteria. From the user’s perspective, this complexity disappears. They see fixed, transparent prices for the compute services they want.

• 7 replies
• 1 recast
• 13 reactions