Pinned Tweet
Periodic reminder: there is only one PoW blockchain called Bellscoin based on work of @BillyM2k . There are "vaulted" versions on ETH and SOL (see @vBells_on_SOL), but low liquidity rn, so recommend exchanges or @AlchemyPay . Other tokens on SOL, ETH, etc. are just imitators.
Most builder friendly Scrypt blockchain 🔔🛠️
(credit: @AMJ_BTC)
Bellscoin Blockchain 🔔 retweeted
Bitcoin: 21 million.
Bells: 2 per minute. Forever.
I've done the math.
🤖 Made with AI
Bellscoin Blockchain 🔔 retweeted
🔔 Before Dogecoin, Billy Markus created Bells.
For anyone unfamiliar with Bellscoin ($BELLS), its story goes back to November 28, 2013, eight days before Dogecoin. It was created by Billy Markus (@BillyM2K), who later co-created Dogecoin with Jackson Palmer. Bells was inspired by the currency in Animal Crossing. (bitcointalk.org, viabtc.net, dogecoin.com)
One fascinating detail is “Nintondo”, the playful Nintendo reference found in the genesis blocks of both Bells and Dogecoin. You can still find it in Dogecoin’s source code today—a small piece of their shared history preserved in the blockchain. (viabtc.net, github.com)
How does Bells work? ⚙️
Bells operates its own blockchain using Scrypt Proof of Work. Miners contribute computing power to produce blocks, while nodes verify transactions and enforce the network’s rules.
It supports merged mining with Litecoin and Dogecoin through AuxPoW. This allows participating miners to reuse the same mining work to secure multiple networks and earn rewards in LTC, DOGE and BELLS. Each blockchain retains its own transactions, currency and rules. ViaBTC is one pool supporting this setup. (github.com, support.viabtc.com, litecoin.com)
What makes it stand out? ✨
• Historical roots: A 2013 creation by the same developer who went on to co-create Dogecoin.
• Its own Layer 1: BELLS is the native coin of an independent blockchain.
• Merged mining: Access to participating Scrypt miners alongside Litecoin and Dogecoin.
• Approximately one-minute blocks: A short target interval for including transactions.
• No premine: The original launch distributed coins through mining.
• Open-source development: Anyone can inspect the code and contribute.
• An expanding ecosystem: Community-built tools include wallets, explorers and inscription/NFT marketplaces such as Nintondo. (bitcointalk.org, viabtc.net, github.com, docs.nintondo.io)
Two details worth understanding: the original project dates to 2013, but its community revival took place in December 2023. Also, BELLS has no fixed maximum supply: its emission schedule eventually settles at 2 BELLS per block, approximately 1.05 million coins annually at the target block time. (bellscoin.com)
For me, the interesting combination is its early history, independent blockchain and place in the Litecoin–Dogecoin merged-mining ecosystem. 🔔⛏️
Explore the sources:
🔗 bitcointalk.org/index.php?to…
🔗 bellscoin.com
🔗 github.com/BellsChain/bellsc…
🔗 github.com/dogecoin/dogecoin…
🔗 support.viabtc.com/hc/en-us/…
#LTC | #DOGE | #BELLS | #ELONMUSK
“I saved your image. Did I steal your inscription?”
You copied a file. That action didn't transfer the inscription.
Take OP_CAT #464 on Nintondo's Bellscoin view. Its artwork is publicly viewable. You can save the image without holding that inscription.
What ends up in your Downloads folder is a copy of the picture. It does not change the inscription's recorded holder or give you the keys needed to transfer it.
The image is what you see. The inscription has its own ID and transaction history on its chain. Sending it requires an authorized transaction, not a browser download.
You can check the distinction on Nintondo:
→ Select Bellscoin and open the OP_CATS collection.
→ Open OP_CAT #464, then find its ID under Inscription Info.
→ Compare the artwork with a saved copy. They can look identical, but possessing that file does not give you control of the inscription identified by that ID.
The ID is public too. Copying it into a message doesn't give you control either.
And if someone inscribes the same image again, that creates a separate inscription. It doesn't take over the existing one.
Right-click copies the picture. It doesn't sign a transfer.
I arrived just in time for all the drama!
bellscoin:native is bellscoin:native
One day it will be $1B+ MC and beyond
@BellsChain
Bellscoin Blockchain 🔔 retweeted
xitter.cf/s_on_chain/status/2112…
we buy all the bellscoin:native using bells magic and bells language, we pull it to 1000u
Bellscoin Blockchain 🔔 retweeted
“I saved your image. Did I steal your inscription?”
You copied a file. That action didn't transfer the inscription.
Take OP_CAT #464 on Nintondo's Bellscoin view. Its artwork is publicly viewable. You can save the image without holding that inscription.
What ends up in your Downloads folder is a copy of the picture. It does not change the inscription's recorded holder or give you the keys needed to transfer it.
The image is what you see. The inscription has its own ID and transaction history on its chain. Sending it requires an authorized transaction, not a browser download.
You can check the distinction on Nintondo:
→ Select Bellscoin and open the OP_CATS collection.
→ Open OP_CAT #464, then find its ID under Inscription Info.
→ Compare the artwork with a saved copy. They can look identical, but possessing that file does not give you control of the inscription identified by that ID.
The ID is public too. Copying it into a message doesn't give you control either.
And if someone inscribes the same image again, that creates a separate inscription. It doesn't take over the existing one.
Right-click copies the picture. It doesn't sign a transfer.





















