Choose Your Path

Two ways to build on Hedera — find the one that fits your background.

Hedera supports two development approaches. Pick the one that matches your background and goals.

Quick Decision Guide

I know Solidity / EVM

You’re an Ethereum or web3 developer familiar with Solidity, Hardhat, Foundry, or Remix. Hedera is fully EVM-compatible — deploy your existing contracts with minimal changes.

What you’ll use: MetaMask, Hardhat, Foundry, Remix, Ethers.js, Viem

What you’ll build: Solidity smart contracts, ERC-20/ERC-721 tokens, dApps with wallet integrations

Start the EVM path →

I want native SDK (JS / Java / Go)

You’re a backend or enterprise developer, or new to web3. The Hiero SDKs give you direct access to all Hedera services without needing Solidity.

What you’ll use: Hiero JavaScript, Java, Go, or Python SDK

What you’ll build: HBAR transfers, native tokens via HTS, verifiable event streams via HCS

Start the Native SDK path →

---

Path 1: EVM Developer

For: Ethereum and Solidity developers, web3 veterans

Deploy Solidity contracts to Hedera using the tools you already know. Hedera’s JSON-RPC Relay makes it seamless — MetaMask, Hardhat, and Foundry all work out of the box.

1. Set up MetaMask

   Add Hedera Testnet to MetaMask and fund your wallet. Set Up MetaMask →

2. Get testnet HBAR

   Fund your account from the testnet faucet to pay for transactions. Get Test HBAR →

3. Deploy your first contract

   Deploy a Solidity contract using Hardhat or Foundry. Deploy with Hardhat →

Start EVM path →

---

Path 2: Native SDK Developer

For: Backend and enterprise developers, developers new to web3

Use the Hiero SDK in your preferred language to interact with Hedera services directly. No Solidity required — create accounts, transfer HBAR, mint tokens, and publish to HCS topics using familiar programming patterns.

1. Create a testnet account

   Set up your Hedera developer portal account and testnet credentials. Create Testnet Account →

2. Get test HBAR

   Fund your testnet account from the faucet. Get Test HBAR →

3. Build with the SDK

   Follow the quickstart for your language: JavaScript, Java, or Go. Native SDK Quickstart →

Start Native SDK path →

---

Not Sure Which Path?

I want to build a token or NFT

Both paths work. Use the EVM path if you want ERC-20/ERC-721 token standards and compatibility with existing Ethereum tooling. Use the Native SDK path if you want the full feature set of Hedera Token Service (HTS), including native fractional fees, royalty schedules, and token-level KYC.

I want to build a dApp with a wallet

Use the EVM path. MetaMask and WalletConnect work natively with Hedera via the JSON-RPC Relay. Your existing frontend code (Ethers.js, Viem, Wagmi) requires minimal changes.

I want enterprise-grade data integrity or messaging

Use the Native SDK path. Hedera Consensus Service (HCS) lets you publish ordered, timestamped, and verifiable messages to a topic — ideal for audit logs, supply chain events, and AI data provenance.

I'm new to blockchain / web3 entirely

Start with the Native SDK path. The SDK abstracts away the complexity of key management and transactions, letting you focus on learning Hedera concepts with familiar language patterns (JS, Java, Go).

Can I use both paths in the same project?

Yes. Many production applications combine both: smart contracts deployed via the EVM path, with HCS or HTS operations performed via the Native SDK. They share the same account system and HBAR balance.