good morning!!!!
Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
B
bor
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Merge requests
0
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Container Registry
Harbor Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
open
bor
Commits
40976ea1
Commit
40976ea1
authored
7 years ago
by
Bas van Kervel
Committed by
Felix Lange
7 years ago
Browse files
Options
Downloads
Patches
Plain Diff
README: update attach instructions for testnet users (#14448)
parent
d18b509e
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+8
-6
8 additions, 6 deletions
README.md
with
8 additions
and
6 deletions
README.md
+
8
−
6
View file @
40976ea1
...
...
@@ -90,15 +90,17 @@ here.
Specifying the
`--testnet`
flag however will reconfigure your Geth instance a bit:
*
Instead of using the default data directory (
`~/.ethereum`
on Linux for example), Geth will nest
itself one level deeper into a
`testnet`
subfolder (
`~/.ethereum/testnet`
on Linux).
itself one level deeper into a
`testnet`
subfolder (
`~/.ethereum/testnet`
on Linux). Note, on OSX
and Linux this also means that attaching to a running testnet node requires the use of a custom
endpoint since
`geth attach`
will try to attach to a production node endpoint by default. E.g.
`geth attach <datadir>/testnet/geth.ipc`
. Windows users are not affected by this.
*
Instead of connecting the main Ethereum network, the client will connect to the test network,
which uses different P2P bootnodes, different network IDs and genesis states.
*
Note: Although there are some internal protective measures to prevent transactions from crossing
over between the main network and test network (different starting nonces), you should make sure to
always use separate accounts for play-money and real-money. Unless you manually move accounts, Geth
will by default correctly separate the two networks and will not make any accounts available between
them.
*
over between the main network and test network, you should make sure to always use separate accounts
for play-money and real-money. Unless you manually move accounts, Geth will by default correctly
separate the two networks and will not make any accounts available between them.
*
#### Docker quick start
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment