Nodes & Blockchain Clients

Dig Chain NodeOpen-Source Cosmos Daemon for Windows Users

Open-source Cosmos-family daemon for the Dig Chain network. Learn what it does, how to install it on Windows and how it compares to other nodes.

Free Open source Windows: Likely v3.6.0 Updated 15 Feb 2024
9 min read Last update 15 Feb 2024 github.com/notional-labs/dig

Dig Chain node is an open-source daemon, called digd, for the Dig Chain network within the Cosmos ecosystem. It is aimed at developers, researchers and technically minded users who want to run their own node, study how a Cosmos-based chain is built, or experiment with blockchain governance ideas.

The software is free and distributed through the project's GitHub repository. Because it is written in Go, it fits the same toolchain used by many other Cosmos projects, which makes it a natural choice for people already familiar with that ecosystem. Note that the latest release is v3.6.0 and the last code update dates back to February 2024, so check the project page for current activity before relying on it.

02

What Is the Dig Chain Node?

The Dig Chain node is the daemon that runs the Dig Chain network. Its binary, digd, validates blocks, relays transactions between peers and keeps a local copy of the chain state. Running it means your machine takes part in the network instead of relying on someone else's server.

Because the project is built on the Cosmos SDK family of tools, many concepts will feel familiar if you have worked with other Cosmos chains. Accounts, validators, governance proposals and the peer-to-peer layer all follow patterns shared across that ecosystem.

03

Who Is Dig Chain Node For?

The software is best suited to developers, blockchain researchers and operators who want hands-on experience with a Cosmos-based chain. A developer might use it to test how a custom module behaves, while a researcher might study the governance design described in the project materials.

Casual users who simply want to send tokens or check a balance will usually find a wallet or web interface more convenient. Running a full node takes disk space, bandwidth and some comfort with the command line.

04

Practical Use Cases

There are several realistic scenarios for this software. A team exploring new governance models can fork the repository and adjust rules to see how they play out in a test environment. A student of blockchain architecture can read a relatively compact monorepo and trace how transactions move from the network layer into state changes.

Operators interested in the charter city and Liquid Land ideas can use a local node to inspect how those on-chain rules are encoded. Anyone building a new chain can use the repository as a reference for how the components fit together.

In each case, the value comes from transparency: the code and the chain state are both open to inspection.

05

Key Concepts Behind Cosmos-Based Nodes

Several terms appear frequently when working with a node like this. A full node stores the complete chain history and verifies every block it receives. A validator is a participant that signs blocks and is typically bonded with stake. Governance proposals let token holders or designated members vote on changes to network parameters.

The Cosmos ecosystem uses Tendermint-family consensus, which provides fast finality compared with many proof-of-work chains. Ethereum (ETH) and Cosmos (ATOM) are mentioned in the project documentation as reference points, so readers comparing designs may find those networks useful for context.

06

How Does a Node Stay in Sync?

When you start digd, the node connects to peers and downloads blocks from the point where your local state ends. Syncing can take a long time depending on the chain's size and your connection speed. During this period the node is not yet fully up to date, so it is normal to see a catching-up status.

If the node falls behind or stalls, common causes include outdated binaries, misconfigured peers or insufficient disk speed. Checking logs and confirming you are running a current release usually resolves the issue.

07

Key features

Monorepo Structure

All essential code for the project lives in a single repository. This makes it easier to clone once, build the node, and read through the components that matter without hunting across multiple projects.

JavaScript Front End

The repository includes front end code written in JavaScript, which supports the web-facing parts of the network. Developers can use it as a reference for how the interface connects to the underlying node.

Built-in Block Explorer

A block explorer is included, allowing users to browse blocks and transactions on the chain. It is useful for verifying that a local node is syncing correctly and for inspecting on-chain activity.

Minimal Mainnet Philosophy

The developers have said they prefer to keep the mainnet as lean as possible and remove features rather than add them. This approach aims to coordinate the efforts of the network around a small, well-understood core.

Liquid Land Concept

Liquid Land is a model for blockchain-style real estate investing, where land ownership and related rights are handled through on-chain mechanisms. It is one of the project's flagship ideas rather than a separate program.

Charter Cities

Charter cities are physical areas whose governing rules are written onto a blockchain. The project treats the chain as the constitution of the community, so the rules are publicly visible and enforceable through code.

Hierarchical Transparent Governance

The project argues that the main problem with hierarchical organizations is opacity rather than hierarchy itself. Its governance model is designed to keep layers of authority visible and auditable on-chain.

Research and Development Focus

The team describes its work as research and development of blockchain governance in both physical and virtual spaces. The software is a tool for that research as much as a network node.

Launch Chains from the Same Code

New chains in the Dig network are designed to launch from the code in this repository, so the node software doubles as a template for building and deploying additional networks.
08

Supported coins

The project documentation mentions Ethereum (ETH) and Cosmos (ATOM) as reference networks. The Dig network itself is a Cosmos-ecosystem chain, and new chains in the network are intended to launch from the same repository.

09

