Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with eosio.token
Search options questions only
not deleted
user 151
Questions related to the system contract for storing the EOS token
2
votes
2
answers
1k
views
Is "cleos transfer" just a shortcut for "cleos push action eosio.token transfer"?
It seems that, whenever we want to write:
cleos transfer account11111 account22222 "0.0001 EOS" "memo text"
We could also write instead:
cleos push action eosio.token transfer '{"from": "account11111 …
- 598
1
vote
1
answer
146
views
In the eosio.token contract, why are the structs private?
::accounts from the eosio.token contract. … The problem is that, in the official eosio.token contract, this type is private, so my code above does not compile.
So, instead of just an #include "... …
- 598