https://twitter.com/bytemaster7/status/1552716410455031811 something to consider for improving EOS resource model

🔗 Context 🔗

This is not spam. It is my ideas on how to improve resoruce billing

🔗 Context 🔗

looks like we arrived at the same conclusion independently

Replying to:
> I'm glad you like the idea to bill for failed txs that I posted a few days ago.

🔗 Context 🔗

you cannot stop people from flocking to the toll roads to drive up the cost of a parade

🔗 Context 🔗

sure, someone could spend their own money to spam the network in order to force others to pay more

🔗 Context 🔗

but that isn't a profitable exersize

🔗 Context 🔗

its just fast typing my friend.

🔗 Context 🔗

did you understand what I was saying?

🔗 Context 🔗

Even if you put an expiration on the gift card people could wait to buy the gift card until right when they want to spam

🔗 Context 🔗

there is nothing that prevents people from using contract-for-difference arrangements to hedge against resource price changes

🔗 Context 🔗

why pay the ransom when you could just spend the same money on fees

🔗 Context 🔗

deferred transactions are deprecated

🔗 Context 🔗

or they could be implimented by doing a bounty on a multisig and the person who executed the multisig gets the bounty

🔗 Context 🔗

Judge a man by his spelling will you? I blame auto-correct for allowing frequent mispellings to go by unnoticed resulting in bad muscle memory being developed which then expresses itself when typing quickly.

🔗 Context 🔗

i and e are just mirrored motions. Signal to left/right hands can get crossed when in a hurry

Replying to:
> E and I are really not close to eachother, at all

🔗 Context 🔗

From Twitter :
@kaktaka123 @Blondin5555 @gofractally @VitalikButerin Funny, Vitalik doesn't think I'm a scammer. How do you square that?

🔗 Context 🔗

From Twitter :
@IgnoreRonPaul @gofractally @VitalikButerin Too much overhead and requires the cooperation of a 3rd party rather than just being built into the chain. I think it is a much-needed patch for the current way #EOS is working, but we can do better.

🔗 Context 🔗

From Twitter :
This is why @gofractally uses true meritocracy with the most democratic, Sybil resistant, government-id-free, system to allocate power to those who reliably contribute the most value to the public good as judged by a random jury of peers each week.

🔗 Context 🔗

From Twitter :
@PhilipChilds_ @VitalikButerin Have you checked out @gofractally and @EdenOnEOS where we solve true democracy, political parties, incumbent advantage, and Sybil attacks and rewarding people for subjective contributions? The wisdom of the crowds is tapped. Traditional voting is broken by ballot selection rules.

🔗 Context 🔗

there is no need to try to execute the failed transaction. Just read the CPU time and bill and move on

Replying to:
> I'm aligned with most of it, but billing for failed transactions on-chain is the one part I did not like.

There is no need to burden all validators of the chain with each of these micro-costs. Especially when you consider that a read-only transaction can be thought of as a "failed transaction". Furthermore, the resources of a handful of nodes (along the upstream path) are expended trying to execute a failed transaction but billing on-chain for this failed transaction isn't necessarily paying the operators of these nodes. It may socialize the profits across the whole network despite the costs privatized to the API nodes.

The UX with the current subject/shadow billing is bad. That needs to be improved IMO by making it transparent, provide better and immediate feedback of failure along the upstream path to the originator of the transaction, and make all of this accessible as part of standard APIs usable by wallets and apps. But I do believe the accounting should remain local to each API provider since this aligns the economic incentives properly. And while ultimately settlement of the bill with API providers does need to go on-chain, it can be aggregated (via micropayment channels) to not put excessive burden on the scarce resources of the blockchain.

🔗 Context 🔗