Objective 1: Inspire and Excite EVM Devs To Supercharge Their EVM Apps Using Cadence Only Features

[gregsantos]

Objective 1: Inspire and Excite EVM Devs To Supercharge Their EVM Apps Using Cadence Only Features

Key Result 1.1: Publish a tweet with a "Did you know...?" hook about the benefits of using Cadence, targeting at least 10,000 impressions.

Key Result 1.2: Create a deep dive blog post showcasing how Cadence can enhance EVM apps, achieving at least 500 reads.

Key Result 1.3: Add a detailed recipe with steps and code snippets to the developer docs, aimed at guiding EVM developers through integrating Cadence features.

Key Result 1.4: Release Powerful, Extendible Code Example repository for above.

Key Result 1.5: Each member of 4D Team to release deploy one contract of their design to mainnet. (Stretch: Share content describing the design and use-case)

DACI

Role	Assigned
Driver	@sisyphusSmiling
Approver	@Kay-Zee
Consulted	@dete, @SeanRobb
Informed	@SeanRobb

Tasks

Preview Give feedback

1. Work with stakeholders to choose best 1st example (shortlist includes: Scripted transaction Example enabling for apps to allow users to pay for gas in a different token than FLOW, conditional batch transactions, and vault functionality extension using attachments.
2. Work with marketing team to craft hook tweet, blog post
3. Create and test example code
4. Create detailed Step by Step guide for developers.flow.com
5. Stretch: Create Additional Practical and Extendable Examples

---

Example Ideas Shortlist

Should be High ROI - Obviously valuable and easy to implement
Should be Remixable and Extendable

• Choose Lighthouse Example
  • Conditional Batch
  • COA Attachment (Dex inside an account, Min/Max Spend)
  • Better Multisig3

Ref

• Part 2: Supercharging EVM apps on Flow

[sisyphusSmiling]

The example moving forward will be a relatively simple one, focussing on showcasing something that's both useful simple enough to get the potential across without diving too far into the Cadence deep end.

We'll showcase a transaction that wraps FLOW as WFLOW and mints an NFT, paying with WFLOW. The signer will be a Flow account and a COA will be configured in the same transaction if need be. In order to demonstrate conditional execution, the ERC721 will be written to fail randomly 50% of the time so the Cadence transaction can condition on a successful minting of the NFT.

This setup allows us to demonstrate:

1. Configuring & funding a COA in a Flow account
2. Batched EVM calls in a single Cadence transaction
   • WFLOW.deposit
   • WFLOW.approve
   • ERC721.mint
3. Randomness in the context of an EVM contract
4. Conditional execution

[sisyphusSmiling]

EPIC

[sisyphusSmiling]

Update: The example is code complete and work has started on the walkthrough documentation. Given Jeremy is no longer with the Foundation, I'll take up writing the accompanying blog post covering with aim to have the walkthrough & blog post ready to publish by 11/22. I'll sync with marketing on getting a tweet thread prepped in time for publishing.

[sisyphusSmiling]

Update: Docs implementation-level walkthrough is in PR - #983

Blog post is in draft and collecting feedback in this notion doc

Next steps include working on diagrams and visuals for the blog post, finalizing the post, and drafting a tweet thread to announce the publishing of both the doc and post.

[sisyphusSmiling]

Update: Blog post now has a tracker in the marketing repo and will be slotted into the content calendar for a time that makes the most sense

[sisyphusSmiling]

Update: Blog published here with announcement post from Flow and personal X accounts.