没有不值得去解决的问题,也没有不值得去学习的技术!

Implementing New Minting Code for Atomicals-js in Windows 10

This time I am minting quark. The on-chain gas is about 124, so the mint command is: yarn cli mint-dft quark --satsbyte 124. This starts the minting process. Once the mint is complete, you can repeat the mint command to continue minting

1. Reference: Atomicals-js code minting tutorial.

2. Node.js is already installed, and the current Node version is the latest LTS version.

Plaintext

PS C:\Users\Lenovo> node -v
v20.10.0

3. Git is already installed.

Plaintext

PS C:\Users\Lenovo> git -v
git version 2.37.0.windows.1

4. Go to the D drive, create a new folder named atomicals, and double-click to enter this folder. Type cmd in the address bar where the path is displayed and press Enter. This opens a terminal with the current directory as the default path. See Figure 1.

Go to the D drive, create a new folder named atomicals, and double-click to enter this folder. Type cmd in the address bar where the path is displayed and press Enter. This opens a terminal with the current directory as the default path
Figure 1

5. Enter git clone https://github.com/atomicals/atomicals-js.git in the terminal and press Enter to download the atomicals-js source code. See Figure 2.

Enter git clone https://github.com/atomicals/atomicals-js.git in the terminal and press Enter to download the atomicals-js source code
Figure 2
Plaintext

D:\atomicals>git clone https://github.com/atomicals/atomicals-js.git
Cloning into 'atomicals-js'...
remote: Enumerating objects: 1629, done.
remote: Counting objects: 100% (1629/1629), done.
remote: Compressing objects: 100% (583/583), done.
remote: Total 1629 (delta 1184), reused 1396 (delta 1028), pack-reused 0Receiving objects:  99% (1613/1629), 3.68 MiB | 661.00 KiB/s
Receiving objects: 100% (1629/1629), 3.78 MiB | 550.00 KiB/s, done.
Resolving deltas: 100% (1184/1184), done.


6. Execute the following commands in sequence. For the command: npm install -g yarn, I did not need to run it on my computer because yarn was already installed. See Figure 3.

Execute the following commands in sequence. For the command: npm install -g yarn, I did not need to run it on my computer because yarn was already installed
Figure 3
Plaintext

D:\atomicals>cd atomicals-js

D:\atomicals\atomicals-js>yarn -v
1.22.15

D:\atomicals\atomicals-js>yarn install
yarn install v1.22.15
[1/4] Resolving packages...
[2/4] Fetching packages...
info fsevents@1.2.13: The platform "win32" is incompatible with this module.
info "fsevents@1.2.13" is an optional dependency and failed compatibility check. Excluding it from installation.
info fsevents@2.3.3: The platform "win32" is incompatible with this module.
info "fsevents@2.3.3" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
[4/4] Building fresh packages...
warning Your current version of Yarn is out of date. The latest version is "1.22.19", while you're on "1.22.15".
Done in 217.51s.

D:\atomicals\atomicals-js>yarn run build
yarn run v1.22.15
$ tsc && gulp build
$ echo '#!/usr/bin/env node:\atomicals\atomicals-js\gulpfile.js
' | cat - dist/cli.js > temp && mv temp dist/cli.js
'#!/usr/bin/env node'build' after 2.12 min
Done in 268.85s.


7. Open the .env file with EditPlus and modify the node settings. The main changes are updating ELECTRUMX_PROXY_BASE_URL and adding the line CONCURRENCY=16.

Plaintext

# Install your own ElectrumX, Proxy and Service to help decentralization
# https://github.com/atomicals/electrumx-proxy
# https://github.com/atomicals/atomicals-electrumx
#
# PUBLIC ELECTRUMX PROXIES
#
# Bitcoin:
# ELECTRUMX_PROXY_BASE_URL=https://ep.atomicals.xyz/proxy
#
# Bitcoin (Testnet):
# ELECTRUMX_PROXY_BASE_URL=https://eptestnet.atomicals.xyz/proxy

ELECTRUMX_PROXY_BASE_URL=https://ep.atomicalmarket.com/proxy
WALLET_PATH=./wallets
WALLET_FILE=wallet.json
# testnet or livenet or regtest
NETWORK=livenet
DISABLE_DONATE_QUOTE=false
CONCURRENCY=16

