UPD 12/03/2020

Opens the December 2020 Cardano360 show, noting this is the first of three episodes that month with a retrospective on December 10th and a final update on December 17th.

Aparna and Tim exchange Thanksgiving small talk before getting into the show.

Previews tonight's agenda: Gogan updates, partner news, and new devnet initiatives.

Introduces IOG's new delegation strategy, shifting from public pools toward a mix of private pools and community delegation.

Colin explains the program's motivation: delegation as a vote for personal responsibility, decentralization, and geographic diversity.

Details the first delegation criteria: high pledge pools not maximizing leverage, plus purpose pools for operators in economies with less capital.

Ben Lando discusses improving SPO feedback loops, citing a delegation survey with over 4,000 respondents and active Telegram engagement.

Announces a chatbot application form launching December 10th for SPOs to apply for delegation, reviewed quarterly in cohorts.

Outlines what the delegation form looks for: eco friendly pools, charity donations, educational content creators, and pools in developing countries.

The rotation policy: cycling through the full SPO list twice before repeat selections, sized to help pools reach block production.

Confirms the application timeline: opens December 10th, closes before year end, first delegations expected by late January.

The k parameter change from 150 to 500 on December 6th, broadening block creation chances for smaller pools and urging delegators in oversaturated pools to move.

Transitions to the Gogan segment covering native tokens, the ERC20 converter, Plutus, Marlowe, and interoperability.

Book walks through native token terminology: tokens versus assets, token bundles for multi asset transactions, and native ledger level tokens versus smart contract tokens.

Covers token use case categories like security tokens, stablecoins, and non fungibles, plus clarifies that the pre production environment is more mature than a testnet.

Details the phased rollout of native token users: CLI first for developers and power users, then startups and enterprises, then everyday wallet users.

Native tokens parallel ADA: they can be minted while ADA is not, fees are paid only in ADA, and only ADA counts toward minimum UTXO value.

Frames the pre production environment as a UAT stage to learn what token properties the community wants before mainnet.

Walks through the CLI workflow for minting and burning tokens, including defining a monetary script and sending to addresses.

The mainnet vision: a normal ADA like experience for token holders through wallets.

Introduces the metadata registry, a name registry style project for token names and symbols on chain.

Pivots to interoperability, recapping the ERC20 converter that brings tokens in from other chains such as Ethereum.

Customer feedback pushed the ERC20 converter to evolve into a general platform for creating new tokens, not just converting existing ones.

Demos the token builder prototype: naming a token, setting supply and decimals, and choosing a monetary policy.

Turns to smart contract interoperability, noting Charles has discussed this in AMAs, and introduces upcoming devnet partnerships with Runtime Verification and Mutual Knowledge Systems.

Runs through terminology for K semantics, KEVM, and Yul, showing how different source languages compile down to different virtual machines.

The philosophy behind the interoperability push: Cardano should fit developers rather than forcing developers to fit Cardano.

Opens a call for Solidity and other language developers to join the early devnet program via a typeform.

Summarizes Gogan progress: metadata feature complete, native token pre prod live, and ERC20 converter productization underway.

Highlights the new interoperability program bringing in Runtime Verification and Mutual Knowledge Systems, plus Marlowe playground alpha progress.

Plutus playground progress and targets a native Plutus smart contract devnet for 2021, with a partnerships focused show later in December 2020.

The difference between a devnet and a testnet, comparing a devnet to a pre production environment for UAT.

Uses a game console developer kit analogy to describe what a devnet offers builders before public launch.

Introduces Runtime Verification founders Grigore Rosu and Everett, who explain the company's origins at the University of Illinois and the coining of the term runtime verification at NASA.

Everett recounts joining Runtime Verification from an automotive and aerospace testing background before the company pivoted toward blockchain.

Demand for smart contract formal verification and audits became commercially viable as the business grew.

The shift from toy smart contracts to serious DeFi applications porting real financial instruments on chain over the past few months.

Grigore argues DeFi needs major liquidity providers to step in, but that requires trust in code that only formal verification can provide.

Warns that enthusiast built contracts hide many possible exploits, and that formal verification is the best tool developed in 50 years of research to catch them.

Criticizes anonymous DeFi protocols like SushiSwap, PancakeSwap, and Pickle for avoiding accountability, arguing reputable audited protocols are the sustainable future.

Grigore explains the K framework as a language semantic framework: define a language once and derive parsers, compilers, and verifiers automatically.

Credits his academic advisor for convincing him rigorous, reusable mathematical definitions beat ad hoc per language tooling.

Traces K framework's timeline from a 2005 academic prototype to its 2015 transition into Runtime Verification the company.

Everett covers KEVM's origin as a university class project that IOHK saw potential in and helped commercialize for smart contract quality assurance.

KEVM is now largely stable, needing maintenance mainly around Ethereum hard forks, with future work focused on tooling.

Introduces Firefly, Runtime Verification's tool that automates parts of the smart contract quality assurance pipeline for developers.