How to install Dig Chain node on Windows

  1. 1

    Download from the official source

    Go to the official GitHub repository at github.com/notional-labs/dig and open the Releases page. Download the latest release, currently v3.6.0, or the Windows build if one is listed. Avoid mirror sites and third-party download portals.

  2. 2

    Verify the file

    Compare the SHA-256 checksum of the downloaded archive with the value published on the release page. If the project provides a signature, verify it as well. A mismatch means the file should not be used.

  3. 3

    Extract the files

    Unpack the archive to a dedicated folder, for example C:\dig. Keeping the binary in a clear location makes it easier to manage configuration and data directories separately.

  4. 4

    Build from source if needed

    If no Windows binary is published, you can build digd yourself. This requires the Go toolchain installed on your system. Follow the build instructions in the repository README and make sure your Go version matches what the project specifies.

  5. Initialize and start the node

    Open a terminal in the folder, initialize the node configuration and then start the daemon. Check the logs to confirm that the node has connected to peers and begun syncing.

10

System requirements

  • Windows operating system with a current 64-bit edition
  • Sufficient free disk space for the full chain data, which grows over time
  • A stable internet connection with enough bandwidth to sync blocks
  • Administrator rights to create folders and open network ports if needed
11

How to use Dig Chain node

Once the node is installed, the basic workflow is simple, though it requires patience and attention to logs. The steps below describe the general flow for running a local node.

  1. Open a terminal in the folder where digd is located.
  2. Initialize the configuration so the node creates its data directories and default settings.
  3. Review the configuration file to confirm the network settings and peer list.
  4. Start the daemon and leave the terminal open while it runs.
  5. Watch the logs until the node reports that it is connected and syncing blocks.
  6. Once synced, open the block explorer to confirm that recent blocks match what you see locally.
  7. Use the command-line tools to query node status, such as the current block height.
  8. Stop the node cleanly before updating the binary, so the chain data is not corrupted.

Keep a note of the version you are running. Upgrades may change configuration options, so reading the release notes before replacing the binary is a sensible habit.

12

Pros & cons

Pros
  • Open source code that can be inspected and modified
  • Free to download and run
  • Includes a block explorer and front end code in one repository
  • Clear focus on transparent, on-chain governance ideas
  • Useful reference for building Cosmos-based chains
Cons
  • The last code update is from February 2024, so activity may be limited
  • No official Windows binary is guaranteed, and building from source may be needed
  • Setup requires comfort with the command line and Go tooling
  • Niche audience compared with mainstream wallets
  • Documentation depth varies, so some configuration takes trial and error
13

Is Dig Chain node safe?

Only download the software from the official GitHub repository or the project's listed website. Verify the SHA-256 checksum or signature before running any binary, and be cautious about third-party copies that claim to offer a faster or modified version. Never enter a seed phrase or private key on a third-party website, and keep wallet keys separate from the node itself.

The project has not been updated since February 2024, which means you may not receive security fixes promptly. Review open issues on the repository and check whether recent maintenance is happening before exposing the node to the internet. Running the daemon behind a firewall and limiting open ports reduces risk.

  • Official source only. Download from github.com/notional-labs/dig. Ignore ads and lookalike domains.
  • Check the SHA-256. Compare the installer hash with the value the developer publishes before running it.
  • Never share your seed phrase. No developer, support agent or website — including CryptApps — will ever ask for it.
14

Alternatives

Dig Chain node focuses on the Dig network and its governance experiments, while most other entries in this category serve different chains. Evmos brings Ethereum-compatible tooling into the Cosmos world, which suits developers building EVM applications. Geth is the reference Ethereum execution client, and Nethermind and Erigon offer alternative Ethereum implementations with different performance trade-offs. OpenEthereum is a former Parity client that is no longer maintained.

For Cosmos users, Cosmos Hub (gaiad) is the reference node for the main Cosmos hub, while Celestia App handles consensus for the data availability network. Karlsen is another node in the catalog. Pick the client that matches the chain you actually want to join, because a node is only useful on its own network.

15

Specifications

Price
Free
Type
Open source
License
—
Latest version
v3.6.0
Last update
15 Feb 2024
Windows support
Likely (builds for Windows; check releases)
Source code
github.com/notional-labs/dig
16

Frequently asked questions

Yes, the software is free and open source. You can download it from the official GitHub repository and inspect the code yourself. There is no purchase required to run the node, though you will need hardware and internet capacity to keep it running.

The project indicates that it builds for Windows, but you should check the Releases page for a ready-made binary. If none is available, you can compile digd from source using the Go toolchain following the repository instructions.

digd is the daemon, or background program, that runs a Dig Chain node. It connects to peers, validates blocks and keeps the local copy of the chain up to date. You start it from a terminal and let it run continuously.

The most recent code update in the repository is dated February 2024, and the current release is v3.6.0. Before relying on the software for anything important, review the repository's commit history and open issues to judge the current level of activity.

A block explorer is a web interface that lets you browse blocks, transactions and addresses on a blockchain. The Dig repository includes one, so you can check that your local node matches the network state.

A basic understanding helps, especially concepts like validators, governance and full nodes. The project is built on Cosmos-family tooling, so reading introductory material on the Cosmos ecosystem will make the configuration and logs much easier to follow.

A node verifies the chain but does not automatically act as a wallet. To hold and send tokens you need a separate wallet with keys you control. Keep seed phrases private and never share them with anyone or enter them on unverified websites.

17

Verdict

Dig Chain node is a niche but interesting tool for developers, researchers and operators who want to run a Cosmos-family node and explore transparent governance ideas. It is free, open source and includes a block explorer and front end code. The main caveats are the limited recent update history and the need to build from source if no Windows binary is published. Check the repository for current activity before committing time to it.

Download now