Repository files navigation

A minter and protocol for dunes on Dogecoin.

You can find general information about Duneshere.

Use this wallet for dunes only! Always mint from this wallet to a different address. This wallet is not meant for storing funds or dunes.

To use this, you'll need to use your console/terminal and install Node.js on your computer. So please ensure, that you have your

Please head over tohttps://nodejs.org/en/download and follow the installation instructions.

In order to inscribe, you will need to have access to a Dogecoin RPC. For example:https://getblock.io/ provides a service to get access to an RPC.You will need that for the configuration.

Install by git clone (requires git and node on your computer)

git clone https://github.com/sirduney/dunes-cli.git

or

download thiszip file and upack in a directory.

Now open your terminal and change to the directory the sources are installed.

cd <path to your download / installation>npm install

After all dependencies are solved, you can configure the environment:

Copy a.env.example to.env and add your node information. Here are also some recommended settings:

PROTOCOL_IDENTIFIER=DNODE_RPC_URL=http://<ip>:<port># This is optional if you have an RPC from getblock.ioNODE_RPC_USER=<username>NODE_RPC_PASS=<password>TESTNET=falseFEE_PER_KB=50000000ORD=https://wonky-ord-v2.dogeord.io/

You can get the current fee per kb fromhere.

Generate a new.wallet.json file:

node dunes.js wallet new

Then send DOGE to the address displayed. Once sent, sync your wallet:

node dunes.js wallet sync

If you are minting a lot, you can split up your UTXOs:

node dunes.js wallet split <splits>

When you are done minting, send the funds back:

node dunes.js wallet send <address> <amount>

Deploy a dune:

node dunes.js deployOpenDune 'RANDOM•DUNE•NAME' <symbol> <limit-per-mint> <decimals> <max-nr-of-mints> <mint-absolute-start-block-height> <mint-absolute-stop-block-height> <mint-relative-start-block-height> <mint-relative-end-block-height> <amount-premined-to-deployer> <opt-in-for-future-protocol-changes> <minting-allowed> [parentId]

Note: The[parentId] parameter is optional and links the new Dune to a parent inscription by specifying its inscription ID (e.g.,e6c6efe91b6084eae2c8a2fd6470d3d0dbfbb342f1b8601904f45be8095058e2i0). To use this, the parent inscription’s private key must be in your wallet (.wallet.json).

Example:

node dunes.js deployOpenDune 'RANDOM•DUNE•NAME' 'R' 100000000 8 null null null null 100 100000000 false true e6c6efe91b6084eae2c8a2fd6470d3d0dbfbb342f1b8601904f45be8095058e2i0

This deploys a Dune namedRANDOM•DUNE•NAME with symbolR, a limit of 100000000 per mint, 8 decimals, and premines 1R (100 atomic units) to the deployer. It’s linked to the parent inscriptione6c6...i0

Mint a dune:

node dunes.js mintDune <id> <amount> <to>

Example:

node dunes.js mintDune '5088000:50' 100000000 DTZSTXecLmSXpRGSfht4tAMyqra1wsL7xb

Mass mint a dune:

node dunes.js batchMintDune <id> <amount> <number-of-mints> <to>

Example (this will do 100x mints):

node dunes.js batchMintDune '5088000:50' 100000000 100 DTZSTXecLmSXpRGSfht4tAMyqra1wsL7xb

Get the ID from:https://ord.dunesprotocol.com/dunes

Print the balance of an address:

node dunes.js printDuneBalance <dune-name> <address>

Example:

node dunes.js printDuneBalance WHO•LET•THE•DUNES•OUT DTZSTXecLmSXpRGSfht4tAMyqra1wsL7xb

Split dunes from one output to many:

node dunes.js sendDuneMulti <txhash> <vout> <dune> <decimals> <amounts> <addresses>

Example:

node dunes.js sendDuneMulti 15a0d646c03e52c3bf66d67c910caa9aa30e40ecf27f495f1b9c307a4ac09c2e 1 WHO•LET•THE•DUNES•OUT 8 2,3 DDjbkNTHPZAq3f6pzApDzP712V1xqSE2Ya,DTnBdk1evnpbKe1qeCoeATHZnAVtwNR2xe

Combine dunes from multiple outputs to one:

node dunes.js sendDunesNoProtocol <address> <utxo-amount> <dune>

Example:

node dunes.js sendDunesNoProtocol DDjbkNTHPZAq3f6pzApDzP712V1xqSE2Ya 10 WHO•LET•THE•DUNES•OUT

You can link a new Dune to an existing "parent" inscription (e.g., an image or another Dune) using the optional[parentId] parameter indeployOpenDune. This creates a hierarchical relationship between digital assets.

Requirements:

• The parent inscription’s private key must be in your wallet (.wallet.json), as the script spends its UTXO to establish the link.
• TheparentId must be a valid inscription ID in the formattxid:iN (e.g.,e6c6efe91b6084eae2c8a2fd6470d3d0dbfbb342f1b8601904f45be8095058e2i0), wheretxid is the transaction ID andN is the output index.

Why Use It?:

• Organize related Dunes under a single parent (e.g., linking single or multiple Dunes to an image).
• Build structured collections with parent-child relationships.

Important Notes:

• This feature is optional. Dunes can be etched without a parent if noparentId is provided.

• This "Requires" the parent’s private key to be accessible in the wallet.

• Ensure that the parent inscription’s private key is accessible in the wallet derived from your MetaMask seed phrase. This is necessary because the transaction will spend the parent UTXO to establish the parent-child relationship

There's a problem with the node connection. Yourdogecoin.conf file should look something like:

rpcuser=aperpcpassword=zordrpcport=22555server=1

Make sureport is not set to the same number asrpcport. Also make surerpcauth is not set.

Your.env file should look like:

NODE_RPC_URL=http://127.0.0.1:22555NODE_RPC_USER=apeNODE_RPC_PASS=zordTESTNET=false

The miner fee is too low. You can increase it up by putting FEE_PER_KB=300000000 in your .env file or just wait it out. The default is 100000000 but spikes up when demand is high.