30 lines
1.8 KiB
Markdown
30 lines
1.8 KiB
Markdown
|
---
|
||
|
|
title: Welcome to go-ethereum documentation
|
||
|
|
description: Documentation for the go-ethereum client
|
||
|
|
---
|
||
|
|
|
||
|
|
## Welcome to go-ethereum
|
||
|
|
|
||
|
|
Go-ethereum (aka Geth) is an Ethereum client built in [Golang](https://go.dev). It is one of the original and most popular Ethereum clients.
|
||
|
|
These documentation pages are intended to help users download, install and use Geth.
|
||
|
|
|
||
|
|
## Where to go from here
|
||
|
|
|
||
|
|
First, make sure you have sufficient [hardware](/docs/getting-started/hardware-requirements), then [download](/downloads) and [install](/docs/getting-started/installing-geth) Geth. Make sure you are familiar with the [security considerations](/docs/fundamentals/security) and have your firewall set up.
|
||
|
|
|
||
|
|
If you are just starting out with Geth, head to the [Getting started](/docs/getting-started/) page. That page guides a new user through some basic functions of Geth such as creating and securing accounts and making a transaction using Geth's built-in account tools.
|
||
|
|
|
||
|
|
A more secure but slightly more advanced setup is to use an external signer instead of Geth's built-in account manager. We have a [getting started](/docs/getting-started/getting-started-with-clef) guide for that too.
|
||
|
|
|
||
|
|
Then, it is recommended to read the material in the [Fundamentals](/docs/fundamentals) section - these pages will help build a foundational understanding of how Geth works from a user perspective and under the hood.
|
||
|
|
|
||
|
|
More advanced topics are also available - explore them using the sidebar!
|
||
|
|
|
||
|
|
## Developers and contributors
|
||
|
|
|
||
|
|
If you want to help develop Geth or build decentralized apps on top of it, head to our [Developers](/docs/developers) documentation.
|
||
|
|
|
||
|
|
## More resources
|
||
|
|
|
||
|
|
We have a library of videos and articles on our [Resources](/docs/resources) page and answers to common questions on the [FAQs](/docs/faq) page.
|