-
Notifications
You must be signed in to change notification settings - Fork 149
client/asset/eth: Use gwei in Balance. #1078
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -78,6 +78,9 @@ cat > "${NODES_ROOT}/genesis.json" <<EOF | |
| "byzantiumBlock": 0, | ||
| "constantinopleBlock": 0, | ||
| "petersburgBlock": 0, | ||
| "istanbulBlock": 0, | ||
| "muirGlacierBlock": 0, | ||
| "berlinBlock": 0, | ||
|
Comment on lines
+81
to
+83
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should put us at the same.. fork as mainnet. |
||
| "clique": { | ||
| "period": 1, | ||
| "epoch": 30000 | ||
|
|
@@ -183,9 +186,7 @@ echo "Sending 5000 eth to delta and gamma." | |
|
|
||
| # Our transactions will PROBABLY appear in one of these blocks. | ||
| echo "Mining some blocks" | ||
| "${NODES_ROOT}/harness-ctl/mine-beta" "1" | ||
| "${NODES_ROOT}/harness-ctl/mine-alpha" "1" | ||
| "${NODES_ROOT}/harness-ctl/mine-beta" "5" | ||
| "${NODES_ROOT}/harness-ctl/mine-beta" "15" | ||
|
Comment on lines
-186
to
+189
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I had a few times where it looked like mining on alpha made transaction inclusion speed worse. Will attempt to solve the problem in a separate pr.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Dang what a drag. Linking back to the original discussion and karalabe's comment in a different thread.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Another related idea was to have the non-miners (clients) connected to each other or at least another non-miner (or not the primary miner): ethereum/go-ethereum#2822 (comment)
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Oh and about the first idea of starting 2 miners, one guy said he "updated the file "static-nodes.json" accordingly". Know what we should do there? Specify enodes? Sounds like an alt was karalabe's other suggestion of enabling discovery with a custom bootnode.
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Will look into this directly after I get #1019 up to speed.
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeah, still scratching my head. These convos are from 2016, so maybe something different. Also, putting sleeps in the wrong places in the harness can just make everything fail. Which seems wierd.
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Pretty sure I found and fixed the problem in #1130 Calling |
||
|
|
||
| # Initial sync for light nodes takes quite a while. Wait for them to show | ||
| # blocks on the network. | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.