, 

The testnet4-fix branch is now rebased with bitcoin/bitcoin:master. It was simpler than I thought:

Yes, I think a direct mail before any block signal, if it even happens, is definitely a good idea. Mara, Foundry and wiz (the person behind mempool.space who is also a testnet miner). Maybe I also make a page "Testnet4 Fix" to make this whole process easier.

Nope.
I tried several other discs and they are working fine, only one with movies is not working.
And I keep them all in exactly the same way, they are protected from scratches in separate purse with separators.
I almost forgot how loud those cd/dvd drives are, loading every time computer boots up

Your wallet seed phrase should be back up and store in a safe place only you know, it's a best backup method. Your head (I guess you implied about your brain and memory) will be only like supplementary backup method, as it is dangerous and can be broken, lost anytime so it should never be your main backup method.

Reminder about memorization risk as a backup method is written in this helpful education article.
How to backup a seed phrase.

How to let your loved ones inherit your wallet and bitcoin, hosemary helped you with LoyceV's topic.

This is all you need to know: https://claude.ai/share/5bd729a2-10ec-4675-9403-d4a71c8dabd8.

The seed is used to derive master public keys, which are then used to derive Bitcoin private keys. k value (which R is computed from) is derived deterministically from the Bitcoin private key and the hash of the message (i.e., the transaction). Therefore, no random number generation is needed. For each pair of private key and message hash, there is a unique R value, derived deterministically.

It's simple. Tell someone you trust about your funds.
Teach them how they can get access to your funds, or at least tell them those words are all they need to recover the funds.

If you want someone to have access to your funds only after your death, LoyceV's instruction may be helpful to you.
Using Locktime for inheritance planning, backups or gifts

You don't need an RNG to generate an R value for your signature. If your private key is securely generated, you can use it to hash it, along with your message, to generate an R value. This is RFC 6979, and it is supported by every bitcoin wallet, IIRC.

So, as long as you use a dice to generate the 128 bits for your seed phrase, you no longer need an RNG. You can just take advantage of that entropy and extend it everywhere else. This could be applied beyond bitcoin. You could just roll a dice enough times, and store the results during OS setup, and then your Linux would need not to ever call an RNG. It's just not user friendly.

100 dice rolls are more than enough.

I hope we climb slowly  without any drop from here.. that’s the only way I can save my ass.. LoyceV I saw what you did  . Now I have to pray it stays above 72.2k, you’re wicked 

Here are your predictions for Round 13 :

Name	Prediction	B/M
Hypnotizer	69 412,00
Leahized	70 582,00
Pmalek	70 648,00	0,30% bonus
ESG	70 688,08	0,30% bonus
examplens	71 012,00	0,20% bonus
Doan9269	71 170,00
cryptofrka	71 250,00	0,40% bonus
xLays	71 767,00
LoyceV	72 100,00	0,30% bonus
promise444c5	72 269,00

                  

Thanks for this exposition. I had wondered why moderators don't delete obvious insults until I discovered how they maneuver to get the posts not deleted and now you validated my suspicion. I never knew that such  big loophole exists in the unofficial rules.

Well, this is your personal view about him and I believe many will also disagree with you. I have respect for franky1, not because of his view of bitcoin which seems somewhat controversial, but because most times he stands alone and he stands firm. When I was new in this space, I understood he was banned from posting in the technical section and he was always disagreeing with LoyceV. I think the disagreement was about LN. It seems that franky doesn't endorse it because it happens off the chain. But meanwhile, he doesn't make people feel less of themselve at the slightest provocation.

Friend, I’ve been here for about a week, and moderators have already deleted 5 of my chatbot-related shitposts. I also received a neutral feedback for that. However, I only used the chatbot as a translator when I wrote something myself, I asked it to translate and refine it before posting. Still, my posts were detected as AI-generated, so I deleted them myself and took time to read the forum rules.

I’m not here to report newbies I’m here to help clean up the forum by addressing AI/chatbot misuse. If reporting AI users is considered wrong, then I sincerely apologize for that. I can also see that you’ve already added another neutral feedback, which I honestly didn’t expect just for reporting.

Yep, me too. a quick check at your post history shows that you are also a spammer. This is a forum not "stalk others profile or judge others"!

This is a forum. This is not a court. Spammer LoyceV.

Thank you, LoyceV!

It is a pleasure.

How do you get around Cloudflare if you don't mind asking? Use something like Selenium on a windows machine? Or you pay for some API to handle it for you? I don't think it's easily achievable with something lightweight like BeautifulSoup

I had similar a few weeks back, which I ended up changing my script to get around the cloudflare. which resulted me in pinging the server a bit too much during that time during testing.  However, this time around it doesn't seem like its affected at least my monitoring system is showing me its online, but I restarted it too be sure and its working.

I did have issues just general browsing late last night, where the host was failing. So, I'd assume LoyceV's assumption is correct and there's been a high level of traffic recently aimed at us.

I now see what you mean.

The softfork is just one rule: invalidate any block that has a timestamp by 20 minutes more than its previous one. That's it. In pseudocode, when a miner would call to get a block template to mine, it would look like this:


