EOS Resource Allocation w/ Daniel Larimer
Why EOS.IO Stack Exchange recommends it
EOS.IO Stack Exchange answerers point people to it as a primary source from Larimer on how staking for CPU/NET and RAM allocation work, including whether staking can be done on behalf of another account.
Recommended by 1 people across 1 different months, 2018 to 2018.
What it is
Daniel Larimer, CTO of block.one, explains how bandwidth (CPU and NET), computation, storage and RAM would be allocated to token holders on a blockchain running the EOS.IO software. It is a short explainer produced by the EOS Go community channel in early 2018, ahead of mainnet launch.
What people said
Recommends Jackson Kelley · 2018-05 · EOS.IO Stack Exchange · on “Staking EOS for bandwidth”
Technically users and dApps are synonymous as far a resource allocation is concerned, similar to Ethereum, where it doesn't matter if the address is a contract or a person, as long as it pays for it's gas. In this video Dan explains the process for resource allocation. [this video] Essentially, bandwidth and CPU are staked for 3 days using a staking contract that will be provided by block.one [LINK] (for both smart contracts and users), and RAM is allocated and paid for in real-time (during this process either the sender or receiver can be charged for this).
Cites expaand · 2018-05 · EOS.IO Stack Exchange · on “Staking on behalf of third party”
I think the answer is "yes". Dan says so in the video: [this video] And if you read the code for the system contract, it has two arguments for staking and unstaking: from and receiver , which can be different. In addition, you can lock out the receiver from unstaking.
Cites Nat · 2018-07 · EOS.IO Stack Exchange · on “How do EOS manage bandwidth or abusing?”
How to prevent account creation abuse: Accounts require "1.5 KB" [LINK] . So this would be one barrier to someone massively creating accounts because they would have to pay for each account. How does deploying contract work: To deploy a contract, it requires a certain amount of RAM for the contract to persist in. You can read a very good example of how an airdrop would look from a resource standpoint to deploy: [LINK] Is fee 0?: Users can execute transfers back and forth freely as long as they have the NET/CPU staked to do so. Think of it like this. You have a pile of 100 EOS. You pay ~1.7 EOS for the RAM to store the account, so you now have 98 EOS. You decide to stake it 46 EOS for NET and
Cites confused00 · 2018-08 · EOS.IO Stack Exchange · on “Understanding the role of bandwidth and resource allocation”
What exactly is a single unit of bandwidth, what’s the difference between net and cpu, how do we determine how much bandwidth we need to perform an action, and how is it priced with demand? Bandwidth is made up of CPU and NET. CPU is computing time measured in microseconds, and NET is data storage measured in bytes. You need NET according to how much space it requires to store your action in the blockchain, and you need CPU according to how much time it takes to the producers to process your action. They're both priced based on the relevant resource supply and the recent demand in the network of said resource. Some information about resource supply for the chain can be found using $ cleos ge