# Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation This site has an agentic ask interface you may use to query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.runealpha.xyz/index.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. --- # Languages * [🏴󠁧󠁢󠁥󠁮󠁧󠁿 English](/en) * [🇨🇳 中文](/cn) # 概览 RuneAlpha 是一个基于比特币公链符文协议的超级APP 🚀.它是你深入研究符文协议的入口 , 查看交易数据, 处理数据, 并为符文协议提供广泛的工具和基础设施💪. RuneAlpha 是的你加密瑞士军刀, 主要特征有如下: * 一个用于token蚀刻和铸造的工具箱，非常适合所有的加密艺术家🎨。 * 一个符文的探索器，帮助你跟踪交易和管理你的符文资产，就像一个专业的资产管理员💼 * 一个符文交易市场，让你成为符文大富豪🏦 # 文档摘要 * [🏂 概述](/cn) * [🏹 Rune Alpha 阶段](/cn/rune-alpha-period) * [🚧 发行例子](/cn/issuance-example) * [🧗‍♀️ 服务条款](/cn/terms-of-service) * [🎨 媒体工具](/cn/media-kit) * [🤺 风险提示](/cn/risk-warning) ## Guides * [🔎 浏览](/cn/guides/scan) * [🤹 创建符文](/cn/guides/create-rune) * [🤼 转账](/cn/guides/transfer) * [👨‍🔬 Rune Alpha - Signet网](/cn/guides/rune-alpha-signet) * [🌀 Bitcoin 地址格式](/cn/guides/bitcoin-address-formats) * [⚗️ Rune Alpha - 测试网](/cn/guides/rune-alpha-testnet) ## 🥇 交易市场 * [❓ 什么是PSBTs技术 ?](/cn/marketplace/what-is-psbts) * [🏊‍♂️ 上架符文](/cn/marketplace/listing-rune) * [⛹️‍♂️ 下架符文](/cn/marketplace/unlist-rune) ## 🖼️ Ordinals 厨师 * [📢 分发](/cn/ordinals-chef/distribution) * [👩‍🍳 质押](/cn/ordinals-chef/cook-staking) * [💯 RuneAlpha 核心要点](/cn/ordinals-chef/runealpha-point) * [🏗️ Bitcoin 建设者](/cn/ordinals-chef/bitcoin-builder) * [🔢 荷兰式拍卖](/cn/ordinals-chef/auction) # 发行例子 `目标:发行$RUNE。总供应量21,000,000` #### 计算协议消息中的第一个数据 协议消息中的第一个数据推送被解码为序列整数。这些整数被解释为(ID, OUTPUT, AMOUNT)元组序列\ 整数被编码为前缀可变数，其中可变数的前导数决定了其字节长度。有很多类型的前缀变体，这是比特币的[风格](https://en.bitcoin.it/wiki/Protocol_documentation#Variable_length_integer) 要发出21000000符文，我们使用这个元组 `[0 , 1, 21000000].` 为什么是 `[0 , 1, 21000000]` ? * [x] 元组中的第一个整数是ID `0` 为了发行交易 * [x] 元组中的第二个整数`1` 映射到事务的输出索引 * [x] 元组中的第三个整数是发行金额 `21000000`
```javascript function encodeBitcoinVarInt(value) { if (value < 0xfd) { return [value]; } else if (value <= 0xffff) { return [0xfd, value & 0xff, (value >> 8) & 0xff]; } else if (value <= 0xffffffff) { return [0xfe, value & 0xff, (value >> 8) & 0xff, (value >> 16) & 0xff, (value >> 24) & 0xff]; } else { return [ 0xff, value & 0xff, (value >> 8) & 0xff, (value >> 16) & 0xff, (value >> 24) & 0xff, (value >> 32) & 0xff, (value >> 40) & 0xff, (value >> 48) & 0xff, (value >> 56) & 0xff, ]; } } function encodeBitcoinVarIntTuple(tuple) { const encodedBytes = tuple.map(encodeBitcoinVarInt).flat(); // Convert the bytes to a hexadecimal string const hexString = encodedBytes.map(byte => byte.toString(16).padStart(2, '0')).join(''); return hexString; } ``` 这是元组的数据 `[0, 1, 21000000]` 在对 **比特币风格的编码** 解码后\\ ```javascript 0 => 00 1 => 01 21000000 => fe406f4001 [0, 1, 21000000] => 0001fe406f4001 ``` #### 计算协议消息中的第一个数据 第二个数据推送被解码为两个整数, `SYMBOL`, `DECIMALS` `SYMBOL` 是一个26进制编码的人类可读符号，类似于oridinals名称中使用的符号。唯一有效的字符是`A`到`Z`. oridinals名称是[base-26](https://docs.ordinals.com/bounty/3.html?highlight=base-26#criteria)序数的编码。为了避免将短名字锁定在不可花费的创世区块coinbase奖励中，序数变得越来越短，序数变得越来越长。第一个要挖掘的卫星0的名称是`nvtdijuwxlp`，最后一个要挖掘的卫星2,099,999,997,689,999的名称是`a`。 ```javascript // Some code const bb26 = require("base26"); const text = 'rune'; const formatOrdinalBase26 = (text) => { const result = (2099999997689999 + 1 - bb26.from(text)); return result; }; ``` 这是元组的数据 `[RUNE, 18]` 在对 **比特币风格的编码** 解码后\\ ```javascript RUNE => 2099999997359067 => ffdbf3de59dbf3de59 18 => 12 [RUNE, 18] => ffdbf3de59dbf3de5912 ``` #### 协议消息的最后结果 ``` OP_RETURN 52 0001fe406f4001 ffdbf3de59dbf3de5912 ``` # 媒体工具
# 风险警告 请小心!在创建抢手的符文资产时，有在内存池中被超过的风险。 当网络拥挤时，mint/铸造新的Rune资产可能会导致资金损失。网络拥塞通常是抢铸造符文资产引起的。 如果交易的费率太低，则在区块事件完全完成之前可能不会确认交易。在这种情况下，您将不会收到任何符文资产，并且您已支付的网络费用将不会退还。 这种领先现象是比特币矿工处理交易方式的结果。他们通过包含基于最高网络费率的交易来创建区块。费率较高的交易获得优先权，即使它们提交的时间较晚。 # Rune Alpha 时期 厨师对它可能还没有完全煮熟，但它提供了一个诱人的一瞥符文协议的未来 符文协议目前处于预发布阶段，我们的专业厨师团队精心制作Alpha版本。这个初步版本旨在满足即将发布的主网版本的严格标准。这个演示是为那些处于技术采用前沿的人准备的，他们是真正的“alpha”。 * 该协议目前坚持序号版本0.11.1，可以在GitHub存储库的提交历史中找到:\[] * 协议签名已更新为' RUNE\_ALPHA ' * 可以通过以下URL扫描主网:[scan.runealpha.xyz](https://scan.runealpha.xyz/)。对于测试网，请使用以下网址:[testnet-scan.runealpha.xyz](https://testnet-scan.runealpha.xyz/) 符文协议标准: 💠 实现开放蚀刻([#2548](https://github.com/ordinals/ord/pull/2548))✅\ 💠 实现分割([#2530](https://github.com/ordinals/ord/pull/2530))✅\ 💠 编码符文石与标签([#2547](https://github.com/ordinals/ord/pull/2547))✅\ 💠 零数量的法令分配所有剩余的符文([#2531](https://github.com/ordinals/ord/pull/2531))✅\ 💠 总是创建符文，即使没有分配([#2543](https://github.com/ordinals/ord/pull/2543))✅\ 💠 Delta在指令中编码符文id ([#2532](https://github.com/ordinals/ord/pull/2532))✅\ 💠 追踪燃烧的符文([#2511](https://github.com/ordinals/ord/pull/2511))✅\ 💠 不编码可除性如果为零([#2510](https://github.com/ordinals/ord/pull/2510))✅\ 💠 使用可除性格式化符文供应([#2509](https://github.com/ordinals/ord/pull/2509))✅ **当心**: 记住，这还不是一顿美食，所以只有最具冒险精神的人才可以品尝.\\
# 符文条款 1. 请注意，如果平台上有积压的订单，这可能会导致链上交易处理的延迟。我们无法向您保证链上处理的确切时间。 2. 你现在看到的速率并不能反映实时链上速率。请记住，链上速率可能会发生变化。 3. 如果您的支付账户有任何尚未确认的出境交易，建议您停止支付或切换到其他账户进行操作。 4. 如果您遇到正在雕刻的订单，请等待矿商的确认。请注意，一旦交易正在进行中，就不能取消。 5. 如果用户从禁止加密货币的司法管辖区访问，我们无法承担责任。用户遵守当地的法律法规是至关重要的。 6. \*\*请小心处理钱包内的铭文。\*\*您使用的钱包可能无法有效处理铭文，导致交易过程中丢失铭文。为了确保重要订阅的安全，建议使用单独的钱包。 请确保您完全理解这些风险，并准备好接受可能由此产生的所有后果。 # guides # 比特币地址格式 原生隔离见证、嵌套隔离见证、Taproot和Legacy都是比特币网络中不同的比特币地址格式或交易类型。每一种都有自己的特点和好处: 1. **本地隔离见证(Segregated Witness Bech32):** 钱包的支持 **Phantom, Leather, Unisat, Okex Wallet** * 本地隔离见证地址以 "**bc1**."开始 * 也称为Bech32地址. * 利用隔离见证(SegWit)升级，将见证数据从交易数据中分离出来，从而减少交易规模和降低费用。. * 与遗留地址相比，提供了改进的安全性和更好的可伸缩性. * 由于较低的费用和增强的功能，建议用于大多数交易. 举例: **bc1qju52hg5v6z0f5ds49p4t33wz8gl88a5cuzx7hf** 2. **嵌套隔离见证(付费见证公钥哈希，P2SH-P2WPKH):** 钱包的支持: **Xverse, Unisat, Okex Wallet** * 嵌套的隔离见证地址以 "**3.**"开始 * 将SegWit的优点与不支持Bech32地址的旧钱包软件的兼容性结合起来. * 允许交易发送到隔离见证地址，即使发送者的钱包本身不支持隔离见证. * 与本地SegWit相比，嵌套SegWit地址的交易略大，费用可能略高. 例子: **3NeLJQTPMJTZwuyYrMJLYHmtpqT7x8dYsk** 3. **Taproot:** 钱包的支持: **Xverse, Phantom, Unisat, Okex Wallet** * Taproot是比特币的一项改进提议，可增强隐私、安全性和智能合约功能. * 用Taproot创建的地址以"**bc1p.**"开始 * 将多个支出条件合并为一个，使复杂的交易与区块链上的简单交易无法区分，以提高隐私性. * 预计将降低交易费用，并实现更先进的智能合约. 例子: **bc1psd90nx647p00y0zx04kl5sx9sgjcpeeqyh9t8d0j220ssvu250hq20c84a** 4. **Legacy (Pay to Public Key Hash, P2PKH):** 钱包的支持: **Unisat**, **Okex Wallet , Unisat** * Legacy 地址以 "**1.**"开始 * 这些是原始比特币地址和交易类型. * 与SegWit地址相比，交易规模更大，通常费用更高. * 虽然仍然得到广泛支持，但传统地址的效率和安全性不如SegWit地址. 例子 : **1HzCQZtedJ5jbn1YBuqgtkPVwfkjkuzyNR** 注意\*\*:\*\* 由于安全问题和成本优化的用户，我们将不支持**LEGACY 钱包** # 创建符文 **步骤一: 填写符文信息** 确保没有创建 **Ticker**
**步骤二: 选择etching(蚀刻)类型** RuneAlpha 提供2种蚀刻 **类型 1:** 市场上限将被**锁定**和**加载**，并且您将在启动符文时指定每个地址的token计数 注意选择小数

