# Previous Version 1.0

Author: Ivan Tsang (@ivantkf) Created: 2023-03-13 Require: Ordinals {% embed url="" %} ## Vision > Be Your Own Bank. Inscription (NFT) is one of the ways to achieve Bitcoin-M instead of USD-M. When Ethereum NFTs have been shown up at the beginning, there was a moment when people were more focused on Ether ($ETH) than USD to reach Ether-M instead of USD-M, and that's what I am trying to achieve and promote to the general public. ## Idea The concept is inspired by the brc-20 and ERC-1155 standards. The inscriptions with BRC-1155 standard are just another kind of Ordinals inscriptions, they can be traded, collected, and transferred as usual. Meanwhile, I am studying more standard protocols on Ethereum and seeing if they are possible to deploy on Bitcoin Core Network to support the inscriptions. The Ordinals Inscription here will be defined as BRC-721.

## Introduction | Project Owner | Inscription Holders | All Users | | :-----------: | :-----------------: | :-------: | | Deploy | Fractionalize | Mint | | Burn | Burn | | | Mint | Mint | | | | Recovery | | This is demonstrating what operations we can do above {deploy, burn, fractionalize, recovery, mint} by using the BRC-1155 standard, and the function structure below,

## Operations {% embed url="" %} A secret code should be set by using SHA-256 algorithm for safety and transperancy during the verification {% endembed %} ### 1.　Deploy The project owners could create a BRC-1155 collection of their inscriptions with a single image to inscribe the rules and save the cost. Here is a basic example below (replace the x), ``` { "p": "brc-1155", "op": "deploy", "abbrev": "xxxx", "url": "inscription xxxxxx" } ``` {% hint style="danger" %} **An inscription with a picture MUST be inscribed before deploying the BRC-1155 standard** {% endhint %}

Key	Must?	Description
p	✅	Protocol: To identify and process BRC-1155 events
op	✅	Operation: Type of events {deploy, fractionalize, mint...}
abbrev	✅	Abbreviation: Set a max. 10 letters identifier of the BRC-1155
url	✅	Identifier of the original image location of the inscription
author	❌	Identifier of the project creator/ team with {.sats} / {.ord} domain
max	❌	Set the total quantity in pieces of the operation, default to "∞"
lim	❌	Limit: Set the fixed amount in every inscription, default to "1"
vfy	❌	Verify: Encrypted by SHA-256 Algorithm for a further action

### 2.　Inscribe (Mint) All users are allowed to inscribe different quantities of the inscriptions with BRC-1155 standard to collect a valid piece of the expensive inscriptions at an affordable price until it reaches the maximum quantity. The reminding available quantity is only valid according to a first-come-first-served basis. Here is a basic example below (replace the x), ``` { "p": "brc-1155", "op": "mint", "abbrev": "xxxx", "url": "inscription xxxxxx" } ``` {% hint style="danger" %} **Stay alert for scammers and focus on the maximum inscription number.** {% endhint %}

Key	Must?	Description
p	✅	Protocol: To identify and process BRC-1155 events
op	✅	Operation: Type of event {deploy, fractionalize, mint...}
abbrev	✅	Abbreviation: Set a max. 10 letters identifier of the BRC-1155
url	✅	Identifier of the original image location of the inscription
author	❌	Identifier of the project creator/ team with {.sats} / {.ord} domain
atm	❌	Amount to mint in a BRC-1155 inscription, default to {deploy} setting
txt	❌	Write a short message on the inscription

### 3.　Burn The project owners / Fractionalized creators could burn inscriptions / fractionalized pieces within the BRC-1155 collections by connecting {deploy} with the verify code if it contains too many uninscribed inscriptions to decrease the total supply or achieve deflation in various activities. Here is a basic example below (replace the x), ``` { "p": "brc-1155", "op": "burn", "abbrev": "xxxx", "url": "inscription xxxxxx", "vfy": "xxxxx" } ``` {% hint style="danger" %} **An {deploy} MUST be inscribed before deploying the {burn} action to connect the {vfy}** {% endhint %}

Key	Must?	Description
p	✅	Protocol: To identify and process BRC-1155 events
op	✅	Operation: Type of events {deploy, fractionalize, mint...}
abbrev	✅	Abbreviation: Set a max. 10 letters identifier of the BRC-1155
url	✅	Identifier of the original image location of the inscription
author	❌	Identifier of the project creator/ team with {.sats} / {.ord} domain
vfy	✅	Verify: Encrypted and show the last 5 digits by SHA-256 Algorithm

### 4.　Fractionalize The holder of each BRC-721 inscription could fractionalize to separate a BRC-721 Inscription into many pieces to save the inscribing cost by inscribing **WITHOUT** the duplicated images. Here is a basic example below (replace the x), ``` { "p": "brc-1155", "op": "fractionalize", "abbrev": "xxxxxxxxx", "url": "inscription xxxxxx" } ``` {% hint style="danger" %} **This operation is ONLY available for the inscriptions with the BRC-721 standard.** {% endhint %}

Key	Must?	Description
p	✅	Protocol: To identify and process BRC-1155 events
op	✅	Operation: Type of events {deploy, fractionalize, mint...}
abbrev	✅	Abbreviation: Set a max. 10 letters identifier of the BRC-1155
url	✅	Identifier of the original image location of the inscription
author	❌	Identifier of the project creator/ team with {.sats} / {.ord} domain
max	❌	Set the total quantity in pieces of the operation, default to "∞"
lim	❌	Limit: Set the fixed amount in every inscription, default to "1"
vfy	❌	Verify: Encrypted and show the last 5 digits by SHA-256 Algorithm

### 5.　Recovery The inscription holder could recover or even get the inscription back by fractionalizing the original inscription for 1 more piece and using the verification code to prove the ownership of the inscription to re-inscribe for taking back control. Here is a basic example below (replace the x), ``` { "p": "brc-1155", "op": "recovery", "abbrev": "xxxxxxxxx", "url": "inscription xxxxxx", "vfy": "xxxxx" } ``` {% hint style="danger" %} **The recovery function for taking back control is depending on the view of project teams.** {% endhint %}

Key	Must?	Description
p	✅	Protocol: To identify and process BRC-1155 events
op	✅	Operation: Type of events {deploy, fractionalize, mint...}
abbrev	✅	Abbreviation: Set a max. 10 letters identifier of the BRC-1155
url	✅	Identifier of the original image location of the inscription
author	❌	Identifier of the project creator/ team with {.sats} / {.ord} domain
vfy	✅	Verify: Encrypted and show the last 5 digits by SHA-256 Algorithm

## 6.　Lock / Unlock (coming soon) {% hint style="info" %} The locking capability of BRC-721 / BRC-1155 will be included in BRC-5058 standard {% endhint %} ## Suggestions It is welcomed to provide recommendations for better improvement upon the structure, designs, rules, or compression issues it poses. For traceability json {} is required, as well as the minimum required information to satisfy one of the functions. ## Ending The standard is still updating. Thank you for taking the time to read the whole passage. You are going to be one of the historical witnesses in Bitcoin development. Please bear in mind that these might be worthless, but the journey should be priceless. ## Extention of Supporting Standard {% embed url="" %} {% embed url="" %} > BRC-5058 Standard: Locking Capability of BRC-721 / BRC-1155 > > Coming Soon