Hot answers tagged

8

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. https://www.youtube.com/watch?v=N6CTRdx6NVE Essentially, bandwidth and CPU are staked ...


7

CPU is measured in microseconds and your stake determines how many microseconds of time a producer should spend processing transactions from your account. This is measured subjectively by the producer that includes the transaction in the block. Net is measured in bytes and your stake determines what share of a blocks' network representation can be used to ...


7

1) what is a stake? Staking is the process of locking your tokens for a fixed period of time. On mainnet, at the moment, this period is at least three days. 2) after making a stake, what cpu and ram gets used? it's said that after staking , you are using block producer's cpu and ram's resources. how am i using their resources at all? When you stake, you ...


6

Via the Developers Portal When adding a entry... orders.emplace( payer, [&]( auto& o ) { o.id = 1; o.expiration = 300; o.owner = N(dan); }); The first parameter payer is the account who pays the bill. When modifying an entry... orders.modify( order2, payer, [&]( auto& o ) { o.expiration = 400; }); Payer is the second argument, ...


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

Update 4/2019: You can use AirdropsDac vRAM enabled service: https://airdropsdac.com/ Recently they launched the Emanate token with this setup: https://medium.com/@airdropsdac/claim-your-emanate-emt-tokens-b24484e84a0e vRAM provides a caching layer for the current RAM system. It works much in the same sense as RAM and a DISK work on a normal PC. RAM is ...


4

Once the EOS are unstaked you issue the 'refund' command to return them to their liquid state. ./cleos push action eosio refund '{"owner": "youraccountname"}' -p youraccountname


4

The economic purpose of staking is to provably commit to a promise that you won't sell the staked tokens for a pre-established period of time. This means that you undertake the duty of holding your tokens through the process of inflation as BPs mint more coins as a reward for their services. Therefore, staking is how you pay the producers for offering ...


3

To the best of my understanding, the EOS system allows users to interact with smart contracts, but in order for this interaction to occur, the contract needs to have enough CPU power and bandwidth to accept the user's actions and then process them. This is the reason that staking tokens is important. The tokens in the system indicate the share of resources ...


3

Yes, all contracts have their own account, the same account a person would have. If you want to deploy a contract for public consumption you would create an account for it, then deploy a contract onto it.


2

Below is the documentation for undelegating bandwidth. I'd assume the command would look like below: cleos system undelegatebw FROM RECEIVER unstake_net_quantity unstake_cpu_quantity system undelegatebw Undelegate bandwidth Positional Arguments from TEXT - The account undelegating bandwidth receiver TEXT - The account to undelegate bandwidth from ...


2

EOS is designed to allow developers creating new business models. Maybe this part of the whitepaper helps you. Delegating Capacity A holder of tokens on a blockchain launched adopting the EOS.IO software who may not have an immediate need to consume all or part of the available bandwidth, can delegate or rent such unconsumed bandwidth to others;...


2

Q1. Can my CPU usage shrinks when I executed transfer commands? If can, how can I know when is that time? Your CPU usage resets after an average of 24 hours. How long is the reset period of the cpu bandwith? Q2. What "claim their tokens" means in dan says? Dan means that once people move their tokens, they'll become the payer of the account balance ...


2

Are the block producers restricted from staking a significant amount of their EOS tokens? No. I think @confused00 is right, EOS is the income for BPs, so they leave it liquid to pay for their operating costs.


1

The wait time for CPU and BET bandwidth to reset is 24 hours, not 72 hours. You have to stake EOS to your account in order to use it. CPU allows you to perform actions and NET is for transferring of data over the network. The bandwidth you have at any moment fluctuates, as although you are guaranteed a fixed amount of CPU time for a given amount of staked ...


1

You cannot get around the unstaking process if all of your EOS is staked on both accounts. With that being said, if you have liquid EOS on another account, you can stake that EOS to another account: cleos system delegatebw from_this_account to_this_account "1 EOS" "1 EOS" Args: from TEXT - The account delegating bandwidth receiver TEXT - The account to ...


1

There is no single "central" server in a decentralized project like EOS.IO. All block producers, active or standby, maintain the same database containing everyone's votes on block producers. Simplifying a bit, at any moment, the 21 block producers with the most votes are active, and the others are standby. Any vote change is a transaction, it must be signed ...


1

That's a test function that helps making sure the stake2vote() works as intended. The stake2vote() function fromcontracts/eosio.system/voting.cpp is as follows: double stake2vote( int64_t staked ) { double weight = int64_t( (now() - (block_timestamp::block_timestamp_epoch / 1000)) / (seconds_per_day * 7) ) / double( 52 ); return double(staked) * std:...


1

I have found a solution to my problem. The problem was caused by the fact that the delegatebw function implicitly calls the transfer function from the contract to the receiver. This, combined with the fact that we have a listening function that waits for transfers to occur and doesn't distinguish between transfers to the account and transfers ...


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

I'm actually guessing with this answer so vote down if you think it's bad! My theory is that it doesn't go straight back into your balance and instead into a Refund section because the EOS is not actually in your account but in a smart contract which holds your EOS in escrow. This is because it costs CPU & bandwidth to refund the EOS which is ...


1

If B delegated to A without transfer, and B wants their stake back: cleos wallet unlock -n walletwithactivekeyforaccountB (enter related password to unlock wallet) cleos system undelegatebw B A "0.0000 EOS" "10.0000 EOS" -p B@active BOOM! That's It! But it is not instant! By design, it will take 3 days to unstake.


1

June 28th 17:39 UTC (Math) According to EOS Authority, the exact Birthdate of EOS is 14 Jun 17:39 UTC. I then added 14 days to that


1

ANSWER TAKEN FROM: https://np.reddit.com/r/eos/comments/8hmpj0/ram_trading/dyl6r5g/ When you "buy" ram you stake for it, using eos, which locks it up while you have the ram. You pay a price determined by the system based on the current % of ram in use (staked for by others). You pay a 1% eos fee when doing this. Later, when you unstake your ram, ...


1

Staked and delegated both assume the same staked status of the SYS token in this case. Staked assumes that you reserve the ability to vote on producers. Delegated assumes that you elect what is known as a "proxy" to vote on your behalf. This logic can be seen in the eosio.system.hpp /** * Total vote weight delegated to this voter. */ double ...


1

I think the answer is "yes". Dan says so in the video: https://www.youtube.com/watch?v=N6CTRdx6NVE 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.


1

When the threshold is achieved. This can be easily confirmed by a post from Thomas Cox (VP of Product for block.one) entitled "Magic 15%-Unlocking the EOSIO Blockchain" Here, Cox states "And even after we hit 15% and the “unstake” command becomes available, it takes three days for unstaking of tokens used for CPU or bandwidth. So relax. Even if we hit 15% ...


1

When you vote your tokens are staked for 3 days. If the exchanges were to use the users's funds to vote, these tokens would get staked (essentially frozen, unmovable) and they run the risk of not having enough tokens should people want to withdraw their tokens. So while it is theoretically and practically possible for exchanges to use the users's funds to ...


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