Gelato
  • Introduction
    • Gelato, The Web3 Cloud Platform
  • Rollup As A Service
    • Introduction
    • Rollup Stacks
      • Arbitrum Orbit
        • Run a Full Orbit Node
      • OP Stack
        • Run OP Node
    • Deploy your Rollup
    • Customization
      • Data Availability
        • Celestia
        • Avail
        • Eigen DA
      • Custom Gas Token
      • Marketplace
        • Gelato Services
        • Data Indexers
        • Block Explorers
        • Oracles
        • Bridges
        • Account Abstraction
        • On & Off-ramp
        • Community
        • Identity & KYC
        • Others
      • Verifier Node Package
    • Public Testnet
  • RPC Nodes
    • Introduction
    • Compute Units
    • Using RPC Nodes
    • Supported Networks
    • Pricing and Plans
    • FAQ
  • Web3 Services
    • Web3 Functions
      • Understanding Web3 Functions
        • Trigger Types
        • Typescript Function
        • Solidity Function
        • Automated Transactions
      • Security Considerations
      • Template & Use Cases
      • Quick Start
        • Writing Typescript Functions
          • Event Trigger
          • Private Typescript Functions
          • Callbacks
        • Test, Deploy & Run Typescript functions
        • Writing Solidity Functions
        • Test, Deploy & Run Solidity Functions
        • Initiate an Automated Transaction
      • Create a Web3 Function Task
        • Using the UI
        • Using the Safe App
        • Using a Smart Contract
        • Using the Automate SDK
      • Analytics & Monitoring
      • Supported Networks
      • Subscription & Payments
      • Legacy Automate Migration Guide
    • Relay
      • What is Relaying?
      • Security Considerations
        • ERC-2771 Delegatecall Vulnerability
      • Templates
      • Quick Start
        • Sponsored Calls
        • Non-Sponsored Calls
      • ERC-2771 (recommended)
        • SponsoredCallERC2771
        • CallWithSyncFeeERC2771
          • Relay Context Contracts ERC2771
      • Non-ERC-2771
        • SponsoredCall
        • CallWithSyncFee
          • Relay Context Contracts
      • Relay API
      • Gelato's Fee Oracle
      • Tracking your Relay Request
      • Supported Networks
      • Subscriptions and Payments
        • 1Balance & Relay
        • SyncFee Payment Tokens
        • Relay Pricing
      • ERC2771 Migration Guide
    • VRF
      • Understanding VRF
      • How does Gelato VRF Work?
      • Security Considerations
      • Template
      • Quick Start
      • Create a VRF Task
        • Create a Fallback VRF
        • Migrating from Chainlink VRF
      • Supported Networks
      • Pricing & Rate Limits
    • Oracles
      • Understanding Gelato Oracles
      • Quick Start
      • Data Providers
        • Stork
        • Choas Labs
      • Migrating from Chainlink Oracles
      • Available Price Feeds
      • Supported Networks
      • Pricing & Rate Limits
    • Account Abstraction
      • Understanding ERC4337
      • Introduction to Gelato Bundler
      • Templates & Examples
      • Quick Start
      • Sponsored UserOps
        • Using 1Balance
        • Using Zerodev Paymaster
      • Non-Sponsored UserOps
        • Pay with Native
        • Pay with ERC20
      • Supported Networks
      • Bundler API Endpoints
        • eth_sendUserOperation
        • eth_estimateUserOperationGas
        • eth_getUserOperationByHash
        • eth_getUserOperationReceipt
        • eth_supportedEntryPoints
        • eth_maxPriorityFeePerGas
        • eth_chainId
    • 1Balance
      • 1Balance Alerts
      • Subscription Plans
      • Subscription Notifications
      • USDC Addresses
    • AI Agents
    • Teams
  • GELATO DAO
    • DAO & Token (GEL)
    • GEL Token Contracts
    • Governance Process
  • Social Media
Powered by GitBook
On this page
  • 1. Gather Necessary Addresses
  • 2. Access the VRF Deployment Portal
  • 3. Choose your VRF Type
  • 4. Select Deployment Network
  • 5. Specify the Request Contract
  • 6. Launch your VRF Instance
  1. Web3 Services
  2. VRF

Create a VRF Task

PreviousQuick StartNextCreate a Fallback VRF

Last updated 1 month ago

Creating your Gelato VRF Task is a straightforward process. Here's a step-by-step guide to get you started:

Upgrade your VRF Task to v1.2

To upgrade your VRF task to version V1.2, please follow these steps:

  1. Navigate to your existing task on the Gelato platform. Ensure you're on the correct network where your task is active. Click on the "Upgrade" button

  2. A transaction prompt will appear asking you to confirm the upgrade. This process will create a new task and simultaneously pause the old one.

  3. After confirming the transaction, you will notice that the task label updates to "VRF v1.2," indicating that the upgrade is complete.

1. Gather Necessary Addresses

Before you begin, make sure you have the address of your requester contract at hand. This will be essential for the deployment process.

Head over to the VRF Quick Start guide to learn how to prepare your contract for requesting randomness

2. Access the VRF Deployment Portal

Navigate to the .

3. Choose your VRF Type

4. Select Deployment Network

Ensure you choose the same network where both your VRF requester and receiver contracts are deployed.

5. Specify the Request Contract

You'll be asked to provide the address of the Request Contract to which the Gelato nodes should respond. Enter the address you gathered in step 1.

6. Launch your VRF Instance

Once all details are correctly entered, go ahead and launch your Gelato VRF instance.

When prompted to select the VRF type, opt for "Gelato VRF". If you previously deployed a Chainlink consumer contract and wish to transition, refer to the section. Or, if you already have a VRF task and want to cover all the missing events, you can set up a fallback task to ensure completeness, refer to the section.

Mirgate from Chainlink VRF
Create a Fallback VRF
Gelato app