8. Note: 54 is the maximum number of threads. Modify this based on your computer’s CPU core count. If your CPU has more than 14 cores, you can set it to 54. If you are unsure, set it to 16 first and adjust the value later based on CPU usage. To check your CPU core count, go to Performance – CPU in Task Manager. As shown there, the core count is 2, so I decided to set it to 6 to avoid severely impacting computer performance. See Figure 4.

Note: 54 is the maximum number of threads. Modify this based on your computer's CPU core count. If your CPU has more than 14 cores, you can set it to 54. If you are unsure, set it to 16 first and adjust the value later based on CPU usage. To check your CPU core count, go to Performance - CPU in Task Manager. As shown there, the core count is 2, so I decided to set it to 6 to avoid severely impacting computer performance
Figure 4

9. Enter yarn cli wallet-init in the terminal to create a wallet, and transfer BTC to the funding address to pay for the minting fees. primary.address is the wallet address for receiving inscriptions. funding.address is the wallet address for paying fees. See Figure 5.

Enter yarn cli wallet-init in the terminal to create a wallet, and transfer BTC to the funding address to pay for the minting fees. primary.address is the wallet address for receiving inscriptions. funding.address is the wallet address for paying fees
Figure 5

10. You can view the file: D:\atomicals\atomicals-js\wallets\wallet.json. WIF is the private key (one private key corresponds to one address). phrase is the mnemonic phrase. In the OKX wallet, you can add a wallet – import existing wallet – private key – import private key. I added up to 2 accounts. See Figure 6.

You can view the file: D:\atomicals\atomicals-js\wallets\wallet.json. WIF is the private key (one private key corresponds to one address). phrase is the mnemonic phrase. In the OKX wallet, you can add a wallet - import existing wallet - private key - import private key. I added up to 2 accounts
Figure 6

11. The values of address are the Taproot format BTC addresses in the accounts. See Figure 7.

The values of address are the Taproot format BTC addresses in the accounts
Figure 7

12. Then scan the receiving address of the funding.address account. Transfer some BTC; I plan to mint about 10 copies. The current cost per copy is about 30U. I decided to deposit BTC worth 300U. Confirm the arrival. See Figure 8.

Then scan the receiving address of the funding.address account. Transfer some BTC; I plan to mint about 10 copies. The current cost per copy is about 30U. I decided to deposit BTC worth 300U. Confirm the arrival
Figure 8

13. Start minting the inscription. The mint command is: yarn cli mint-dft xxxx –satsbyte xx. xxxx is the name of the inscription and needs to be changed to the actual name. –satsbyte xx sets the gas, which is determined by on-chain conditions. I confirmed the average on-chain gas is: 124. See Figure 9.

Start minting the inscription. The mint command is: yarn cli mint-dft xxxx --satsbyte xx. xxxx is the name of the inscription and needs to be changed to the actual name. --satsbyte xx sets the gas, which is determined by on-chain conditions. I confirmed the average on-chain gas is: 124
Figure 9

14. This time I am minting quark. The on-chain gas is about 124, so the mint command is: yarn cli mint-dft quark –satsbyte 124. This starts the minting process. Once the mint is complete, you can repeat the mint command to continue minting. See Figure 10.

This time I am minting quark. The on-chain gas is about 124, so the mint command is: yarn cli mint-dft quark --satsbyte 124. This starts the minting process. Once the mint is complete, you can repeat the mint command to continue minting
Figure 10

关于作者 · 持续学习与技术实践

我是一名拥有 15 年以上开发经验的技术从业者,自 2013 年起持续运营个人技术博客,记录工作与个人项目中遇到的真实问题,以及解决问题过程中的探索、实践和思考。

除了技术写作,我也在持续开发和维护自己的独立项目,探索新技术和新工具在实际场景中的应用。我始终相信,没有不值得去解决的问题,也没有不值得去学习的技术。

如果这篇文章对你有所帮助,欢迎浏览博客中的其他文章,也欢迎交流技术经验与想法。

关于我  ·  GitHub  ·  邮件联系