Hot answers tagged

4

From Dan Larimer himself when you asked in the EOS Developer telegram current_time() returns time in microseconds (rounded to block time)


2

eosiolib/* headers are deprecated and will be removed in eosio.cdt v1.7.x. Use eosio/* instead. #include <eosio/system.hpp> time_point_sec current_time_point_sec() { return time_point_sec(current_time_point()); }


2

In EOS contract library, it supports the now() and current_time()method to get the current time, but it only represent the block time and won't be changed during the execution. Yes, because contracts need to be deterministic and output the same result for anyone who replays the blockchain at any point in the future. If it showed the current time, it would ...


1

eosio.cdt doesn't support time library in its libc, so you cannot use time related functions. eoscc, a customized version of eosio.cdt, supports it. (I'm a writer of that) You can check it from here. Use std::strftime instead of std::put_time. put_time needs stream. std::time_t accepts seconds, so do not multiply time_point::sec_since_epoch() with 1000. ...


1

You can use timestamp to have this functionality. You can use now() this function will return you current timestamp(in seconds),you can set your own timestamp with help of this function Let say for example you want to increase timestamp by 24 hour then you can simpally do it by now() + 84600.


1

How about this ? /// @abi action void transfer( account_name from, account_name to, asset quantity, string memo ); ///@abi action void transferf(account_name from, account_name to, asset quantity, string memo, ...


1

The failed transaction will not be attempted again automatically. If you're the dApp owner, you should increase the CPU resources or wait for them to replete and try again. Or better yet, redesign the dApp to make it more efficient if possible.


1

dApp developers don't really need to manage max-transaction-time. This is not the way to plan your dApp. Your share of CPU is determined by your share of the EOS tokens you delegate towards CPU as a percent of total CPU. In case of over capacity, you will enjoy additional CPU processing power. Regarding the unpredictable factors: 21 different CPUs, they ...


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