<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Web3 on Matt Suiche</title><link>https://www.msuiche.com/categories/web3/</link><description>Recent content in Web3 on Matt Suiche</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 22 Aug 2022 12:00:00 +0200</lastBuildDate><atom:link href="https://www.msuiche.com/categories/web3/index.xml" rel="self" type="application/rss+xml"/><item><title>Vegas 2022 - A web3 security review</title><link>https://www.msuiche.com/posts/vegas-2022-a-web3-security-review/</link><pubDate>Mon, 22 Aug 2022 12:00:00 +0200</pubDate><guid>https://www.msuiche.com/posts/vegas-2022-a-web3-security-review/</guid><description>&lt;p&gt;This year marks 5 year since I gave my first blockchain/web3 related presentation at DEFCON 25 when I presented &lt;a href="https://www.msuiche.com/posts/porosity-a-decompiler-for-blockchain-based-smart-contracts-bytecode/" target="_blank" rel="noopener"&gt;Porosity&lt;/a&gt; which was an experimental decompiler and static analysis tool for Ethereum Virtual Machine bytecode, but also mentioned on why we should keep an eye on WebAssembly Virtual Machines back when eWASM was being drafted and an option for Ethereum as a replacement for EVM itself.&lt;/p&gt;
&lt;p&gt;Since then, new layer 1 blockchains have emerged such as &lt;a href="https://docs.solana.com/developing/on-chain-programs/overview" target="_blank" rel="noopener"&gt;Solana&lt;/a&gt; (eBPF-variant), and &lt;a href="https://nomicon.io/RuntimeSpec/Components/" target="_blank" rel="noopener"&gt;NEAR&lt;/a&gt; &amp;amp; &lt;a href="https://medium.com/polkadot-network/wasm-on-the-blockchain-the-lesser-evil-da8d7c6ef6bd" target="_blank" rel="noopener"&gt;Polkadot&lt;/a&gt; (WebAssembly) as part of a new wave of architectures relying on the LLVM compiler and ELF file formats, instead of reinventing the wheel like the Ethereum Virtual Machine and Solidity programming language.&lt;/p&gt;</description></item><item><title>Smart Contract Languages to Follow</title><link>https://www.msuiche.com/posts/smart-contract-languages-to-follow/</link><pubDate>Wed, 27 Dec 2017 12:00:00 +0200</pubDate><guid>https://www.msuiche.com/posts/smart-contract-languages-to-follow/</guid><description>&lt;p&gt;What languages I’ll keep a close look at next year (2018)&lt;/p&gt;
&lt;p&gt;&lt;p class="markdown-image"&gt;
 &lt;img src="https://cdn-images-1.medium.com/max/2000/1*LBiugCr0P4iN_qhHfthhQQ.png" alt="If “crypto” stands for cryptography… then, is my auto-correct right to call “cryptocurrencies” just “currencies”?" /&gt;
&lt;/p&gt;&lt;em&gt;If “crypto” stands for cryptography… then, is my auto-correct right to call “cryptocurrencies” just “currencies”?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Cryptocurrencies and blockchain made a lot of noise this year, good and bad. Smart contracts are finding new use cases (e.g. &lt;a href="https://www.cryptokitties.co/" target="_blank" rel="noopener"&gt;CryptoKitties&lt;/a&gt;), and some existing use case like multi-sig wallets (e.g. Parity) have been challenged due to their high complexity which introduced, like any piece of complex software, &lt;a href="https://www.msuiche.com" target="_blank" rel="noopener"&gt;security vulnerabilities.&lt;/a&gt;&lt;/p&gt;</description></item></channel></rss>