<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Cktcracker on Medium]]></title>
        <description><![CDATA[Stories by Cktcracker on Medium]]></description>
        <link>https://medium.com/@cktcracker?source=rss-4d4acbb54cdf------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*7zG3CvTvwBaXbaJ5</url>
            <title>Stories by Cktcracker on Medium</title>
            <link>https://medium.com/@cktcracker?source=rss-4d4acbb54cdf------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 11:48:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cktcracker/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Validade de Tokens]]></title>
            <link>https://medium.com/@cktcracker/validade-de-tokens-66dabba7332a?source=rss-4d4acbb54cdf------2</link>
            <guid isPermaLink="false">https://medium.com/p/66dabba7332a</guid>
            <category><![CDATA[eficiência]]></category>
            <category><![CDATA[utxo]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[token]]></category>
            <dc:creator><![CDATA[Cktcracker]]></dc:creator>
            <pubDate>Sun, 06 Jul 2025 16:07:54 GMT</pubDate>
            <atom:updated>2025-07-06T16:09:16.572Z</atom:updated>
            <content:encoded><![CDATA[<h3>✅ 1. Modelo UTXO — Eficiência pela Imutabilidade e Simplicidade</h3><ul><li><strong>Validação de validade</strong>: basta verificar se o UTXO ainda não foi gasto.</li><li><strong>Sem necessidade de estado global</strong>.</li><li><strong>Muito eficiente em termos de leitura</strong>: isUnspent(UTXO) basta para saber se o token é válido.</li><li><strong>Escalável para paralelismo</strong> (ex: Solana também adota ideia semelhante via contas independentes).</li></ul><p>📌 <strong>Ideal para</strong>: NFTs, jogos P2P, rastreabilidade, cash-like tokens.</p><h3>⚖️ 2. Modelo de Contas (Account Model) — Usado em Ethereum, Polygon, etc.</h3><ul><li><strong>Cada token é um número armazenado num contrato</strong> (ex: balances[address]).</li><li><strong>Para saber se um token é válido</strong>, precisa:</li><li>Ver o contrato;</li><li>Ver se balanceOf &gt; 0;</li><li>Em caso de NFT, ver se o ownerOf(tokenId) ainda é um endereço válido.</li></ul><p>🔴 <strong>Problemas potenciais</strong>:</p><ul><li>Precisa confiar no contrato estar corretamente implementado.</li><li>Exige mais leitura e mais lógica para ver validade.</li><li>Mais sujeito a <strong>erros de estado ou falhas de contrato</strong>.</li></ul><p>🟢 <strong>Por outro lado</strong>:</p><ul><li>Mais <strong>flexível</strong>: tokens podem ser pausados, bloqueados, resgatados etc.</li><li><strong>Melhor interoperabilidade com contratos complexos</strong>, como DEXs ou DAOs.</li></ul><p>📌 <strong>Ideal para</strong>: finanças descentralizadas, lógica de governança, tokens complexos com estados variáveis.</p><h3>⚡ 3. Solana (Sealevel Model) — Contas como objetos isolados com paralelismo</h3><ul><li>Cada conta armazena o estado do token.</li><li>Tokens (ex: SPL Tokens) são estruturas em contas associadas.</li><li>A verificação de validade depende de campos como amount, owner, delegate, isFrozen, etc.</li></ul><p>🟢 <strong>Eficiência extrema</strong> em throughput, mas com custo em complexidade e sincronização de contas.</p><p>📌 <strong>Ideal para</strong>: jogos em massa, DeFi de alta frequência, aplicações paralelizáveis.</p><h3>📚 Comparativo Simplificado:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/822/1*OqJBcbRqyPjADdoWHgG_1w.png" /></figure><h3>📌 Conclusão</h3><p>Em termos de eficiência e coesão para validação de tokens, o modelo UTXO continua imbatível para:</p><p><strong>Verificação rápida da validade</strong></p><p><strong>Simplicidade de auditoria</strong></p><p><strong>Baixo custo computacional</strong></p><p><strong>Rastreabilidade natural (linha do tempo de UTXOs)</strong></p><p>No entanto, se você precisa de lógica complexa sobre o token (pausar, alugar, votar, dividir, congelar, integrar com DEXs), então modelos baseados em contratos (EVM, Sealevel) oferecem mais flexibilidade, ainda que à custa de uma verificação mais complexa.</p><h3>✅ Blockchains mais adequadas para o modelo de tokenização com UTXO:</h3><p>Em termos de <strong>tokenização com verificação clara de validade</strong>, os <strong>UTXOs (Unspent Transaction Outputs)</strong> representam uma das abordagens mais simples e robustas. Isso porque <strong>se o UTXO ainda não foi gasto, o token é válido</strong>; se foi, o token está “morto” — sem a necessidade de lógica adicional de verificação.</p><h3>1. Bitcoin SV (BSV)</h3><ul><li><strong>Vantagens</strong>:</li><li>UTXO nativo.</li><li>Baixas taxas e alta escalabilidade (em blocos grandes).</li><li>Suporte a contratos inteligentes via <em>sCrypt</em>, com estado codificado nos próprios UTXOs.</li><li>Ideal para <strong>jogos, NFTs, rastreabilidade</strong>, e <strong>sistemas P2P simples</strong>.</li><li><strong>Ferramentas</strong>: sCrypt, Bitcoin Script, MetaNet, Run (descontinuado, mas conceitualmente relevante).</li></ul><h3>2. Bitcoin Cash (BCH)</h3><ul><li><strong>Vantagens</strong>:</li><li>UTXO nativo.</li><li>Suporte ao padrão <strong>CashTokens</strong> para tokenização.</li><li>Baixas taxas.</li><li>Boa base de usuários para aplicativos peer-to-peer.</li><li><strong>Observação</strong>: Menos recursos para smart contracts comparado ao BSV, mas suficiente para representar validade via UTXO.</li></ul><h3>3. Bitcoin (BTC)</h3><ul><li><strong>Vantagens</strong>:</li><li>UTXO nativo.</li><li>Extremamente seguro e descentralizado.</li><li>Altas taxas.</li><li>Limitações em scripting e contratos inteligentes.</li><li>Não ideal para tokenização extensiva, mas pode ser usado em modelos off-chain com verificação on-chain.</li></ul><h3>4. eCash (XEC) (antigo BCHA)</h3><ul><li><strong>Vantagens</strong>:</li><li>UTXO nativo.</li><li>Foco em usabilidade e inovação.</li><li>Suporte à tokenização programável em roadmap.</li><li><strong>Desvantagem</strong>:</li></ul><h3>Considerações Técnicas:</h3><ul><li><strong>Modelo UTXO</strong> → validação nativa via existência do UTXO.</li><li><strong>Tokens como UTXOs</strong> → cada token é um output, que pode ser gasto ou não. Isso <strong>evita necessidade de tabelas de “status”</strong>, como em blockchains de contas (account model).</li><li><strong>Smart contracts em UTXO</strong> (ex: Bitcoin Script ou sCrypt) permitem embutir condições extras se necessário.</li></ul><h3>Menção honrosa:</h3><h4>5. Cardano (ADA)</h4><ul><li><strong>Modelo eUTXO (extended UTXO)</strong>.</li><li>Suporte a <strong>Plutus smart contracts</strong>.</li><li>Mais próximo de Ethereum em complexidade, mas mantém a vantagem do modelo UTXO.</li><li>Ideal para <strong>tokenização com lógica mais complexa</strong>, mas mais difícil de desenvolver.</li></ul><h3>Resumo (Tabela):</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/869/1*CfrUcBzQZ9OuX3zj6KkhMA.png" /></figure><h3>Conclusão:</h3><p>Se o seu objetivo é <strong>verificação simples da validade de tokens com eficiência</strong>, <strong>Bitcoin SV (BSV)</strong> e <strong>Bitcoin Cash (BCH)</strong> são as melhores opções práticas hoje. Para soluções que exigem <strong>contratos mais elaborados sem abrir mão do modelo UTXO</strong>, <strong>Cardano</strong> pode ser considerado, embora com mais complexidade.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=66dabba7332a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Paralelismo em SVM, EVM e BVM]]></title>
            <link>https://medium.com/@cktcracker/paralelismo-em-svm-evm-e-bvm-acb4ec82b076?source=rss-4d4acbb54cdf------2</link>
            <guid isPermaLink="false">https://medium.com/p/acb4ec82b076</guid>
            <dc:creator><![CDATA[Cktcracker]]></dc:creator>
            <pubDate>Thu, 22 May 2025 16:40:45 GMT</pubDate>
            <atom:updated>2025-05-22T16:40:45.206Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/981/1*gR7wQNSDV_xwz8TGJQf7ow.png" /><figcaption>SVM-EVM-BVM</figcaption></figure><h3>🔍 Diferenças e Comparações</h3><h3>1. Solana (Sealevel)</h3><h4>✅ Vantagens:</h4><ul><li><strong>Paralelismo real nativo</strong>: a execução de transações pode ser feita em paralelo se elas não acessarem as mesmas contas.</li><li><strong>Contas explícitas</strong>: cada transação declara todas as contas que irá acessar, facilitando a análise estática de conflitos.</li><li><strong>Alta taxa de throughput</strong> devido ao mecanismo de paralelização (Sealevel).</li></ul><h4>❌ Desvantagens:</h4><ul><li><strong>Maior complexidade para desenvolvedores</strong>: você precisa declarar e gerenciar contas manualmente.</li><li><strong>Limites de número de contas por transação</strong> podem restringir aplicações muito complexas.</li><li>Depende fortemente de uma arquitetura de hardware paralela (núcleos múltiplos, GPU, etc).</li></ul><h3>2. Ethereum (EVM)</h3><h4>✅ Vantagens:</h4><ul><li><strong>Simplicidade para desenvolvedores</strong>: modelo Account-Based é mais fácil de entender.</li><li><strong>Amplo suporte de ferramentas, carteiras e frameworks</strong>.</li><li><strong>Popularidade e comunidade sólida</strong>, com muitos contratos já escritos e auditados.</li></ul><h4>❌ Desvantagens:</h4><ul><li><strong>Execução sequencial de transações</strong>: não há paralelismo real no nível da EVM — o estado é global e compartilhado.</li><li><strong>Problemas de escalabilidade</strong>: gargalo em aplicações de alto throughput (jogos, DeFi de alta frequência).</li><li><strong>Possibilidade de reentrância e conflitos de estado</strong> mais difíceis de detectar.</li></ul><h3>3. Bitcoin/BSV (UTXO/BVM)</h3><h4>✅ Vantagens:</h4><ul><li><strong>Paralelismo total</strong>: transações que gastam UTXOs distintos podem ser processadas em paralelo sem conflitos.</li><li><strong>Alta previsibilidade</strong>: o estado não muda fora dos UTXOs referenciados.</li><li><strong>Maior segurança estrutural</strong>: não há chamadas arbitrárias entre contratos (reduz ataques por reentrância, por exemplo).</li><li><strong>Escalabilidade horizontal</strong>: ideal para jogos, micropagamentos, e operações P2P massivas.</li></ul><h4>❌ Desvantagens:</h4><ul><li><strong>Maior complexidade na modelagem de estado complexo</strong>: como cada estado é um output consumível, exige lógica mais detalhada para rastrear e encadear dados.</li><li><strong>Desenvolvimento menos intuitivo para quem vem do modelo EVM</strong>.</li><li><strong>Ecossistema menor</strong> fora de Bitcoin/BSV.</li></ul><h3>🎯 Conclusão</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0xq_xJFerWLrXkFmqxkyMA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=acb4ec82b076" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UTXO vs Account]]></title>
            <link>https://medium.com/@cktcracker/utxo-vs-account-fa19cd5a4ce7?source=rss-4d4acbb54cdf------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa19cd5a4ce7</guid>
            <dc:creator><![CDATA[Cktcracker]]></dc:creator>
            <pubDate>Thu, 22 May 2025 16:02:57 GMT</pubDate>
            <atom:updated>2025-05-22T16:05:31.018Z</atom:updated>
            <content:encoded><![CDATA[<p>Na <strong>EVM (Ethereum Virtual Machine)</strong>, <strong>não é possível</strong> realizar uma <strong>única transação</strong> que tenha <strong>mais de uma conta como input direto</strong>, no sentido tradicional de “inputs” como em UTXO (Unspent Transaction Output), usado em blockchains como Bitcoin. A arquitetura da EVM é baseada em <strong>contas com saldo</strong> (modelo <strong>Global State Account-Based</strong>), e <strong>cada transação só pode ser iniciada (assinada) por uma única conta externa (EOA — Externally Owned Account)</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SvtKXlgwBO4hxKXh" /><figcaption>UTXO vs Account Blockchains</figcaption></figure><h3>📌 Explicando por partes:</h3><h4>✅ O que uma transação EVM pode conter:</h4><ul><li>Um <strong>único remetente</strong> (originador), que assina a transação com sua chave privada.</li><li>Um ou mais contratos podem ser chamados <strong>em cascata</strong> dentro dessa transação (via chamadas internas), mas sempre com o mesmo msg.sender ou tx.origin inicial.</li></ul><h4>🚫 O que não é possível diretamente:</h4><ul><li>Ter <strong>múltiplas contas assinando a mesma transação</strong> como se fossem “inputs” distintos (como em Bitcoin, onde uma transação pode gastar múltiplos UTXOs de diferentes endereços, desde que todos assinem).</li></ul><h3>💡 Mas dá pra contornar?</h3><p>Sim! Existem padrões e técnicas para <strong>simular esse comportamento</strong> com contratos inteligentes:</p><h4>1. Multisig Wallet (como Gnosis Safe)</h4><ul><li>Um contrato que <strong>aguarda assinaturas de múltiplas partes</strong>.</li><li>Nenhuma “ação” (como enviar ETH ou tokens) acontece até que <strong>N de M assinaturas</strong> tenham sido coletadas.</li><li>A transação final é executada por apenas uma conta, mas <strong>valida que múltiplas aprovações foram dadas</strong>.</li></ul><h4>2. Meta-transactions (relayers)</h4><ul><li>Cada participante <strong>assina uma mensagem off-chain</strong>, e uma outra conta (relayer) agrupa as assinaturas e envia uma única transação on-chain.</li><li>O contrato valida que <strong>as assinaturas correspondem às partes envolvidas</strong>.</li></ul><h4>3. Aggregate signatures (fora da EVM padrão)</h4><ul><li>Em blockchains com suporte nativo a BLS ou Schnorr (como Solana ou Bitcoin), é possível criar uma única assinatura válida por múltiplos participantes.</li><li>A EVM <strong>ainda não tem suporte nativo</strong> a isso, mas existem tentativas de simular.</li></ul><h3>✅ Conclusão</h3><p>Não, <strong>a EVM não permite múltiplas contas como input de uma única transação</strong> no modelo nativo. Mas sim, <strong>você pode construir contratos inteligentes que exijam múltiplas assinaturas ou confirmações para agir como se fosse isso</strong>, usando multisig, meta-transactions, ou lógica personalizada.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa19cd5a4ce7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Transações sem Permissão em Bitcoin: A Última Fronteira da Descentralização]]></title>
            <link>https://medium.com/@cktcracker/transa%C3%A7%C3%B5es-sem-permiss%C3%A3o-em-bitcoin-a-%C3%BAltima-fronteira-da-descentraliza%C3%A7%C3%A3o-11bfb4a00121?source=rss-4d4acbb54cdf------2</link>
            <guid isPermaLink="false">https://medium.com/p/11bfb4a00121</guid>
            <dc:creator><![CDATA[Cktcracker]]></dc:creator>
            <pubDate>Mon, 21 Apr 2025 00:53:27 GMT</pubDate>
            <atom:updated>2025-04-21T01:14:04.500Z</atom:updated>
            <content:encoded><![CDATA[<p>No contexto do sistema Bitcoin, a capacidade de permitir que o usuário realize transações peer-to-peer (P2P), de forma autônoma e sem intermediários, é mais essencial para a preservação da descentralização prática do que a distribuição geográfica ou organizacional da mineração.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*My_xreCNFMrllzCm" /><figcaption>Transações sem Permissão: A Última Fronteira da Descentralização</figcaption></figure><p><strong>Na filosofia original do Bitcoin</strong>: mesmo com a mineração sendo dominada por grandes centros, a <strong>capacidade dos usuários de fazer transações diretas, sem intermediários e com privacidade</strong>, ainda sustenta a <strong>descentralização funcional</strong> da rede.</p><p><strong>O papel de um nó completo é validar e retransmitir. O papel do usuário é assinar e enviar.</strong> Você pode usar nós de terceiros para retransmitir, sem entregar suas chaves.</p><h3>🧱 1. Descentralização da mineração ≠ descentralização do uso</h3><p>Embora a mineração esteja concentrada:</p><ul><li>A <strong>capacidade de qualquer pessoa gerar e assinar uma transação</strong> continua viva e acessível.</li><li>Qualquer um pode usar <strong>carteiras não custodiais</strong>, criar endereços, assinar digitalmente e transmitir transações diretamente à rede — <strong>sem precisar de permissão</strong>.</li></ul><p>Ou seja, mesmo que poucos validem os blocos, <strong>muitos participam como emissores e receptores de valor</strong>.</p><h3>🔄 2. Transações P2P: a essência da descentralização</h3><p>O próprio whitepaper do Bitcoin se chama:</p><blockquote><strong><em>“Bitcoin: A Peer-to-Peer Electronic Cash System”</em></strong></blockquote><p>Isso destaca que o objetivo principal era permitir:</p><ul><li><strong>Transferência direta entre pares</strong>, sem intermediários.</li><li>Resiliência contra censura e controle central.</li><li>Funcionalidade mesmo que a infraestrutura por trás se torne mais centralizada (Mineração Especializada e Centralizada).</li></ul><p>Desde que o protocolo continue aceitando transações assinadas de qualquer ponto da rede, essa <strong>liberdade P2P</strong> se mantém.</p><p><strong>A priori qualquer pessoa pode criar, assinar e transmitir uma transação sem rodar um full node ou minerar blocos</strong>.</p><p>Você pode enviar uma transação para a rede Bitcoin (ou outra blockchain) <strong>utilizando carteiras leves (light wallets)</strong> ou <strong>serviços de broadcast online</strong> que <strong>encaminham sua transação para nós completos</strong> que já estão conectados à rede.</p><p><strong>Como isso funciona em camadas:</strong></p><p>Criação e assinatura da transação</p><p>Você precisa de:</p><ul><li>As <strong>chaves privadas</strong> para assinar os inputs (UTXOs) da sua carteira.</li><li>As informações de destino, valor e taxa de transação.</li></ul><p>Ferramentas que fazem isso:</p><ul><li><strong>Carteiras leves com autocustódia</strong>, como:</li><li><strong>Electrum (para BTC)</strong></li><li><strong>SPV wallets como BRD, BlueWallet, Phoenix, entre outras</strong></li><li><strong>APIs locais/offline</strong> (ex: bitcoinjs-lib em JS, bitcore-lib, bsv, etc.)</li></ul><p>Mesmo sem full node:</p><ul><li>Você ainda tem <strong>soberania se a chave privada estiver com você.</strong></li><li>Você pode verificar as transações usando vários exploradores para evitar ataques tipo <em>man-in-the-middle</em>.</li></ul><h3>🕵️ 3. Anonimato (ou pseudoanonimato) e pulverização</h3><p>Embora o Bitcoin não seja 100% anônimo (ele é <em>pseudônimo</em>), ele permite:</p><ul><li><strong>Geração ilimitada de endereços</strong>.</li><li><strong>Controle pessoal das chaves privadas</strong>.</li><li>Técnicas como <strong>CoinJoin</strong>, <strong>Whirlpool</strong>, <strong>Wasabi Wallet</strong> e outros mixers para aumentar a privacidade.</li><li>Uso de <strong>redes sobrepostas (overlay)</strong> como <strong>Tor</strong> ou <strong>VPNs</strong> para ocultar o IP de origem.</li></ul><p>Além disso, a pulverização dos UTXOs e o uso de <strong>múltiplos endereços</strong> por usuário reduzem a capacidade de monitoramento direto.</p><h3>🔐 4. Descentralização de transmissão</h3><p>Mesmo sem minerar, um usuário pode:</p><ul><li>Rodar um <strong>full node</strong>, conectando-se diretamente à rede.</li><li>Transmitir suas transações sem depender de terceiros.</li><li>Contribuir para a <strong>resiliência da rede</strong> contra censura e interrupção de conectividade.</li></ul><h3>🧠 Conclusão:</h3><blockquote><strong><em>A liberdade de transacionar de forma anônima e pulverizada ainda representa uma das maiores formas de descentralização no uso das tecnologias blockchain.</em></strong></blockquote><blockquote><em>Mesmo que a base de mineração tenda à concentração, enquanto houver:</em></blockquote><ul><li><strong>Código aberto.</strong></li><li><strong>Nós independentes.</strong></li><li><strong>Autocustódia.</strong></li><li><strong>Capacidade de assinar e enviar transações.</strong></li></ul><p>…a <strong>descentralização de uso</strong> ainda estará presente — e talvez, mais importante do que a descentralização da mineração em si.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11bfb4a00121" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Escalabilidade do DREX e Alternativas]]></title>
            <link>https://medium.com/@cktcracker/escalabilidade-do-drex-e-alternativas-836d8a8a772e?source=rss-4d4acbb54cdf------2</link>
            <guid isPermaLink="false">https://medium.com/p/836d8a8a772e</guid>
            <dc:creator><![CDATA[Cktcracker]]></dc:creator>
            <pubDate>Fri, 18 Apr 2025 18:30:07 GMT</pubDate>
            <atom:updated>2025-04-18T19:26:02.690Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Desafios de Escalabilidade do DREX e Alternativas</strong></h3><h3>Introdução</h3><p>O <strong>DREX</strong> (sigla para <strong>Digital Real Electronic eXperience</strong>), nome dado ao projeto do <strong>Real Digital</strong> — a moeda digital do Banco Central do Brasil (CBDC) — , está sendo desenvolvido inicialmente <strong>sobre a arquitetura EVM</strong> (Ethereum Virtual Machine), usando uma blockchain de consórcio baseada em <strong>Hyperledger Besu</strong>.</p><p>Isso traz muitas vantagens, mas também alguns <strong>desafios críticos de escalabilidade</strong>, que merecem atenção. Vamos destrinchar:</p><h3>🚧 Desafios de Escalabilidade do DREX com Arquitetura EVM</h3><h3>1. 🔗 Limitação de throughput (TPS)</h3><ul><li>A <strong>EVM foi originalmente projetada para ambientes públicos</strong>, com taxas de transação que giram em torno de <strong>15–30 TPS</strong> no Ethereum mainnet.</li><li>Mesmo em redes permissionadas como o DREX, o desempenho da EVM <strong>ainda sofre gargalos</strong> com o modelo sequencial de execução.</li><li>Soluções para escalar horizontalmente contratos e transações <strong>não são triviais na EVM</strong>, e o modelo de <strong>estado global compartilhado</strong> impõe sérias limitações.</li></ul><h3>2. 📦 Problemas com armazenamento de estado global</h3><ul><li>Cada contrato mantém <strong>estado persistente em disco</strong>, o que aumenta o tamanho do ledger e requer <strong>sincronização constante entre nós</strong>.</li><li>Isso causa <strong>crescimento exponencial do banco de dados</strong> em operações bancárias e interbancárias de alta frequência, como:</li><li>Liquidação instantânea de ativos tokenizados</li><li>Movimentações de carteira de grandes instituições</li><li>Pagamentos fracionários ou automatizados</li></ul><h3>3. ⛓️ Modelo sequencial de execução dos contratos</h3><ul><li>A EVM <strong>executa contratos de forma síncrona e sequencial</strong>.</li><li>Isso significa que <strong>uma transação deve ser completamente processada antes que a próxima seja executada</strong>.</li><li>Em um sistema como o DREX, que pode ter milhares de operações simultâneas de diversas instituições, esse modelo <strong>é um gargalo natural</strong>.</li></ul><h3>4. ⚠️ Custos computacionais e complexidade</h3><ul><li>Mesmo com taxas removidas (sem gás), os <strong>custos computacionais da EVM ainda existem</strong>.</li><li>Processos bancários com lógica complexa (como rastreamento de propriedade, compliance, auditoria e lógica de liquidação automática) são pesados para a EVM.</li><li>A complexidade <strong>torna a validação mais lenta</strong> e a <strong>auditoria mais desafiadora</strong>.</li></ul><h3>5. 🧩 Interoperabilidade com sistemas legados</h3><ul><li>A arquitetura da EVM <strong>não foi pensada para integrar facilmente com sistemas bancários tradicionais</strong>.</li><li>Adaptar a EVM para atender normas como SPB, Pix, e registradoras como CIP, B3, Selic, etc., <strong>exige middleware pesado ou camadas adicionais</strong>.</li></ul><h3>✅ Oportunidades e soluções sendo exploradas</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hQXQhIo1_E5HD9lZc4nPMg.png" /></figure><h3>🧠 Resumo</h3><p>O uso da <strong>EVM para o DREX</strong> foi uma decisão estratégica que favorece:</p><ul><li>Interoperabilidade com o ecossistema DeFi</li><li>Familiaridade com ferramentas existentes</li><li>Base sólida para tokenização de ativos</li></ul><p>No entanto, <strong>a arquitetura da EVM é naturalmente limitada em termos de escalabilidade</strong>, e o DREX terá que superar esses obstáculos por meio de:</p><ul><li>Soluções arquiteturais auxiliares</li><li>Mecanismos de paralelização ou execução off-chain</li><li>Alternativas futuras, como substituição ou complementação da EVM com VMs mais performáticas</li></ul><h3>🚧 <strong>Arquiteturas Alternativas a EVM para Implementar as Funcionalidade do DREX</strong></h3><p><strong>Comparação direta entre a EVM (usada no DREX)</strong> e outras arquiteturas que oferecem <strong>maior escalabilidade</strong>, como a <strong>BVM (Bitcoin Virtual Machine — usada na BSV)</strong> e a <strong>Sealevel VM (usada na Solana)</strong>.</p><h3>⚙️ Comparativo Técnico: EVM vs BVM vs Sealevel</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/610/1*AEp6jgpki23vyUtAbr9-bg.png" /></figure><h3>🧠 Resumo por Aplicabilidade no DREX (CBDC)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/896/1*c7TeRO_5AK1teeWtYXcnjA.png" /></figure><h3>🔍 Exemplos práticos de escalabilidade</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/906/1*ti968z8AIz3QF9xmqpyGVg.png" /></figure><h3>🏁 Conclusão</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/1*JFnWGhjLxzoCyeoM_PgQPw.png" /></figure><h3>🎯 Cenário Simulado 1: Pagamentos Simultâneos</h3><p><strong>Objetivo</strong>: medir a capacidade de cada arquitetura em processar <strong>100.000 pagamentos P2P</strong> no menor tempo possível, com custo mínimo.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/778/1*5y7jWjjlP5wxP0KhyeJUMw.png" /></figure><h3>🎮 Cenário Simulado 2: Jogos de Apostas em Massa (P2P Par ou Ímpar)</h3><p><strong>Objetivo</strong>: executar <strong>50.000 jogos Par ou Ímpar simultâneos</strong>, cada um com lógica de 2 jogadores + verificação + premiação automática.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/615/1*hVgP54A4vNkiEhHTDdi3CA.png" /></figure><h3>🧠 Resumo: Quem se destaca em quê?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/777/1*DE5t5H0GIFiLPGKTkjg5nA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=836d8a8a772e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Smart Ordinals — Test]]></title>
            <link>https://medium.com/@cktcracker/smart-ordinals-test-c071424e6269?source=rss-4d4acbb54cdf------2</link>
            <guid isPermaLink="false">https://medium.com/p/c071424e6269</guid>
            <dc:creator><![CDATA[Cktcracker]]></dc:creator>
            <pubDate>Sun, 28 Apr 2024 02:04:53 GMT</pubDate>
            <atom:updated>2024-04-28T03:09:03.728Z</atom:updated>
            <content:encoded><![CDATA[<h3>Smart Ordinals — Tutorial</h3><p><strong>Tutorial on How to Use Smart Ordinals</strong></p><p>To run a test on the Smart Ordinals project the user must either install it on his computer following the <a href="https://github.com/carlosamcruz/maoonchain/blob/main/README.md">README instructions</a>, or he can run it directly from the site <a href="https://carlosamcruz.github.io/maoonchain/">MaoOnChain</a>. In both cases the welcome page will be presented as in Fig. 1.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/634/1*m1UiPlewVBbWJ5d8TOFfaA.png" /><figcaption>Figure 1 — Welcome Page</figcaption></figure><p>The user then goes to menu <strong>(Home / Access)</strong> and insert his private key, as shown in Fig. 2.</p><p>The private key, can be any hexadecima number between the following 2 values, including them:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/645/1*YR1sm04GFnhB5WMDVRNE-Q.png" /></figure><p>For this tutorial lets use the following private key:</p><p>771f6266849ef422cc6566291c1e27ff857b86fc9d7c51d983b72269290fb639</p><p>TestNet Addresses:</p><p>Compressed: mzdFVzhBwD164rLTJvbnyzEzRCCrE9Jqr7</p><p>Uncompressed: mgNcHR65mVftGELRJ6XLb8MuLs3QHrUpxr</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/672/1*NZFNFfloaeoMOBE2zivmYg.png" /><figcaption>Figure 2: Access Console with private key on TestNet Mode</figcaption></figure><p>Next the user needs a 1SatOrdinals Token. Lets create a token at menu <strong>(Smart Ord / 1SatOrdinals / Create)</strong>, as shwon in Fig. 3. The user can both choose a file or use a text. For this example, we create a text token ASDFGH.</p><p>The token can be explored on-chain at:</p><p><a href="https://test.whatsonchain.com/tx/b5f02aa6c078fae219eb54db9f9b5e1b116b6aee61288c9e4d249908a6b5d28b">https://test.whatsonchain.com/tx/b5f02aa6c078fae219eb54db9f9b5e1b116b6aee61288c9e4d249908a6b5d28b</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/703/1*1UqVcwiiJrjhex86ILg0xw.png" /><figcaption>Figure 3 — Creating a 1SatOrdinals Token</figcaption></figure><p>Using the TXID of the token, the user can open an on-chain p2p sell order using menu <strong>(Smart Ord / Market OnChain / Order Lock)</strong>. The user inform the TXID and the price he want to sell his token. In case he has a single specific buyer he can inform his address at the field: Send 2 Add (Optional), in this case only the specific buyer can pay for the token. In this example, anyone can pay for the token.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/689/1*m7sNhEV6r-_HQE1emefaBQ.png" /><figcaption>Figure 4 — Creating an Order Lock</figcaption></figure><p>The contract with the order lock can be explored on-chain at:</p><p><a href="https://test.whatsonchain.com/tx/a295b85573363ac39841750ebcff513185e9a756cf3c384ad7f4213ff800de65">https://test.whatsonchain.com/tx/a295b85573363ac39841750ebcff513185e9a756cf3c384ad7f4213ff800de65</a></p><p>If the owner regrets before any other user buy his token, he can cancel the order. Using the TXID of the order lock, the user can cancel the order using menu <strong>(Smart Ord / Market OnChain / Cancel)</strong> as show in Fig. 5.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/679/1*O8F2qtMmm2FO8dKBs-Yt9w.png" /><figcaption>Figure 5 — Order Lock Cancelled</figcaption></figure><p>The token brought back to the owner can be explored on-chain at:</p><p><a href="https://test.whatsonchain.com/tx/88b8bd59c90cbedd104cc8746126d404a3413e62ce62d21ac5d2ce923de8a557">https://test.whatsonchain.com/tx/88b8bd59c90cbedd104cc8746126d404a3413e62ce62d21ac5d2ce923de8a557</a></p><p>Using the current TXID of the token, lets open a new sell order with a higher price using menu <strong>(Smart Ord / Market OnChain / Order Lock)</strong>, as shown in Fig. 6.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/705/1*wmCtakLpK84GYW86_3JS8Q.png" /><figcaption>Figure 6 — New Order Lock with price of 2000 satoshis</figcaption></figure><p>The new contract with the order lock can be explored on-chain at:</p><p><a href="https://test.whatsonchain.com/tx/ddda569d52c0c5699a388cb36a77052b528cfcde5021cac95782ee43de09c14a">https://test.whatsonchain.com/tx/ddda569d52c0c5699a388cb36a77052b528cfcde5021cac95782ee43de09c14a</a></p><p>Details of the contract can be explored using the TXID of the order lock at menu <strong>(Smart Ord / Market OnChain / Details)</strong>, as shown in Fig. 7.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/715/1*GaK31l6KPSWL_SdIJR3INw.png" /><figcaption>Figure 7 — Details of the Current Contract</figcaption></figure><p>Another user can execute the buy order, using the TXID of the open order lock, just offering a price equal or higher than that required by the current owner of the token. To emulate a new user, we can just switch the publick key compression at menu <strong>(Home / Access)</strong> and the system will interpret it as a different user, as show in Fig. 8.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/697/1*CNc4dD9rG_ldZppbE5iQgw.png" /><figcaption>Figure 8 — Public Key Compression Changed to Uncompressed</figcaption></figure><p>Now the new user can buy the token, by informing the TXID of the open sell order at menu <strong>(Smart Ord / Market OnChain / Details)</strong>. He need to inform the price he wants to pay for the token, as show in Fig. 9.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/675/1*erKrECmZPl_IwyumKvxHqQ.png" /><figcaption>Figure 9 — Buy order execute by a different user</figcaption></figure><p>The conclusion of the contract can be explored at:</p><p><a href="https://test.whatsonchain.com/tx/4adaf5a451b813161b64096e52f28816ead5f5b51ec1c5f20d085eab0c921f75">https://test.whatsonchain.com/tx/4adaf5a451b813161b64096e52f28816ead5f5b51ec1c5f20d085eab0c921f75</a></p><p>Where the anyone can see that the price paid by the buyer goes directly to the address of the former owner of the token, while the ownership of the token goes to the buyer, as shown in Fig. 10:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vdUZVX38umRf4O4UUn1nPw.png" /><figcaption>Figure 10 — Buy Order Execution</figcaption></figure><p>Details of the new characteristics of the 1SatOrdinals can be explored at menu <strong>(Smart Ord / 1SatOrdinals / Details)</strong>, using the TXID of the token after it was bought on-chain, as shown in Fig. 11, where we can see the address of the new owner of the token.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/695/1*wIopz1vW21rljY0eP6W0LQ.png" /><figcaption>Figure 11 — Details of the Token with the new Owner</figcaption></figure><p>For more details watch the following video:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FvwlL89Gu0R0%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DvwlL89Gu0R0&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FvwlL89Gu0R0%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/1ca213ee017113ddd88de43671d2aa8c/href">https://medium.com/media/1ca213ee017113ddd88de43671d2aa8c/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c071424e6269" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Web Com Token]]></title>
            <link>https://medium.com/@cktcracker/web-com-token-540f8d090205?source=rss-4d4acbb54cdf------2</link>
            <guid isPermaLink="false">https://medium.com/p/540f8d090205</guid>
            <dc:creator><![CDATA[Cktcracker]]></dc:creator>
            <pubDate>Fri, 19 Jan 2024 21:49:39 GMT</pubDate>
            <atom:updated>2024-01-22T15:15:11.112Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>1 — Introdução</strong></p><p><a href="https://carlosamcruz.github.io/webcomtoken/"><strong>Web Com Token</strong></a> é uma interface web 3.0 onde o usuário é capaz de criar tokens para inúmeras aplicações, incluindo: Cupons de Desconto; Tokens Colecionáveis (como Figurinhas, Selos comemorativos, etc); Ingressos de Eventos; Tokens de Redes Sociais; Tokens de Jogos; Tokens de Cash Back; NFTs Diversos; e Brindes em Satoshis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AzoNIBlpC8NO7ajAaIbGzQ.png" /><figcaption>Figura 1 — Tokens para Aplicações Diversas</figcaption></figure><p>Isto é possível, pois a interface permite ao seu usuário interagir de forma simplificada com o sistema de tokenização da Blockchain da rede Bitcoin, dando acesso direto a ferramentas da WEB 3.0 que permite ao usuário uma experiência web mais personalizada, com maior controle sobre seus dados e produtos digitais.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8JTi13OMSYfWBiNBF98kqA.png" /><figcaption>Figura 2 — WEB com Token</figcaption></figure><p>Através da interface Web Com Token, o usuário pode criar, configurar, gerenciar e compartilhar seus próprios tokens, assim como interagir com tokens de outros usuários da rede.</p><p><strong>2 — Novo Usuário</strong></p><p>Para utilizar a interface, o usuário tem a opção de criar uma nova chave de usuário ou utilizar qualquer chave pessoal previamente existente. Esta flexibilidade permite que o usuário crie quantas chaves de uso forem desejadas, sendo necessário apenas armazená-las e gerenciá-las de maneira apropriada. É importante ressaltar que não é necessário criar uma conta para uso desta interface, e, adicionalmente, nenhum dado de usuário é armazenado pela plataforma, garantindo total privacidade e segurança.</p><p>A criação de uma chave de uso é feita no menu ( Home / Novo Usuário ) como mostrado na Fig. 3, o usuário deve informar um e-mail pessoal e uma nova senha de pelo menos 8 dígitos e repetir a nova senha. Em seguida, é só apertar no botão criar e o sistema criara uma chave privada de usuário e um endereço referente a esta chave. Ao final, é importante que o usuário faço o download do arquivo da sua nova chave e guarde em um local seguro. É importante fazer um backup deste arquivo e principalmente da sua nova chave privada. Se o usuário for utilizar esta chave regularmente, o arquivo pode ser acessado diretamente no dispositivo onde o download foi realizado.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/741/1*4Mm36Yt2E52mV1nAwSQq3Q.png" /><figcaption>Figura 3 — Criação e Armazenamento de Nova Chave de Usário</figcaption></figure><p><strong>3 — Acesso</strong></p><p>O acesso a interface é realizada através do menu ( Home / Acesso ), onde o usuário tem a opção de informar a chave privada, ou informar e-mail e senha, ou ainda informar o arquivo de chave privada para acessar seu endereço único, como mostrado na Fig. 4. O acesso as informações neste endereço só são possíveis através da chave privada, portanto esta não deve ser informada a terceiros não autorizados.</p><p>O endereço de usuário é publico e deve ser informado para qualquer interação com outro usuário da rede, como por exemplo: receber satoshis ou receber um token de outro usuário da rede. O QRcode identifica o endereço e pode ser informado a outros usuário. A chave publica também pode ser informada a outros usuário, entretanto o endereço é a forma mais versátil de interagir na rede.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/767/1*8LPG5oBKxJWw7LikX7CA7w.png" /><figcaption>Figura 4 — Acessado as Funções da Interface Web Com Token</figcaption></figure><p><strong>4 —Criando um Novo Token</strong></p><p>A criação de um token é realizada através do menu ( Web Tokens / Token / Criar )</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=540f8d090205" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Six Compact Scripts to Best Store Data on BTC UTXOs]]></title>
            <link>https://medium.com/@cktcracker/six-compact-scripts-to-best-store-data-on-btc-utxos-bdd15f4cf46d?source=rss-4d4acbb54cdf------2</link>
            <guid isPermaLink="false">https://medium.com/p/bdd15f4cf46d</guid>
            <dc:creator><![CDATA[Cktcracker]]></dc:creator>
            <pubDate>Fri, 05 Jan 2024 14:46:05 GMT</pubDate>
            <atom:updated>2024-01-05T17:36:02.473Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>1 — Introduction</strong></p><p>Storing data on BTC UTXOs is thing the bothers BTC developers for years, first they made UTXOs using <a href="https://en.bitcoin.it/wiki/OP_RETURN"><strong>OP_RETURN unspendable</strong></a> and trying to use any script containing OP_RETURN makes the transaction invalid. Besides that, they crippled <a href="https://en.bitcoin.it/wiki/Script"><strong>BTC script language</strong></a> and badly limited the block size, the size of spendable UTXO script is also limited to around 549 bytes.</p><p>However, what remains of Bitcoin Protocol on BTC still allows for some cool UTXO script for data storage. In order to overcome the limitation of not having a spendable UTXO by using OP_RETURN opcode, we present here six UTXOs scripts that are useful to store data on BTC UTXOs up to the current limit of 520 bytes. The six versions of the proposed scripts are shown in Fig. 1.</p><p>It is worth noting that the scripts presented here can be employed on any Bitcoin chain that follows the Bitcoin Protocol.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/977/1*it8jD1MaDvq132ys5UWapQ.png" /><figcaption>Figure 1 — Six Useful Script Versions To Store Data on BTC UTXOs up to 520 bytes</figcaption></figure><p><strong>2— BTC UTXO Scripts For Data Storage</strong></p><p>All six version of the presented script variants were produced with P2PKH script operators plus push data and OP_DROP opcodes. The first version, shown on Fig. 2 the data is pushed in front the the P2PKH script.</p><p>Example of the use of this script is shown on the following transaction on the BTC TestNet. The data pushed on all the examples are the same 520 bytes text inside the red polygon of Fig. 3, when decoded from HEX do ASCII you find the text of (Prophet Jeremiah 29:11–14a) plus some additional characters to complete the 520 bytes. Part of the decoded text are presented in Fig. 4.</p><p><a href="https://blockstream.info/testnet/tx/519cac3c535fbe35903e43f420f4fd99380133ca64297f263c6e95d980df8e47?expand">https://blockstream.info/testnet/tx/519cac3c535fbe35903e43f420f4fd99380133ca64297f263c6e95d980df8e47?expand</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/207/1*ruo9SUB6l3GXfusZvj8JXw.png" /><figcaption>Figure 2 — First Proposed Script</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZvgIcMPx-bEMLT93ZyjBCw.png" /><figcaption>Figure 3 — <a href="https://blockstream.info/testnet/tx/519cac3c535fbe35903e43f420f4fd99380133ca64297f263c6e95d980df8e47?expand">Data Pushed on the UTXO of the First Script</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/605/0*ja-ktCGnQnErgk8R.png" /><figcaption>Figure 4 — Part of the Decoded HEX to ASCII Text From Fig. 3</figcaption></figure><p>From the second to the fifth versions of the script, the data is pushed inside the P2PKH script, that is between its operator as show in the Fig. 5. The following set of four transactions show examples of these UTXOs being created and than spent into another UTXO, as can be directly verified on chain by the links provided.</p><p>The first transaction of this set spent the UTXO of the first script type and creates the UTXO of the second script type:</p><p><a href="https://blockstream.info/testnet/tx/5ff1f8ecb9eb605811d1129a99199e57d7300cd9d94bdc3727b7dbdcd50186fb?expand">https://blockstream.info/testnet/tx/5ff1f8ecb9eb605811d1129a99199e57d7300cd9d94bdc3727b7dbdcd50186fb?expand</a></p><p>The second transaction of this set spent the UTXO of the second script type and creates the UTXO of the third script type:</p><p><a href="https://blockstream.info/testnet/tx/7a9eca6cdf869b85fb5bed590010e3313efdbe691e244b09745b90346f571751?expand">https://blockstream.info/testnet/tx/7a9eca6cdf869b85fb5bed590010e3313efdbe691e244b09745b90346f571751?expand</a></p><p>The third transaction of this set spent the UTXO of the third script type and creates the UTXO of the fourth script type:</p><p><a href="https://blockstream.info/testnet/tx/ec30577903d93207bda949ac769028267b5f1dd021109702c8450678249c151f?expand">https://blockstream.info/testnet/tx/ec30577903d93207bda949ac769028267b5f1dd021109702c8450678249c151f?expand</a></p><p>The last transaction of this set spent the UTXO of the fourth script type and creates the UTXO of the fifth script type:</p><p><a href="https://blockstream.info/testnet/tx/50b98c5eaa541127947796890f7f28d7a06c7acd056c09d4d180340386b28f5b?expand">https://blockstream.info/testnet/tx/50b98c5eaa541127947796890f7f28d7a06c7acd056c09d4d180340386b28f5b?expand</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gMHVaZqGehoLxtDuZGKdXQ.png" /><figcaption>Figure 5 — Script versions with data pushed inside the P2PKH script</figcaption></figure><p>The sixth versions of the script has its data pushed after the P2PKH script, as show in the Fig. 6. The following set of two transactions show examples of the UTXO of the six being created and than spent into another UTXO, as can be directly verified on chain by the links provided.</p><p>The first transaction of this set spent the UTXO of the fifth script type and creates the UTXO of the six script type:</p><p><a href="https://blockstream.info/testnet/tx/42ad14e032855041098c977f1de7524768ec11082d23390e6e31ce0f94cb2ae2?expand">https://blockstream.info/testnet/tx/42ad14e032855041098c977f1de7524768ec11082d23390e6e31ce0f94cb2ae2?expand</a></p><p>The last transaction of this set spent the UTXO of the sixth script type and creates the UTXO of a simple P2PKH script:</p><p><a href="https://blockstream.info/testnet/tx/0acc621d0d3cd2ebb6a0a5bf7fcf3c3e7d3d47d19c6b807f25b404c71829c56e?expand">https://blockstream.info/testnet/tx/0acc621d0d3cd2ebb6a0a5bf7fcf3c3e7d3d47d19c6b807f25b404c71829c56e?expand</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/272/1*IsrnofvHJ0qa547TgCOSfw.png" /><figcaption>Figure 6— Script version with data pushed after the P2PKH script</figcaption></figure><p><strong>3 — Conclusions</strong></p><p>As show in this article, it is still possible to create cool unprunable UTXO scripts on the BTC chain to store data, so that every node must keep it on their UTXO set. Though, it is very limited to 520 bytes per UTXO, that is to store a 5.2 k bytes file it is necessary at least 10 UTXOs.</p><p>Of course, BTC develops can still cripple the chain capabilities even more in order to avoid such presented scripts to be widely produced on the chain. Notwithstanding, its still possible to create such cool scripts.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bdd15f4cf46d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Optimized BTC Spendable UTXO Data Token]]></title>
            <link>https://medium.com/@cktcracker/optimized-btc-spendable-utxo-data-token-bd4d74ed63c1?source=rss-4d4acbb54cdf------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd4d74ed63c1</guid>
            <dc:creator><![CDATA[Cktcracker]]></dc:creator>
            <pubDate>Sun, 31 Dec 2023 19:57:31 GMT</pubDate>
            <atom:updated>2024-01-02T21:49:24.123Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>1 — Introduction</strong></p><p>Currently the two most well know types of data token on the BTC blockchain are <a href="https://docs.ordinals.com/inscriptions.html"><strong>Inscriptions Ordinals</strong></a> and <a href="https://stampchain.io/index.html"><strong>Stamps tokens</strong></a>. Inscriptions Ordinals have their data stored on the witness section of the transaction and, therefore, its data is prunable. It is worth noting that the Inscriptions Ordinals token data are not even used to produce the TXID of its transaction because witness information data is pruned to produce the transaction TXID. Stamps are tokens which have data stored in UTXOs, however, as their developers build the tokens on unspendable UTXOs they can also be pruned from the UTXO set of miners with very small side effect.</p><p>In this article we will discuss and show some more optimized UTXO token data options for the BTC chain, using multi-signature scripts and also P2PKH assisted scripts, as the example shown in Fig 1.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aMFcwl_ULmitC0H2Wdpyvg.png" /><figcaption>Figure 1 — Unprunable and Spendable BTC UTXO Data Script</figcaption></figure><p><strong>2 — Current Limitations and Uselessness of Stamps UTXOs</strong></p><p><a href="https://stampchain.io/index.html"><strong>Stamps tokens</strong></a> were first proposed by BTC developers to produce unprunable UTXOs art on the BTC Blockchain, since <a href="https://docs.ordinals.com/inscriptions.html"><strong>Inscriptions Ordinals</strong></a> token data can be prunable from the Blockchain.</p><p>Currently BTC Stamps use the following script to build their UTXOs:</p><p>OP_1<br>&lt;compressed PBK1&gt;<br>&lt;compressed PBK2&gt;<br>&lt;compressed PBK3&gt;<br>OP_3<br>OP_CHECKMULTISIG</p><p>This is a multi signature script where a single signature that matches one of the three public keys is required to use the UTXO. On Stamps approach, the first and second public keys PBK1 and PBK2 are used to store the token data, or at least part of the data in each UTXO.</p><p>The third public key PBK3 is supposed to be a real public key which private key is kept by the owner of the token. However, they use a <a href="https://medium.com/@cktcracker/dummy-stamps-public-key-src-20-f8adba2f94fc"><strong>burn key</strong></a> as the third public key, making it unspendable since nobody can sign this UTXO. Unless, someone can brute force the burn key or find a collision with one of the two first data public keys. As these UTXOs are unpendable, they can also be pruned from the UTXO set of miners with little side effect, unless some very lucky person can find a private key to use some of them.</p><p>Moreover, Stamps UTXOs in the way they are built have a series of limitations, not only due to the limitations of blocks sizes in the BTC blockchain, but mainly because of the way developers chose to build them on chain specially concerning the burn key.</p><p>Therefore, the current BTC Stamps UTXOs cannot be used to build a new version of its content such as creating a new UTXO with a new content. They cannot be used to transfer its content to another user by creating a new UTXO where the new user have control. They cannot be used to have the token data updated in a new UTXO. The token cannot be undone, that is the satoshis backed by the UTXO script is locked ‘forever’. The only thing you can do on chain is to stare at those UTXOs and say: There are some unspendable UTXOs.</p><p><strong>3— Optimized and Useful Stamps UTXO Script for Data</strong></p><p>Optimized versions of Stamps UTXO script that allow the UTXO to be transferred to another user, or build a new UTXO with updated data from the former, or even undo the UTXO, can be built as follows:</p><p>An script with only two “public keys” can be applied to optimize the space of the UTXO script to accommodate data up to around 460 bytes per UTXO.</p><p>OP_1<br>&lt;uncompressed PBK1&gt;<br>&lt;compressed PBK2&gt;<br>OP_2<br>OP_CHECKMULTISIG</p><p>Where all token data needed can be stored on the first public key of the script, and the second public key is the one controlled buy the owner of the token.</p><p>We first chose to use the uncompressed format for the first public key, but there would be no problem to use the compressed format as well. However, there is a very small but real possibility of collision for either compressed or uncompressed SEC format. That is when the data is exactly 64 bytes long for uncompressed format or 32 bytes compressed format, that may happen a collision with a real public key of another user, allowing him to unlock the UTXO.</p><p>In order to avoid this collision for any SEC format public key, we changed the compression flag to 0x05, that avoids collision with uncompressed format that is 0x04 and with the compressed format 0x02 for even y and 0x03 for odd y.</p><p>Moreover, the Bitcoin protocol does not care about the compression flag at all, as can be see in the transaction where in 2013–04–06 17:28:10 GMT -3 the Bitcoin White Paper where uploaded, if we browse the UTXOs we find that the first byte after the push data size had nothing do to with SEC key compression format, as shown in Fig. 2. It could well be considered the first Stamps on chain.</p><p><a href="https://blockstream.info/tx/54e48e5f5c656b26c3bca14a8c95aa583d07ebe84dde3b7dd4a78f4e4186e713?expand">https://blockstream.info/tx/54e48e5f5c656b26c3bca14a8c95aa583d07ebe84dde3b7dd4a78f4e4186e713?expand</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nvc48Sn7konBv_Uh9kQp-A.png" /><figcaption>Figure 2 — No SEC Compression Format in the UTXO of the Bitcoin White Paper on Chain</figcaption></figure><p><strong>4 — BTC TestNet vs SigNet</strong></p><p>We learnt from our BTC friends that they use two different networks for test, the regular TestNet and also another one called SigNet. According to a friend form Bitcoin Script Project on Telegram, the main difference is that while TestNet have its blocks mined, SigNet have its blocks signed into the blockchain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_xu4RjVj1LMcxM8Mjd7pxg.png" /><figcaption>Figure 3 — TestNet vs SigNet</figcaption></figure><p>During our many tests, we discovered that SigNet imposes limitations not found even on the BTC MainNet, for example: on 2023–12–12 Counterparty send a TX to the MainNet with an OP_RETURN output (the 2nd output) of the transaction shown below. But when we try to Broadcast a TX with an OP_RETURN on the SigNet it rejects, but TestNet accepts it fine as the MainNet does.</p><p><a href="https://blockstream.info/tx/549a5cc4bc189c800f0f9ea01068e8a7fd987c7dadb40c0b6a224d489ed070cc?expand">https://blockstream.info/tx/549a5cc4bc189c800f0f9ea01068e8a7fd987c7dadb40c0b6a224d489ed070cc?expand</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0DAyI1jdh-BHtQZPhGvN_w.png" /><figcaption>Figure 4 — Modern OP_RETURN UTXO on BTC MainNet (2023–12–12 Counterparty)</figcaption></figure><p>On this oddness, we consulted some BTC specialist friends and learnt from Super Testnet expert on Twitter, that the closest possible version of the Current BTC MainNet is the TestNet provided at <a href="https://mempool.space/testnet">https://mempool.space/testnet</a>, as show in Fig. 5.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/589/1*5s7UIsFsIGk4d917digozQ.png" /><figcaption>Figure 5— The closest possible TestNet version of the current BTC MainNet (<a href="https://x.com/circuitcracker/status/1741499701155733531?s=20">https://x.com/circuitcracker/status/1741499701155733531?s=20</a>)</figcaption></figure><p><strong>5— Proposed BTC Stamps UTXO Script for Data on TestNet</strong></p><p>In the test version of the token on the BTC TestNet we don´t use any SEC format compression for the first byte after push data size flag, all data are inserted in the raw format without any encryption or additional codification as in the current BTC Stamps version. Fig. 6 shows the the 460 bytes data inserted on the spendable UTXO (actually already spent). The red underlined hex data represent a text data, part of which is shown in Fig. 7 when converted from HEX to ASCII (Prophet Jeremiah 29:11–14a).</p><p><a href="https://blockstream.info/testnet/tx/9f42628352e8ba48b5c934e17a6ecb4c82e5ac8172366af98cb379d5ba0ba318?expand">https://blockstream.info/testnet/tx/9f42628352e8ba48b5c934e17a6ecb4c82e5ac8172366af98cb379d5ba0ba318?expand</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WmB8yrkwsPX2Eqx5zZRmMw.png" /><figcaption>Figure 6–BTC TestNet 460 bytes Data Spendable UTXO</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/605/1*_vZQUnhtKvuasHfbnDet6Q.png" /><figcaption>Figure 7— HEX data from Fig. 6 converted to ASCII</figcaption></figure><p><strong>6 — Proposed BTC Stamps UTXO Script for Data on SigNet (Very Limited)</strong></p><p>We carried similar test on SigNet, but found boundaries that limited the UTXO data size to only 128 bytes, and that using the current Stamps Script version with three “public keys”. SigNet is very strict on verification of the script and detect if we use of not the public key SEC compression Flag, reducing a lot the possibilities of new use of the Bitcoin Protocol.</p><p>OP_1<br>&lt;compressed PBK1&gt;<br>&lt;compressed PBK2&gt;<br>&lt;compressed PBK3&gt;<br>OP_3<br>OP_CHECKMULTISIG</p><p>As in the previous section, Fig. 8 shows the the 128 bytes data inserted on the spendable UTXO (actually already spent) on the BTC SigNet. The red underlined data shows the 128 bytes data plus 2 bytes representing the SEC format compression flags of the public keys.</p><p>While in the UTXO on Fig. 6 we could upload more than four verses of the chapter 29 of the book of the Prophet Jeremiah, on this UTXO on SigNet it was possible to upload on part of verse 11, as shown in Fig. 9.</p><p><a href="https://explorer.bc-2.jp/tx/9becb93a15ab4b47eaca85c852d4309f82a28677a0a557df3c0fa6b82ef9293d?expand">https://explorer.bc-2.jp/tx/9becb93a15ab4b47eaca85c852d4309f82a28677a0a557df3c0fa6b82ef9293d?expand</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nD3apHmney5DOaRTxO66eQ.png" /><figcaption>Figure 8–BTC SigNet 128 bytes Data Spendable UTXO</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/597/1*V5a9DEPGwaUkS5KTSbPSng.png" /><figcaption>Figure 9— HEX data from Fig. 8 converted to ASCII</figcaption></figure><p><strong>8— Proposed BTC P2PKH UTXO Script for Data on TestNet</strong></p><p>The P2PKH UTXO was testet only on TestNet, that follows more closely the Bitcoin protocol, SigNet just rejects transactions when different UTXO scripts of what it recognizes are sent to it.</p><p><strong><em>8 .1— P2PKH script + OP_RETURN + &lt;data&gt;</em></strong></p><p>The first P2PKH token we tested was of the form:</p><p>P2PKH script + OP_RETURN + &lt;data&gt;</p><p>The test token transaction was successfully broadcasted as show in Fig. 10. However, when we tried to use this UTXO we got the erro shown if Fig. 11. It seems that BTC TestNet node searches for the OP_RETURN opcode on the UTXO script upon its use and does not allow it to be spent.</p><p>So currently, it is a type of unspendable token on the Blockchain. It is not good, because being unspendable it can be pruned from the blockchain UTXO set of miners, the thing that we want not to be done.</p><p><a href="https://blockstream.info/testnet/tx/b6903b5cd4271a49853a2779a1d1b126793354aa8be5d4039d9f98769c3c5af1?expand">https://blockstream.info/testnet/tx/b6903b5cd4271a49853a2779a1d1b126793354aa8be5d4039d9f98769c3c5af1?expand</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6CHlbaBdxAkAZ0Eixbvb0A.png" /><figcaption>Figure 10 —Currently Unspendable P2PKH + OP_RETURN + DATA Token</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/1*clBefDwzPI28uJu0JR9kmA.png" /><figcaption>Figure 11 — Error Trying to use the UTXO shown in Fig. 10</figcaption></figure><p><strong><em>8 .2 — P2PKH script + &lt;data&gt; + OP_DROP</em></strong></p><p>The second P2PKH token we tested was of the form:</p><p>P2PKH script + &lt;data&gt; + OP_DROP</p><p>The test token transaction was successfully broadcasted as show in Fig. 12, and also was successfully spent as can be verified on the blockchain explorer.</p><p>As the proposed token script shown in section 5, this a very useful UTXO token where we can perform all desirable functions on a UTXO: it can be used to transfer its content to another user by creating a new UTXO where the new user have control; it can have its content updated in a new UTXO; and it can be undone, that is the satoshis backed by the UTXO can be unlocked.</p><p><a href="https://blockstream.info/testnet/tx/9fbe9bf87f6e35f5ed78980e88dec80985dcef4d0bb8b3dd67378b7dea114093?expand">https://blockstream.info/testnet/tx/9fbe9bf87f6e35f5ed78980e88dec80985dcef4d0bb8b3dd67378b7dea114093?expand</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g8RVmtWY4_449Kg4UVrHfg.png" /><figcaption>Figure 12 — Spendable P2PKH + DATA + OP_DROP Token</figcaption></figure><p><strong>9 — Current BTC Push Data Limit Per UTXO Script on TestNet</strong></p><p>Using the UTXO script proposed on section 8.2 we verified that currently the maximum size for a spendable UTXO script on the BTC chain is 549 bytes. Using the proposed UTXO script we can upload 520 bytes of data on a spendable UTXO as show in Fig. 13. The data content is the same of that shown in Fig. 7 plus some additional characters in order to find the current allowed limit. This UTXO was also spent as can be verified on the BlockStream explorer.</p><p><a href="https://blockstream.info/testnet/tx/3fb8f2e6ac1fe0da51a7d2ed7aae4aba0c19da25bc8bd93ef29fed5fe767c3da?expand">https://blockstream.info/testnet/tx/3fb8f2e6ac1fe0da51a7d2ed7aae4aba0c19da25bc8bd93ef29fed5fe767c3da?expand</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fz2xgLM3fUP5tQT7B56zxg.png" /><figcaption>Figure 13–540 bytes Spendable P2PKH + DATA + OP_DROP Token</figcaption></figure><p><strong>10 — Conclusions</strong></p><p>Though the BTC script has been crippled very much, as has very serious limitations to build new scripts, it is still possible to make some cool scripts on BTC blockchain, in particular scripts for keeping data on the UTXO set of miners. Though it is very limited, up to 520 bytes of data per UTXO, using multi-UTXO scheme it is possible to store data up to the current allowed transactions size.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd4d74ed63c1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Optimized Stamps on Bitcoin SV Because Satoshis do Exist]]></title>
            <link>https://medium.com/@cktcracker/optimized-stamps-on-bitcoin-sv-because-satoshis-do-exist-b6c74094c302?source=rss-4d4acbb54cdf------2</link>
            <guid isPermaLink="false">https://medium.com/p/b6c74094c302</guid>
            <dc:creator><![CDATA[Cktcracker]]></dc:creator>
            <pubDate>Mon, 25 Dec 2023 22:58:21 GMT</pubDate>
            <atom:updated>2023-12-26T14:21:05.021Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>1 — INTRODUCTION</strong></p><p><a href="https://stampchain.io/index.html"><strong>Stamps tokens</strong></a> were first proposed by BTC developers to produce unprunable UTXOs art on the BTC Blockchain, since <a href="https://docs.ordinals.com/inscriptions.html"><strong>Incriptions Ordinals</strong></a> tokens can be prunable from the Blockchain.</p><p>BTC Stamps use the following script to build their UTXOs:</p><p>OP_1<br>&lt;compressed PBK1&gt;<br>&lt;compressed PBK2&gt;<br>&lt;compressed PBK3&gt;<br>OP_3<br>OP_CHECKMULTISIG</p><p>This is a multi signature script where a single signature that matches one of the three public keys is required to use the UTXO. The first and second public keys PBK1 and PBK2, are used to store the token data, or at least part of the data in each UTXO.</p><p>The third public key PBK3 is supposed to be a real public key which private key is kept by the owner of the token. However, they use a <a href="https://medium.com/@cktcracker/dummy-stamps-public-key-src-20-f8adba2f94fc"><strong>burn key</strong></a> as the third public key, making it unspendable since nobody can sign this UTXO, unless someone can brute force the burn key or find a collision with one of the two first data public keys. And as it is unpendable, it can also be pruned from the UTXO set of miners with little side effect, unless some very lucky person can find the private keys to use them.</p><p>Moreover, Stamps UTXOs in the way they are built have a series of limitations, not only due to the limitations of blocks sizes in the BTC blockchain, but mainly because of the way developers chose to build them on chain specially concerning the burn key.</p><p>BTC Stamps UTXOs cannot be used to build a new version of its content such as creating a new UTXO with a new content. They cannot be used to transfer its content to another user by creating a new UTXO where the new user have control. The token cannot be undone, that is the satoshis backed by the UTXO script is locked ‘forever’. The only thing you can do on chain is to stare at those UTXOs and say: There are some Unspendable UTXOs.</p><p>In this article we show how to build optimized stamps tokens on the Bitcoin SV Blockchain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/824/1*QTf6lHXPQoNWKI3h_jGCLg.png" /><figcaption>Figure 1 — Stamps Token on the Bitcoin SV Blockchain</figcaption></figure><p><strong>2 — SINGLE UTXO STAMPS ON BITCOIN</strong></p><p>On the Bitcoin SV blockchain it is possible to build very optimizes stamps tokens, using a single UTXO to store all the data of the token. On the BTC chain each a Stamps UTXO is used to store at most most 64 bytes, the byte size of the two first public keys on the script above. It is likely that even at BTC chain <a href="https://bitcoin.stackexchange.com/questions/23893/what-are-the-limits-of-m-and-n-in-m-of-n-multisig-addresses?rq=1"><strong>this byte limite can be increase</strong></a> for this purpose, but they don´t go beyond that very conservative 64 bytes per UTXO. Therefore, for 1 kByte token data, it is necessary at least 16 UTXOs to store all the data of that token.</p><p>On the Bitcoin SV blockchain as the limits are still to be explored, we can build very optimized stamps, using the following script:</p><p>OP_1<br>&lt;uncompressed PBK1&gt;<br>&lt;compressed PBK2&gt;<br>OP_2<br>OP_CHECKMULTISIG</p><p>Where all token data needed can be stored on the first public key of the script, and the second public key is the one controlled buy the owner of the token.</p><p>We first chose to use the uncompressed format for the first public key, but there would be no problem to use the compressed format as well. However, there is a very small but real possibility of collision for either compressed or uncompressed SEC format. That is when the data is exactly 64 bytes long for uncompressed format or 32 bytes compressed format, that may happen a collision with a real public key of another user, allowing him to unlock the UTXO.</p><p>In order to avoid this collision for any SEC format public key, we changed the compression flag to 0x05, that avoids collision with uncompressed format that is 0x04 and with the compressed format 0x02 for even y and 0x03 for odd y.</p><p>In this first version of the token, all data are inserted in the raw format without any encryption or additional codification as in the BTC version.</p><p><strong>3 — CREATING STAMPS ON BTICOIN SV</strong></p><p>Stamps of Bitcoin SV can be created on our experimental site <a href="https://carlosamcruz.github.io/websvmenu/"><strong>websvmenu</strong></a>. On the site the user first go to <a href="https://medium.com/@cktcracker/access-console-4489593b83e3"><strong>Access Console</strong></a> menu and insert his experimental private key to use the site, and it can produce the token both on MainNet or TestNet.</p><p>After inserting his private key, the user goes to menu ( <strong>Satoshi to Peer / Opt Stamps</strong> ), as shown in Fig. 2. Next the user inform the number of satoshis to be locked on the UTXO, at least 1 satoshi, then it can informa a text of select a file from his device and press create. Upon success the result will show the TXID of the token transaction, as shown in Fig. 3.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/688/1*1fE29F0I-P536WJJUAjzRg.png" /><figcaption>Figure 2— Menu to Create Stamps on BSV</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/803/1*wgLA96z8J-6rgugxTav-vw.png" /><figcaption>Figure 3— Creation of a Stamps Token on the Bitcoin SV Blockchain</figcaption></figure><p>On chain, the explorer the token appear as a multi-signature UTXO, as shown in Fig. 4. Using its TXID, it is possible to execute different operations with the token, as shown in the menu of Fig. 2, such as, reshape its content, transfer the ownership of the token UTXO to a different user, also the current owner of the token can undo it using the MELT menu and use the satoshi in a different application.</p><p><a href="https://whatsonchain.com/tx/5e8ccbb76be9f57b7665056b06458395051e0fe5346fdf03902e607c3ad6af31"><strong>5e8ccbb76be9f57b7665056b06458395051e0fe5346fdf03902e607c3ad6af31</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aPRd_1JA-_UmtsOL3fs6Kw.png" /><figcaption>Figure 4— Details of the Token on the WhatsOnChain Explorer</figcaption></figure><p><strong>4 — RETRIEVING STAMPS DATA</strong></p><p>To retrieve the token data, the user goes to menu ( <strong>Satoshi to Peer / Data on Chain / Read Data</strong> ), as shown in Fig. 5. Then the user insert the TXID of the token current state and press read button. The data of the token will be displayed to the user as shown in Fig. 6. Additional information such as, token type, balance in satoshis, state of the token in that TX (Current if the UTXO is still unspent, Past if it is already spent), the block height on which the TX was was included, and also the address of the current owner of the token, that is the user that can use the UTXO of that transaction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/593/1*EGN6MM6b0kYnR9-Tz5ZkfA.png" /><figcaption>Figure 5— Retrieving Token Data</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/631/1*2R0rLB5egIBflvYFKEwrPg.png" /><figcaption>Figure 6— Token Data Retrieve From the Blockchain</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b6c74094c302" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>