HTTP/2 200 date: Sun, 01 Aug 2021 20:05:45 GMT content-type: text/html; charset=UTF-8 vary: Accept-Encoding set-cookie: PHPSESSID=oo70e006iht2cdplfvpfu22qeb; path=/ expires: Thu, 19 Nov 1981 08:52:00 GMT cache-control: no-store, no-cache, must-revalidate pragma: no-cache x-pingback: https://ambcrypto.com/xmlrpc.php link: ; rel="https://api.w.org/" link: ; rel="alternate"; type="application/json" link: ; rel=shortlink cf-cache-status: DYNAMIC expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct" report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=89rFUwBfKSItErkdGs%2FhxpCR3QehWD0%2BuYNumFfjMsddb70ZaTvkTQmcALIi%2BBzDM0cwQxt533kUlw1toseirXgTRwhsKPACoL%2F8IkxE6AwRSB8c0Q3ZQZ4tPpBnWX1%2F"}],"group":"cf-nel","max_age":604800} nel: {"report_to":"cf-nel","max_age":604800} server: cloudflare cf-ray: 6781aede29c25a7b-IAD alt-svc: h3-27=":443"; ma=86400, h3-28=":443"; ma=86400, h3-29=":443"; ma=86400, h3=":443"; ma=86400 Cardano: 'We can begin the countdown' to Alonzo HFC event when... - AMBCrypto
A look at the two-part changes
According to IOHK’s Charles Hoskinson, the Alonzo update on the mainnet is still a few weeks from now. In revealing so, the exec also shared two-part changes that will take place on the network. For starters, addressing the Alonzo hard fork combinator event in a recent vlog[2], Hoskinson said,“Now the Hard fork combinator event is strictly about getting Alonzo capabilities to the node and meaning that if the Plutus code was submitted, you would be able to execute those transactions to be valid.”Meanwhile, the second event is about building the infrastructure around that node. This is expected to allow both off-chain and on-chain code, while also encouraging the building of full DApps inside the system. Hoskinson added,
“…so, the first part is
