transfer100.pizza#71,336,531brc-20Inscription #59914375#59,914,375webp"the commit transaction, a taproot output committing to a script containing " "the inscription content is created. Second, in the reveal transaction, the " "output created by the commit transaction is spent, revealing the inscription " "content on-chain." msgstr "" "Como os gastos com script taproot só podem ser feitos a partir de saídas taproot existentes, " "as inscrições são feitas usando um procedimento de confirmação/revelação de duas fases. Primeiro, na " "transação de confirmação, uma saída taproot confirmando um script contendo " "o conteúdo da inscrição é criado. Depois, na transação de revelação, " "a saída criada pela transação de confirmação é gasta, revelando o conteúdo da inscrição " "na rede." #: src/inscriptions.md:33 msgid "" "Inscription content is serialized using data pushes within unexecuted " "conditionals, called \"envelopes\". Envelopes consist of an `OP_FALSE OP_IF " "… OP_ENDIF` wrapping any number of data pushes. Because envelopes are " "effectively no-ops, they do not change the semantics of the script in which " #45,002,872text"in all respects, with the exception that in order to send individual sats, " "transactions must control the order and value of inputs and outputs " "according to ordinal theory." msgstr "" "Esses sats inscritos podem então ser transferidos usando transações de bitcoin, " "enviados para endereços de bitcoin e mantidos em UTXOs de bitcoin. Essas transações, " "endereços e UTXOs são transações, endereços e UTXOS normais de bitcoin " "em todos os aspectos, com a exceção de que, para enviar sats individuais, " "as transações devem controlar tanto a ordem quanto o valor das entradas e das saídas " "de acordo com a teoria ordinal." #: src/inscriptions.md:15 msgid "" "The inscription content model is that of the web. An inscription consists of " "a content type, also known as a MIME type, and the content itself, which is " "a byte string. This allows inscription content to be returned from a web " "server, and for creating HTML inscriptions that use and remix the content of " "other inscriptions." msgstr "" "O modelo de conteúdo da inscrição é o da web. Uma inscrição consiste em " #45,002,871textfantasyland 28621 caermarthen 28631 cyproterone 28655 boutonniere 28657 generalitat 28670 hyperphagia 28682 communautes 28704 bracegirdle 28706 meddelelser 28712 mastroianni 28751 lactiferous 28762 interisland 28763 choreograph 28779 disobliging 28779 inghilterra 28807 disbeliever 28842 contraintes 28845 lincolnwood 28848 consortiums 28850 gradualness 28851 leaseholder 28852 nuncupative 28867 clientelist 28869 eeformation 28877 baryshnikov 28885 communalist 28886 moviemaking 28887 castelvetro 28900 antecedence 28903 caprolactam 28909 misconceive 28926 narcissists 28931 ingenuities 28944 computerize 28967 fractionate 28976 irksomeness 29026 canaanitish 29027 gemfibrozil 29047 hershberger 29058 myringotomy 29061 easthampton 29075 jackrabbits 29118 brahmachari 29126 erodibility 29131 circulators 29138 blackwelder 29172 microcystis 29194 nonminority 29205 catabolized 29226 natriuresis 29246 kostelanetz 29252 harassments 29265 dentofacial 29269 fundamentum 29270 ceftazidime 29276 chromophobe 29290 herpetology 29299 #45,002,870text outpoint ), ); ord_server.assert_response_regex( format!("/inscription/{}", output.inscriptions[2].id), format!( r".*<dt>location</dt>.*<dd class=monospace>{}:20000</dd>.*", outpoint ), ); ord_server.assert_response_regex( format!("/output/{}", output.inscriptions[0].location.outpoint), format!(r".*<a href=/inscription/{}>.*</a>.*<a href=/inscription/{}>.*</a>.*<a href=/inscription/{}>.*</a>.*", output.inscriptions[0].id, output.inscriptions[1].id, output.inscriptions[2].id), ); } #[test] fn batch_in_same_output_with_non_default_postage() { let rpc_server = test_bitcoincore_rpc::spawn(); rpc_server.mine_blocks(1); create_wallet(&rpc_server); let output = CommandBuilder::new("wallet inscribe --fee-rate 1 --batch batch.yaml") .write("inscription.txt", "Hello World") .write("tulip.png", [0; 555]) .write("meow.wav", [0; 2048]) .write( "batch.yaml", "mode: shared-output\npostage: 777\ninscriptions:\n- file: inscription.txt\n- file: tulip.png\n- file: meow.wav\n" #44,996,678text let coinbase_tx = test_server.mine_blocks(1)[0].txdata[0].clone(); let txid = coinbase_tx.txid(); test_server.assert_response_regex( format!("/tx/{txid}"), StatusCode::OK, format!( ".*<title>Transaction {txid}</title>.*<h1>Transaction <span class=monospace>{txid}</span></h1> <dl> </dl> <h2>1 Input</h2> <ul> <li><a class=monospace href=/output/0000000000000000000000000000000000000000000000000000000000000000:4294967295>0000000000000000000000000000000000000000000000000000000000000000:4294967295</a></li> </ul> <h2>1 Output</h2> <ul class=monospace> <li> <a href=/output/30f2f037629c6a21c1f40ed39b9bd6278df39762d68d07f49582b23bcb23386a:0 class=monospace> 30f2f037629c6a21c1f40ed39b9bd6278df39762d68d07f49582b23bcb23386a:0 </a> <dl> <dt>value</dt><dd>5000000000</dd> <dt>script pubkey</dt><dd class=monospace></dd> </dl> </li> </ul>.*" ), ); } #[test] fn detect_unrecoverable_reorg() { let test_server = TestServer::new(); #44,994,765textSat Hunting =========== *This guide is out of date. Since it was written, the `ord` binary was changed to only build the full satoshi index when the `--index-sats` flag is supplied. Additionally, `ord` now has a built-in wallet that wraps a Bitcoin Core wallet. See `ord wallet --help`.* Ordinal hunting is difficult but rewarding. The feeling of owning a wallet full of UTXOs, redolent with the scent of rare and exotic sats, is beyond compare. Ordinals are numbers for satoshis. Every satoshi has an ordinal number and every ordinal number has a satoshi. Preparation ----------- There are a few things you'll need before you start. 1. First, you'll need a synced Bitcoin Core node with a transaction index. To turn on transaction indexing, pass `-txindex` on the command-line: ```sh bitcoind -txindex ``` Or put the following in your [Bitcoin configuration file](https://github.com/bitcoin/bitcoin/blob/master/doc/bitcoin-conf.md#configuration-file-path): ``` txindex=1 ``` Launch it and wait for it to catch up to the chain tip, at which point the #44,994,763text"follows:" msgstr "" "文字列「Hello,world！」を含むのテキスト銘文を以下のようにシリアル化されていま" "す：" #: src/inscriptions.md:42 msgid "" "```\n" "OP_FALSE\n" "OP_IF\n" " OP_PUSH \"ord\"\n" " OP_PUSH 1\n" " OP_PUSH \"text/plain;charset=utf-8\"\n" " OP_PUSH 0\n" " OP_PUSH \"Hello, world!\"\n" "OP_ENDIF\n" "```" msgstr "" #: src/inscriptions.md:53 msgid "" "First the string `ord` is pushed, to disambiguate inscriptions from other " "uses of envelopes." msgstr "" "まず文字列'ord'がプッシュされ、銘文と封筒の他の用途との曖昧さを解消します。" #: src/inscriptions.md:56 msgid "" "`OP_PUSH 1` indicates that the next push contains the content type, and " "`OP_PUSH 0`indicates that subsequent data pushes contain the content itself. " "Multiple data pushes must be used for large inscriptions, as one of " "taproot's few restrictions is that individual data pushes may not be larger " "than 520 bytes." msgstr "" "`OP_PUSH 1'は、次のプッシュにコンテンツタイプが含まれていることを示しま" "す。'OP_PUSH 0'は、後続のデータプッシュがコンテンツ自体を含むことを示す。の大" "規模な銘文は複数回のデータプッシュを使用しなければならない。taprootの少数の制" "限の一つは、単一のデータプッシュが520バイトを超えないことであります。" #44,991,120text