Make Prerequisites
The codebase is currently not public. We will be sharing more details about the validator's role and functionality soon. We appreciate your patience and interest. Thank you for your understanding and continued support.
Note: Note: Thanks to your contributions, cycle I of our TestNet Phase 3 journey has officially wrapped up! Now we're one step closer to onboarding the world to Bitcoin. Stay tuned for the next steps!
The following prerequisites are essential for running a validator, a bridge node, and a full/light node.
Setup Environment
Upgrade and Install Dependencies
Ensure your system and tools are up-to-date and equipped with essential development utilities including compilers (clang
), network utilities (curl
, wget
, aria2
), archive tools (tar
), and essential build tools (make
, build-essential
).
Install Golang
This project requires Go version 1.22.1 or higher. Install Go by following the instructions on the official Go installation guide. Begin by installing the essential tools required for compiling and building binaries:
Set up Python Environment
Prepare the Python environment for managing AWS services and SSH communications. To maintain a clean and conflict-free environment, it's recommended to use a Python virtual environment. You can create one by installing virtualenv
(pip install --user virtualenv
), then setting it up with python3 -m virtualenv ~/myenv
and activating it using source ~/myenv/bin/activate
.
Setup SSH for Our Private Repos
Note: This step is temporary for the Nubit DA Alpha Testnet phase and can be skipped afterward.
Tell Nubit Team Your GitHub Account
Contact the Nubit team and provide the email associated with your GitHub account. We will grant your GitHub account access to specific private repositories.
Please send your email and contact information to [email protected] to get in touch with the Nubit Team for accessing Nubit DA Alpha Testnet Chain Nodes. The email should include your contact details, a brief introduction of your team, and contact person information.
Generate New SSH Keys
Note: Replace [email protected]
with the email you provided to Nubit in the previous step, which is your GitHub email with repository access.
RiemaLabs Key: Generate an SSH key dedicated to RiemaLabs using the following command:
General GitHub Key: If you haven't already generated an SSH key pair for GitHub, create one using:
Add SSH Keys to GitHub:
Add RiemaLabs Public Key: Copy the content of ~/.ssh/riema_id_ed25519.pub
and ~/.ssh/id_ed25519.pub
:
Add this two public keys to your GitHub account at GitHub SSH keys settings.
Configure SSH and Git:
Set up SSH Configuration: Edit or create the ~/.ssh/config
file to use specific keys for RiemaLabs and other repositories:
Add the following lines to the config
file:
Redirect Git HTTPS URLs to SSH for RiemaLabs:
Secure Your SSH Configuration:
Set appropriate permissions for your SSH keys and configuration files to secure your connection:
Add SSH Keys to SSH Agent:
Start the SSH agent:
Add your keys to the SSH agent:
Bypass Go's Checksum Verification:
To avoid issues with private repositories lacking records in Go's official SUMDB, set the GOPRIVATE
environment variable:
Add this command to your shell profile file (e.g., ~/.bash_profile
) to apply it to all sessions:
Apply the changes immediately (if in an active session):
By following these steps, you will have securely set up and configured access to RiemaLabs' private repositories using SSH. Make sure each step is completed accurately to maintain a secure and efficient workflow. Should you encounter any issues or require further assistance, contact our support team for help.
Basic Configuration
Create and switch to the nubit-da
directory in your home directory, setting up a designated workspace.
Last updated