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

[gregsantos]

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

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

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

Key Result 3.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 3.4: Release Powerful, Extendible Code Example repository for above.

Key Result 3.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	@gregsantos
Consulted	@dete, @SeanRobb
Informed	@SeanRobb

Tasks

Beta 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 Extendable Solutions

---

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