# \[Ideas\] Metaprotocol Ideas Discussion

**URL:** <https://l1f.discourse.group/t/ideas-metaprotocol-ideas-discussion/376>\
**Category:** General\
**Tags:** general\
**Created:** [January 18, 2024, 2:32pm UTC](https://l1f.discourse.group/t/ideas-metaprotocol-ideas-discussion/376 "2024-01-18T14:32:35Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![domo](https://yyz1.discourse-cdn.com/flex007/user_avatar/l1f.discourse.group/domo/32/10_2.png) [@domo](https://l1f.discourse.group/u/domo)\
**Post date:** [January 18, 2024, 2:32pm UTC](https://l1f.discourse.group/t/ideas-metaprotocol-ideas-discussion/376/1 "2024-01-18T14:32:35Z")

</div>

Thread for general metaprotocol ideas discussion

---

<div class="post-metadata">

**Author:** ![domo](https://yyz1.discourse-cdn.com/flex007/user_avatar/l1f.discourse.group/domo/32/10_2.png) [@domo](https://l1f.discourse.group/u/domo)\
**Post date:** [January 18, 2024, 2:49pm UTC](https://l1f.discourse.group/t/ideas-metaprotocol-ideas-discussion/376/2 "2024-01-18T14:49:11Z")

</div>

“First is First” mint style drop validity rule initialization before launch.

---

<div class="post-metadata">

**Author:** ![domo](https://yyz1.discourse-cdn.com/flex007/user_avatar/l1f.discourse.group/domo/32/10_2.png) [@domo](https://l1f.discourse.group/u/domo)\
**Post date:** [January 18, 2024, 3:36pm UTC](https://l1f.discourse.group/t/ideas-metaprotocol-ideas-discussion/376/3 "2024-01-18T15:36:25Z")

</div>

Standard method to formulaically define a new satribute or save an existing satribute to a repository.

---

<div class="post-metadata">

**Author:** ![lgc1190](https://avatars.discourse-cdn.com/v4/letter/l/87869e/32.png) [@lgc1190](https://l1f.discourse.group/u/lgc1190)\
**Post date:** [January 18, 2024, 4:34pm UTC](https://l1f.discourse.group/t/ideas-metaprotocol-ideas-discussion/376/4 "2024-01-18T16:34:39Z")

</div>

Let us turn our attention to cbrc20. They are doing some great things. They use the field information on the meta protocol to perform virtualization operations. Combined with their own designed xord indexer, they are implementing the swap function on btc layer1. They will soon Will launch this big bang！

---

<div class="post-metadata">

**Author:** ![domo](https://yyz1.discourse-cdn.com/flex007/user_avatar/l1f.discourse.group/domo/32/10_2.png) [@domo](https://l1f.discourse.group/u/domo)\
**Post date:** [January 18, 2024, 4:52pm UTC](https://l1f.discourse.group/t/ideas-metaprotocol-ideas-discussion/376/5 "2024-01-18T16:52:48Z")

</div>

We’d be happy to have them post their primordial singularity here!

---

<div class="post-metadata">

**Author:** ![Mika](https://avatars.discourse-cdn.com/v4/letter/m/ea5d25/32.png) [@Mika](https://l1f.discourse.group/u/Mika)\
**Post date:** [January 19, 2024, 12:28am UTC](https://l1f.discourse.group/t/ideas-metaprotocol-ideas-discussion/376/6 "2024-01-19T00:28:36Z")

</div>

Hi Domo, we would like to share our protocol BRC1024, but we don’t have permission. Could you help us add it to my account? BRC1024 is an open metaverse construction protocol. You can take a look, and we believe you will like it.  
whitepaper: www[dot]brc1024[dot]io

---

<div class="post-metadata">

**Author:** ![domo](https://yyz1.discourse-cdn.com/flex007/user_avatar/l1f.discourse.group/domo/32/10_2.png) [@domo](https://l1f.discourse.group/u/domo)\
**Post date:** [January 19, 2024, 12:45am UTC](https://l1f.discourse.group/t/ideas-metaprotocol-ideas-discussion/376/7 "2024-01-19T00:45:26Z")

</div>

Have granted the necessary permissions. For others with similar requests please follow:

> [@Please DM @domo on discourse to post new topic](https://l1f.discourse.group/t/please-dm-domo-on-discourse-to-post-new-topic/384):
>
> Permission to post new topics is currently limited to prevent phishing and scams. Please dm me (@domo) via the chat feature on discourse to get access.

---

<div class="post-metadata">

**Author:** ![Mika](https://avatars.discourse-cdn.com/v4/letter/m/ea5d25/32.png) [@Mika](https://l1f.discourse.group/u/Mika)\
**Post date:** [January 19, 2024, 1:25am UTC](https://l1f.discourse.group/t/ideas-metaprotocol-ideas-discussion/376/8 "2024-01-19T01:25:34Z")

</div>

Hi Domo, I still can’t post. It said “An error occurred: You are not permitted to view the requested resource.” PPPPlease help us again 😂

---

<div class="post-metadata">

**Author:** ![ismail](https://yyz1.discourse-cdn.com/flex007/user_avatar/l1f.discourse.group/ismail/32/135_2.png) [@ismail](https://l1f.discourse.group/u/ismail)\
**Post date:** [January 19, 2024, 8:03am UTC](https://l1f.discourse.group/t/ideas-metaprotocol-ideas-discussion/376/9 "2024-01-19T08:03:54Z")

</div>

CBRC-20 is best metaprotocol as far as I got it. Lets see how it grows.

---

<div class="post-metadata">

**Author:** ![cadmusbenedictus](https://avatars.discourse-cdn.com/v4/letter/c/7bcc69/32.png) [@cadmusbenedictus](https://l1f.discourse.group/u/cadmusbenedictus)\
**Post date:** [January 19, 2024, 2:46pm UTC](https://l1f.discourse.group/t/ideas-metaprotocol-ideas-discussion/376/11 "2024-01-19T14:46:23Z")

</div>

The docs are quite detailed and are available in their website: cybord org/#introduction

CBRC-20 uses custom Ordinal client called xORD: github com/the-moto/xord

Can’t post links, will have to add the “.” after the domain. 🙂

---

<div class="post-metadata">

**Author:** ![shiftshapr](https://avatars.discourse-cdn.com/v4/letter/s/839c29/32.png) [@shiftshapr](https://l1f.discourse.group/u/shiftshapr)\
**Post date:** [January 30, 2024, 2:37am UTC](https://l1f.discourse.group/t/ideas-metaprotocol-ideas-discussion/376/12 "2024-01-30T02:37:05Z")

</div>

I am working on a knowledge artifact metaprotocol that builds an information ecology on Ordinals and, ultimately, the entire web. “Bridge inscriptions” connect inscription and/or web content snippets with a relationship. For example, imagine a citing bridge between a sentence in a hard media blog post and a PFP inscription that it refers to. Or a contradictory bridge between the sentence and a segment of a video where the person in the video is saying something that contradicts what was written in the sentence. The bridges can be ordinal to ordinal, ordinal to web page, or web page to web page. Bridge inscriptions aggregate into a knowledge graph, which can be used to improve search on Ordinals and the web. Bridge ordinals can be traded as bitcoin native assets. First is first.

---

<div class="post-metadata">

**Author:** ![0xBes](https://yyz1.discourse-cdn.com/flex007/user_avatar/l1f.discourse.group/0xbes/32/88_2.png) [@0xBes](https://l1f.discourse.group/u/0xBes)\
**Post date:** [March 10, 2024, 3:07pm UTC](https://l1f.discourse.group/t/ideas-metaprotocol-ideas-discussion/376/13 "2024-03-10T15:07:43Z")

</div>

Hello guys, why is no one talking about BRC20S ?

Introduction to BRC20-S 🟧

The BRC20-S introduces an extended version of the BRC-20 standard for the #Bitcoin blockchain, incorporating #BRC20 design principles while adding functionalities for staking operations such as deposits, minting, and withdrawals.

This protocol offers a staking mechanism specifically tailored for BRC-20 tokens or, allowing users to stake their BRC-20 tokens or bitcoins in exchange for BRC20-S tokens.

These extend the functionalities of BRC-20 tokens with a detailed staking protocol, rewarding engagement and participation in the Bitcoin network.

ORDI: 09.03.23  
sORDI: 09.03.24  
For the culture🧠

Im on X: @Besbtc

I cant share link+image

@domo thank you 🟧

---

<div class="post-metadata">

**Author:** ![walodopi](https://yyz1.discourse-cdn.com/flex007/user_avatar/l1f.discourse.group/walodopi/32/314_2.png) [@walodopi](https://l1f.discourse.group/u/walodopi)\
**Post date:** [October 29, 2026, 12:27pm UTC](https://l1f.discourse.group/t/ideas-metaprotocol-ideas-discussion/376/15 "2026-10-29T12:27:37Z")

</div>

A shared event format could make separate metaprotocols easier for wallets to recognize without forcing them to share application rules. Each event could declare a protocol identifier and version, with unknown fields preserved rather than silently discarded. That gives clients a safe way to display unfamiliar data and leaves room for incompatible versions to coexist.