Yul's origin as a purpose built, register based virtual machine designed for Cardano, informed by LLVM compiler expertise.

Outlines near term plans to update Yul and apply the Firefly tool to it within four to six months.

Grigore praises Cardano's research driven, long term approach, contrasting it with other chains chasing unsustainable staking rewards, and credits Charles Hoskinson's research focus.

Everett agrees, noting Cardano's methodical, research first approach suits DeFi's novelty better than a shotgun approach of trying everything.

Tim reflects that Runtime Verification's universality approach lets many programming languages be verified through a common K semantics foundation.

Welcomes back Fare of Mutual Knowledge Systems for a part two on the Glow language, this time focused on trust and attack scenarios plus a live demo.

Fare introduces Glow's attack model taxonomy, starting with abstraction failures where low level implementation bugs shouldn't leak to the user.

Cites real losses from Solidity level bugs like reentrancy and bad delegatecall permission checks that Glow's higher abstraction avoids entirely.

Covers the misplaced trust attack category, arguing Glow can't prevent bad oracles or hacked exchanges but makes trust assumptions explicit in the app.

Lists low level engineering attacks like DDoS and data loss that Glow abstracts away, framing Glow as an open source shared solution to these problems.

The value proposition: developers focus on business logic while Glow's shared engineering team handles the underlying systems concerns.

Demos a six line Glow contract for a buyer purchasing a signature from a seller, illustrating the language's minimal syntax.

Compares Glow's abstraction level favorably to Solidity, JavaScript, and even Plutus or Marlowe, noting it stays in sync by construction.

Shows the compiled output: six lines of Glow generate roughly 53 lines of Solidity split across contract, buyer, and seller code that always stay in sync.

Runs the live integration test against a private blockchain, showing the buyer creating the contract and the seller publishing a signature.

Reviews the resulting transaction receipt confirming the signature was published on chain as expected.

Glow's code generator targets multiple languages like JavaScript and Solidity, so most developers will never write raw Glow code themselves.

Wraps up by tying Glow into the Gogan interoperability strategy, giving developers optionality across blockchains.

Fare confirms Glow currently targets EVM chains but already has a Plutus prototype ready for when Plutus goes live, plus portability to any blockchain.

Tim recaps the Gogan rollout timeline, Marlowe end user product targeted for Q1 2021, and teases more from Charles on his YouTube channel soon.

Introduces Jeremy Firster of the Cardano Foundation, covering his corporate banking background and move into blockchain policy work in Taiwan.

Jeremy outlines the Foundation's partnership strategy: showcase economic utility through mass market use cases, starting with transactional metadata integrations.

ScanTrust's Ricardo Garcia introduces the company: anti counterfeit QR technology active in 130 countries, serving FMCG and industrial goods clients.

Details ScanTrust's three value pillars: counterfeit protection, supply chain tracking, and consumer engagement through unique per unit QR codes.

ScanTrust's patented secure graphic embedded in QR codes that makes each code unique and copy proof.

Clarifies ScanTrust itself isn't a blockchain company but provides tamper proof physical identifiers that link products to a blockchain audit trail.

Ricardo explains why Cardano specifically: a large active community and a metadata feature that's cheaper to integrate than requiring smart contracts.

The integration lets end users independently verify on chain claims, using a wine provenance example.

Mel from the Cardano Foundation details the tamper proofing mechanics: SHA-256 hashes and digital signatures for data integrity and attribution.

Wraps the ScanTrust segment noting more integration opportunities will open as additional Cardano features ship.

Jeremy closes by framing integrations as the key driver for growing Cardano's market infrastructure and adoption.

Kevin returns to preview the next hard fork combinator event, rolling the protocol from Shelley 2.0 to Allegra 3.0 with a new token locking feature.

Frames the repeatable hard fork process as proof Cardano can upgrade smoothly again and again, unlike the disruptive hard forks of other chains.

Kevin explains how the hard fork combinator keeps the network running and extends chain history rather than restarting the chain.

Details the technical challenge of synchronizing blocks produced under old and new protocol rules during the transition window.

Token locking: placing a hold on a token for a period of time so its unavailability becomes provable and can trigger conditional contracts.

Uses a real estate purchase agreement analogy to illustrate how token locking secures a future contractual obligation.

Frames token locking as a foundational building block for future smart contracts and non fungible tokens.

Token locking will power Project Catalyst voting: locking ADA during a vote secures voting rights and prevents double voting or vote buying.

Kevin jokes that if this system existed a month earlier, the US presidential election could have been settled by ADA holders voting directly.

Outlines the rollout plan: internal QA and scalability testing now, moving to the Cardano testnet before mainnet deployment.

Expects a faster rollout than Shelley's long testnet period since token locking is a smaller, simpler feature, with mainnet in two to three weeks.

Wraps the show recapping Gogan devnets, the hard fork combinator, and the call for developers to sign up via the typeform link.

Previews the next episode's Africa segment with John O'Connor covering 2020 progress and 2021 plans.

Teases upcoming Basho phase content, including a Hydra scaling update as it moves from concept into active development.