Search content
Sort by
Showing 20 of 1,634 results by lcharles123
Re: testnet4 in a SAFER container (bitcoin core, lightning core, ckpool, cpuminer)
⭐ Merited by mocacinno (1)
I just set a ckpool image, you can mine using
fvm.giize.com:3334
wallet_addr_testnet4:x
This node is reachable using I2P:
And Yggdrasil-network, an ipv6 overlay network (that also works over IPv4). If anyone is interested connecting using this network, you need to install and configure it on your machine using latest release from their github repository, it takes no more than 10min, my address inside this network:
fvm.giize.com:3334
wallet_addr_testnet4:x
This node is reachable using I2P:
Code:
c46mtw4jk37vzc3qxa53ec5odqgq5slsvzvhstutcxmwpakklxqa.b32.i2p
And Yggdrasil-network, an ipv6 overlay network (that also works over IPv4). If anyone is interested connecting using this network, you need to install and configure it on your machine using latest release from their github repository, it takes no more than 10min, my address inside this network:
Code:
201:d5df:f4ca:b9b3:5ea0:f8f8:c87:1611
There is nothing wrong with downloading a torrent just to set up a dedicated full-node. But the torrent must be the complete data folder as it is with no modifications or compression, with a fixed version of bitcoind. So it will be much more faster to just download it to actual data folder and avoid validation. The torrent can be launched and maintained by some group of trustworthy members here on the forum, who can also compare it with their own full-nodes. No need for constant updates, maybe one in 5 to 10 years.
I made a backup of the data folder at july-2024 to an HD, so if for any reason my full node become corrupted, I just need to repair it, restore the data folder from the backup point.
Its handy for those with old or low-performance hardware, taking less than one day instead of months for the IBD.
I made a backup of the data folder at july-2024 to an HD, so if for any reason my full node become corrupted, I just need to repair it, restore the data folder from the backup point.
Its handy for those with old or low-performance hardware, taking less than one day instead of months for the IBD.
Re: Your IP network is currently pending review. ( Bitcoin Core )
This all of a sudden started to work a few days later
I did send an email to bitnodes.io but got no reply, so it might have been coincidental that it started to work.
Thanks to all those people that contributed.
I did send an email to bitnodes.io but got no reply, so it might have been coincidental that it started to work.
Thanks to all those people that contributed.
Hello, can you tell me how you contacted bitnodes.io? I also have two ISPs and both are "pending review" with both ipv4 and v6, I have only ipv6 public.
Thank you!
~
Interesting solution for IBD, never encountered it before.
Having in mind 16 Gb RAM, what size should be assigned to RAMdisk ? And how to set up dbcache in this case, dbcache=1/4 RAMdisk or 1/4(RAM - RAMdisk).
And another question. What is gain in comparison with M.2 NVme SSD?
I assigned 10GB for dbcache, and 4GB for RAMDISK. Not needed big RAMdisk because it will store only a few blk and rev files, the rest will be links of that files to persistent storage.
There are many access to latest blk and rev files during syncronization.
The writes on chainstate are made up periodically or if you interrupt the sync, so this work will be amortized by download activity.
I said gain because generally RAM are faster than any SSD. But it depends on the machine you are using too. I do not have machines with M.2 connector to test.
I just synced the blockchain with this setup, have to reindex from 49% because the system crashed, since I am using 2x 500GB HDDs on a docking station connected though USB to notebook. The sync from scratch was going well with about 15% a day, but the reindex process was really slow, because i have put only index folder and chain state on RAMdisk, but not helped much.
The script needs some adjusts, removing set -e, because it not needed since if the script exits, the RAMdisk will be filled up and the bitcoind will stop after that.
So instead re-indexing, downloading from scratch is much more faster, and you can make checkpoints by interrupting the program at 30% for example, and saving chainstate and index folders and some of the recent blk and rev files. To put it back in the case of any critical event occurs further on the process.
Beginning of 2023 I was trying to run a full-node, but it doesn't worked because some problems with mergerfs. The initial sync long lasted about 4 months. But now with this strategy, i can conclude it in the same machine in less than one week.
...
I wouldnt help yogg with anything if I where you.
(Yogg hasn't been around since he swept all the keys and coin from coldkey wallets from the collectibles section)
And why are you necro posting? This topic is years old now.
I wouldnt help yogg with anything if I where you.
(Yogg hasn't been around since he swept all the keys and coin from coldkey wallets from the collectibles section)
And why are you necro posting? This topic is years old now.
I searched in this forum using many terms about "speeding up initial sync" and all the time it returned this thread as the only relevant one. But it lacks a satisfactory answer, so I just give one.
Answering the OP I just found a way to sync as fast as possible using RAMdisk, it will work even if you has a slow HDD or NAS. RAMdisk is faster than SSD but requires some complexity, like linking files
I observed which files are written frequently on sync, and I saw that are only the blk and rev dat ones on blocks folder.
bitcoind has the -blocksdir option, to specify the blocks folder, you just need to point it to a folder on RAMdisk.
I write the following script that check for completed blk and rev files on ramdisk/blocks folder and move them to persistent storage, and create a link to them, because these .dat files are used to build chainstate after completing initial sync (or successfully shutting down before it).
With this strategy the initial sync will have only network speed as bottleneck. At least for me, I have at most 10 Mb/s.
I am using a single core notebook from 2011 with debian 11, 16GB of RAM and two 500GB HDDs merged using mergerfs.
mergerfs was always using CPU before, and with this strategy, it use 0 almost all time, only when a dat file are completed.
I will post the results here after finishing the initial sync
I observed which files are written frequently on sync, and I saw that are only the blk and rev dat ones on blocks folder.
bitcoind has the -blocksdir option, to specify the blocks folder, you just need to point it to a folder on RAMdisk.
I write the following script that check for completed blk and rev files on ramdisk/blocks folder and move them to persistent storage, and create a link to them, because these .dat files are used to build chainstate after completing initial sync (or successfully shutting down before it).
With this strategy the initial sync will have only network speed as bottleneck. At least for me, I have at most 10 Mb/s.
I am using a single core notebook from 2011 with debian 11, 16GB of RAM and two 500GB HDDs merged using mergerfs.
mergerfs was always using CPU before, and with this strategy, it use 0 almost all time, only when a dat file are completed.
I will post the results here after finishing the initial sync
Code:
#!/bin/bash
# first of all create and mount a ramdisk, i.e.
# sudo mkdir -p /mount/point/folder -m 755 alice
# sudo mount -o size=12G -t tmpfs tmpdir /mount/point/folder
# ajust the variables below
# point only blocks folder to ramdisk, i.e. -blocksdir=/mount/point/folder
# use it on first run
# run this script BEFORE starting bitcoind
# otherwise move some last blk and rev files to ramdisk
# symlink all blk and rev files from ramfs -> hdd/ssd
# make sure your pc doesnt run out of power
# I have a nobreak for that
# with this setup, the sync will be limited by others factors than media speed
# shutdown bitcoind with ctrl + c, and move all non link elements to hdd/ssd
# get the blocks starting from BNBER
# this will let at least 7 blk and 7 rev files on ramdisk
BNBER=7
ACTUALDIR=/home/alice/bcdata/BTC/blocks
RAMDISK=/home/alice/temp/BTC/blocks
set -e
while true
do
# iterate only over regular files excluding links and the BNBER most recent ones
for blkfile in $(find $RAMDISK/blk*.dat -type f -printf "%f\n" | sort -r | tail -n +$BNBER)
do
mv $RAMDISK/$blkfile $ACTUALDIR/$blkfile
ln -s $ACTUALDIR/$blkfile $RAMDISK/$blkfile
done
for blkfile in $(find $RAMDISK/rev*.dat -type f -printf "%f\n" | sort -r | tail -n +$BNBER)
do
mv $RAMDISK/$blkfile $ACTUALDIR/$blkfile
ln -s $ACTUALDIR/$blkfile $RAMDISK/$blkfile
done
sleep 10m
done
# first of all create and mount a ramdisk, i.e.
# sudo mkdir -p /mount/point/folder -m 755 alice
# sudo mount -o size=12G -t tmpfs tmpdir /mount/point/folder
# ajust the variables below
# point only blocks folder to ramdisk, i.e. -blocksdir=/mount/point/folder
# use it on first run
# run this script BEFORE starting bitcoind
# otherwise move some last blk and rev files to ramdisk
# symlink all blk and rev files from ramfs -> hdd/ssd
# make sure your pc doesnt run out of power
# I have a nobreak for that
# with this setup, the sync will be limited by others factors than media speed
# shutdown bitcoind with ctrl + c, and move all non link elements to hdd/ssd
# get the blocks starting from BNBER
# this will let at least 7 blk and 7 rev files on ramdisk
BNBER=7
ACTUALDIR=/home/alice/bcdata/BTC/blocks
RAMDISK=/home/alice/temp/BTC/blocks
set -e
while true
do
# iterate only over regular files excluding links and the BNBER most recent ones
for blkfile in $(find $RAMDISK/blk*.dat -type f -printf "%f\n" | sort -r | tail -n +$BNBER)
do
mv $RAMDISK/$blkfile $ACTUALDIR/$blkfile
ln -s $ACTUALDIR/$blkfile $RAMDISK/$blkfile
done
for blkfile in $(find $RAMDISK/rev*.dat -type f -printf "%f\n" | sort -r | tail -n +$BNBER)
do
mv $RAMDISK/$blkfile $ACTUALDIR/$blkfile
ln -s $ACTUALDIR/$blkfile $RAMDISK/$blkfile
done
sleep 10m
done
How did you run the -reindex?
I never heard someone use mergefs for Bitcoin node but it looks like you are trying to combine two hard drives?
Bitcoin core might be confused on reading the drive. If I were you better not to use mergerfs instead use the 2nd drive or external drive as a Bitcoin directory for downloaded blocks and point the Bitcoin core manually on that drive(path).
I Just run ./bitcoind -reindexI never heard someone use mergefs for Bitcoin node but it looks like you are trying to combine two hard drives?
Bitcoin core might be confused on reading the drive. If I were you better not to use mergerfs instead use the 2nd drive or external drive as a Bitcoin directory for downloaded blocks and point the Bitcoin core manually on that drive(path).
Yes
I choose mergerfs because it is easy to replace and add drives without effort or losing data.
There is some other alternatives to easy combine drives?
Operating System: Linux casa2 5.10.0-20-amd64 #1 SMP Debian 5.10.158-2 (2022-12-13) x86_64 GNU/Linux
I'm not aware of any Linux distro called casa? By any chance, do you own computer created by https://keys.casa/ (which no longer receive update since 2-3 years ago)?
Started syncing from scratch, have downloaded around 20GB and occurred a irrecoverable error, because -reindex did not worked:
2023-04-05T14:35:47Z Fatal LevelDB error: IO error: /home/bob/bitcoin-core/.bitcoin/blocks/index/000005.ldb: No such device
I does not have physical access to this computer now.
2023-04-05T14:35:47Z Fatal LevelDB error: IO error: /home/bob/bitcoin-core/.bitcoin/blocks/index/000005.ldb: No such device
I does not have physical access to this computer now.
After you saw this error, did you check whether you can access /home and perform file read/write?
Someone uses mergerfs or know if the mount options are ok?
This isn't related with Bitcoin Core, so i expect you have better luck if you ask this question on mergerfs issue page or it's discord community.
Thank you all for the answers!
Bitcoin Client Software and Version Number: Bitcoin Core version v24.0.0 (release build)
Operating System: Linux casa2 5.10.0-20-amd64 #1 SMP Debian 5.10.158-2 (2022-12-13) x86_64 GNU/Linux
System Hardware Specs: 4GB RAM , 4 Cores Intel(R) Atom(TM) CPU D525 , 2 HDDs 500GB pooled with mergerfs: total of around 1 TB
Description of Problem:
I have some issues with this node. I think is a issue with mergerfs. I tested the system, filled all of the ~1 TB pool space with 100MB files and worked fine.
Started syncing from scratch, have downloaded around 20GB and occurred a irrecoverable error, because -reindex did not worked:
2023-04-05T14:35:47Z Fatal LevelDB error: IO error: /home/bob/bitcoin-core/.bitcoin/blocks/index/000005.ldb: No such device
I does not have physical access to this computer now.
Log Files from the Bitcoin Client: https://pastebin.com/Q4htt3Ue
Someone uses mergerfs or know if the mount options are ok?
Thank you!!
Operating System: Linux casa2 5.10.0-20-amd64 #1 SMP Debian 5.10.158-2 (2022-12-13) x86_64 GNU/Linux
System Hardware Specs: 4GB RAM , 4 Cores Intel(R) Atom(TM) CPU D525 , 2 HDDs 500GB pooled with mergerfs: total of around 1 TB
Description of Problem:
I have some issues with this node. I think is a issue with mergerfs. I tested the system, filled all of the ~1 TB pool space with 100MB files and worked fine.
Started syncing from scratch, have downloaded around 20GB and occurred a irrecoverable error, because -reindex did not worked:
2023-04-05T14:35:47Z Fatal LevelDB error: IO error: /home/bob/bitcoin-core/.bitcoin/blocks/index/000005.ldb: No such device
I does not have physical access to this computer now.
Code:
$ ls blocks/index
000003.log 000004.log CURRENT LOCK MANIFEST-000002
000003.log 000004.log CURRENT LOCK MANIFEST-000002
Code:
root@casa2:~# cat /etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda5 during installation
UUID=85701e6a-0a36-4295-8f57-41bb44eb53bc / ext4 noatime,nodiratime,errors=remount-ro 0 1
# /boot was on /dev/sda1 during installation
UUID=819cb633-8fa4-4384-843e-486d7ce3c53c /boot ext4 defaults 0 2
# /home was on /dev/sda6 during installation
# partition with system
UUID=4551582e-57a9-4a4c-9a95-4b5e3d1df2d6 /mnt/hdd1 ext4 noatime,nodiratime 0 0
# 2nd partition, mount /dev/sdb1 /mnt/hdd2
UUID=661363b3-eec9-4cf6-a1a0-0ee06df52604 /mnt/hdd2 ext4 noatime,nodiratime 0 0
# mergint the two mount points into home
/mnt/hdd1:/mnt/hdd2 /home fuse.mergerfs fsname=mergerFS,use_ino,cache.files=off,dropcacheonclose=true,allow_other,category.create=mfs
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda5 during installation
UUID=85701e6a-0a36-4295-8f57-41bb44eb53bc / ext4 noatime,nodiratime,errors=remount-ro 0 1
# /boot was on /dev/sda1 during installation
UUID=819cb633-8fa4-4384-843e-486d7ce3c53c /boot ext4 defaults 0 2
# /home was on /dev/sda6 during installation
# partition with system
UUID=4551582e-57a9-4a4c-9a95-4b5e3d1df2d6 /mnt/hdd1 ext4 noatime,nodiratime 0 0
# 2nd partition, mount /dev/sdb1 /mnt/hdd2
UUID=661363b3-eec9-4cf6-a1a0-0ee06df52604 /mnt/hdd2 ext4 noatime,nodiratime 0 0
# mergint the two mount points into home
/mnt/hdd1:/mnt/hdd2 /home fuse.mergerfs fsname=mergerFS,use_ino,cache.files=off,dropcacheonclose=true,allow_other,category.create=mfs
Log Files from the Bitcoin Client: https://pastebin.com/Q4htt3Ue
Someone uses mergerfs or know if the mount options are ok?
Thank you!!
Re: [ABERTO] Sorteio de entrada gratuita! [0,0008 BTC ~ R$ 100,00]
Já faz 1 semana que o sorteio acabou e ainda não obtive uma resposta do @lcharles123, o vencedor. Mandei uma DM e vou dar mais uns 4 dias para ver se ele aparece por aqui, caso contrário vou escolher outro bloco para sortear o prêmio.
Opa, cheguei, foi mal, eu estava sem computador Desculpa galera, por ter ganhando o bolão da copa e este também
Pode enviar pra este endereço, por favor.
1CvjihU9gsRkQUYvemHQy5JKj7fs3Hb3mZ
O curioso é que eu escolhi números seguindo uma lógica: eu tinha pensado em 1, 3, 7, f porque eles possuem 1's no final em sua forma binária, 1, 11, 111, 1111.
Foi só um palpite aleatório mesmo, acabou dando certo.
Re: [ABERTO] Sorteio de entrada gratuita! [0,0008 BTC ~ R$ 100,00]
Eu sou sumido do fórum, mas acontece que nao tenho tempo de acompanhar todas as discussões do pessoal daqui, que sempre traz assuntos relevantes, melhor que as noticias do coinmarketcap 
O que significa que você também pode pegar mais um ticket logo de cara. Fique à vontade. Re: [ABERTO] Sorteio de entrada gratuita! [0,0008 BTC ~ R$ 100,00]
Vou ficar com o 7
Eu sou sumido do fórum, mas acontece que nao tenho tempo de acompanhar todas as discussões do pessoal daqui, que sempre traz assuntos relevantes, melhor que as noticias do coinmarketcap
Eu sou sumido do fórum, mas acontece que nao tenho tempo de acompanhar todas as discussões do pessoal daqui, que sempre traz assuntos relevantes, melhor que as noticias do coinmarketcap
Re: LastPass foi hackedo (de novo) ,passwords, cartões de crédito e dados pessoais
⭐ Merited by bitmover (1)
Eu uso o gerenciador de senhas do Firefox, absolutamente todas as minhas senhas foram geradas aleatoriamente por este navegador. Ele gera sequencias de 15 caracteres entre letras maiusculas, minusculas e numeros. Imagino que quem use gerenciador de senhas deve sempre usar senhas aleatorias, afinal precisa de memorizar apenas uma senha. A senha mestra tambem deve ser aleatoria e forte. Seria interessante que estes gerenciadores obriguem o uso de uma senha mestra adequada, forçando o usuario a anota-la
Re: ⚽ Torneio / Bolão para a Copa do Mundo 2022 ⚽ ATUALIZAÇÃO OITAVAS DE FINAL
Valeu pessoal!
Pode enviar para este por favor
1CvjihU9gsRkQUYvemHQy5JKj7fs3Hb3mZ
Eu reparei que tinha muita gente torcendo para a Argentina aqui em BH, nao assisti a partida mas nao precisou porque a vibraçao do pessoal já indicava a direção do jogo.
Bom ver o brasileiro deixar a rivalidade de lado e dar uma força para o vizinho.
Pode enviar para este por favor
1CvjihU9gsRkQUYvemHQy5JKj7fs3Hb3mZ
Eu reparei que tinha muita gente torcendo para a Argentina aqui em BH, nao assisti a partida mas nao precisou porque a vibraçao do pessoal já indicava a direção do jogo.
Bom ver o brasileiro deixar a rivalidade de lado e dar uma força para o vizinho.
Re: ⚽ Torneio / Bolão para a Copa do Mundo 2022 ⚽ ATUALIZAÇÃO OITAVAS DE FINAL
1º - lcharles123 --> 13 pontos
Todos users ainda com chances matemáticas de serem o 1º colocado
Todos users ainda com chances matemáticas de serem o 1º colocado
Mas, eu dou já os parabéns ao lcharles123, arriscou e correu bem. Se calhar não arriscou!
Eu faço já os meus palpites, que isto não tem muito a dizer:
Croácia x Marrocos = Marrocos (acho que eles até estão a jogar muito bem, depois do que fizeram contra França em boa parte do jogo)
Argentina x França = Argentina
Obrigado
Eu vou copiar os seus palpites para os proximos jogos.
Eu gostaria que o Marrocos levasse o primeiro titulo para o continente Africano, mas nao foi desta vez.
Porem ainda podem ficar em terceiro lugar, que eh uma posiçao de destaque.
Re: ⚽ Torneio / Bolão para a Copa do Mundo 2022 ⚽ ATUALIZAÇÃO OITAVAS DE FINAL
Foi exatamente o que eu pensei depois da eliminação do Brasil. 
Se o Brasil não pode ganhar, que ganhe uma "zebra" como Marrocos, que ninguém espera ganhar. Melhor do que uma Argentina ou França da vida.
Se o Brasil não pode ganhar, que ganhe uma "zebra" como Marrocos, que ninguém espera ganhar. Melhor do que uma Argentina ou França da vida.
Que seja Marrocos então hahaha
Ruim agora é esperar 4 anos para ter essa festa novamente, o Brasil é mal acostumado com copa, achamos que temos que ganhar todas
Classificação atualizada dia 10/12 após as quartas de final
1º - lcharles123 --> 12 pontos
2º - rdluffy --> 10 pontos
2º - tg88 --> 10 pontos
3º - Joker --> 8 pontos
3º - bitmover --> 8 pontos
3º - TryNinja --> 8 pontos
lcharles123 incrivelmente acertou todos os jogos das quartas de final, Croácia e Marrocos, estou achando que ele tem informações de dentro da Fifa, exigimos explicações
Foi sorte, kkk, ainda mais que as duas foram para disputa de penalti, que traz mais imprevistos ainda.
Pra proxima rodada eu manteho uma posiçao e mudo outra:
Sexta-feira 13/12 - 16h - Croácia vs Argentina --> Argentina
Sábado 14/12 - 16h - Marrocos vs França --> Marrocos
Re: ⚽ Torneio / Bolão para a Copa do Mundo 2022 ⚽ ATUALIZAÇÃO OITAVAS DE FINAL
Sexta-feira 09/12 - 12h - Croácia vs Brasil --> Croácia
- Trust negativo enviado- Reportado à Policia Federal e à ABIN
- Printado e enviado para seus familiares e amigos + cancelado em todas as redes sociais
Pode deixar que já vou tirar uns 5 pontos dele
Aliás descobri que o lcharles123 na verdade é Luka Charlesić 123
Hahahahaha
Esqueces-te de mencionar, de informar a todos os gestores de campanha aqui do forum, para que nunca seja aceite em nenhuma campanha!
Hahaha
Boa jokerHaha! O Cancelamento chegou aqui no fórum? Tempos sombrios estes
Re: ⚽ Torneio / Bolão para a Copa do Mundo 2022 ⚽ ATUALIZAÇÃO OITAVAS DE FINAL
⭐ Merited by sabotag3x (1)
Estes sao os meus palpites para a próxima rodada 
Sexta-feira 09/12 - 12h - Croácia vs Brasil --> Croácia
Sexta-feira 09/12 - 16h - Holanda vs Argentina --> Argentina
Sábado 10/12 - 12h - Marrocos vs Portugal --> Marrocos
Sábado 10/12 - 16h - Inglaterra vs França --> França
Sexta-feira 09/12 - 12h - Croácia vs Brasil --> Croácia
Sexta-feira 09/12 - 16h - Holanda vs Argentina --> Argentina
Sábado 10/12 - 12h - Marrocos vs Portugal --> Marrocos
Sábado 10/12 - 16h - Inglaterra vs França --> França
Re: ⚽ Torneio / Bolão para a Copa do Mundo 2022 ⚽ ATUALIZAÇÃO OITAVAS DE FINAL
Ja estava esquecendo dos palpites, kkk
03/12 às 12h - Holanda x Estados Unidos -> Classificado para próxima fase: Holanda
03/12 às 16h - Argentina x Austrália -> Classificado para próxima fase: Argentina
04/12 às 12h - França x Polônia -> Classificado para próxima fase: Polonia
04/12 às 16h - Inglaterra x Senegal -> Classificado para próxima fase: Inglaterra
05/12 às 12h - Japão x Croácia -> Classificado para próxima fase: Japao
05/12 às 16h - Brasil x Coreia do Sul -> Classificado para próxima fase: Brasil
06/12 às 12h - Marrocos x Espanha -> Classificado para próxima fase: Espanha
06/12 às 16h - Portugal x Suiça -> Classificado para próxima fase: Portugal
03/12 às 12h - Holanda x Estados Unidos -> Classificado para próxima fase: Holanda
03/12 às 16h - Argentina x Austrália -> Classificado para próxima fase: Argentina
04/12 às 12h - França x Polônia -> Classificado para próxima fase: Polonia
04/12 às 16h - Inglaterra x Senegal -> Classificado para próxima fase: Inglaterra
05/12 às 12h - Japão x Croácia -> Classificado para próxima fase: Japao
05/12 às 16h - Brasil x Coreia do Sul -> Classificado para próxima fase: Brasil
06/12 às 12h - Marrocos x Espanha -> Classificado para próxima fase: Espanha
06/12 às 16h - Portugal x Suiça -> Classificado para próxima fase: Portugal
Re: ⚽ Torneio / Bolão para a Copa do Mundo 2022 ⚽ últimas horas, participem!
⭐ Merited by bitmover (4)
Pergunta: alguém sabe um código / script pra eu colocar aqui no meu primeiro post para aparecer o saldo em tempo real dos BTC que serão depositados?
Eu sei, mas parece que não está funcionando... Hey @TryNinja
No sorteio oficial do whitepapper eu utilizei essas urls, mas verifiquei agora que os links estão quebrados:
Code:
[img]https://btc.ninjastic.space/balance/bc1qd2dlejjp09up4xq4aulehjrkmxspqq67ekafczt7q3femwwyamas27dc6m/f00000[/img]
Code:
[img]https://btc.ninjastic.space/price/bc1qd2dlejjp09up4xq4aulehjrkmxspqq67ekafczt7q3femwwyamas27dc6m[/img]
Resultado:
Não sei se o serviço foi desabilitado ou se o TryNinja só fez alguma mudança no endereço, daqui a pouco ele nos atualiza.
Tinha um outro que eu utilizava anteriormente também, porém não encontrei mais, qualquer coisa lhes atualiza por aqui se der tempo.
Eu fiz uma imagem que pode ser acessada neste link
Code:
http://serv.hopto.org/image.png
Esta feia mais funciona, ela eh gerada a partir de um texto usando o comando convert do pacote imagimagick do linux, se alguem souber como colocar cor no fundo igual do forum me diga por favor.
