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 smart-contract
Search options not deleted
user 1216
Anything related to decentralized application (dApp) development, concepts, and possibilities with smart contracts, or technical questions for the development of smart contracts.
1
vote
2
answers
1k
views
in the system contract, what is required for require_auth(_self)
In the system contract (eosio_system.cpp) there are some functions which require
require_auth( _self );
How is this auth level achieved by the 21 producers?
9
votes
Accepted
in the system contract, what is required for require_auth(_self)
The _self auth, shown here
require_auth( _self );
requires the authority of the owner of the contract, in this case eosio. If we inspect that account with get account we see this
owner 1: …