7

It is all based upon Web Assembly specification which I believe is 32 bit at this time. https://github.com/sunfishcode/wasm-reference-manual/blob/master/WebAssembly.md


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

Just add a created_at field to your table. struct blog { uint64_t id; time created_at; uint64_t primary_key()const { return id; } EOSLIB_SERIALIZE(blog, (id)(created_at)) } typedef multi_index<N(blog), blog> blog_index; blog_index blogs; When creating a record, set created_at to now(). blogs.emplace(_self, [&](auto& x) { ...


3

The scope can be used to narrow down a table list to contain only some fraction of the total entries available. However, you can also have the best of both worlds if you are willing to pay for the RAM involved. Why not create a scope called global, which contains all of the entries from each individual scope, or alternatively contains a list of each scope ...


3

Does anyone have the definition of scope ? To me, it basically looks like a way to compartmentalize data in a contract so that it only accessible within a certain space. In the above example, the data account balance and friends will exist in the contract only for the matching username given. When a different username is given as the scope, a new account ...


3

By using the scope you can have easier fetches. Think of it like the exact index you are searching for without have to use upper/lower bounds. If we take that same logic to a user's info we could do cleos get table contract username account cleos get table contract username balance cleos get table contract username friends instead of cleos get table ...


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