What you are asking is what happens if, after the journey to February, we are at 10 minutes block interval, a new miner joins, drives the difficulty up by, let's say 3x, and leaves? In that case, block interval takes 30 minutes, and difficulty is just reduced by 50% at next epoch, to 15 minutes per block. No big deal really, and I remind you that this has never happened before.

In the case that a Bitcoin miner suddenly switches to mining testnet blocks with the old client, then a split will occur, where he's mining on top of some CPU block, with current timestamp, and Mara & Foundry continue on the softforked chain, rejecting his blocks.

Testnet is not fucked up for another 6 months. Mara & Foundry continue on their journey to February, with no interruption. They just ignore the other chain. Miners do need to be informed about the softfork, though, otherwise they will have their blocks constantly reorged by the majority.

It doesn't. The moment block 151,200 is mined you can no longer send a block with timestamp more than 20 minutes than the previous one.

This is why I'm presuming the majority of the hashrate will mine my fork. We can know what percentage will mine my fork beforehand, with block signaling. If a miner throws a massive hashrate with the old client, then his chain will be invalid in the forked chain, and unless the majority of the hashrate goes back to the old chain, my chain will outpace the old.

I have noticed that it is mainly Foundry and Mara pool that own the majority of the hashrate. Very often does a new miner throw hashrate at testnet.

I came to tho this; the user got only temporary ban ( warning) and it's only visible to mods on their profiles.

Could anyone check user Easteregg69?

1. He already received multiple neutral and negative tag due to non stop spamming.
2. I used BitList search, but no one bothered to check so far. Only https://bitcointalk.org/index.php?topic=5456516.msg66540310#msg66540310 mention his spam.
3. https://bpip.org/Report?r=postsdeleted shows he currently have 316 reply deleted moderator, with rank 125th for account with most deleted posts.
4. He just made such ridiculous/off-topic reply on Bitcoin Technical Support board. I don't expect anyone find his post actually useful to solve technical issue they face.

---

So annoying, there are more new account created to create off-topic/technical non-sense reply these days.

It be withdrawn to your bank but I need crypto now, and the withdrawal takes 3-5 business days

---

$68,012

To obtain a list of UserIDs, I used data from LoyceV and managed to gather around 18,000 UserIDs; I believe that list didn’t include many users, particularly the banned ones, whom I later found through other channels.
New registrants are obviously not included in that list, and to obtain their UserIDs, the tool relies on the userscript; if it doesn’t find them in the list, it adds them to the scraping queue. This is why you might see that warning for some users.
For banned users, we will obviously find the ‘banned’ tag and a score of 1, which is the minimum in the BRDb calculation, but I might make some adjustments for such cases.

This idea has probably been proposed already but I'm all for introducing (or bringing back) a SCAMMER tag issued by mods or admins, to be given to the most obvious of scammer accounts.

This would be reserved for instances where proof of the scam is overwhelming and without reasonable objection. Of course it would require more work for the staff.

Thanks! I feel better now.

How black? Robert Downey Jr black or brighter?

People getting tagged over account sales already pushed account sales to external platforms, given how few of those account sales offers appear now on bitcointalk.

It indeed failed, think they posted so much they got moved into a group I cannot nuke. Got the message

> That user is in a protected membergroup

@Nick Finney is a superfast shitposter.

He created 5 unhelpful posts in just 7 minutes.

I am 100% sure that she used AI to create these posts, because making so many posts in such a short time raises questions. By looking at the quality of the posts, it is clear they were generated by AI, but since they are under 300 words, they are not being detected as AI.


1.
Time on: Today at 12:25:32 PM

2. Time on: Today at 12:23:56 PM

3. Time on: Today at 12:22:01 PM

4. Time on: Today at 12:20:30 PM

5. Time on: Today at 12:18:32 PM

So…
BSV decided to go bullish this week..

