Use EOS' standard C++ toolkit to build your smart contract logic in a .cpp file inside your project.


Lamington uses the standard Contract Development Toolkit (CDT) to build your contracts. You can even change the version of the tools used to match the ones you're used to.


Lamington creates full TypeScript interfaces for your contract actions, tables, and rows. This means you get full autocomplete in your IDE even if you don't use Typescript! And if you do use Typescript, then when you rename anything in your C++ code, your tests will break at compile time instead of breaking later.


Lamington automatically spins up a fully functioning EOS blockchain (including nodeos, cleos, and CDT) inside a Docker container and makes it easy to deploy your contracts for testing.


Using Mocha and Typescript / Javascript, write unit and integration tests for your contract actions. You can assert on your table contents as well as ensuring actions you expect to fail actually fail.


Because you're only worried about your C++ contracts, not tooling, you can rapidly iterate, testing how changes effect your overall decentralised system.

Getting Started Guides

Get started with Lamington the easy way.

Contributing to Lamington

Want to make changes to Lamington? Here's how to get started.

Read More
Getting Started With Lamington

Getting started with Lamington is easier than you think! We'll get you started the easy way.

Read More
Configuring VSCode for Lamington

VSCode with Lamington gives you autocomplete and error notifications right in your editor.

Read More

Join us on Slack

Want to link up with the core dev team and other EOS devs? Invites are open, join us!