a read transaction would be marked as a read and it would be up to each API node to handle that. Read transactions would not be signed therefore could not be billed
🔗 Context 🔗
🔗 Context 🔗
you wouldn't record failrues on accounts that have no resources to charge
Replying to:
> It doesn't address the issue that API nodes are not getting compensated for their services. You can add a record to the blockchain capturing the claim of some block proposer that a particular account has signed and broadcast a transaction to some nodes that eventually made its way to them, and this transaction failed when it reached them. However:
* This does not pay the API provider for the costs of consuming their scarce CPU resources along that upstream path of evaluating the transaction.
* Increases the upstream costs and uses more of the block proposers' scarce CPU resources since now API nodes are expected to forward failed transactions to block proposers so that they can record it on the blockchain as the means of providing feedback to the user (as opposed to just providing that feedback themselves bypassing the blockchain).
* Also, some types of resource failures could still not go on-chain otherwise it opens up an attack vector. Imagine an account with no gas available spamming failed accounts to bloat the blocks with many small records indicating those failures. The account has no gas to consume, so they would not pay any cost for the bloat. To prevent this, a transaction paid by an account without the minimum amount of gas available would still need to be dropped as is done today rather than reported as a failure on the blockchain.
🔗 Context 🔗
Replying to:
> It doesn't address the issue that API nodes are not getting compensated for their services. You can add a record to the blockchain capturing the claim of some block proposer that a particular account has signed and broadcast a transaction to some nodes that eventually made its way to them, and this transaction failed when it reached them. However:
* This does not pay the API provider for the costs of consuming their scarce CPU resources along that upstream path of evaluating the transaction.
* Increases the upstream costs and uses more of the block proposers' scarce CPU resources since now API nodes are expected to forward failed transactions to block proposers so that they can record it on the blockchain as the means of providing feedback to the user (as opposed to just providing that feedback themselves bypassing the blockchain).
* Also, some types of resource failures could still not go on-chain otherwise it opens up an attack vector. Imagine an account with no gas available spamming failed accounts to bloat the blocks with many small records indicating those failures. The account has no gas to consume, so they would not pay any cost for the bloat. To prevent this, a transaction paid by an account without the minimum amount of gas available would still need to be dropped as is done today rather than reported as a failure on the blockchain.
🔗 Context 🔗
From Twitter :
@PhilipChilds_ @VitalikButerin @gofractally @EdenOnEOS I'm not advocating for #EOS governed by ENF. Eden on EOS is an attempt to decentralize the governance of EOS. In any event, @gofractally is actually using decentralized governance.
🔗 Context 🔗
@PhilipChilds_ @VitalikButerin @gofractally @EdenOnEOS I'm not advocating for #EOS governed by ENF. Eden on EOS is an attempt to decentralize the governance of EOS. In any event, @gofractally is actually using decentralized governance.
🔗 Context 🔗
From Twitter :
@TheDEROchan @gofractally If we cannot figure out how to work together without creating incumbent powers that end up ruling without accountability, then nothing will work. That said, I think we need both good governance solutions and good tools for independence from everyone else.
🔗 Context 🔗
@TheDEROchan @gofractally If we cannot figure out how to work together without creating incumbent powers that end up ruling without accountability, then nothing will work. That said, I think we need both good governance solutions and good tools for independence from everyone else.
🔗 Context 🔗
From Twitter :
RT @lexfridman: "Thinking is difficult, that's why most people judge." - Carl Jung
🔗 Context 🔗
RT @lexfridman: "Thinking is difficult, that's why most people judge." - Carl Jung
🔗 Context 🔗
From Twitter :
@vonlooten @andrarchy Main problem with koinos is Pareto distribution of tokens does not match the Pareto distribution of resource use which means most people have to pay someone to delegate and capital costs are too high for “free” mana. This is exasperated by exchanges.
🔗 Context 🔗
@vonlooten @andrarchy Main problem with koinos is Pareto distribution of tokens does not match the Pareto distribution of resource use which means most people have to pay someone to delegate and capital costs are too high for “free” mana. This is exasperated by exchanges.
🔗 Context 🔗
From Twitter :
@WeleleTumblr @vonlooten @andrarchy Given exchanges have 0, I can only assume that the network is only used by a small group of people who all have more tokens than they need. Things change at scale.
🔗 Context 🔗
@WeleleTumblr @vonlooten @andrarchy Given exchanges have 0, I can only assume that the network is only used by a small group of people who all have more tokens than they need. Things change at scale.
🔗 Context 🔗
Bcuaese "to colpime" manes to "usndarnted and purcdoe outupt". Egslnih is ceploimd by poeple who hvae a far mroe ruosbt gamramr maincthg engnie.
Replying to:
> why should it be any different with the English language ?
🔗 Context 🔗
Replying to:
> why should it be any different with the English language ?
🔗 Context 🔗
From Twitter :
@IgnoreRonPaul @PhilipChilds_ @VitalikButerin @gofractally @EdenOnEOS Funding is the expression of economic power and its allocation is a large part of governance.
🔗 Context 🔗
@IgnoreRonPaul @PhilipChilds_ @VitalikButerin @gofractally @EdenOnEOS Funding is the expression of economic power and its allocation is a large part of governance.
🔗 Context 🔗
From Twitter :
@RubenCress Hive is a fork of steem which I happen to believe is a legitimate dpos response to an attack. It was renamed but nevertheless is a continuation and it shows my account as one of the first created.
🔗 Context 🔗
@RubenCress Hive is a fork of steem which I happen to believe is a legitimate dpos response to an attack. It was renamed but nevertheless is a continuation and it shows my account as one of the first created.
🔗 Context 🔗
From Twitter :
@andrarchy @joticajulian @_JamesMart @vonlooten It’s only a problem if you measure the overhead of redistribution of resource rights from those earning them by holding to those using them. It could be done more efficiently with direct fees that are burned.
🔗 Context 🔗
@andrarchy @joticajulian @_JamesMart @vonlooten It’s only a problem if you measure the overhead of redistribution of resource rights from those earning them by holding to those using them. It could be done more efficiently with direct fees that are burned.
🔗 Context 🔗
From Twitter :
@koinosthegoat @hggnooo @joticajulian @vonlooten @andrarchy It’s not about inequality but reducing overhead for sake of performance, reducing costs for all, scale, and ultimately ease of use.
🔗 Context 🔗
@koinosthegoat @hggnooo @joticajulian @vonlooten @andrarchy It’s not about inequality but reducing overhead for sake of performance, reducing costs for all, scale, and ultimately ease of use.
🔗 Context 🔗
From Twitter :
@WeleleTumblr @vonlooten @andrarchy In other words koinos is still theory and we will have to wait for my predictions to play out. Maybe koinos could team up with @gofractally because we share some common ideas and history
🔗 Context 🔗
@WeleleTumblr @vonlooten @andrarchy In other words koinos is still theory and we will have to wait for my predictions to play out. Maybe koinos could team up with @gofractally because we share some common ideas and history
🔗 Context 🔗
From Twitter :
@AmbyR00 @cybermiron @RubenCress @hiveblocks @timberners_lee It was built on bitshares which I created.
🔗 Context 🔗
@AmbyR00 @cybermiron @RubenCress @hiveblocks @timberners_lee It was built on bitshares which I created.
🔗 Context 🔗
From Twitter :
@andrarchy @stamina115 @joticajulian @_JamesMart @vonlooten @gofractally Nothing is truly free to use. As long as you are blind to the true costs you won’t be able to understand the problems.
🔗 Context 🔗
@andrarchy @stamina115 @joticajulian @_JamesMart @vonlooten @gofractally Nothing is truly free to use. As long as you are blind to the true costs you won’t be able to understand the problems.
🔗 Context 🔗
From Twitter :
@stamina115 @andrarchy @joticajulian @_JamesMart @vonlooten Don’t say I didn’t warn you when your network is congested and a meaningful percentage of cpu time and user experience is dealing with buying delegated mana.
🔗 Context 🔗
@stamina115 @andrarchy @joticajulian @_JamesMart @vonlooten Don’t say I didn’t warn you when your network is congested and a meaningful percentage of cpu time and user experience is dealing with buying delegated mana.
🔗 Context 🔗
From Twitter :
One of my biggest mistakes with #EOS was pushing resource management on to app developers. Most app devs didn’t have the experience, time, or desire to host infrastructure necessary to hide resource management from their users.
🔗 Context 🔗
One of my biggest mistakes with #EOS was pushing resource management on to app developers. Most app devs didn’t have the experience, time, or desire to host infrastructure necessary to hide resource management from their users.
🔗 Context 🔗
From Twitter :
@Shawn_Pane The resource model expected app devs to delegate resources to their users and then utilize app level resource limits to prevent abuse. In practice not a single app dev was able to do this and they all expected users to figure out how to get resources.
🔗 Context 🔗
@Shawn_Pane The resource model expected app devs to delegate resources to their users and then utilize app level resource limits to prevent abuse. In practice not a single app dev was able to do this and they all expected users to figure out how to get resources.
🔗 Context 🔗
From Twitter :
@bywirenews Great to hear. Your dedication to solving that is more than most app devs are willing to do. Plus it likely makes things far more centralized than it could be.
🔗 Context 🔗
@bywirenews Great to hear. Your dedication to solving that is more than most app devs are willing to do. Plus it likely makes things far more centralized than it could be.
🔗 Context 🔗