{"id":7698,"date":"2025-01-24T03:38:49","date_gmt":"2025-01-24T02:38:49","guid":{"rendered":"https:\/\/wsj-crypto.com\/?p=7698"},"modified":"2025-01-24T03:38:49","modified_gmt":"2025-01-24T02:38:49","slug":"unlocking-error-handling-in-solidity-0-6-x-the-power-of-try-catch-statements","status":"publish","type":"post","link":"https:\/\/wsj-crypto.com\/index.php\/2025\/01\/24\/unlocking-error-handling-in-solidity-0-6-x-the-power-of-try-catch-statements\/","title":{"rendered":"Unlocking Error Handling in Solidity 0.6.x: The Power of Try\/Catch Statements"},"content":{"rendered":"\n
\n

The try\/catch syntax unveiled in 0.6.0<\/a> is arguably the most significant advancement in error management functionalities in Solidity, since reason strings for revert<\/span> and require<\/span> were introduced in v0.4.22. Both try<\/span> and catch<\/span> have been designated keywords since v0.5.9<\/a> and now we can leverage them to manage failures in external<\/span> function transactions without reverting the entire transaction (state changes in the invoked function are still reverted, but those in the invoking function are preserved).<\/p>\n

<\/p>\n

We are taking a step away from the strict “all-or-nothing” paradigm in a transaction lifecycle, which often does not align with the practical behaviour we usually desire.<\/p>\n

<\/p>\n

Managing external call failures<\/h2>\n

<\/p>\n

The try\/catch statement enables you to respond to unsuccessful external<\/em> calls and contract creation<\/em> attempts, hence it cannot be utilized for internal<\/em> function calls. Keep in mind that to enclose a public function call within the same contract with try\/catch, it can be executed externally by invoking the function with this.<\/span>.<\/p>\n

<\/p>\n

The illustration below shows how try\/catch is implemented in a factory model where contract creation may encounter failure. The following CharitySplitter<\/span> contract necessitates a required address attribute _owner<\/span> in its constructor.<\/p>\n

<\/p>\n

\n
pragma solidity ^0.6.1<\/span>;<\/span>\n<\/span>\ncontract CharitySplitter <\/span>{<\/span>\n<\/span>    address public owner<\/span>;<\/span>\n<\/span>    constructor <\/span>(<\/span>address _owner<\/span>)<\/span> public <\/span>{<\/span>\n<\/span>        require<\/span>(<\/span>_owner <\/span>!=<\/span> address<\/span>(<\/span>0<\/span>)<\/span>, <\/span>\"no-owner-provided\"<\/span>)<\/span>;<\/span>\n<\/span>        owner <\/span>=<\/span> _owner<\/span>;<\/span>\n<\/span>    <\/span>}<\/span>\n<\/span>}<\/span>\n<\/span><\/code><\/pre>\n<\/div>\n
<\/p>\n
There exists a factory contract \u2014 CharitySplitterFactory<\/span> which facilitates the creation and oversight of instances of CharitySplitter<\/span>. Within the factory, we can encapsulate the new CharitySplitter(charityOwner)<\/span> within a try\/catch as a precaution in case that constructor fails due to an absent charityOwner<\/span>.<\/p>\n
<\/p>\n
\n
pragma solidity ^0.6.1<\/span>;<\/span>\n<\/span>import<\/span> <\/span>\".\/CharitySplitter.sol\"<\/span>;<\/span>\n<\/span>contract CharitySplitterFactory <\/span>{<\/span>\n<\/span>    mapping <\/span>(<\/span>address <\/span>=<\/span>><\/span> CharitySplitter<\/span>)<\/span> public charitySplitters<\/span>;<\/span>\n<\/span>    uint public errorCount<\/span>;<\/span>\n<\/span>    event ErrorHandled<\/span>(<\/span>string reason<\/span>)<\/span>;<\/span>\n<\/span>    event ErrorNotHandled<\/span>(<\/span>bytes reason<\/span>)<\/span>;<\/span>\n<\/span>    <\/span>function<\/span> createCharitySplitter<\/span>(<\/span>address charityOwner<\/span>)<\/span> public <\/span>{<\/span>\n<\/span>        try new CharitySplitter<\/span>(<\/span>charityOwner<\/span>)<\/span>\n<\/span>            returns <\/span>(<\/span>CharitySplitter newCharitySplitter<\/span>)<\/span>\n<\/span>        <\/span>{<\/span>\n<\/span>            charitySplitters<\/span>[<\/span>msg.sender<\/span>]<\/span> <\/span>=<\/span> newCharitySplitter<\/span>;<\/span>\n<\/span>        <\/span>}<\/span> catch <\/span>{<\/span>\n<\/span>            errorCount++<\/span>;<\/span>\n<\/span>        <\/span>}<\/span>\n<\/span>    <\/span>}<\/span>\n<\/span>}<\/span>\n<\/span><\/code><\/pre>\n<\/div>\n
<\/p>\n
Please note that within try\/catch, only exceptions that occur inside the external invocation itself are captured. Issues occurring within the expression are not captured; for instance, if the input parameter for the new CharitySplitter<\/span> is a part of an internal call, any issues it generates will not be captured. An example illustrating this behavior is the altered createCharitySplitter<\/span> function. In this instance, the CharitySplitter<\/span> constructor input parameter is sourced dynamically from another function \u2014 getCharityOwner<\/span>. If that function fails, in this case with “revert-required-for-testing”<\/span>, that will not be captured in the try\/catch block.<\/p>\n
<\/p>\n
\n
function<\/span> createCharitySplitter<\/span>(<\/span>address _charityOwner<\/span>)<\/span> public <\/span>{<\/span>\n<\/span>    try new CharitySplitter<\/span>(<\/span>getCharityOwner<\/span>(<\/span>_charityOwner, <\/span>false<\/span>))<\/span>\n<\/span>        returns <\/span>(<\/span>CharitySplitter newCharitySplitter<\/span>)<\/span>\n<\/span>    <\/span>{<\/span>\n<\/span>        charitySplitters<\/span>[<\/span>msg.sender<\/span>]<\/span> <\/span>=<\/span> newCharitySplitter<\/span>;<\/span>\n<\/span>    <\/span>}<\/span> catch <\/span>(<\/span>bytes memory reason<\/span>)<\/span> <\/span>{<\/span>\n<\/span>        <\/span>..<\/span>.\n<\/span>    <\/span>}<\/span>\n<\/span>}<\/span>\n<\/span>function<\/span> getCharityOwner<\/span>(<\/span>address _charityOwner, bool _toPass<\/span>)<\/span>\n<\/span>        internal returns <\/span>(<\/span>address<\/span>)<\/span> <\/span>{<\/span>\n<\/span>    require<\/span>(<\/span>_toPass, <\/span>\"revert-required-for-testing\"<\/span>)<\/span>;<\/span>\n<\/span>    <\/span>return<\/span> _charityOwner<\/span>;<\/span>\n<\/span>}<\/span>\n<\/span><\/code><\/pre>\n<\/div>\n
<\/p>\n
Retrieving the error message<\/h2>\n
<\/p>\n
We can further enhance the try\/catch mechanism within the createCharitySplitter<\/span> function to obtain the error message if one was triggered by a failing revert<\/span> or require<\/span> and emit it in an event. There are two methods to accomplish this:<\/p>\n
<\/p>\n
1. Using catch Error(string memory reason)<\/span><\/h3>\n
<\/p>\n
\n
function<\/span> createCharitySplitter<\/span>(<\/span>address _charityOwner<\/span>)<\/span> public <\/span>{<\/span>\n<\/span>    try new CharitySplitter<\/span>(<\/span>_charityOwner<\/span>)<\/span> returns <\/span>(CharitySplitter newCharitySplitter<\/span><\/span>)<\/span>\n<\/span>    <\/span>{<\/span>\n<\/span>        charitySplitters<\/span>[<\/span>msg.sender<\/span>]<\/span> <\/span>=<\/span> newCharitySplitter<\/span>;<\/span>\n<\/span>    <\/span>}<\/span>\n<\/span>    catch Error<\/span>(<\/span>string memory reason<\/span>)<\/span>\n<\/span>    <\/span>{<\/span>\n<\/span>        errorCount++<\/span>;<\/span>\n<\/span>        CharitySplitter newCharitySplitter <\/span>=<\/span> new\n<\/span>            CharitySplitter<\/span>(<\/span>msg.sender<\/span>)<\/span>;<\/span>\n<\/span>        charitySplitters<\/span>[<\/span>msg.sender<\/span>]<\/span> <\/span>=<\/span> newCharitySplitter<\/span>;<\/span>\n<\/span>        \/\/ Emitting the error <\/span>in<\/span> event\n<\/span>        emit ErrorHandled<\/span>(<\/span>reason<\/span>)<\/span>;<\/span>\n<\/span>    <\/span>}<\/span>\n<\/span>    catch\n    <\/span>{<\/span>\n<\/span>        errorCount++<\/span>;<\/span>\n<\/span>    <\/span>}<\/span>\n<\/span>}<\/span>\n<\/span><\/code><\/pre>\n<\/div>\n
<\/p>\n
Which triggers the subsequent event on a failed constructor require error:<\/p>\n
<\/p>\n
\n
CharitySplitterFactory.ErrorHandled<\/span>(<\/span>\n<\/span>    reason: <\/span>'no-owner-provided'<\/span> <\/span>(<\/span>type: string<\/span>)<\/span>\n<\/span>)<\/span>\n<\/span><\/code><\/pre>\n<\/div>\n
<\/p>\n
2. Using catch (bytes memory reason)<\/span><\/h3>\n
<\/p>\n
\n
function<\/span> createCharitySplitter<\/span>(<\/span>address charityOwner<\/span>)<\/span> public <\/span>{<\/span>\n<\/span>    try new CharitySplitter<\/span>(<\/span>charityOwner<\/span>)<\/span>\n<\/span>        returns <\/span>(<\/span>CharitySplitter newCharitySplitter<\/span>)<\/span>\n<\/span>    <\/span>{<\/span>\n<\/span>        charitySplitters<\/span>[<\/span>msg.sender<\/span>]<\/span> <\/span>=<\/span> newCharitySplitter<\/span>;<\/span>\n<\/span>    <\/span>}<\/span>\n<\/span>    catch <\/span>(<\/span>bytes memory reason<\/span>)<\/span> <\/span>{<\/span>\n<\/span>        errorCount++<\/span>;<\/span>\n<\/span>        emit ErrorNotHandled<\/span>(<\/span>reason<\/span>)<\/span>;<\/span>\n<\/span>    <\/span>}<\/span>\n<\/span>}<\/span>\n<\/span><\/code><\/pre>\n<\/div>\n
<\/p>\n
This emits the subsequent event during a failed constructor require mistake:<\/p>\n
<\/p>\n
\n
CharitySplitterFactory.ErrorNotHandled<\/span>(<\/span>\n<\/span>  reason: hex<\/span>'08c379a0000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000116e6f2d6f776e65722d70726f7669646564000000000000000000000000000000'<\/span> <\/span>(<\/span>type: bytes<\/span>)<\/span>\n<\/span><\/code><\/pre>\n<\/div>\n
<\/p>\n
The preceding two approaches for obtaining the error string yield a comparable outcome. The distinction is that the latter method does not ABI-decode the error string. The benefit of the latter method is that it also executes if ABI decoding the error string is unsuccessful or if no reason was supplied.<\/p>\n
<\/p>\n
Future intentions<\/h2>\n
<\/p>\n
There are intentions to introduce support for error categories, meaning we will be able to declare errors in a way similar to events, enabling us to catch various types of errors, for instance:<\/p>\n
<\/p>\n
\n
catch CustomErrorA<\/span>(<\/span>uint data1<\/span>)<\/span> <\/span>{<\/span> \u2026 <\/span>}<\/span>\n<\/span>catch CustomErrorB<\/span>(<\/span>uint<\/span>[<\/span>]<\/span> memory data2<\/span>)<\/span> <\/span>{<\/span> \u2026 <\/span>}<\/span>\n<\/span>catch <\/span>{<\/span>}<\/span>\n<\/span><\/code><\/pre>\n<\/div>\n<\/div>\n

\n
Source link <\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
The try\/catch syntax unveiled in 0.6.0 is arguably the most significant advancement in error management functionalities in Solidity, since reason strings for revert and require were introduced in v0.4.22. Both try and catch have been designated keywords since v0.5.9 and now we can leverage them to manage failures in external function transactions without reverting the<\/p>\n","protected":false},"author":3,"featured_media":7699,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[23],"tags":[981],"class_list":["post-7698","post","type-post","status-publish","format-standard","has-post-thumbnail","category-ethereum","tag-return-a-list-of-comma-separated-tags-from-this-title-solidity-0-6-x-features-try-catch-statement"],"yoast_head":"\nUnlocking Error Handling in Solidity 0.6.x: The Power of Try\/Catch Statements - WSJ-Crypto<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/wsj-crypto.com\/index.php\/2025\/01\/24\/unlocking-error-handling-in-solidity-0-6-x-the-power-of-try-catch-statements\/\" \/>\n<meta property=\"og:locale\" content=\"it_IT\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Unlocking Error Handling in Solidity 0.6.x: The Power of Try\/Catch Statements - WSJ-Crypto\" \/>\n<meta property=\"og:description\" content=\"The try\/catch syntax unveiled in 0.6.0 is arguably the most significant advancement in error management functionalities in Solidity, since reason strings for revert and require were introduced in v0.4.22. Both try and catch have been designated keywords since v0.5.9 and now we can leverage them to manage failures in external function transactions without reverting the\" \/>\n<meta property=\"og:url\" content=\"https:\/\/wsj-crypto.com\/index.php\/2025\/01\/24\/unlocking-error-handling-in-solidity-0-6-x-the-power-of-try-catch-statements\/\" \/>\n<meta property=\"og:site_name\" content=\"WSJ-Crypto\" \/>\n<meta property=\"article:published_time\" content=\"2025-01-24T02:38:49+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/wsj-crypto.com\/wp-content\/uploads\/2025\/01\/solidity-logo.svg.svg+xml\" \/>\n\t<meta property=\"og:image:width\" content=\"1\" \/>\n\t<meta property=\"og:image:height\" content=\"1\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"wsjcrypto\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Scritto da\" \/>\n\t<meta name=\"twitter:data1\" content=\"wsjcrypto\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tempo di lettura stimato\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 minuti\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/wsj-crypto.com\/index.php\/2025\/01\/24\/unlocking-error-handling-in-solidity-0-6-x-the-power-of-try-catch-statements\/\",\"url\":\"https:\/\/wsj-crypto.com\/index.php\/2025\/01\/24\/unlocking-error-handling-in-solidity-0-6-x-the-power-of-try-catch-statements\/\",\"name\":\"Unlocking Error Handling in Solidity 0.6.x: The Power of Try\/Catch Statements - WSJ-Crypto\",\"isPartOf\":{\"@id\":\"https:\/\/wsj-crypto.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/wsj-crypto.com\/index.php\/2025\/01\/24\/unlocking-error-handling-in-solidity-0-6-x-the-power-of-try-catch-statements\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/wsj-crypto.com\/index.php\/2025\/01\/24\/unlocking-error-handling-in-solidity-0-6-x-the-power-of-try-catch-statements\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/wsj-crypto.com\/wp-content\/uploads\/2025\/01\/solidity-logo.svg.svg+xml\",\"datePublished\":\"2025-01-24T02:38:49+00:00\",\"author\":{\"@id\":\"https:\/\/wsj-crypto.com\/#\/schema\/person\/88a93723b30416db1a352d5a0096c4a7\"},\"breadcrumb\":{\"@id\":\"https:\/\/wsj-crypto.com\/index.php\/2025\/01\/24\/unlocking-error-handling-in-solidity-0-6-x-the-power-of-try-catch-statements\/#breadcrumb\"},\"inLanguage\":\"it-IT\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/wsj-crypto.com\/index.php\/2025\/01\/24\/unlocking-error-handling-in-solidity-0-6-x-the-power-of-try-catch-statements\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"it-IT\",\"@id\":\"https:\/\/wsj-crypto.com\/index.php\/2025\/01\/24\/unlocking-error-handling-in-solidity-0-6-x-the-power-of-try-catch-statements\/#primaryimage\",\"url\":\"https:\/\/wsj-crypto.com\/wp-content\/uploads\/2025\/01\/solidity-logo.svg.svg+xml\",\"contentUrl\":\"https:\/\/wsj-crypto.com\/wp-content\/uploads\/2025\/01\/solidity-logo.svg.svg+xml\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/wsj-crypto.com\/index.php\/2025\/01\/24\/unlocking-error-handling-in-solidity-0-6-x-the-power-of-try-catch-statements\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/wsj-crypto.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Unlocking Error Handling in Solidity 0.6.x: The Power of Try\/Catch Statements\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/wsj-crypto.com\/#website\",\"url\":\"https:\/\/wsj-crypto.com\/\",\"name\":\"WSJ-Crypto\",\"description\":\"Just Another Crypto News Website\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/wsj-crypto.com\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"it-IT\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/wsj-crypto.com\/#\/schema\/person\/88a93723b30416db1a352d5a0096c4a7\",\"name\":\"wsjcrypto\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"it-IT\",\"@id\":\"https:\/\/wsj-crypto.com\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/86fe8af82ea089646d6639ca2f87e0243d8688d957bd8e3ec22ec3c457cc16d4?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/86fe8af82ea089646d6639ca2f87e0243d8688d957bd8e3ec22ec3c457cc16d4?s=96&d=mm&r=g\",\"caption\":\"wsjcrypto\"},\"url\":\"https:\/\/wsj-crypto.com\/index.php\/author\/wsjcrypto\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Unlocking Error Handling in Solidity 0.6.x: The Power of Try\/Catch Statements - WSJ-Crypto","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/wsj-crypto.com\/index.php\/2025\/01\/24\/unlocking-error-handling-in-solidity-0-6-x-the-power-of-try-catch-statements\/","og_locale":"it_IT","og_type":"article","og_title":"Unlocking Error Handling in Solidity 0.6.x: The Power of Try\/Catch Statements - WSJ-Crypto","og_description":"The try\/catch syntax unveiled in 0.6.0 is arguably the most significant advancement in error management functionalities in Solidity, since reason strings for revert and require were introduced in v0.4.22. Both try and catch have been designated keywords since v0.5.9 and now we can leverage them to manage failures in external function transactions without reverting the","og_url":"https:\/\/wsj-crypto.com\/index.php\/2025\/01\/24\/unlocking-error-handling-in-solidity-0-6-x-the-power-of-try-catch-statements\/","og_site_name":"WSJ-Crypto","article_published_time":"2025-01-24T02:38:49+00:00","og_image":[{"url":"https:\/\/wsj-crypto.com\/wp-content\/uploads\/2025\/01\/solidity-logo.svg.svg+xml","width":1,"height":1,"type":"image\/jpeg"}],"author":"wsjcrypto","twitter_card":"summary_large_image","twitter_misc":{"Scritto da":"wsjcrypto","Tempo di lettura stimato":"3 minuti"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/wsj-crypto.com\/index.php\/2025\/01\/24\/unlocking-error-handling-in-solidity-0-6-x-the-power-of-try-catch-statements\/","url":"https:\/\/wsj-crypto.com\/index.php\/2025\/01\/24\/unlocking-error-handling-in-solidity-0-6-x-the-power-of-try-catch-statements\/","name":"Unlocking Error Handling in Solidity 0.6.x: The Power of Try\/Catch Statements - WSJ-Crypto","isPartOf":{"@id":"https:\/\/wsj-crypto.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/wsj-crypto.com\/index.php\/2025\/01\/24\/unlocking-error-handling-in-solidity-0-6-x-the-power-of-try-catch-statements\/#primaryimage"},"image":{"@id":"https:\/\/wsj-crypto.com\/index.php\/2025\/01\/24\/unlocking-error-handling-in-solidity-0-6-x-the-power-of-try-catch-statements\/#primaryimage"},"thumbnailUrl":"https:\/\/wsj-crypto.com\/wp-content\/uploads\/2025\/01\/solidity-logo.svg.svg+xml","datePublished":"2025-01-24T02:38:49+00:00","author":{"@id":"https:\/\/wsj-crypto.com\/#\/schema\/person\/88a93723b30416db1a352d5a0096c4a7"},"breadcrumb":{"@id":"https:\/\/wsj-crypto.com\/index.php\/2025\/01\/24\/unlocking-error-handling-in-solidity-0-6-x-the-power-of-try-catch-statements\/#breadcrumb"},"inLanguage":"it-IT","potentialAction":[{"@type":"ReadAction","target":["https:\/\/wsj-crypto.com\/index.php\/2025\/01\/24\/unlocking-error-handling-in-solidity-0-6-x-the-power-of-try-catch-statements\/"]}]},{"@type":"ImageObject","inLanguage":"it-IT","@id":"https:\/\/wsj-crypto.com\/index.php\/2025\/01\/24\/unlocking-error-handling-in-solidity-0-6-x-the-power-of-try-catch-statements\/#primaryimage","url":"https:\/\/wsj-crypto.com\/wp-content\/uploads\/2025\/01\/solidity-logo.svg.svg+xml","contentUrl":"https:\/\/wsj-crypto.com\/wp-content\/uploads\/2025\/01\/solidity-logo.svg.svg+xml"},{"@type":"BreadcrumbList","@id":"https:\/\/wsj-crypto.com\/index.php\/2025\/01\/24\/unlocking-error-handling-in-solidity-0-6-x-the-power-of-try-catch-statements\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/wsj-crypto.com\/"},{"@type":"ListItem","position":2,"name":"Unlocking Error Handling in Solidity 0.6.x: The Power of Try\/Catch Statements"}]},{"@type":"WebSite","@id":"https:\/\/wsj-crypto.com\/#website","url":"https:\/\/wsj-crypto.com\/","name":"WSJ-Crypto","description":"Just Another Crypto News Website","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/wsj-crypto.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"it-IT"},{"@type":"Person","@id":"https:\/\/wsj-crypto.com\/#\/schema\/person\/88a93723b30416db1a352d5a0096c4a7","name":"wsjcrypto","image":{"@type":"ImageObject","inLanguage":"it-IT","@id":"https:\/\/wsj-crypto.com\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/86fe8af82ea089646d6639ca2f87e0243d8688d957bd8e3ec22ec3c457cc16d4?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/86fe8af82ea089646d6639ca2f87e0243d8688d957bd8e3ec22ec3c457cc16d4?s=96&d=mm&r=g","caption":"wsjcrypto"},"url":"https:\/\/wsj-crypto.com\/index.php\/author\/wsjcrypto\/"}]}},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/wsj-crypto.com\/index.php\/wp-json\/wp\/v2\/posts\/7698","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wsj-crypto.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wsj-crypto.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wsj-crypto.com\/index.php\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/wsj-crypto.com\/index.php\/wp-json\/wp\/v2\/comments?post=7698"}],"version-history":[{"count":2,"href":"https:\/\/wsj-crypto.com\/index.php\/wp-json\/wp\/v2\/posts\/7698\/revisions"}],"predecessor-version":[{"id":7701,"href":"https:\/\/wsj-crypto.com\/index.php\/wp-json\/wp\/v2\/posts\/7698\/revisions\/7701"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/wsj-crypto.com\/index.php\/wp-json\/wp\/v2\/media\/7699"}],"wp:attachment":[{"href":"https:\/\/wsj-crypto.com\/index.php\/wp-json\/wp\/v2\/media?parent=7698"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wsj-crypto.com\/index.php\/wp-json\/wp\/v2\/categories?post=7698"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wsj-crypto.com\/index.php\/wp-json\/wp\/v2\/tags?post=7698"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}