SHOWING: First 60
#: src/overview.md:255
msgid ""
"On August 21st, 2012, Charlie Lee [posted a proposal to add proof-of-stake "
"to Bitcoin to the Bitcoin Talk forum](https://bitcointalk.org/index.php?"
"topic=102355.0). This wasn't an asset scheme, but did use the ordinal "
"algorithm, and was implemented but never deployed."
msgstr ""
"Noong Agosto 21, 2012, nag-post si Charlie Lee ng [panukalang magdagdag ng "
"proof-of-stake sa Bitcoin sa Bitcoin Talk forum](https://bitcointalk.org/"
"index.php?topic=102355.0). Hindi ito isang scheme ng asset, ngunit ginamit "
"ang ordinal na algorithm, at ipinatupad ngunit hindi kailanman na-deploy."
#: src/overview.md:261
msgid ""
"On October 8th, 2012, jl2012 [posted a scheme to the same forum](https://"
"bitcointalk.org/index.php?topic=117224.0) which uses decimal notation and "
"has all the important properties of ordinals. The scheme was discussed but "
"never implemented."
msgstr ""
"Noong ika-8 ng Oktubre, 2012, [nag-post si jl2012 ng scheme sa parehong "
"forum](https://bitcointalk.org/index.php?topic=117224.0) na gumagamit ng "
#45,043,957text"uses of envelopes."
msgstr ""
"Una ang string na `ord` ay pushed, upang i-dismbiguate ang mga inskripsiyon "
"mula sa iba pang gamit ng envelopes."
#: 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 ""
"Ang `OP_PUSH 1` ay nagpapahiwatig na ang susunod na push ay naglalaman ng "
"content type, at `OP_PUSH 0` naman ay nagpapahiwatig na ang mga kasunod na "
"data ay naglalaman ng content mismo. Dapat gumamit ng maraming push data "
"para sa isang malalaking inskripsiyon, dahil ito sa limitasyon ng taproot, "
"na kung saan hindi maaring lumagpas sa 520 bytes ang bawat isang data push."
#: src/inscriptions.md:62
msgid ""
"The inscription content is contained within the input of a reveal "
"transaction, and the inscription is made on the first sat of its input. This "
#45,022,867text"with the highest number of occurrences in `frequency.tsv` shall be the "
"winner of part 1."
msgstr ""
"Die Transaktion, die die UTXO mit dem Namen des Sats enthält, der in "
"`frequency.tsv` am häufigsten vorkommt, wird der Gewinner von Teil 1 sein."
#: src\bounty/3.md:58
msgid "Tie Breaking"
msgstr "Entscheidung bei Unentschieden"
#: src\bounty/3.md:60
msgid ""
"In the case of a tie, where two submissions occur with the same frequency, "
"the earlier submission shall be the winner."
msgstr ""
"Im Falle eines Unentschiedens, bei dem zwei Einsendungen mit der gleichen "
"Häufigkeit erfolgen, geht die frühere Einsendung als Sieger hervor."
#: src\bounty/3.md:66
msgid "Part 0: 200,000 sats"
msgstr "Teil 0: 200,000 sats"
#: src\bounty/3.md:67
msgid "Part 1: 200,000 sats"
msgstr "Teil 1: 200,000 sats"
#: src\bounty/3.md:68
msgid "Total: 400,000 sats"
msgstr "Gesamt: 400,000 sats"
#: src\bounty/3.md:73
msgid ""
"[`17m5rvMpi78zG8RUpCRd6NWWMJtWmu65kg`](https://mempool.space/"
"address/17m5rvMpi78zG8RUpCRd6NWWMJtWmu65kg)"#45,022,215text