Smart contract development

[PaulRBerg]

In its early days, I was somewhat adamant to keep Create Eth App a frontend-only development tool. However, with time, interesting use cases for smart contract development came to mind: flash loans, buidler setups, etc.

I'm still not convinced that it is worth it, particularly given the complexity it would bring, but I decided to open the GitHub issue to entertain the idea further.

[PaulRBerg]

Received a request for this:

Any thoughts on using @ethPM1 as a way to simplify the creation of new templates?

[samajammin]

I've used create-eth-app in tandem with buidler. e.g. here's an old demo dapp of a buidler project on the top level of the repo, with a create-eth-app project within the /frontend/ directory.

My 2 Gwei: I think it would be a nice addition to provide a flag option when creating a new project.

[PaulRBerg]

Thanks for your feedback, @samajammin! This helps a lot with deciding what are the best features to implement next.

In the interim, @austintgriffith made huge progress with scaffold-eth; a tool that generalises what your honeypot app does by assembling buidler and create-eth-app together.

[martinoss]

Hi @PaulRBerg
Coming a little late to the discussion but I just noticed, both create-eth-app and the solidity-template I was looking at is your awesome work.
I like the stacks of both projects and it would be great to combine these two in some form.
Guess it would be great to have an option in create-eth-app to add smart contract development or as alternative - having just a guide for combining these two gems.

[PaulRBerg]

Thanks for sharing your feedback, @martinoss. Glad you like my templates.

I agree that having the option to enable SC templating in create-eth-app may be helpful. I'm looking to make this possible in CEA v2.

[cswkim]

If using your solidity-template and this front-end side by side, would the workflow be:

Work on your contracts in one repo (that was started with solidity-template) -> compile your contracts -> take the artifacts and copy to the other repo (started with create-eth-app) packages/contracts directory?

[PaulRBerg]

@cswkim that sounds like a good plan. But if I were to work on a serious project, I would use TypeScript (which is not available with CEA), and I would include the contract types generated via TypeChain in the artifacts that you port over to the frontend app.

See my work on Hifi.

[PaulRBerg]

This project will remain frontend-only. Closing.

I have separate templates for smart contract development:

https://twitter.com/PaulRBerg/status/1586829581499224065