固定限额

**类型2:** 公平铸币(如 **$COOK** 蚀刻)，创建者规定每笔交易可以铸造多少代币以及矿工可以交易的区块数量

公平铸币

每个模块在10分钟内完成，认为它有一个合理的时间。 **步骤 三: 选择 sats/vB** (Gas) **然后处理**
请在执行交易前查看**风险警告** # Rune Alpha - Signet 我们永远不会忘记凯西的最新更新，以保持#阿尔法 ! ### 配置的钱包 在Signet中，连接的主要方式是通过 [Leather Wallet](https://chromewebstore.google.com/detail/leather/ldinpeekobnhjjdofggfgjlcehhmanlj). 要开始，请遵循以下步骤: 1. 从扩展商店安装 Leather 钱包. 2. 配置连接Signet的网络设置." 第一步:改变网络

Change network

第一步: 选择 Signet

Select network

### Faucet BTC signet 你可以在这里获得一些免费的比特币 signet {% embed url="" %} ### 连接 Rune Alpha \[Signet] {% embed url="" %} 让我们开始你的DEGEN之旅吧:
# Rune Alpha - Testnet 欢迎来到我们的创新乐园，在这里我们把我们的产品 最终的考验! 💥🔬 ## 配置网络 ### Unisat: * 步骤1:选择setting
### * 第二步:选择网络
* 步骤3:选择Testnet
### Xverse * 步骤 1:
* 步骤 2:
* 步骤 3:
### Leather 步骤 1:
步骤 2:
# 浏览 搜索框接受钱包地址，符文名称，交易哈希值 transactions 交易可以通过哈希搜索，例如:$COOK 创建 transaction: {% embed url="" %} Runes Runes 可以通过符文名称搜索，例如，$COOK可以通过id搜索: {% embed url="" %} Address 地址可以通过地址哈希搜索，这将显示所有的交易。我们还提供了一个选项，只显示符文交易. {% embed url="" %} # 转账 烹饪的杰作是完美的，将很快被优雅地镀为一场感官盛宴!🍽️🚀 # marketplace # 上架符文 Step by step to list your rune **注意**: **Listing是完全免费的，因为我们使用PSBT，但请注意，取消上架需要您进行交易，这意味着您将放弃一些sats来刷新上架期间使用的UTXO.** 步骤1: 在首页点击市场
步骤2: 选择您想要交换的符文
步骤3: 单击列表符文按钮，显示可用的符文列表
步骤4: 选择您想要在弹出框中列出的确切符文
# 取消上架 符文 **注意:** * **取消时您必须支付网络费用，因为出于安全原因，我们需要更新您的UTXO** * **当交易成功时，您的符文将被发送回您的钱包** **步骤1:** 选择您想要取消订单的符文
**=步骤2:** 点击**我的订单**显示您的所有订单
**步骤3:** 您只能取消正在上市的订单
步骤4: 选择 **现在取消** 进行交易
步骤5: 一旦交易成功，您的符文将被发送回您的钱包，您可以再次列出它。
# ❓什么是 PSBTs 技术? 部分签名比特币交易(PSBTs)是一种数据格式，允许钱包和其他工具交换有关比特币交易的信息以及完成交易所需的签名 可以创建一个PSBTs来标识一组要花费的未花费事务输出(Unspent Transaction output, utxo)和一组接收花费值的输出。 RuneAlpha的市场正在以一些非常棒的方式利用PSBTs的力量: * **多签交易**: PSBTs 非常适合让多方签署同一笔交易。我们可以混合和匹配买家和卖家的签名，然后将结果广播到比特币网络。它是安全的，为用户节省了一大笔钱. * **离线签名**: PSBTs 带有方便的元数据，可以帮助设备检查正在签署的交易中涉及的地址和金额。这意味着卖家可以以更低的交易成本列出他们的物品，随时更新，并且仍然保持他们的资产安全可靠。都是关于比特币的生活，对吧? # Ordinals-厨师 # 荷兰拍卖 ## 什么是荷兰式拍卖 ? 荷兰拍卖开始时价格很高，然后价格下降，直到有人决定购买它。 出售的物品开始时价格很高，并不断降低，直到有人同意购买。这种拍卖通常用于需要快速出售的物品，如鲜花、鱼和蔬菜。它也用于一次卖出很多东西，比如股票和债券。
## 荷兰拍卖如何运作 ? * 起拍价：拍卖商以较高的价格开始，然后逐渐降低价格，直到所有物品都出售。 * 竞价程序：拍卖人可以报出初始价格，物品的资产价格持续下跌，直到命中中标者出价。 * 清算价：当前价格达到保留价或当前需求满足或超过供应时，拍卖将被清除。 * 时机：在荷兰拍卖中，时机决定一切。价格会改变区间，如果买家想购买商品，他们需要迅速采取行动。每次价格下降，就会减少或**消除**购买该物品的机会，因为之前出价更高的人出的钱越多，他们就可以以新的更低价格购买更多的物品。 在计算出**清算价格**后，所有达到或超过该价格的出价都将被接受。每个中标者支付**相同的价格**。然而，谁的出价最先被接受取决于出价和他们出价的时间。价格较高的出价优先，但如果几个出价相同，则顺序取决于谁先出价。 如果您的出价高于最终的**结算价**，您将根据您的出价除以每件物品的结算价得到物品。 **清算价格**可以等于或低于参与者的出价，但不能高于。 # Bitcoin 建设者 TBA # Cook 质押 ## 规则 游戏规则很简单:每 **5000 个$COOK（5张）下注** 等于一张抽奖入场券。 门票号码将显示在RuneAlpha结束块的出现之前 **快照时期:** * **开始块:** 待定 * **结束块:** 待定 ## 选拔过程 确定获胜者的选择过程经过精心设计，以确保公平性和随机性，利用区块链技术。下面是我们选择算法的一步一步指南: #### 事前公告 * 在**结束块**时，将宣布获胜者。 #### 初步获奖者评选 * 从**结束块**中提取哈希的最后8个字符 * 将这8个字符转换为十进制数，记为`s` * 计算第一张中奖彩票的索引为`index_1 = s mod n`，其中`n`是彩票的初始总数 * 从列表中删除中奖彩票，减少总彩票计数`1` #### 随后的获奖者评选 对于每个后续获奖者' i '(从第二个获奖者开始): 1. 使用前一位获奖者地址的最后5个字符。 2. 将这5个字符转换为十进制数`s_i`。 3. 计算中奖彩票的索引为`index_i = s_i mod (n - (i-1))`，其中`n - (i-1)`反映删除中奖者后更新的彩票总数。 4. 从列表中删除中奖彩票，继续调整每次选择的总票数。 #### 重复这个过程 * 继续这个过程，使用最近赢家地址的最后8个字符来选择下一个赢家。 * 重复，直到所有所需的票被选中或没有票剩下 #### Example: * 假设结束区块是834200，它的区块散列是:\ * 有效门票总数: **888**\ \ **选择第一名获胜者:** * 提取哈希码的最后8个字符: `634b70dd` * 将' 634b70dd '转换为十进制数: **1665888477** * 执行操作: **1665888477 mod 888** = **477** * 因此，票号**477**是第一张被选中的票.\ \ 与彩票号码477相关联的钱包地址将作为决定下一位获胜者的基础(或“种子”) 这个过程将重复，使用每个新获胜者的钱包地址作为后续选择的种子，直到总共333名获胜者被选中。 # 分配 3500名顶级厨师都准备好了，准备用唯一的食材——“中本聪”制作这道终极美食 每个厨师都有自己的招牌动作和特色菜，所以选择合适的厨师来做你最喜欢的菜 🔥 333名厨师将属于 [$Cook](https://twitter.com/search?q=%24Cook\&src=cashtag_click) 持有者 \ 符文OG们 [#runes](https://twitter.com/hashtag/runes?src=hashtag_click) ，质押你的 cook 在 [@runealpha\_btc](https://twitter.com/runealpha_btc) (很快就会出现在你的直播中)，并抢购一些门票，厨师们会直接根据中奖者空投，免费赠送。 只需入股，无需任何费用。 🔥 101名厨师将提供给为Runealpha 提供服务的用户 对于所有从第一天开始就参与Run Alpha的人来说，请密切关注您的钱包!厨师们走进你的厨房。都是免费的，没有附加费用。保持好! 🔥 为比特币生态系统的建设者保留了66名厨师。.\ \ 我们没有忘记那些努力塑造比特币生态系统的人。他们应该得到一些史诗般的食物. 🔥 剩下的3000名厨师将在荷兰拍卖网站([https://runealpha.xyz\]\\(https://t.co/NTfFfcVzfx)上拍卖。(详情即将公布)](https://docs.runealpha.xyz/cn/ordinals-chef/https:/runealpha.xyz]\\\(https:/t.co/NTfFfcVzfx\)上拍卖。\(详情即将公布\)) Runealpha已经确定了[#launchpad](https://twitter.com/hashtag/launchpad?src=hashtag_click)功能，而Ordinals Chef将成为首发明星 # 💯积分活动 TBA # Overview What Is RuneAlpha ? RuneAlpha is a Super-Dapp on the Runes Protocol (Bitcoin) 🚀. It’s your gateway to dive deep into the Rune protocol, keep an eye on transactions, crunch data, and offer extensive support for Rune 💪. RuneAlpha is your crypto Swiss Army knife, featuring: * A toolbox for token etching and minting, perfect for all you crypto artists out there 🎨 * A Rune Explorer to help you trail transactions and manage your Rune assets like a pro 💼 * A marketplace for Rune Trader, turning you into a Rune mogul 🏦 # Table of contents * [🏂 Overview](/en) * [🏹 Rune Alpha Period](/en/rune-alpha-period) * [🚧 Issuance example](/en/issuance-example) * [🧗‍♀️ Terms of service](/en/terms-of-service) * [🎨 Media kit](/en/media-kit) * [🤺 Risk Warning](/en/risk-warning) ## Guides * [🔎 Scan](/en/guides/scan) * [🤹 Create Rune](/en/guides/create-rune) * [🤼 Transfer](/en/guides/transfer) * [👨‍🔬 Rune Alpha - Signet](/en/guides/rune-alpha-signet) * [🌀 Bitcoin Address Formats](/en/guides/bitcoin-address-formats) * [⚗️ Rune Alpha - Testnet](/en/guides/rune-alpha-testnet) ## 🥇 Marketplace * [❓ What is PSBTs ?](/en/marketplace/what-is-psbts) * [🏊‍♂️ Listing Rune](/en/marketplace/listing-rune) * [⛹️‍♂️ Unlist Rune](/en/marketplace/unlist-rune) ## 🖼️ Ordinals Chef * [📢 Distribution](/en/ordinals-chef/distribution) * [👩‍🍳 Cook Staking](/en/ordinals-chef/cook-staking) * [💯 RuneAlpha Point](/cn/ordinals-chef/runealpha-point) * [🏗️ Bitcoin Builder](/cn/ordinals-chef/bitcoin-builder) * [🔢 Auction](/cn/ordinals-chef/auction) # Issuance example `Goal: Issuance $RUNE. total supply 21,000,000` #### Calculate the first data in protocol message The first data push in a protocol message is decoded as a sequence integers. These integers are interpreted as a sequence of (ID, OUTPUT, AMOUNT) tuples\ Integers are encoded as prefix varints, where the number of leading ones in a varint determines its length in bytes. There is many types of prefix varints, and here is the Bitcoin [style](https://en.bitcoin.it/wiki/Protocol_documentation#Variable_length_integer)
To issue 21000000 rune we use this tuple `[0 , 1, 21000000].` But why `[0 , 1, 21000000]` ? * [x] First Integer in tuple is ID `0` for Issuance transaction * [x] Second Integer in tuple mapped to output index `1` of transaction * [x] Third Integer in tuple is amount to issue `21000000`
```javascript function encodeBitcoinVarInt(value) { if (value < 0xfd) { return [value]; } else if (value <= 0xffff) { return [0xfd, value & 0xff, (value >> 8) & 0xff]; } else if (value <= 0xffffffff) { return [0xfe, value & 0xff, (value >> 8) & 0xff, (value >> 16) & 0xff, (value >> 24) & 0xff]; } else { return [ 0xff, value & 0xff, (value >> 8) & 0xff, (value >> 16) & 0xff, (value >> 24) & 0xff, (value >> 32) & 0xff, (value >> 40) & 0xff, (value >> 48) & 0xff, (value >> 56) & 0xff, ]; } } function encodeBitcoinVarIntTuple(tuple) { const encodedBytes = tuple.map(encodeBitcoinVarInt).flat(); // Convert the bytes to a hexadecimal string const hexString = encodedBytes.map(byte => byte.toString(16).padStart(2, '0')).join(''); return hexString; } ``` Here is data of tuple `[0, 1, 21000000]` after **prefix varints Bitcoin-style** encode
```javascript 0 => 00 1 => 01 21000000 => fe406f4001 [0, 1, 21000000] => 0001fe406f4001 ``` #### Calculate the first data in protocol message The second data push is decoded as two integers, `SYMBOL`, `DECIMALS` `SYMBOL` is a base 26-encoded human readable symbol, similar to that used in ordinal number sat names. The only valid characters are `A` through `Z`. Ordinal names are a modified [base-26](https://docs.ordinals.com/bounty/3.html?highlight=base-26#criteria) encoding of ordinal numbers. To avoid locking short names inside the unspendable genesis block coinbase reward, ordinal names get *shorter* as the ordinal number gets *longer*. The name of sat 0, the first sat to be mined is `nvtdijuwxlp` and the name of sat 2,099,999,997,689,999, the last sat to be mined, is `a`. ```javascript // Some code const bb26 = require("base26"); const text = 'rune'; const formatOrdinalBase26 = (text) => { const result = (2099999997689999 + 1 - bb26.from(text)); return result; }; ``` Here is data of tuple `[RUNE, 18]` after **prefix varints Bitcoin-style** encode
```javascript RUNE => 2099999997359067 => ffdbf3de59dbf3de59 18 => 12 [RUNE, 18] => ffdbf3de59dbf3de5912 ``` #### Last result of Protocol message ``` OP_RETURN 52 0001fe406f4001 ffdbf3de59dbf3de5912 ``` # Media kit
# Risk Warning Please be careful! There’s a risk of frontrunning in the mempool when creating sought-after Rune assets. When the network is congested, minting new Rune assets could potentially lead to a loss of funds. Network congestion is often caused by the creation of in-demand Rune assets. If the fee rate for your transaction is too low, your transaction might not get confirmed until the creation event is fully completed. In such a case, you won’t receive any Rune assets and the network fee you’ve paid will not be returned. This frontrunning phenomenon is a result of the way Bitcoin miners handle transactions. They create blocks by including transactions based on the highest network fee rate. Transactions with higher fee rates get priority, even if they were submitted later. # Rune Alpha Period It may not be fully cooked yet, but it offers a tantalizing glimpse into the future of the Rune protocol The Rune protocol is currently in the pre-launch phase, with our dedicated Chef team meticulously crafting an Alpha version. This preliminary version is designed to meet the exacting standards of the upcoming mainnet release. This demo is intended for those who are at the forefront of technology adoption, the true "Alphas." * The protocol is currently adhering to the ordinal version 0.11.1, which can be found in the commit history on the GitHub repository: * The protocol signature has been updated to `RUNE_ALPHA`. * The mainnet can be scanned at the following URL: [scan.runealpha.xyz](https://scan.runealpha.xyz/). For the testnet, please use this URL: [testnet-scan.runealpha.xyz](https://testnet-scan.runealpha.xyz/) Rune Standards: 💠 Implement open etchings ([#2548](https://github.com/ordinals/ord/pull/2548)) ✅\ 💠 Implement splits ([#2530](https://github.com/ordinals/ord/pull/2530))✅\ 💠 Encode runestones with tags ([#2547](https://github.com/ordinals/ord/pull/2547))✅\ 💠 Edict with zero amount allocates all remaining runes ([#2531](https://github.com/ordinals/ord/pull/2531))✅\ 💠 Always create rune, even if none were allocated ([#2543](https://github.com/ordinals/ord/pull/2543))✅\ 💠 Delta encode Rune IDs in edicts ([#2532](https://github.com/ordinals/ord/pull/2532))✅\ 💠 Track burned runes ([#2511](https://github.com/ordinals/ord/pull/2511))✅\ 💠 Don't encode divisibility if zero ([#2510](https://github.com/ordinals/ord/pull/2510))✅\ 💠 Format rune supply using divisibility ([#2509](https://github.com/ordinals/ord/pull/2509))✅ **CAUTION**: Remember, this is not a gourmet meal, so only the most adventurous palates should take a bite.
# Terms of service 1. Be aware that if there’s a backlog of orders on the platform, this could cause delays in the processing of on-chain transactions. We can’t assure you of the exact timing for on-chain processing. 2. The rate you’re seeing now doesn’t reflect the real-time on-chain rate. Keep in mind that the on-chain rate is subject to change. 3. If your payment account has any outbound transactions that are yet to be confirmed, it’s advisable to halt the payment or switch to a different account for the operation. 4. If you come across orders that are currently being engraved, kindly wait for the miner’s confirmation. Please note that once a transaction is in progress, it cannot be cancelled. 5. We cannot be held accountable if users are accessing from jurisdictions where cryptocurrency is prohibited. It’s crucial for users to comply with their local laws and regulations. 6. **Please exercise caution when dealing with inscriptions in your wallet.** There’s a possibility that the wallet you’re using may not handle inscriptions effectively, leading to the loss of inscriptions during transactions. For the safekeeping of important subscriptions, it is recommended to use a separate wallet. Please make sure you fully comprehend these risks and are prepared to accept all consequences that may arise from them. # Roadmap
# Guides # Bitcoin Address Formats Native SegWit, Nested SegWit, Taproot, and Legacy are all different Bitcoin address formats or transaction types within the Bitcoin network. Each has its own characteristics and benefits: 1. **Native SegWit (Segregated Witness Bech32):** Wallet Supported: **Phantom, Leather, Unisat, Okex Wallet** * Native SegWit addresses start with "**bc1**." * Also known as Bech32 addresses. * Utilizes the Segregated Witness (SegWit) upgrade, which segregates the witness data from the transaction data, resulting in smaller transaction sizes and lower fees. * Offers improved security and better scalability compared to legacy addresses. * Recommended for most transactions due to lower fees and enhanced features. Example: **bc1qju52hg5v6z0f5ds49p4t33wz8gl88a5cuzx7hf** 2. **Nested SegWit (Pay to Witness Public Key Hash, P2SH-P2WPKH):** Wallet Supported: **Xverse, Unisat, Okex Wallet** * Nested SegWit addresses start with "**3.**" * Combines the SegWit benefits with compatibility for older wallet software that does not support Bech32 addresses. * Allows for transactions to be sent to a SegWit address even if the sender's wallet doesn't natively support SegWit. * Transactions to nested SegWit addresses are slightly larger and may have slightly higher fees compared to native SegWit. Example: **3NeLJQTPMJTZwuyYrMJLYHmtpqT7x8dYsk** 3. **Taproot:** Wallet Supported: **Xverse, Phantom, Unisat, Okex Wallet** * Taproot is a proposed Bitcoin improvement that enhances privacy, security, and smart contract capabilities. * Addresses created with Taproot start with "**bc1p.**" * Combines multiple spending conditions into one, making complex transactions indistinguishable from simpler ones on the blockchain for improved privacy. * Expected to reduce transaction fees and enable more advanced smart contracts. Example: **bc1psd90nx647p00y0zx04kl5sx9sgjcpeeqyh9t8d0j220ssvu250hq20c84a** 4. **Legacy (Pay to Public Key Hash, P2PKH):** Wallet Supported: **Unisat**, **Okex Wallet , Unisat** * Legacy addresses start with "**1.**" * These are the original Bitcoin addresses and transaction types. * Larger transaction sizes and typically higher fees compared to SegWit addresses. * While still widely supported, legacy addresses are less efficient and secure than SegWit addresses. Example : **1HzCQZtedJ5jbn1YBuqgtkPVwfkjkuzyNR** NOTE**:** DUE TO SECURITY ISSUES AND COST OPTIMIZATION FOR USERS, WE WILL NOT SUPPORT **LEGACY WALLET** # Create Rune In the Rune Protocol, we refer to it as “ETCH”. **Step 1: Fill out Rune information** Make sure **Ticker** is not created
**Step 2: Select etching type** RuneAlpha ís offering 2 type of etching **Type 1:** The market cap will be **locked** and **loaded**, and you’ll specify the token count for each address when you’re booting up that Rune Be careful of decimal selected