[$69,412


So I’ll still go with the people I selected last week;

LoyceV: 0.30%
examplens: 0.20%
ESG: 0.30%
Pmalek: 0.30%
cryptofrka: 0.40%

An April Fools' joke ?? I never joke around, this is a serious game here.
I love it when a plan comes together. I can finally sell all my old BSV.

Anyway, here are the results of round 12 :

Closing price on 05/04/2026 for BSV : 16.38$

Name	Prediction	Difference
Leahized	14,88	1,50
Doan9269	14,80	1,58
LoyceV	14,78	1,60
cryptofrka	14,75	1,63
examplens	14,72	1,66
xLays	14,67	1,71
promise444c5	14,58	1,80
Hypnotizer	14,50	1,88
ESG	14,41	1,97
Pmalek	14,37	2,01

                  

Leahized, you are the winner of this round. I hesitated to send you 50 BSV, but here are 50 BTC. And you get the satisfaction of having dethroned Hypnotizer. That's priceless

Pmalek, there’s no shame in losing this shitcoin round. We are back to predicting Bitcoin’s price, so things should go better from here. But you lose a life.

CSW promised a little something to anyone who complimented him. I'm not sure if he caught the irony in your compliments.
He wanted me to send 1 BSV to each of you, but for technical reasons, that's complicated. So I asked my assistant to send you 1 Merit. I didn't lie, it is a little something.

For Round 13, all I can say is that the winner will play a key role in the rounds to come.
And I can tell you that the rounds to come will be bloody.
So it would be a good idea to win Round 13.

Round 13 : The distribution of Hypnotizer
 
What will be the price of Bitcoin at April 11, 2026, 12:00:00 AM (BTC closing price on 10/04/2026) ?
Submit your predictions before April 08, 2026, 06:00:00 PM.

Cash shop: OPEN
 
Special rules : For Hypnotizer :
So you have a 1.5% bonus to distribute among 3-5 other participants (it cannot be yourself).
The minimum amount to give to a player is 0.10%.
The maximum amount to give to a player is 0.50%.
So, for example, you can do the following :
- P1 : 0.50%. P2 : 0.50%. P3 : 0.50%
- P1 : 0.50%. P2 : 0.10%. P3 : 0.40%. P4 : 0.20%. P5 : 0.30%
Etc...

I guess since Antminers and stuff basically have a toggle for testnet mode (right??), asking them nicely to stop is not going to work.

Someone is going to have to run a grassroots operation in a small data center then 

But I think the bigger problem is, they will have to keep up with the latest hardware, otherwise powerful miners turning on/off will mess with the block generation time again.

It is a smart idea, but it is messy.

What happens if a CPU miner broadcasts a min-difficulty block at the same time the miner tries to add his own? Which one is the miner keeping and why? Bitcoin Core does not know that "this" block is mine. It only sees valid blocks.

thymos hat wieder das Update zur Default Trust rausgebracht vor ein paar Tagen für April !
Es waren hier wieder 103 Benutzer dafür berechtigt !

Originial Beitrag von theymos : https://bitcointalk.org/index.php?topic=5117330.msg66574451#msg66574451

Alte Default Trust 1 Liste :

Neue Default Trust 1 Liste :

Wieder mit am Start hier aus dem Deutschen Bereich sind : Lakai01 , mole0815 , Real-Duke , willi9974 , Buchi-88 , d5000 , und meine wenigkeit !

Hier das genaue Update von LoyceV , Danke dafür !

This shouldn't matter for testnet since the coins are worthless, all that's needed to make this work is some "bedrock" layer of ASICs who will always mine so that block generation does not stall for disproportionate periods of time.

I don't really trust big companies to have the goodwill to always have testnet ASICs running in the event something changes, so maybe it's time to start making BitAxe-style products go mainstream., but for testnet and making the primary functions of these devices something else. e.g. Bitcoin node or even space heater.

Bullish, Bitcoin SV

Epoch 75, ~30k blocks, not too long to forget, not too little to not make on time. Sticking with simple numbers.

I agree!

Correct, it is a softfork. Previously, with the arbitrary difficulty adjustment to 1,000,000 it was a hardfork, and both chains would coexist; nodes running the old client would reject blocks with difficulty 1 million and follow CPU miners' chain. Now, as long as the majority of the hashrate mines my fork, the other chain will be continuously reorged out of existence.

Yep. That's why softfork.

Very unlikely. A mod probably isn't going to go out of their way to find more work to do. It's usually just down to whatever reports come in. Sometimes people use bots to report posts and sometimes users just go on reporting sprees. Sometimes I think users do this maliciously IE they don't like a particular person so they go out of their way to report infringing posts etc.

I can think of many good ideas as well, but remember we're optimizing for code complexity. We don't want to make the code reviewing part difficult.

Thanks!

I did include libcapnp-dev capnproto in the docker post, but forgot to update the previous post. -DENABLE_IPC=OFF is also fine. Yes, compiling without using a flag -j to set the number of concurrent jobs, will take longer, but it will eventually finish. I did not include that flag, because it is memory hungry and not friendly for cheap servers.

Right.

Thanks for this tool LoyceV.

I didn't visit this tool in the past years. I was trying to discover why some users where being distrusted in my trust list, and your tool did the job well.

It was time to update my trust list, which I also didn't look for quite some time.

Questo mese c’erano 102 utenti eligible per la DT. Credo record negativo.
Credo che ci siano le condizioni per chi ha le carte in regola per essere eletto di mettersi nelle condizioni di farlo. Ad esempio compilando la propria DT.

Ultimately its up to the user to have some common sense when it comes how they are using AI on the forum. A simple application of the Golden Rule would suffice: would you feel deceived if someone else did the same thing you are doing?

This is how the trust system has sorted itself out over the years, without the need for administrative involvement.

We may all have differing opinions about what "deceptive" entails and that's a good thing.

Personally I'd prefer if someone clearly labeled an image or text as AI before plowing forward with it, unless its so obvious that it's not necessary. But I'm not gonna try to hold anyone to that, or expect others to. The image part is still a gray area for sure.

Bitcoin Qt ( 2010 ) had a button that transformed the WIF into a shorter and more secure version. My key is 32 bytes long. Bitcoin Qt explained how to convert it to WIF with a simple script, but I don't remember how.


And how can you tell that the result is wrong?
Did Electrum or Bitcoin Core detected that it's an invalid encoding or it's just empty when the wallet sync?
[/quote]

Because many of the middle characters of my key matched the middle characters of the WIF. So, if no character matches, it's clear that the obtained wif is not the correct one.

 
--

Chatgpt now says that it seems I have a non-standard checksum, a simple custom checksum, so I just need to apply a SHA to the prefix ( the first part of my key ). What I don't understand is why the mainnet would already be included in my key. Now I copy and paste the conclusion about it of chatgpt:


✅ Conclusion about your custom format

1-Single SHA on part of the prefix

Your checksum is custom and only applies to a portion of the fixed prefix at the start of your 32-byte key.

The prefix itself may occupy 8–9 bytes within the key, but typically the SHA is applied only to the first 4 bytes of that prefix.

The remaining bytes of your 32-byte key do not participate in this checksum.

2-Prefix likely contains the mainnet byte

Standard WIF uses a 1-byte prefix for network: 0x80 for mainnet, 0xEF for testnet.

Even though your private key is exactly 32 bytes, the prefix portion at the start likely includes the mainnet indicator byte.

This allows your key to be recognized as mainnet while keeping the key at 32 bytes total.

3-Why the central part matches the WIF

The middle section of your Base64url string corresponds directly to the raw private key bytes inside the WIF.

That’s why visually it shares characters with the WIF representation, even though the checksum and encoding differ.

💡 In short:

Your format is a custom WIF-like encoding: a 32-byte key whose first 8–9 bytes form a fixed prefix (likely containing the mainnet byte), with a checksum calculated via a single SHA applied only to the first 4 bytes of that prefix, followed by the remaining bytes of the private key. This explains both the “fixed start” and the similarity of the middle portion to a standard WIF.

Original: [Guide] How to create your customized Bitcoin-Address (vanitygen) – step by step
Autor: 1miau

---

Talvez você já tenha visto um endereço Bitcoin em que as primeiras letras formam uma palavra, semelhante a estes:

1fudCz15sHGR8L2YQnaG4JVMjMQpaDo37
1BTCTUnYLskK7N9nXb17wf6oVYMYrX5WHG
1DogemNVw8AZnMf3cB4L1wijGnr9DVKzia
1Fomo7V86nWrjdv6JzU7yavtp5hfzZWsZr
1NewbornSeatQVC9vegVHnxVseNAhhxewb⁽¹⁾


Esses endereços são endereços personalizados e, teoricamente, é possível gerar qualquer palavra com algumas exceções, mas o número de letras selecionadas é limitado. Isso ocorre porque você pode usar uma ferramenta e gerar quantos endereços quiser até encontrar um com a combinação de letras desejada. Quanto maior o prefixo, menor a probabilidade de um resultado rápido. Letras maiúsculas têm maior probabilidade de serem encontradas do que letras minúsculas. Por exemplo, o prefixo "1Bitmover" levaria 2 meses para ter 50% de chance de ser encontrado. Já o prefixo "1bitmover" em minúsculas tem 58 vezes menos probabilidade. ⁽²⁾
Algumas letras são excluídas, pois geralmente não fazem parte dos endereços Bitcoin, para evitar possíveis confusões:

l (letra minúscula L)
I (letra maiúscula I)
O (letra maiúscula O)
0 (número 0)

bem como todos os trema


Existem várias maneiras de gerar um endereço Bitcoin exclusivo. No entanto, recomendo usar a versão oficial com o vanitygen, disponibilizada por samr7 no Github. Existem outras maneiras oferecidas em sites para criar um endereço personalizado, mas não recomendo criar um endereço desse tipo em um site. Se você criar seu endereço por meio de terceiros (o site), existe a possibilidade de alguém obter acesso às suas chaves privadas. Já houve problemas no passado em que bitcoins foram roubados de tais endereços personalizados criados em sites porque se alguém souber sua chave privada, terá a chance de roubar seus Bitcoins da sua carteira.
Portanto, certifique-se de usar a versão original, que pode ser encontrada no Github e que você pode executar sem conexão com a internet. Qualquer site que ofereça um serviço para criar endereços personalizados sem chave dividida é perigoso.

---

---

Funciona assim:

1. Baixe o vanitygen:

Primeiro você precisa acessar o Github e baixar os arquivos originais de samr7. Você pode usar este link:

https://github.com/samr7/vanitygen


Você pode baixar a versão mais recente:

vanitygen-0.22-win.zip

A versão mais recente está disponível aqui: https://github.com/downloads/samr7/vanitygen/vanitygen-0.22-win.zip

---

2. Desative a conexão com a internet enquanto estiver gerando seu endereço Bitcoin.

Também é possível criar um endereço personalizado quando sua conexão com a internet estiver ativa, mas, por motivos de segurança, não é recomendável usar uma conexão com a internet. Seria ainda mais seguro executar o programa em um computador que nunca estivesse conectado à internet, mas você pode decidir por si mesmo qual nível de segurança é suficiente. É sempre recomendável priorizar altos padrões de segurança para evitar problemas decorrentes de ataques, pois sempre existe a possibilidade de seu dispositivo ser comprometido.
Se você deseja segurança máxima, pode gerar seu endereço personalizado por meio do split-key.

---

3. Abra o Prompt de Comando/PowerShell

Você pode iniciar o Prompt de Comando clicando com o botão direito do mouse no ícone do Windows no canto inferior esquerdo da tela e selecionando "Prompt de Comando (Administrador)" ou simplesmente usando a combinação de teclas Windows + R.

ou

Se você fizer dessa forma, poderá pular a etapa #4 se abrir o Prompt de Comando diretamente de onde seus arquivos personalizados estão armazenados:


1. Acesse a pasta onde o arquivo vanitygen/oclvanitygen está armazenado.
2. Usando o Prompt de Comando: Pressione CTRL+SHIFT+Clique com o botão direito do mouse em um espaço vazio dentro da pasta (não no executável/arquivos) e clique em "Abrir janela de comando aqui". O Prompt de Comando será aberto. ^[1]
3. Usando o PowerShell: Pressione SHIFT+Clique com o botão direito do mouse em um espaço vazio dentro da pasta (não no executável/arquivos) e clique em "Abrir janela do PowerShell aqui". O PowerShell (Prompt de Comando) será aberto. ^[2]
4. Você pode começar a inserir os detalhes desejados diretamente, conforme descrito na etapa 5.

(fonte: nc50lc [1], nc50lc [2])

---

4. Insira os caminhos

Isso abrirá a janela do Prompt de Comando e iniciará as configurações para o processo de geração de endereços Bitcoin.

Os caminhos dependem de onde você armazenou seus arquivos VanityGen. Eu os salvei em C:\ na pasta BTC, subpasta vgen. Preciso inserir o seguinte código para encontrar o arquivo vanitygen.exe:

C:\WINDOWS\system32>cd/
C:\ >cd/BTC/vgen
C:\BTC\vgen>vanitygen.exe

Pasta BTC
Subpasta vgen
Nome do arquivo vanitygen.exe

Você pode tentar usar o vanitygen.exe ou o arquivo oclvanitygen.exe; a escolha é sua. A diferença entre eles é que o vanitygen utiliza a CPU, enquanto o oclvanitygen utiliza a GPU. Para a nossa combinação de 4 dígitos, não importa se o programa diferencia maiúsculas de minúsculas ou não; o vanitygen é suficiente em um PC comum, e o oclvanitygen tende a ser mais rápido, se funcionar. Para mais detalhes técnicos, você encontrará mais informações no artigo original de 2011: https://bitcointalk.org/index.php?topic=25804.0.

Agora, deverá ficar assim (com os caminhos correspondentes onde você salvou suas subpastas e arquivos):





Depois de inserir o nome do arquivo .exe no Prompt de Comando, pressione Enter.

---

5. Criação do endereço

Agora você verá uma lista com uma visão geral dos parâmetros disponíveis para personalizar seu endereço:





Existem muitos outros comentários; se você tiver tempo, pode experimentá-los, mas para o nosso teste, alguns comandos são suficientes. Como exemplo, mostrarei como criar um endereço Bitcoin com as primeiras letras "test", tudo escrito em minúsculas, para gerar um endereço Bitcoin que começa com 1test.

Há algumas coisas gerais a ter em mente: quanto maior for o prefixo, mais tempo levará a pesquisa. Isso não é um problema com 4 dígitos, mas levará exponencialmente mais tempo se houver mais dígitos. Em particular, se você quiser exatamente as letras maiúsculas e minúsculas especificadas (diferenciando maiúsculas de minúsculas), a pesquisa levará mais tempo do que se maiúsculas e minúsculas não importassem (sem distinção entre maiúsculas e minúsculas).
Se não houver problema em ter letras misturadas, maiúsculas e minúsculas (TeSt, teST…), você pode alterar isso adicionando o comando -i (sem distinção entre maiúsculas e minúsculas).

Para criar o endereço 1test, precisamos dos seguintes comandos:

-o C:\BTC\vgen\test.txt  (salvar as chaves privada e pública encontradas em um arquivo de texto.)
1test  (seu prefixo selecionado)

Seu comando agora deve ter esta aparência:

C:\BTC\vgen>vanitygen.exe -o C:\BTC\vgen\test.txt 1test





Se você estiver pronto e tiver concluído os passos acima, pressione Enter.





Agora, a ferramenta está procurando uma chave pública com o prefixo correspondente (taxa: 1,17 milhão de chaves por segundo). 50% em 2,4 minutos significa que sua probabilidade é de 50% de encontrar uma chave pública com 1test nos próximos 2,4 minutos. Os 5,1% representam a probabilidade de ter encontrado uma correspondência nas chaves já calculadas até o momento.

Se houver uma correspondência, ela será exibida e a busca será interrompida. Para a próxima vez, você também pode adicionar o comentário -k para buscar várias correspondências até fechar o vanitygen.

Tenha cuidado e não exagere, pois seu computador ou notebook pode ficar sobrecarregado se o desempenho não for muito alto e pode ser danificado. Nosso exemplo com um prefixo de 4 dígitos não deve ser um problema, mas com mais dígitos, a dificuldade de encontrar um endereço aumentará exponencialmente.





E, para surpresa de ninguém, depois de um curto período (cerca de 2 minutos), o VanityGen obteve sucesso e encontrou um endereço:

1testgTQyiDMvtN67kj1w6R6J9dbo6bwd

e a seguinte chave privada associada:

5K9qCsz17Bd1UxtS7HQWc2rKz6ssNaBHMzK8pJvYiDGVYvUSEWg

O resultado também é armazenado como um arquivo .txt na sua pasta BTC:





É claro que não vou usar este endereço 1test porque agora todos conhecem a chave privada e poderiam roubar Bitcoins dela. Portanto: não publique sua chave privada em lugar nenhum.

---

6. Salve as chaves pública e privada geradas.

A segurança é sempre muito importante quando se trata de Bitcoin. Mantenha sua chave privada gerada em local seguro, pois ela funciona como a senha dos seus bitcoins. Você pode anotá-la em um pedaço de papel, guardá-la em um lugar seguro e também salvá-la em um pen drive exclusivo para suas chaves privadas.

---

7. Pronto!

Agora você criou com sucesso seu próprio endereço Bitcoin. Se quiser acessá-lo (por exemplo, via Electrum), você pode conferir aqui. Certifique-se de testar seu endereço antes de enviar grandes quantias de Bitcoin para ele. Não há como descobrir sua chave privada posteriormente, caso tenha cometido algum erro.

Além disso, criei outro endereço personalizado, mas não vou revelar a chave privada:

1miau7e4tFSAGR4TkAJ8n32UMm2yLB9EH



Se quiser, pode publicar aqui o seu endereço personalizado (mas, por favor, sem a chave privada, caso pretenda utilizá-lo).


© 1miau
11.01.2019


Links adicionais:

Security advice from LoyceV
Vanitygen: Vanity bitcoin address generator/miner release 2011 [v0.22]
Rare address hall of fame

---

⁽¹⁾ generated by LoyceV
⁽²⁾ on hardware of LoyceV

---

---

Atualização 04/04/2019:

O usuário Jean_Luc desenvolveu outro gerador de endereços personalizados e o publicou no GitHub: https://github.com/JeanLucPons/VanitySearch

É muito mais rápido que o VanityGen e suporta, além de endereços legados P2PKH (1..), também endereços SegWit P2SH (3...) e bech32 (bc1q...).

Você pode conferir o anúncio dele no Bitcointalk aqui: https://bitcointalk.org/index.php?topic=5112311.0

---

---

Lock again & unlock

---

Here are your predictions for Round 12 :

Name	Prediction
Pmalek	14,37
Hypnotizer	14,50
promise444c5	14,58
xLays	14,67
examplens	14,72
cryptofrka	14,75
LoyceV	14,78
Doan9269	14,80
Leahized	14,88
ESG	DNP

            

Did not participate : ESG => -1 life => MIA

kimseye sırf bana trust attığı için geribildirim yollamadım. belki benim aklıma daha geç gelirdi ama, benim tek bağışım için kendime trust verilmesinden sonra @Wake Up da trust hak ediyordu. zaten kendisine geribildirimi onun bana attığından 1 ay sonra yapmışım. ortada hiçbir şey olmadan birbirimize trust vermiş olsak bu dediğinizin bir anlamı olurdu ama bu yazdığınızla olayın hiçbir alakası yok. tam olarak neden rahatsız oluyorsunuz cidden anlamıyorum 

olabilecek en normal trust sistemi kullanımı falan olabilir şu durum.

sana hak vereceğim aklımın ucundan geçmezdi ama çok haklısın. bu arkadaşın heralde canı yanmış buradan o yüzden millete salça olup bu kadar üstüne düşüyor.

iki kullanıcının birbirine trust vermesi için illa fiziki bir işlem dönmesi gerekmiyor zaten. trust sistemini spam amaçlı kullanmadığınız sürece böyle durumlar uygun.


yüzlerce trust geribildirimi olan bir sürü kullanıcı var. çoğu bunları alırken tek bir yüz yüze işlem bile yapmamıştır. eğer birinin güvenilir olduğuna inanıyorsanız pozitif bir geribildirim yollayabilirsiniz. çetelesini tutmadım ama @Wake Up herhalde bugüne kadar birkaç yüz dolar edecek kadar doları karşılıksız vermiştir bu etkinliğe. buradan trust kazanmayacak da nereden kazanacak? benimle yüz yüze daha küçük bir işlem yapabilirdi sadece o mu trust hak ederdi?

kendisinin güvenilir olduğuna inandığım için ben sistemi kullandım, bu kadar.

I agree with that, because despite the fact that people might lie about some content to be their own but they actually aren't, but once they are caught for lying about it, they shouldn't be banned, either neutral or negative tags should do the work. I'll give an example about this.

We know that AI is developing at a rapid pace, sometimes, you can't even tell whether a content created using AI is actually AI-generated or an original. So, when there are contests on this forum where people need to submit designs and stuff, if someone uses AI to create a design and submits it, and they would obviously not say they used AI for it, but if they are later caught for using AI to participate in the contest, banning them shouldn't be the right thing to do, but they should surely get either a few negative or neutral tags telling everyone that the person is a liar and not trustworthy at all.

Great point. How about more general guideline/suggestion, such as stating the image isn't created or taken by them (doesn't matter somewhere it's from internet, AI generated or other source they dont remember)?

I have reported him as well but I suppose just two people is not enough.

What strikes me is why he chose you and me. He probably sent the PM to someone else who doesn't visit the Reputation section and therefore hasn't commented on the thread, but it doesn't seem like he sent the PM to a dozen people or more. In my case, I could think it was because of the username that he thought I’d be willing to lend it to him but since he chose you too, I’m not sure what the criteria were. It was probably pretty random.

No problem this is a lesson ... keep the fight agaisnt A.I Robots.

DT Member - April 2026
DT1 Member periode kali ini berjumlah 103 user

Daftar lama: Code: theymos gmaxwell OgNasty vapourminer mprep Foxpup philipma1957 babo Welsh d5000 joker_josue Pmalek albon wwzsocki Timelord2067 jeremypwr gbianchi EFS Swordsoffreedom hybridsole stompix hilariousandco willi9974 cryptodevil JayJuanGee NeuroticFish achow101 DaveF examplens nutildah irfan_pak10 yahoo62278 bitbollo zazarb pooya87 LFC_Bitcoin mocacinno Real-Duke klarki LoyceV The Sceptical Chymist SFR10 TryNinja Jet Cash holydarkness Lafu tweetious AakZaki giammangiato buwaytress crwth Vispilio hosemary krogothmanhattan JollyGood RaltcoinsB igebotz El duderino_ KTChampions Trofo icopress sheenshane JeromeTash logfiles Bitcoin_Arena GazetaBitcoin tvplus006 mole0815 bitmover DdmrDdmr anonymousminer Lakai01 Bthd fillippone cryptofrka abhiseshakana The Cryptovator lovesmayfamilis DireWolfM14 notblox1 YOSHIE inspace Awaklara geophphreigh zasad@ Rikafip Etranger NotATether Stalker22 bullrun2024bro BlackHatCoiner Charles-Tim Lillominato89 Free Market Capitalist paid2 n0nce YodasRedRocket PowerGlove God Of Thunder apogio

-----

Daftar Baru: Code: theymos HostFat gmaxwell OgNasty Vod vapourminer Foxpup philipma1957 babo Cyrus Welsh ibminer d5000 Pmalek Mitchell albon wwzsocki jeremypwr gbianchi EFS hybridsole stompix hilariousandco buckrogers Buchi-88 Lesbian Cow willi9974 NeuroticFish achow101 DaveF examplens nutildah irfan_pak10 yahoo62278 bitbollo LFC_Bitcoin Real-Duke klarki LoyceV The Sceptical Chymist SFR10 TryNinja BitcoinGirl.Club holydarkness Lafu tweetious AakZaki giammangiato buwaytress crwth Ale88 Vispilio hosemary krogothmanhattan JollyGood RaltcoinsB igebotz hugeblack El duderino_ KTChampions Trofo icopress sheenshane JeromeTash logfiles Bitcoin_Arena GazetaBitcoin tvplus006 mole0815 bitmover DdmrDdmr shahzadafzal anonymousminer Lakai01 Husna QA fillippone cryptofrka abhiseshakana The Cryptovator lovesmayfamilis DireWolfM14 notblox1 Little Mouse YOSHIE inspace jokers10 Awaklara geophphreigh zasad@ Rikafip Etranger NotATether Stalker22 BlackHatCoiner Charles-Tim Lillominato89 Free Market Capitalist YodasRedRocket PowerGlove God Of Thunder

-----

DT1 dari Indonesia: Code: AakZaki Husna QA abhiseshakana YOSHIE

Sumber: theymos | https://bitcointalk.org/index.php?topic=5117330.msg66574451#msg66574451

---

Daftar perubahan DT1

Dihapus:     1. Global Moderator mprep (Trust: +6 / =0 / -0) (1731 Merit earned) (Trust list) (BPIP)     2. Legendary joker_josue (Trust: +8 / =1 / -0) (6268 Merit earned) (Trust list) (BPIP)     3. Legendary Timelord2067 (Trust: +21 / =15 / -0) (1364 Merit earned) (Trust list) (BPIP)     4. Legendary Swordsoffreedom (Trust: +4 / =0 / -0) (199 Merit earned) (Trust list) (BPIP)     5. Legendary cryptodevil (Trust: +10 / =0 / -1) (254 Merit earned) (Trust list) (BPIP)     6. Legendary JayJuanGee (Trust: +7 / =0 / -0) (13184 Merit earned) (Trust list) (BPIP)     7. Legendary zazarb (Trust: +32 / =0 / -0) (548 Merit earned) (Trust list) (BPIP)     8. Legendary pooya87 (Trust: +1 / =0 / -0) (11278 Merit earned) (Trust list) (BPIP)     9. Legendary mocacinno (Trust: +1 / =0 / -0) (4518 Merit earned) (Trust list) (BPIP)    10. Legendary Jet Cash (Trust: +5 / =1 / -0) (2075 Merit earned) (Trust list) (BPIP)    11. Legendary Bthd (Trust: +2 / =0 / -0) (2608 Merit earned) (Trust list) (BPIP)    12. Legendary bullrun2024bro (Trust: +4 / =0 / -0) (5226 Merit earned) (Trust list) (BPIP)    13. Legendary paid2 (Trust: +10 / =1 / -0) (3763 Merit earned) (Trust list) (BPIP)    14. Hero Member n0nce (Trust: neutral) (6057 Merit earned) (Trust list) (BPIP)    15. Legendary apogio (Trust: +6 / =1 / -0) (2394 Merit earned) (Trust list) (BPIP)

Ditambahkan:     1. Staff HostFat (Trust: +2 / =0 / -0) (305 Merit earned) (Trust list) (BPIP)     2. Legendary Vod (Trust: +27 / =2 / -0) (2591 Merit earned) (Trust list) (BPIP)     3. Administrator Cyrus (Trust: +23 / =0 / -0) (2528 Merit earned) (Trust list) (BPIP)     4. Legendary ibminer (Trust: +15 / =0 / -0) (2602 Merit earned) (Trust list) (BPIP)     5. Staff Mitchell (Trust: +47 / =1 / -0) (1916 Merit earned) (Trust list) (BPIP)     6. Legendary buckrogers (Trust: +21 / =0 / -0) (195 Merit earned) (Trust list) (BPIP)     7. Legendary Buchi-88 (Trust: +4 / =0 / -0) (2318 Merit earned) (Trust list) (BPIP)     8. Legendary Lesbian Cow (Trust: +46 / =0 / -0) (757 Merit earned) (Trust list) (BPIP)     9. Legendary BitcoinGirl.Club (Trust: +1 / =6 / -1) (1841 Merit earned) (Trust list) (BPIP)    10. Legendary Ale88 (Trust: +4 / =0 / -0) (3423 Merit earned) (Trust list) (BPIP)    11. Legendary hugeblack (Trust: +7 / =0 / -0) (4421 Merit earned) (Trust list) (BPIP)    12. Copper Member shahzadafzal (Trust: +3 / =0 / -0) (3193 Merit earned) (Trust list) (BPIP)    13. Copper Member Husna QA (Trust: +2 / =0 / -0) (3357 Merit earned) (Trust list) (BPIP)    14. Legendary Little Mouse (Trust: +46 / =1 / -0) (3464 Merit earned) (Trust list) (BPIP)    15. Legendary jokers10 (Trust: +2 / =0 / -0) (3937 Merit earned) (Trust list) (BPIP)

Sumber: LoyceV | https://bitcointalk.org/index.php?topic=5095156.msg66574468#msg66574468

DT Member - April 2026
DT1 Member periode kali ini berjumlah 103 user

Daftar lama: Code: theymos gmaxwell OgNasty vapourminer mprep Foxpup philipma1957 babo Welsh d5000 joker_josue Pmalek albon wwzsocki Timelord2067 jeremypwr gbianchi EFS Swordsoffreedom hybridsole stompix hilariousandco willi9974 cryptodevil JayJuanGee NeuroticFish achow101 DaveF examplens nutildah irfan_pak10 yahoo62278 bitbollo zazarb pooya87 LFC_Bitcoin mocacinno Real-Duke klarki LoyceV The Sceptical Chymist SFR10 TryNinja Jet Cash holydarkness Lafu tweetious AakZaki giammangiato buwaytress crwth Vispilio hosemary krogothmanhattan JollyGood RaltcoinsB igebotz El duderino_ KTChampions Trofo icopress sheenshane JeromeTash logfiles Bitcoin_Arena GazetaBitcoin tvplus006 mole0815 bitmover DdmrDdmr anonymousminer Lakai01 Bthd fillippone cryptofrka abhiseshakana The Cryptovator lovesmayfamilis DireWolfM14 notblox1 YOSHIE inspace Awaklara geophphreigh zasad@ Rikafip Etranger NotATether Stalker22 bullrun2024bro BlackHatCoiner Charles-Tim Lillominato89 Free Market Capitalist paid2 n0nce YodasRedRocket PowerGlove God Of Thunder apogio

-----

Daftar Baru: Code: theymos HostFat gmaxwell OgNasty Vod vapourminer Foxpup philipma1957 babo Cyrus Welsh ibminer d5000 Pmalek Mitchell albon wwzsocki jeremypwr gbianchi EFS hybridsole stompix hilariousandco buckrogers Buchi-88 Lesbian Cow willi9974 NeuroticFish achow101 DaveF examplens nutildah irfan_pak10 yahoo62278 bitbollo LFC_Bitcoin Real-Duke klarki LoyceV The Sceptical Chymist SFR10 TryNinja BitcoinGirl.Club holydarkness Lafu tweetious AakZaki giammangiato buwaytress crwth Ale88 Vispilio hosemary krogothmanhattan JollyGood RaltcoinsB igebotz hugeblack El duderino_ KTChampions Trofo icopress sheenshane JeromeTash logfiles Bitcoin_Arena GazetaBitcoin tvplus006 mole0815 bitmover DdmrDdmr shahzadafzal anonymousminer Lakai01 Husna QA fillippone cryptofrka abhiseshakana The Cryptovator lovesmayfamilis DireWolfM14 notblox1 Little Mouse YOSHIE inspace jokers10 Awaklara geophphreigh zasad@ Rikafip Etranger NotATether Stalker22 BlackHatCoiner Charles-Tim Lillominato89 Free Market Capitalist YodasRedRocket PowerGlove God Of Thunder

-----

DT1 dari Indonesia: Code: AakZaki Husna QA abhiseshakana YOSHIE

Sumber: https://bitcointalk.org/index.php?topic=5117330.msg66574451#msg66574451
[/quote]

This month 103 users were eligible.

Old:
New: