9

This is what I understand after a quick walk, through the code. Your usage status is checked and updated on the chain only when an action​ is done with your account.( This is intuitive, when I look back, because updating all the account usage statuses periodically will be a huge load on the blockchain) So what you see when you check your usage is the ...


6

EOS account can choose to buy ram or cpu? Can they not buy any at all? You need RAM for the nodes to store data about your account,--including account name, public keys, and other meta-data--in the blockchain state. CPU and NET are needed for executing the transaction that creates your account and storing that transaction on the blockchain, respectively. ...


4

It depends on your understanding of cost. You don't loose an absolute number of tokens. So if you stake 3 token you will receive 3 token back after unstaking. But... What you do pay is some opportunity cost in form of time, because you have to wait 3 days before you can unstake. Another thing you pay is the lets call it inflation cost because of the ...


4

EOS is a specific blockchain implemented using the open source EOSIO software built originally by Block One. EOSIO can be used to create new blockchains with varying degree of changes in many areas -- technical and non-technical. For example, TELOS is such a blockchain based on EOSIO with significant governance tweaks. Similarly, there are other ...


3

You can do that by simply running cleos get account youraccount, also you can check it out in https://eosflare.io Finally, if you want to have a better understanding about EOS RAM and Bandwith check my study here: https://steemit.com/eos/@leordev/eos-ram-and-bandwith-analysis-airdropping-steps-on-junglenet I hope it helps you!


3

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


3

https://eostracker.io - this is the one that I'm using the most, recently, and in my opinion is more accurate There's also this one which I love: https://eosflare.io/


2

Here is what I found: http://core.eostracker.io/ I am still seeking.


2

CPU bandwidth depends on execution time and net bandwidth depends on the transaction size (bytes). The only way to know is to measure, either on the mainnet or on a similarly-loaded testnet. CPU bandwidth will vary between producers. Option A: Run cleos get account and look at the used fields under net bandwidth and cpu bandwidth Issue the transaction Run ...


1

My understand of the way this works is that the first signature that signs the transaction will be charged for the resources of the transaction, but this is only true once BILL_FIRST_AUTH is activated in the code. Once this is done, the payer is whoever is the first authoriser of the transaction, which means that the dApp will have to pre-sign the ...


1

In the EOSIO ecosystem, the CPU, RAM, and NET are all provided to the chain by the block producers. The EOS tokens gives you access to the staking resources (CPU & NET = Bandwidth) which are replenished after an amount of time and then there is RAM (on-chain storage). Keep in mind that developers have to purchase enough RAM to run a smart contract. ...


1

Apart from the official Technical Whitepaper V2, followings are the few documents which were released even before the EOS mainnet launch:- EOS: an Introduction: This describes about the way to reach DPoS consensus mechanism. EOS Multi-signature: This tells you about how to ensure an account (user or contract) with multi-signature feature. EOS: Explanation ...


1

You are not charged for any RPC getter API calls. If you're not forced to sign the transaction, then there's no way to know which account to charge. You're charged if you're changing state or pushing data to the chain.


1

Depends on code if you have set ram payer for multi_indexed table as self then you need to pay for that ram(whenever emplace implemented, No RAM for modifying) and if you have set players as RAM payer then you don't need to pay for RAM. For example in code in this case you became payer of RAM. orders.emplace( self, [&]( auto& o ) { o.id = 1; ...


1

There are some other blockchains in different stages of starting up which are based on the same code base called, EOSIO. Worbli, Telos The main feature required for this type of resource allocation is DPOS and there are not many blockchains with that at their base. This doens't work on a POW blockchain. You can also start a EOSIO private blockchain on ...


1

EOSIO by default has unlimited resources for users until you load the system contract. The bios contract is under the control of the account eosio by default as well which is the key pair that comes in the config.ini. You can read more about these contracts here. You can also see the difference in API calls once the system contract is loaded here.


1

You can now estimate your costs for a transaction by using EOS New York's EOS Charge. Methodology: We use a a MongoDB query that runs hourly and averages the CPU and NET resource costs experienced for every action performed on the EOS Mainnet within the previous 100,000 blocks (13.8 hours) across all Block Producers.


1

There is no tool as such but you can estimate the cost by looking at how are you storing the data (this will tell the estimation about RAM) and how much time does your action take (this will give you the idea about CPU). BTW, This video explains a lot about how to decide the cost estimation. If you get the time, go through the full video. HTH!


1

It depends on the nature of the application actually suppose you have an application to upload a file and read it. Suppose the maximum file size limit you allow in your application is 500 kb then the max_transaction_cpu_usage must be greater than or equal to that limit. I have this smart contract to upload data #include <eosiolib/eosio.hpp> #...


1

RAM is not a constant at 64GB, it is being expanded at a rate of 1KB per block so in a year we will have about double the amount or 128GB. This rate of change could change in the future, it depends on the system contract and to change it there should be a majority of BP voting to change it. Regarding CPU and NET, these are temporal, if they are not ...


1

static const uint32_t account_cpu_usage_average_window_ms = 24*60*60*1000l; static const uint32_t account_net_usage_average_window_ms = 24*60*60*1000l; It's 24 hours. 1000ms = 1s 1s * 60 = 1m 1m * 60 = 1 hr 1 hr * 24 = .. 24 hours.


1

That means payer "safarilion23" has limited CPU usage quota. You should expand "safarilion23"'s CPU quota first.


1

"I am confused about the Token model and Resource Usage the white paper. If I hold 1% of the total tokens, I can use 1% of the total resource. But who guarantees this?" The Block Producers are responsible for making that happen, should they fail to do so and it's recognised they'll be voted out from the community and replaced by another Block Producer in ...


Only top voted, non community-wiki answers of a minimum length are eligible