 My name is Max Palazzo. I'm an engineer with Coinbase Customy. I am extremely excited to be here today. And as you can see, my talk is titled, Smart Contract Interaction Out of the Coldest Restorage. So at Coinbase Customy, we provide friction as a feature. We introduce barriers that make it extremely difficult for attackers to steal our customer response. We take our private keys, show them up into many, many pieces, and sort them completely offline. We only use any given address once to sign transactions, and then we roll over customer response to a new address. And we also have a very talented ops team who personally verify each transaction. So these features differentiate ourselves from our competitors. They are the reason why more people choose us to hold their crypto than any other custodian on the planet. And so we support many currencies, but as the most successful smart contract platform, Ethereum provides unique challenges to how our system works. So, you know, our top-of-the-line security comes out of the box. You know, you're either safe, but we natively struggle to do some of the things that make Ethereum the most exciting platform. So as far as interacting with contracts that require high transaction throughput, like garnets, or paving, or you name it, you know, since it takes a non-trivial amount of time for us to reconstruct our keys, you know, we struggle to do that. You know, and for interacting with smart contracts like Edgeware Signaling that require funds to stay put, we simply can't support that out of the box since we roll over our funds to a new address every time we sign transactions. But at Coinbase Custody, you take a cue from my manga hero, Yabe Suki Hero, and we surpass our limits right here, right now. So how do we do that? I will introduce to you the proxy smart contract battery that we use. So using this pattern, we can continue to provide world-class security while also giving our users a frictionless user experience. So how does it work? Let's say we want to let our customers participate in maker governance. Well, in coincidence. So whenever we approach a new integration, we start by writing a customized proxy contract that fits around the external contract like a glove. So as you can see, there aren't really a lot of bells and whistles. You know, we just create a thin facade over the external contract, and we call the external contract methods using the proxy contract as the identity. And so when we onboard a new customer to one of these integrations, we start by pairing them with a hot address with a tiny bit of ether in it. Just to make contract calls and pinups. We then use that hot address to deploy a contract on behalf of the customer. And we designate a new cold storage address, a return address that the funds will ultimately arrive. And so once the contract is deployed, we move the customer's full balance of either either or tokens to the contract, depending on what it's trying to do. And once the funds are in the contract, the fund can really begin. We can use the hot address to make as many quick and risk-free contract calls to the external contract as possible, using the proxy as the bridge. Since the proxy has the customer's full balance, they don't find an influence on any of these networks in the nation. So if you're voting for mega-governance, you're voting with all your data. If you're signaling for edgeware signaling, you're signaling with all your data. They're still able to wield the full heft of their currency. And when customers are done interacting with the proxy contracts, we call that previously shown release method, which will send the funds back to safety in the cold storage. So with this pattern, we're able to smash our limits. We're able to continue to provide world-class security, while also giving our users a frictionless customer experience while interacting with extra contracts. Our anime hero, Yame Suka Hiro, is brought. So that's my talk. Thank you for listening. My name is Max. Thank you.