Top Tweets for #Block20

🟪 An evolution of the BLOCK-20 DMT-like proposal for the community to consider! | 向社区提出的 BLOCK-20 DMT-like 进化版提案，供大家思考！ 🟣 Instead of referencing existing Ordinals DMT elements, what if the des field in a deploy inscription directly defined the minting conditions based on raw block data? | 如果 deploy 铭文中的 des 字段不再引用现有的 Ordinals DMT 元素，而是直接根据原始区块数据来定义铸造条件，您觉得怎么样？ For example, a deploy could now look like this: | 例如，一个部署(deploy)现在可以像这样： { "p": "block-20", "op": "deploy", "tick": "natcats", "des": "1:3b:11:h" } This "des" field would set the rules. In this example, "1:3b:11:h" could mean: | 这个 "des" 字段会为有效的铸造设定条件。在此示例中，“1:3b:11:h” 可以意味着： 1: The mint must be in the latest block (Block Hash Recency). | 1: 铸造必须发生在最新的区块中（区块哈希新近度）。 3b:11: The block must contain the specific pattern ('3b') within the Bitcoin data field number ('11'). | 3b:11: 该区块必须在比特币数据字段编号('11')中包含特定的模式('3b')。 h: The data type to check for is hexadecimal (h, n, s, or b). | :h: 所检查的数据类型为十六进制 (h, n, s, 或 b)。 🟣 To add more creative control, deployers could also use optional lim and max metafields to define the tokenomics: | 为了增加更多创造性的控制，部署者还可以使用可选的 lim 和 max 元字段来定义代币经济模型： lim (Limit per Mint): Set how many tokens each valid mint receive (e.g., 1000). If you don't set it, the default is 1 token per mint. | lim (每次铸造限制): 设置每次有效铸造可获得的代币数量（例如1000）。如果未设置，则默认为每次铸造1个代币。 max (Max Supply): Set a hard cap for the total supply. If you don't set it, the supply becomes dynamic, tied to how many times the required on-chain conditions are met. | max (最大供应量): 为总供应量设定一个硬上限。如果未设置，供应量将是动态的，与链上条件满足的次数相关联。 🟣 This allows for new creative possibilities and game-like mechanics, all while the minting process for users remains the same. What are your thoughts on this more direct approach? | 这可以为协议引入新的创造可能性和类似游戏的机制，而用户的铸造过程保持不变。您对这种更直接的方法有何看法？