BDAG Mining Pool
stratum.dagcore.net:3334
Connect your mining hardware to the DagCore pool.
Independent infrastructure for BlockDAG Community
Mine it. Explore it. Build on it. Verify it.
DagCore provides independent infrastructure for the BlockDAG Community network, giving you direct access to the chain through mining, a public RPC, a blockchain explorer and node tools.
stratum.dagcore.net:3334
Connect your mining hardware to the DagCore pool.
Blocks · Transactions · Addresses
Browse and inspect blockchain data.
Wallets · dApps · Scripts
Use the public RPC to build, connect and integrate. No API key.
Run · Sync · Verify
Run your own node and verify the chain independently.
DAGCORE
BLOCKDAG COMMUNITY
CHAIN 1404
Checking node…
Mining
Any BlockDAG miner that connects over Stratum V1. For graphics cards and processors there is DagCore Miner, a free OpenCL miner for Linux and Windows, already set up for this pool.
Download DagCore MinerUse the bare wallet address as the username. Worker names are not supported: a login in the form address.worker is rejected by the pool.
Connecting mining hardware to this pool is an acceptance of the Terms of Service, which cover payouts, inactive balances and what the pool does not guarantee.
Accepted shares appear within about a minute. Search your address on the dashboard for hashrate, balance and every payout with its transaction.
DagCore runs its own BlockDAG Community node, operated in the European Union, and opens it to the public three ways: a mining pool, a JSON-RPC endpoint and an explorer. The node guide shows how to run the same stack yourself, so no one has to depend on DagCore.
| Network | BlockDAG Community |
|---|---|
| Chain ID | 1404 |
| Currency | BDAG |
| Decimals | 18 |
| RPC URL | https://rpc.dagcore.net |
| Explorer | https://explorer.dagcore.net |
Two blockchain networks currently use Chain ID 1404 but have divergent block histories.
DagCore serves the BlockDAG Community / engineering-token network.
Because the blockchain histories diverge, the same wallet address may show different balances or transactions depending on the RPC endpoint and network being queried.
Always verify the RPC endpoint and blockchain history before sending transactions or configuring mining software.
Learn more at BDAG Community.
Ask our RPC for block 316,002 and compare its hash with the one below: the same hash means the same chain history.
curl -s https://rpc.dagcore.net -H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"eth_getBlockByNumber","params":["0x4d262",false]}' \
| grep -o '"hash":"0x[a-f0-9]*"' | head -1
0x4d262 is block 316,002. On the network DagCore serves, its hash is 0xcd4d2568e9cba6725329e8cf6d96217ace7acb03d71d9b519c8b2560bb6bb781.
To compare other public endpoints, see the Network page: every one is probed every 20 seconds, and each is shown as following this chain or serving a different one.
No account or sign-up needed.