docs: correct Ethereum network options for roller, claz, and azimuth - #274
Open
sigilante wants to merge 1 commit into
Open
docs: correct Ethereum network options for roller, claz, and azimuth#274sigilante wants to merge 1 commit into
sigilante wants to merge 1 commit into
Conversation
Urbit ID corrections against urbit/docs.urbit.org@08026c84b2. The three affected pages each name a different network type, and they are NOT the same set -- checking one and generalising would give the wrong answer for the other two. roller-tutorial.md `:roller|ropsten` does not exist. pkg/arvo/gen/roller/ contains goerli.hoon, not ropsten.hoon, and gen/roller/endpoint.hoon declares its own inline type `?(%mainnet %goerli %local)` -- so %ropsten is not accepted there at all. Corrected the command name, the documented argument type, and the intro prose which offered Ropsten as a supported alternative. Also added the two roller generators missing from the command table: |assign `[ship (unit @ud)]` (per-ship quota; omit the quota for unlimited) and |refuel `[@ @ud (unit @ux)]` (bump gas price for a sending transaction). Added a note that the testnet path is unmaintained UPSTREAM, not merely in the docs: gen/roller/goerli.hoon hardcodes a Goerli Infura URL, Goerli has been deprecated, and there is no Sepolia or Holesky generator in the directory. Points readers at |local plus an explicit |endpoint instead. advanced-azimuth-tools.md Said other claz networks are "possible including the test-net %ropsten". `+network` in /sur/claz.hoon is `?(%mainnet %goerli %fakenet [%other id=@])` -- there is no %ropsten, and the dispatch in app/claz.hoon:187-192 agrees. Replaced with the real set, noting `[%other id]` takes a chain ID directly and is the practical testnet choice now that Goerli is deprecated. dojo-tools.md `:azimuth|watch` documented its network argument as `?(%mainnet %ropsten %local %default)`. Here %ropsten is NOT stale: `+$ net` in /sur/dice.hoon is `?(%mainnet %ropsten %goerli %local %default)`. The doc was merely INCOMPLETE, missing %goerli, so that is what was added. Removing %ropsten -- the obvious move after the other two files -- would have been wrong. flow.md Used Ropsten as the illustrative example for replay protection. Changed to "a test network" so the example does not go stale again; the point is about chain IDs, not any particular chain. Two broken anchors in dojo-tools.md (#vat, #claycancelautocommit x2) are deliberately NOT touched here: they are already fixed in the mechanical and dev-tooling PRs respectively, and fixing them again would conflict. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This was referenced Aug 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ninth PR from the audit against
urbit/urbit@08026c84b2. Urbit ID network options.Companion PRs: #266, #267, #268, #269, #270, #271, #272, #273.
The headline for reviewers: these three pages each name a different network type, and they are not the same set. Checking one and generalising gives the wrong answer for the other two — which is exactly the mistake this PR avoids.
%ropsten?gen/roller/endpoint.hoon?(%mainnet %goerli %local)sur/claz.hoon+network?(%mainnet %goerli %fakenet [%other id=@])sur/dice.hoon+$ net?(%mainnet %ropsten %goerli %local %default)roller-tutorial.md:roller|ropstendoes not exist —pkg/arvo/gen/roller/containsgoerli.hoon, notropsten.hoon, andendpoint.hoondeclares its own inline type that doesn't accept%ropstenat all. Corrected the command name, the documented argument type, and the intro prose which offered Ropsten as a supported alternative.Also added two roller generators missing from the command table entirely:
|assign[ship (unit @ud)](per-ship quota; omit the quota for unlimited) and|refuel[@ @ud (unit @ux)](bump gas price for a sending transaction).Added a note that the testnet path is unmaintained upstream, not merely in the docs:
gen/roller/goerli.hoonhardcodes a Goerli Infura URL, Goerli has been deprecated by the Ethereum Foundation, and there is no Sepolia or Holešky generator in the directory. Readers are pointed at|localplus an explicit|endpointinstead.advanced-azimuth-tools.mdSaid other
claznetworks are "possible including the test-net%ropsten".+networkin/sur/claz.hoonhas no%ropsten, and the dispatch inapp/claz.hoon:187-192agrees. Replaced with the real set, noting[%other id]takes a chain ID directly and is the practical testnet choice now.dojo-tools.md:azimuth|watchdocumented its network argument as?(%mainnet %ropsten %local %default). Here%ropstenis not stale —+$ netin/sur/dice.hoonstill includes it. The doc was merely incomplete, missing%goerli, so that is what was added. Removing%ropsten— the obvious move after the other two files — would have been wrong.flow.mdUsed Ropsten as the illustrative example for replay protection. Changed to "a test network" so the example doesn't go stale again; the point is about chain IDs, not any particular chain.
Not touched
Two broken anchors in
dojo-tools.md(#vat,#claycancelautocommit×2) are deliberately left alone — already fixed in #266 and #273 respectively. Verified in a combined test-merge of all nine branches that the mergeddojo-tools.mdhas zero broken anchors and the correct$nettype, with each fix applied exactly once.🤖 Generated with Claude Code