SHOWING: First 60
#50,013,050text"fraudulent. However, there are many that are fantastically creative, and "
"creating and collecting art has been a part of the human story since its "
"inception, and predates even trade and money, which are also ancient "
"technologies."
msgstr ""
"他のパクリ通貨分野のものとは異なり、デジタル文化財には利点がある。もちろん、"
"多くのNFTは醜い、愚か、詐欺的です。しかし、素晴らしいアイデアはたくさんありま"
"す。芸術を創造し、収蔵することはもともと人間の物語の一部です。は貿易やお金と"
"いった同じ古い技術よりも早いです。"
#: src/faq.md:302
msgid ""
"Bitcoin provides an amazing platform for creating and collecting digital "
"artifacts in a secure, decentralized way, that protects users and artists in "
"the same way that it provides an amazing platform for sending and receiving "
"value, and for all the same reasons."
msgstr ""
"ビットコインは、安全で分散化された方法でデジタルアーティファクトを作成し、収"
"集するための素晴らしいプラットフォームを提供しています。も同様にユーザーと"
"アーティストを保護し、同時に価値を送受信する優れたプラットフォームを提供して"
"います。"
#: src/faq.md:307
msgid ""
"Ordinals and inscriptions increase demand for Bitcoin block space, which "
"increase Bitcoin's security budget, which is vital for safeguarding "
"Bitcoin's transition to a fee-dependent security model, as the block subsidy "
#44,984,349text"要ないわけではないので、デジタル文化財ではありません。"
#: src/digital-artifacts.md:33
msgid ""
"Digital artifacts are uncensorable. Perhaps you can change a database entry "
"on a centralized ledger today, but maybe not tomorrow, and thus one cannot "
"be a digital artifact."
msgstr ""
"デジタル文化財は審査不可能です。今日は集中元帳のデータベースエントリを変更で"
"きるかもしれませんが、明日はできないかもしれません。そのため、デジタル文化財"
"ではありません。"
#: src/digital-artifacts.md:37
msgid ""
"Digital artifacts are immutable. An NFT with an upgrade key is not a digital "
"artifact."
msgstr ""
"デジタルコンテンツは改ざんできません。アップグレードキーを持つNFTはデジタルコ"
"ンテンツではありません。"
#: src/digital-artifacts.md:40
msgid ""
"The definition of a digital artifact is intended to reflect what NFTs "
"_should_ be, sometimes are, and what inscriptions _always_ are, by their "
"very nature."
msgstr ""
"デジタル文化財の定義は、その特定の性質からNFTを反映することを目的としています"
"_べき_は何か、時には何か、そして銘文_終始_は何ですか "
#: src/inscriptions.md:4
msgid ""
"Inscriptions inscribe sats with arbitrary content, creating bitcoin-native "
"digital artifacts, more commonly known as NFTs. Inscriptions do not require "
#44,982,953textauthorities 23140132
experiences 23348429
composition 23811933
fundamental 24446253
alternative 25454157
examination 28006878
corporation 28525051
educational 30723713
interesting 34827606
description 35857768
appropriate 40011026
independent 41486618
environment 42200540
differences 43796751
individuals 43927186
immediately 46139894
application 49581511
association 51831793
established 59517867
information 142566230
development 146283633
#44,982,473text <dt>genesis height</dt>
<dd><a href=/block/2>2</a></dd>
<dt>genesis fee</dt>
<dd>138</dd>
<dt>genesis transaction</dt>
<dd><a class=monospace href=/tx/{reveal}>{reveal}</a></dd>
<dt>location</dt>
<dd class=monospace>{reveal}:0:0</dd>
<dt>output</dt>
<dd><a class=monospace href=/output/{reveal}:0>{reveal}:0</a></dd>
<dt>offset</dt>
<dd>0</dd>
<dt>ethereum teleburn address</dt>
<dd>{ethereum_teleburn_address}</dd>
</dl>.*",
),
);
}
#[test]
fn inscription_appears_on_reveal_transaction_page() {
let rpc_server = test_bitcoincore_rpc::spawn();
create_wallet(&rpc_server);
let (_, reveal) = inscribe(&rpc_server);
rpc_server.mine_blocks(1);
TestServer::spawn_with_args(&rpc_server, &[]).assert_response_regex(
format!("/tx/{reveal}"),
format!(".*<h1>Transaction .*</h1>.*<a href=/inscription/{reveal}.*"),
);
}
#[test]
fn inscription_appears_on_output_page() {
let rpc_server = test_bitcoincore_rpc::spawn();
create_wallet(&rpc_server);
let (inscription, reveal) = inscribe(&rpc_server);
#44,979,177textordinals.
#44,979,176textOrdinal Explorer
================
The `ord` binary includes a block explorer. We host a instance of the block
explorer on mainnet at [ordinals.com](https://ordinals.com), and on signet at
[signet.ordinals.com](https://signet.ordinals.com).
### Running The Explorer
The server can be run locally with:
`ord server`
To specify a port add the `--http-port` flag:
`ord server --http-port 8080`
To enable the JSON-API endpoints add the `--enable-json-api` or `-j` flag (see
[here](#json-api) for more info):
`ord server --enable-json-api`
To test how your inscriptions will look you can run:
`ord preview <FILE1> <FILE2> ...`
Search
------
The search box accepts a variety of object representations.
### Blocks
Blocks can be searched by hash, for example, the genesis block:
[000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f](https://ordinals.com/search/000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f)
### Transactions
Transactions can be searched by hash, for example, the genesis block coinbase
#44,979,175text coinbase_ordinals = list(range(first, last))
for transaction in block.transactions[1:]:
ordinals = []
for input in transaction.inputs:
ordinals.extend(input.ordinals)
for output in transaction.outputs:
output.ordinals = ordinals[:output.value]
del ordinals[:output.value]
coinbase_ordinals.extend(ordinals)
for output in block.transaction[0].outputs:
output.ordinals = coinbase_ordinals[:output.value]
del coinbase_ordinals[:output.value]
</pre>
=== Terminology and Notation ===
A satpoint may be used to indicate the location of a sat within an output. A
satpoint consists of an outpoint, i.e., a transaction ID and output index, with
the addition of the offset of the ordinal within that output. For example, if
the sat in question is at offset 6 in the first output of a transaction, its
satpoint is:
`680df1e4d43016571e504b0b142ee43c5c0b83398a97bdcfd94ea6f287322d22:0:6`
== Discussion ==
=== Rationale ===
Ordinal numbers are designed to be orthogonal to other aspects of the Bitcoin
#44,977,109textartifacts.
How does ordinal theory work?
-----------------------------
Ordinal numbers are assigned to satoshis in the order in which they are mined.
The first satoshi in the first block has ordinal number 0, the second has
ordinal number 1, and the last satoshi of the first block has ordinal number
4,999,999,999.
Satoshis live in outputs, but transactions destroy outputs and create new ones,
so ordinal theory uses an algorithm to determine how satoshis hop from the
inputs of a transaction to its outputs.
Fortunately, that algorithm is very simple.
Satoshis transfer in first-in-first-out order. Think of the inputs to a
transaction as being a list of satoshis, and the outputs as a list of slots,
waiting to receive a satoshi. To assign input satoshis to slots, go through
each satoshi in the inputs in order, and assign each to the first available
slot in the outputs.
Let's imagine a transaction with three inputs and two outputs. The inputs are
on the left of the arrow and the outputs are on the right, all labeled with
#44,977,010text<pre>
BIP: ?
Layer: Applications
Title: Ordinal Numbers
Author: Casey Rodarmor <[email protected]>
Comments-Summary: No comments yet.
Comments-URI: https://github.com/ordinals/ord/discussions/126
Status: Draft
Type: Informational
Created: 2022-02-02
License: PD
</pre>
== Introduction ==
=== Abstract ===
This document defines a scheme for assigning serial numbers to sats.
=== Copyright ===
This work is placed in the public domain.
=== Motivation ===
Bitcoin has no notion of stable, public accounts or identities. Addresses are
single-use, and wallet accounts are private. Additionally, the use of addresses
or public keys as stable identifiers precludes transfer of ownership or key
rotation.
This proposal is motivated by the desire to provide stable identifiers that may
be used by Bitcoin applications.
== Description ==
=== Design ===
Every sat is serially numbered, starting at 0, in the order in which it is
mined. These numbers are termed "ordinal numbers", or "ordinals", as they are
#44,976,945text "futures",
"futures-lite 1.13.0",
"generic_static",
"http",
"log",
"rand",
"ring 0.16.20",
"strum",
"thiserror",
"utf-8",
]
[[package]]
name = "atom_syndication"
version = "0.12.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "571832dcff775e26562e8e6930cd483de5587301d40d3a3b85d532b6383e15a7"
dependencies = [
"chrono",
"derive_builder",
"diligent-date-parser",
"never",
"quick-xml",
]
[[package]]
name = "atomic-waker"
version = "1.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1505bd5d3d116872e7271a6d4e16d81d0c8570876c8de68093a09ac269d8aac0"
[[package]]
name = "autocfg"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d468802bab17cbc0cc575e9b053f41e72aa36bfa6b7f55e3529ffa43161b97fa"
[[package]]
name = "axum"
version = "0.6.20"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3b829e4e32b91e643de6eafe82b1d90675f5874230191a4ffbc1b336dec4d6bf"
dependencies = [
#44,976,561text#!/usr/bin/env python3
import re, sys
from matplotlib.pyplot import *
from dataclasses import dataclass
@dataclass
class Block:
height: int
ranges: int
time: int
transactions: int
pat = re.compile(
'''Block (?P<height>[0-9]+) at.*with (?P<transactions>[0-9]+) transactions.*
.*Wrote (?P<ranges>[0-9]+) sat ranges from .* outputs in (?P<time>[0-9]+) ms'''
)
blocks = [
Block(**{k : int(v) for k, v in group.items()})
for group in [
match.groupdict() for match in pat.finditer(open(sys.argv[1]).read())
]
]
start = 0
for i in range(len(blocks)):
if blocks[i].height == 1:
start = i
print(f"Skipping {start + 1} blocks from previous sync")
sync = blocks[start:]
_, (a, b, c) = subplots(3)
a.set_xlabel('Height')
a.set_ylabel('Time')
a.plot(
[block.height for block in sync],
[block.time for block in sync],
)
b.set_xlabel('Ranges')
b.set_ylabel('Time')
b.scatter(
[block.ranges for block in sync],
[block.time for block in sync],
)
c.set_xlabel('Tx\'s in block')
c.set_ylabel('Time')
#44,976,560textmsgid ""
"Additionally, \"NFT\" feels like financial terminology, and the both word "
"\"fungible\" and sense of the word \"token\" as used in \"NFT\" is uncommon "
"outside of financial contexts."
msgstr ""
"Además, la palabra, \"NFT\" suena como terminología financiera, y tanto "
"la palabra \"fungible\" como el sentido de la palabra \"token\" como se usa en los "
"\"NFT\" no son comunes fuera de los contextos financieros."
#: src/faq.md:108
msgid "How do sat inscriptions compare to…"
msgstr "¿Cómo se comparan las inscripciones con..."
#: src/faq.md:111
msgid "Ethereum NFTs?"
msgstr "¿Los NFT de Ethereum?"
#: src/faq.md:113
msgid "_Inscriptions are always immutable._"
msgstr "_Las inscripciones siempre son inmutables._"
#: src/faq.md:115
msgid ""
"There is simply no way to for the creator of an inscription, or the owner of "
"an inscription, to modify it after it has been created."
msgstr ""
"No hay forma de que el creador de una inscripción, o el propietario de "
"una inscripción, la modifique después de haber sido creada."
#44,976,559textchecksum = "d3831c2651acb5177cbd83943f3d9c8912c5ad03c76afcc0e9511ba568ec5ebb"
dependencies = [
"futures-core",
"pin-project-lite",
]
[[package]]
name = "futures-macro"
version = "0.3.29"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "53b153fd91e4b0147f4aced87be237c98248656bb01050b96bf3ee89220a8ddb"
dependencies = [
"proc-macro2",
"quote",
"syn 2.0.39",
]
[[package]]
name = "futures-rustls"
version = "0.24.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "35bd3cf68c183738046838e300353e4716c674dc5e56890de4826801a6622a28"
dependencies = [
"futures-io",
"rustls",
]
[[package]]
name = "futures-sink"
version = "0.3.29"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e36d3378ee38c2a36ad710c5d30c2911d752cb941c00c72dbabfb786a7970817"
[[package]]
name = "futures-task"
version = "0.3.29"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "efd193069b0ddadc69c46389b740bbccdd97203899b48d09c5f7969591d6bae2"
#44,976,557texttransfer10.rcsv#35,289,225brc-20regwildwiz.sats#14,957,910sns{
"p": "og",
"game": "cd282b9b1658ca3010221f6fb088d77e56dede84329c431aa1c60cd4075a02a9i0",
"op": "loot",
"class": "armor",
"loot": "cybernetic",
}#13,183,928text