How I made this (yep, it was all me 😉)
Step 1: Prompt for grok:
"Hey, i want to use the new version of Nano Banana Pro to help make a technical infographic that describes how pheonix wallet started using taproot channels and how that translates to the reduction in on-chain fees avertised in this article:
https://atlas21.com/phoenix-wallet-introduces-taproot-channels/
Can you help me write a prompt that i could give to Nano Banana Pro that would get me what im looking for?
Also feel free to include the technical details included in the Taproot BIP here:
https://en.bitcoin.it/wiki/BIP_0341"
Step 2: Take the output from grok (as follows) and put it into Nano Banana Pro:
"Create a professional technical infographic in a clean, modern style with a Bitcoin and Lightning Network theme—use orange and purple accents, circuit-like icons, and blockchain node illustrations. The infographic should explain how Phoenix Wallet introduced Taproot channels in version 2.7.0 (for Android and iOS) and how this leads to a 20% reduction in on-chain fees, based on BIP 341 technical details.
Divide the infographic into four main sections with bold headings, connected by arrows or flow lines for a logical progression:
Phoenix Wallet's Taproot Introduction: Show a timeline icon with 'Version 2.7.0' highlighted. Illustrate automatic migration for existing users during their next on-chain transaction (no manual action needed). Depict a smartphone wallet app icon upgrading a Lightning channel to Taproot, making the on-chain footprint indistinguishable from a standard P2TR (Pay-to-Taproot) wallet unless force-closed. Mention future plans like V3 transactions and zero-fee commits.
Taproot Basics (BIP 341): Use a central tree diagram to represent Merkleized Abstract Syntax Trees (MAST), showing multiple spending scripts committed in a Merkle tree, with only the executed branch revealed on-chain (control block: 33 + 32m bytes). Include a key icon for Schnorr signatures, illustrating key aggregation (MuSig) where multiple public keys combine into one aggregated key Q (tweaked from internal key P + hash tweak). Highlight batch validation and smaller signatures (64-65 bytes) for efficiency.
Taproot in Lightning Channels: Diagram a before-and-after comparison of Lightning channels. 'Before' (legacy): Multi-signature setups with larger witness data and exposed scripts. 'After' (Taproot): Cooperative settlements via aggregated keys in key-path spends, hiding scripts for privacy; script-path spends reveal only necessary Merkle proofs. Show how this supports efficient multi-party channels without on-chain exposure, improving privacy (indistinguishable from single-key spends) and reducing data overhead.
Fee Reduction Benefits: Bar chart or scale icon comparing transaction sizes—weigh 'Legacy Channel Ops' (higher weight, more data) vs. 'Taproot Channels' (20% lower on-chain fees for operations like splicing). Explain visually: Merged pay-to-pubkey/scripthash into single 32-byte Taproot output; less witness data in spends; aggregation lowers signature/validation overhead. Note how smaller tx weights translate to cost-effective Lightning transactions of any size.
Include subtle Bitcoin logos, fee icons (coins stacking lower), and privacy shields. Use bullet points or short captions for clarity, sans-serif fonts, and ensure the layout is vertical for easy reading on a poster or screen. High resolution, informative yet not cluttered."
Result:
