Bellscriptions
A minter and protocol for inscriptions on Bells forked from Ordinals Wallet.
⚠️⚠️⚠️ Important ⚠️⚠️⚠️
Use this wallet for inscribing only! Always inscribe from this wallet to a different address, e.g. one you created with Ordinals Wallet. This wallet is not meant for storing funds or inscriptions.
Prerequisites
This guide requires a bit of coding knowledge and running Ubuntu on your local machine or a rented one. To use this, you'll need to use your terminal to setup a Bellscoin node, clone this repo and install Node.js on your computer.
Setup Bellscoin node
Get Nintondo Core Wallet (v3)
On your Terminal, type the following commands:
cd
wget https://github.com/Nintondo/bellscoinV3/releases/download/v3.0.0-rc2/bells-3.0.0-rc2-x86_64-linux-gnu.tar.gz
tar -xvzf bells-3.0.0-rc2-x86_64-linux-gnu.tar.gzRename Bells folder
Will be much easier to navigate thru your folders.
mv bells-3.0.0-rc2 bellsRun Bellscoin node
cd bells
cd bin
./bellsd -daemonConfigure node
Create a bells.conf file with your node information:
Copy and Paste the following into the bells.conf file
Wait for the node to fully sync. Check the status by typing the command bells-cli getinfo on the same directory.
Install NodeJS
Please head over to (https://github.com/nodesource/distributions#using-ubuntu) and follow the installation instructions.
Check if they are installed by running the following commands: node -v and npm -v
Setup Bellscriptions
Clone Bellscription minter
On your Terminal, type the following commands:
Setup minter
Install dependencies:
Create a .env file with your node information:
On your Terminal, type the following commands:
Copy and Paste the following into the .env file
Funding
Generate a new .wallet.json file:
Then send BELLS to the address displayed. Once sent, sync your wallet:
If you are minting a lot, you can split up your UTXOs:
When you are done minting, send the funds back:
Minting
From file:
Repeating:
Examples:
Bellmap
You may bulk mint bellmap by specifying an address to receive and a start and end bellmap number
Examples:
Viewing
Start the server:
And open your browser to:
Protocol
The bellscriptions protocol allows any size data to be inscribed onto subwoofers.
An inscription is defined as a series of push datas:
For bellscriptions, we introduce a couple extensions. First, content may spread across multiple parts:
This content here would be concatenated as "Woof and woof woof!". This allows up to ~1500 bytes of data per transaction.
Second, P2SH is used to encode inscriptions.
There are no restrictions on what P2SH scripts may do as long as the redeem scripts start with inscription push datas.
And third, inscriptions are allowed to chain across transactions:
Transaction 1:
Transaction 2
With the restriction that each inscription part after the first must start with a number separator, and number separators must count down to 0.
This allows indexers to know how much data remains.
FAQ
I'm getting ECONNREFUSED errors when minting
There's a problem with the node connection. Your bellscoin.conf file should look something like:
Make sure port is not set to the same number as rpcport. Also make sure rpcauth is not set.
Your .env file should look like:
I'm getting "insufficient priority" errors when minting
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.
Last updated