Skip to content
This repository was archived by the owner on Apr 4, 2023. It is now read-only.

Commit 9aafa35

Browse files
cleanup README
1 parent 356bf3a commit 9aafa35

File tree

1 file changed

+25
-15
lines changed

1 file changed

+25
-15
lines changed

README.md

Lines changed: 25 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -525,23 +525,31 @@ cd spacesvm;
525525
./scripts/build.sh
526526
```
527527

528-
Running the above commands will generate a binary and save it at
529-
`./build/sqja3uK17MJxfC7AN8nGadBw9JK5BcrsNwNynsqP5Gih8M5Bm`.
528+
Running the above commands will generate a binary and save it at
529+
`~/spacesvm/build/sqja3uK17MJxfC7AN8nGadBw9JK5BcrsNwNynsqP5Gih8M5Bm`.
530530

531531
#### Move Binary
532532
Once the SpacesVM binary is built, you'll need to move it to AvalancheGo's
533-
plugin directory (within the `--build-dir`). By default, this is `~/avalanchego/build/plugins`.
533+
plugin directory (within the `--build-dir`) so it can be run by your node.
534+
When building from source, this defaults to `~/avalanchego/build/plugins`.
535+
This build directory is structured as:
536+
```
537+
build-dir
538+
|_avalanchego
539+
|_plugins
540+
|_evm
541+
```
534542

535-
When inside of the `avalanchego` directory (assuming you built `avalanchego`
536-
from source), run the following command to move the binary your generated:
543+
To put the SpacesVM binary in the right place, run the following command
544+
(assuming the `avalanchego` and `spacesvm` repos are in the same folder):
537545
```bash
538-
mv ../spacesvm/build/sqja3uK17MJxfC7AN8nGadBw9JK5BcrsNwNynsqP5Gih8M5Bm
539-
build/plugins;
546+
mv ./spacesvm/build/sqja3uK17MJxfC7AN8nGadBw9JK5BcrsNwNynsqP5Gih8M5Bm ./avalanchego/build/plugins;
540547
```
541548

542549
#### Add Subnet to Whitelist
543-
Next, you'll need to either modify your config file or provide an argument on
544-
startup telling your node to connect to the Spaces Subnet Demo.
550+
Next, you'll need to provide the `whitelisted-subnets` argument by
551+
modifying your config file or providing an argument on
552+
startup (which tells your node to connect to the Spaces Subnet Demo).
545553

546554
Example Config File:
547555
```json
@@ -595,15 +603,17 @@ Once your node is up and running with the SpacesVM, you'll need to [become a Fuj
595603
This is the exact same flow as Mainnet except you only need to stake
596604
`1 AVAX` instead of `2000 AVAX`.
597605
598-
Recall, only validators on the Primary Network (in this case Fuji) can become
599-
validators of subnets.
606+
Recall, **only validators on the Primary Network (in this case Fuji) can become
607+
validators of subnets.**
600608
601609
#### Submit a Validator Request
602610
Once you've completed the above steps and your node is fully bootstrapped, submit a
603-
[Spaces Demo Validator Request] to be considered as a validator. The Spaces
604-
Subnet Demo is a Permissioned Subnet and requires explicit approval from the
605-
creator to validate. In the near future, it will be possible to create
606-
permissionless subnets that anyone can join.
611+
[Spaces Demo Validator Request] to be considered as a validator (everyone will
612+
be approved).
613+
614+
The Spaces Subnet Demo is a Permissioned Subnet and requires explicit approval from the
615+
creator to validate. In the near future, it will be possible to create permissionless
616+
subnets that anyone can join.
607617
608618
If you have any questions, reach out to @\_patrickogrady on Twitter!
609619

0 commit comments

Comments
 (0)