Fixed Cap

**Type 2:** Fair mint (Like **$COOK** etching), where the creator lays down the law on how many tokens can be minted per transaction and the number of blocks a minter can transact

Fair mint

Each block takes place within 10 minutes, consider it to have a reasonable time. **Step 3: Select sats/vB** (Gas) **then Process**
Please take a look **risk warning** before executing transaction # Rune Alpha - Signet We never lose sight of Casey's latest updates to stay #Alpha ! ### Config Wallet In Signet, the primary means of connection is through the [Leather Wallet](https://chromewebstore.google.com/detail/leather/ldinpeekobnhjjdofggfgjlcehhmanlj). To get started, follow these steps: 1. Install the Leather Wallet from the Extension Store. 2. Configure the network settings to connect to Signet." Step 1: Change network

Change network

Step 2: Select Signet

Select network

### Faucet BTC signet You can get some free BTC signet here: {% embed url="" %} ### Connect with Rune Alpha \[Signet] {% embed url="" %} Let's embark on your DEGEN journey:
# Rune Alpha - Testnet Welcome to our innovation playground, where we put our products to the ultimate test! 💥🔬 ## Config Network ### Unisat: * Step1: Select setting
### * Step2 : Select Network
* Step 3: Select Testnet
### Xverse * Step 1:
* Step 2:
* Step 3:
### Leather Step 1:
Step 2:
# Scan The search box accepts Wallet Address, Rune name, Transaction Hash Transactions Transactions can be search by hash, for example, $COOK created transaction: {% embed url="" %} Runes Runes can be search by rune name, for example, $COOK can be search by id: {% embed url="" %} Address Addresses can be searched by address hash, which will display all transactions. We also provide an option to show only Rune transactions. {% embed url="" %} # Transfer The culinary masterpiece is simmering to perfection and will soon be elegantly plated for a feast of the senses! 🍽️🚀 # Marketplace # Listing Rune Step by step to list your rune **Note**: **Listing is completely free since we utilize PSBT, but be aware that unlisting requires you to make a transaction, meaning you'll part with some sats to refresh the UTXO utilized during the listing.** Step 1: Click Market in Home Page
Step 2: Select which rune you want to exchange
Step 3: Click List Rune button to show available rune to list
Step 4: Select exact rune you want to list in pop-up
# Unlist Rune We do not expect you to read this manual :D **Note:** * **You will have to pay a network fee when canceling because we need to renew your UTXO for security reasons** * **Your Runes will be sent back to your wallet when the transaction is successful** **Step 1:** Select which Rune you want to unlist your Orders
**Step 2:** Click **My Orders** to show your all order
**Step 3:** You only cancel order which is listing
Step 4: Select **Cancel Now** to make transaction
Step 5: Once this transaction is successful, your Rune will be sent back to your wallet, and you can list it again.
# What is PSBTs ? This dish has so much technical content, it’s like eating a computer chip with a side of salsa! 🍽️💻🌶️ Partially Signed Bitcoin Transactions (PSBTs) are a data format that allows wallets and other tools to exchange information about a Bitcoin transaction and the signatures necessary to complete it A PSBT can be created that identifies a set of Unspent Transaction Outputs (UTXOs) to spend and a set of outputs to receive that spent value. RuneAlpha’s marketplace is harnessing the power of PSBTs in some pretty rad ways: * **Multi-party Transactions**: PSBTs are perfect for getting multiple parties to sign off on the same transaction. We can mix and match signatures from buyers and sellers, then broadcast the result to the Bitcoin network. It’s secure and saves users a bundle. * **Offline Signing**: PSBTs come with handy metadata that helps devices check the addresses and amounts involved in a transaction they’re signing. This means sellers can list their items at a lower transaction cost, update anytime, and still keep their assets safe and sound. It’s all about that Bitcoin life, right? # Ordinals-chef # Dutch Auction Participants bid on how many items they wish to buy and the price per item they're willing to offer ## What is Dutch Auction ? Dutch auctions start with a high price for something and then the price goes down until someone decides to buy it. The person selling the item begins with a high price and keeps lowering it until someone agrees to buy. This kind of auction is often used for items that need to be sold quickly like flowers, fish, and vegetables. It's also used for selling a lot of something at once, like stocks and bonds.
## How Dutch Auctions work ? * Starting Price: The auctioneer starts with a high price and then gradually lowers it until all items have been secured. * The Bidding Process: As soon as the auctioneer sets the initial price. The price of the asset continues to fall until the winning bid is made * Clearing Price: The auction will clear when current price hits a reserve price or current demand meets or exceeds supply. * Timing: Timing is everything in Dutch Auction. The price will change interval, and buyers need to act fast if they want to purchase the item. Every time the price drops, it reduces or **eliminates** the chance to buy the item because with the amount of money from someone who bid higher before, they could buy more items at the new lower price. After figuring out the **Clearing Price**, all bids that meet or exceed this price get accepted. Every winning bid pays the **same price**. However, who gets their bid accepted first depends on the bid price and when they made their bid. Bids with higher prices get priority, but if several bids are the same price, the order is based on who bid first. If your bid was higher than the final **Clearing Price**, you'll get items based on how much you bid divided by the clearing price for each item.\ The **Clearing Price** can be the same as or less than a participant's bid, but it can't be higher. # Cook Staking ## Rules \ The rules of the game are straightforward: every **5,000 $COOK** **STAKING** will equal one entry ticket for the prize draw. The ticket numbers will be displayed on RuneAlpha before the appearance of the Root block.
**Snapshot Period:** * **Start Block:** 837669 * **End Block:** 838669 ## Selection Process The selection process for determining winners is carefully designed to ensure fairness and randomness, leveraging blockchain technology. Here is a step-by-step guide to our selection algorithm: #### Pre-Event Announcement * The **Root Block** to determine the winner(s) will be announced before the event. #### Initial Winner Selection * Extract the last 9 characters of the hash from the **Root Block** * Convert these 9 characters into a decimal number, denoted as `s`. * Calculate the index of the first winning ticket as `index_1 = s mod n`, where `n` is the initial total number of tickets. * Remove the winning ticket from the list, decreasing the total ticket count by 1. #### Subsequent Winner Selections For each subsequent winner `i` (starting from the second winner): 1. Use the **ticket\_id** of the previous winner's address. 2. Declare **ticket\_id** is `s_i`. 3. Calculate the index of the winning ticket as `index_i = s_i mod (n - (i-1))`, where `n - (i-1)` reflects the updated total number of tickets after removing winners. 4. Remove the winning ticket from the list, continuing to adjust the total ticket count for each selection. #### Repeat the Process * Continue the process, using the **ticket\_id** of the most recent winner's address to select the next winner. * Repeat until all desired tickets are picked or no tickets remain.
#### #### EXAMPLE: * Let's say the **Root Block** will be 838769 Its blockhash will be: \ * Total valid tickets: **888**\ \ **Select first winner:** * Extract the last 9 characters of the hash code: `2634b70dd` * Convert `634b70dd` to a decimal number: **10255823069** * Perform the operation: **10255823069 mod 888** = **269** * Therefore, address with index **269** is the first selected => **ticket\_id:** **7146** * Next index selected will be **7146 mod 888** = 42 => **ticket\_id : 79040** * **......**
ticket\_id **79040** will serve as the basis (or 'seed') for determining the next winner\ This procedure will be repeated, using each new winner's wallet address as the seed for the subsequent selection, until a total of 333 winners have been chosen. # RuneAlpha Point First 50 legends score a FREE CHEF! Check out leaderboard now: # Distribution 3,500 top chefs are locked and loaded to whip up the ultimate dish with the exclusive ingredient: Satoshi Each chef's got their own signature moves and specialties, so pick the right one to cook up your fave dish 🔥 333 Chefs will belong to [$Cook](https://twitter.com/search?q=%24Cook\&src=cashtag_click) holders \ The OG alphas of [#runes](https://twitter.com/hashtag/runes?src=hashtag_click)\ Stake your cook on [@runealpha\_btc](https://twitter.com/runealpha_btc) (coming at ya live real soon) and snag some tickets. Chefs drop straight to winning tickets, on the house.\ Just Stake, No Fee required. 🔥 101 Chefs will serve up for Runealpha users For everyone who's engaged with Run Alpha from day one, keep a close watch on your wallets! Chefs dropping into your kitchen. It's all free, no fees attached. Stay ready! 🔥 66 Chefs are reserved for the Bitcoin ecosystem builders. \ \ We haven’t forgotten those who've hustled to shape the Bitcoin ecosystem. They deserving of some epic grub.
🔥 The remaining 3,000 Chefs are hitting the Dutch Auction at [https://runealpha.xyz](https://t.co/NTfFfcVzfx) website. (Details coming soon) Runealpha has nailed the [#launchpad](https://twitter.com/hashtag/launchpad?src=hashtag_click) feature – and Ordinals Chef is set to be the debut star