Topic: [ANN] Mini-Bitcoin (MBTC) - Bitcoin made simple (Read 631 times)

Yeah no problem I will create a better view soon

Good Work Mate can we make UTXO page more readable for example in a table like excel or list one by one sometimes hard to sort what is what. Cheers

Hello everybody

i just update the address. Now it is like A1B2, just 4 characters.

very easy to remember 

English / Portuguese

WhatsApp https://chat.whatsapp.com/DVjTNFvuC6a81Q3vT4P1ay
Discord     https://discord.gg/bhN5kxd
Facebook  https://www.facebook.com/1mbtc/
Twitter      https://twitter.com/1mbtc

Again we have issues it went from block 1400+ to 5000 in minutes. It is mining like crazy.
I stopped all new coins gone.
Some new issue seems.

WhatsApp group https://chat.whatsapp.com/DVjTNFvuC6a81Q3vT4P1ay

Seems all fixed now.
Chain moving now.

here discord:

https://discord.gg/bhN5kxd

Lets use WhatsApp group https://chat.whatsapp.com/DVjTNFvuC6a81Q3vT4P1ay

Can I mine with few instances on same address because when I try to copy keys and one of inner found a block other start saying we already found that block

Also will be nice if you can add browser to localhost:8080 where you can check other address balance

seems it back to norm now i see all works fine

someone should create it then we can speak with dev in real time

Do we have a discord? Better to have one 😃

I see data folder on git hub is making auto update each 10 seconds

I also get similar logs now.
Is this some problem?
Can you please fix the block time, I guess this is the major bug now.
I have being mining from day 1. You are doing a great job and working good on the fixes.

Edit - I got block #1253 so seems it is working. I got a block after 2 days. Blocks are really slow. 10-15 blocks a day.

I now see that we have some problem :
WARN: NOT sending this request
2020-08-23 13:22:49: NET: READ a BLOCK /172.17.0.2:33908 -> /64.227.25.70:10762
2020-08-23 13:22:49: WARN: Unknown 'last block' of this Block. Asking for block.
2020-08-23 13:22:49: INFO: WRITE syncMessage /172.17.0.2:33908 -> /64.227.25.70:10762
2020-08-23 13:22:51: NET: READ a BLOCK /172.17.0.2:33908 -> /64.227.25.70:10762
2020-08-23 13:22:51: WARN: Unknown 'last block' of this Block. Asking for block.
2020-08-23 13:22:51: INFO: WRITE syncMessage /172.17.0.2:33908 -> /64.227.25.70:10762
2020-08-23 13:22:52: Ask for block after this: 14347931893555168202540026671506743116786081000773794401609867221736
2020-08-23 13:23:25: Ask for block after this: 14347931893555168202540026671506743116786081000773794401609867221736

and after that :
N: read IGNORING /172.17.0.2:33908 -> /64.227.25.70:10762
2020-08-23 13:24:38: WARN: read IGNORING /172.17.0.2:33908 -> /64.227.25.70:10762
2020-08-23 13:24:39: WARN: read IGNORING /172.17.0.2:33908 -> /64.227.25.70:10762
2020-08-23 13:24:39: WARN: read IGNORING /172.17.0.2:33908 -> /64.227.25.70:10762
2020-08-23 13:24:39: WARN: read IGNORING /172.17.0.2:33908 -> /64.227.25.70:10762
2020-08-23 13:24:39: WARN: read IGNORING /172.17.0.2:33908 -> /64.227.25.70:10762
2020-08-23 13:24:40: WARN: read IGNORING /172.17.0.2:33908 -> /64.227.25.70:10762
2020-08-23 13:24:40: WARN: read IGNORING /172.17.0.2:33908 -> /64.227.25.70:10762
2020-08-23 13:24:40: Ask for block after this: 14347931893555168202540026671506743116786081000773794401609867221736
2020-08-23 13:24:40: WARN: write IGNORING /172.17.0.2:33908 -> /64.227.25.70:10762
2020-08-23 13:24:40: WARN: read IGNORING /172.17.0.2:33908 -> /64.227.25.70:10762
2020-08-23 13:24:40: WARN: read IGNORING /172.17.0.2:33908 -> /64.227.25.70:10762
2020-08-23 13:24:41: WARN: read IGNORING /172.17.0.2:33908 -> /64.227.25.70:10762
2020-08-23 13:24:41: WARN: read IGNORING /172.17.0.2:33908 -> /64.227.25.70:10762
2020-08-23 13:24:41: WARN: read IGNORING /172.17.0.2:33908 -> /64.227.25.70:10762
2020-08-23 13:24:41: WARN: read IGNORING /172.17.0.2:33908 -> /64.227.25.70:10762
2020-08-23 13:24:42: WARN: read IGNORING /172.17.0.2:33908 -> /64.227.25.70:10762
2020-08-23 13:24:42: WARN: read IGNORING /172.17.0.2:33908 -> /64.227.25.70:10762
2020-08-23 13:24:42: WARN: read IGNORING /172.17.0.2:33908 -> /64.227.25.70:10762
2020-08-23 13:24:42: WARN: read IGNORING /172.17.0.2:33908 -> /64.227.25.70:10762
2020-08-23 13:24:43: WARN: read IGNORING /172.17.0.2:33908 -> /64.227.25.70:10762
2020-08-23 13:24:43: WARN: read IGNORING /172.17.0.2:33908 -> /64.227.25.70:10762

Hi thanks for reply are You planning any Windows Gui wallet, it will bring more interest. Also I think You should add feature start mining and stop mining. But to be honest already found a block it is a norm that diff goes up and down

Hi a two days ago I made a big change in code. Now it’s working clear address (if you have no balance, your address became available to others get) and Fusion transactions (miners can join your money for you, decreasing utxo  size). I also create a snapshot (After validate the blocks, you don’t need revalidate  every time you run).

I also made a mistake in block validation, so the chain stuck. Now it’s working but still very slow block generation. I don’t know if has something wrong In diff calculation.

All your data is inside mini-bitcoin/data folder. You need to backup the keypair (Like Wallet) folder.

Thanks

or no one is mining and diff is high, well I will mine a day and see do I pass that block