SHOWING: First 60
use super::*;
#[derive(Boilerplate)]
pub(crate) struct SatHtml {
pub(crate) sat: Sat,
pub(crate) satpoint: Option<SatPoint>,
pub(crate) blocktime: Blocktime,
pub(crate) inscriptions: Vec<InscriptionId>,
}
#[derive(Debug, PartialEq, Serialize, Deserialize)]
pub struct SatJson {
pub number: u64,
pub decimal: String,
pub degree: String,
pub name: String,
pub block: u32,
pub cycle: u32,
pub epoch: u32,
pub period: u32,
pub offset: u64,
pub rarity: Rarity,
pub percentile: String,
pub satpoint: Option<SatPoint>,
pub timestamp: i64,
pub inscriptions: Vec<InscriptionId>,
}
#[derive(Debug, PartialEq, Serialize, Deserialize)]
pub struct SatInscriptionsJson {
pub ids: Vec<InscriptionId>,
pub more: bool,
pub page: u64,
}
#[derive(Debug, PartialEq, Serialize, Deserialize)]
pub struct SatInscriptionJson {
pub id: Option<InscriptionId>,
}
impl PageContent for SatHtml {
fn title(&self) -> String {
format!("Sat {}", self.sat)
}
}
#[cfg(test)]
mod tests {
use super::*;
#45,004,207text"À collectionner, échanger et innover. La théorie ordinale attribue une "
"identité aux satoshis, ce qui permet de les suivre et de les échanger, à la "
"fois comme curiosités et pour leur valeur numismatique."
#: src\faq.md:27
msgid ""
"Ordinal theory also enables inscriptions, a protocol for attaching arbitrary "
"content to individual satoshis, turning them into bitcoin-native digital "
"artifacts."
msgstr ""
"La théorie ordinale permet également les inscriptions, un protocole capable "
"d’attacher du contenu arbitraire à des satoshis individuels, les "
"transformant ainsi en artefacts numériques natifs de Bitcoin."
#: src\faq.md:31
msgid "How does ordinal theory work?"
msgstr "Comment fonctionne la théorie ordinale ?"
#: src\faq.md:34
msgid ""
"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."
msgstr ""#45,004,062textmsgid "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` указывает, что следующий push содержит тип содержимого, а `OP_PUSH 0` - что последующие push-файлы содержат само содержимое. Для больших надписей "
"необходимо использовать несколько push данных, так как одно из немногих ограничений taproot заключается в том, что размер отдельных push данных не может "
"превышать 520 байт."
#: 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 sat can then be "
#45,001,724text