ZeppelinOS

Zeppelin and TabooKey bringing the Gas Station Network into production will be the culmination of months of momentum building up around meta transactions.

The ZeppelinOS ZepKit is designed to be a one-stop shop for getting started with developing secure, upgradable smart contracts and EVM packages.

For the last few years, OpenZeppelin has been the standard for smart contract development. OpenZeppelin is a battle-tested framework of reusable smart contracts for Ethereum that has powered more than $4.5 billion worth of digital assets.

Few blockchain applications have real adoption. It’s a fact. Barely a few surpass the low hundreds in terms of daily users.

Deploying to production can be a stressful experience, especially if you don’t have a proper suite of tests to ensure that what you built will run smoothly.

Now that you’ve created your first EVM package, let’s go through the steps you would take to link it to your project as if you were linking directly from NPM. These commands you already know, so I’ll just run through them quickly

In this section, we’ll make sure the contract we’ve deployed to our local network works by testing directly against it in Truffle Console. Once we’re happy it works, we’ll publish to the mainnet and create an EVM package for others to access.

If you’re familiar with Node.js, then you will be familiar with NPM (Node Package Manager). You will also know that the ability to npm install existing code in your project makes your life as a programmer easier and, frequently, more secure.

 Two months ago, we presented the EVM package standard as a means to securely share on-chain upgradeable smart contract code. Since then, we have had a great response from the community...

Smart contract development is still in its early days. We’re all still trying to figure out what it will look like and how to polish the developer experience.