Clarify upkeep funding requirements for Data Streams examples (#1681)

* Clarify upkeep funding requirements for Data Streams examples * Update src/features/data-streams/common/gettingStarted.mdx Co-authored-by: Andrej <andrej.rakic.97@gmail.com> --------- Co-authored-by: Andrej <andrej.rakic.97@gmail.com>
smartcontractkit · Dec 11, 2023 · 641f514 · 641f514 · vercel · Dec 11, 2023
1 parent b127b1f
commit 641f514
Showing 1 changed file with 5 additions and 0 deletions.
diff --git a/src/features/data-streams/common/gettingStarted.mdx b/src/features/data-streams/common/gettingStarted.mdx
@@ -83,6 +83,11 @@ Register a new **Log Trigger** upkeep. See [Automation Log Triggers](/chainlink-
 
 1. Leave the **Check data** value and other fields blank for now, and click **Register Upkeep**. MetaMask prompts you to confirm the transaction.
 
+## Fund the upkeep contract
+
+In this example, the upkeep contract pays for the verification. The Automation subscription does not cover that cost. Send LINK to your upkeep contract to pay for the verification costs.
+
+In MetaMask, send 1 testnet LINK to your contract address before you proceed to the next step and trigger the upkeep.
 ## Emit a log
 
 Now you can use your emitter contract to emit a log and initiate the upkeep, which retrieves data for the specified Data Streams asset ID.