Search content
Sort by
Showing 13 of 13 results by merc1er
I have not "stolen" anything. This guy gave me $1000 (harassing me on Telegram and calling me at night to get my BTC address) to look at his crappy code, which I did. He replied things that made absolutely no sense when asked about his code, which is probably not fixable at this point...
If anyone has issues with bitcash, open an issue at https://github.com/pybitcash/bitcash
For the record, I sent this guy $1,000 worth of BTC: https://blockchair.com/bitcoin/transaction/90441b99bb0646750a61ffb119a4823db72941c2578d6ae23a7a270f17e1a62a
If anyone has issues with bitcash, open an issue at https://github.com/pybitcash/bitcash
For the record, I sent this guy $1,000 worth of BTC: https://blockchair.com/bitcoin/transaction/90441b99bb0646750a61ffb119a4823db72941c2578d6ae23a7a270f17e1a62a
You can also find brick and mortars that take Bitcoin Cash here: https://marcocoino.bitcoin.com
Re: Bitcoind stops while syncing - "Failed to open mempool file from disk"
It's very slow IMO, but i guess it's better than can't sync properly.
Depending on percentage free RAM, you could increase dbcache or/and maxsigcachesize number slightly (between 5-25%) if you want faster sync and prepare to take risks. If you have PC/notebook, you could sync from it and on Pi you just need to wait for block verification.
Depending on percentage free RAM, you could increase dbcache or/and maxsigcachesize number slightly (between 5-25%) if you want faster sync and prepare to take risks. If you have PC/notebook, you could sync from it and on Pi you just need to wait for block verification.
Indeed, 17% after 2 days. I increased -dbcache by 25% but RAM went over 95%.
I will be playing with the arguments to reach a faster stable syncing.
Re: Bitcoind stops while syncing - "Failed to open mempool file from disk"
⭐ Merited by Jet Cash (2)
Okay so I am giving it another try with the following parameters:
I tried with -dbcache set to 50 but the verification progress (syncing) was way too slow!
It seems to be syncing a bit slower than before with the current parameters but let's hope it keeps the RAM usage below 80%.
Code:
bitcoind -daemon -maxmempool=100 -dbcache=200 -maxsigcachesize=4
I tried with -dbcache set to 50 but the verification progress (syncing) was way too slow!
It seems to be syncing a bit slower than before with the current parameters but let's hope it keeps the RAM usage below 80%.
Re: Bitcoind stops while syncing - "Failed to open mempool file from disk"
Since v0.6, C-Lightning does support running on top of pruned nodes, and the doc I provided is not only for pruned nodes (for instance just lower the `dbcache` would reduce the RAM usage).
Oh thats interesting! I will look into it, thank you.
Re: Bitcoind stops while syncing - "Failed to open mempool file from disk"
You might want to take a look to https://bitcoin.org/en/full-node#reduce-storage (there are options to reduce traffic too).
I do need to run an unpruned node as my goal is to run a lightning node
Re: Bitcoind stops while syncing - "Failed to open mempool file from disk"
It stopped with the following at the end of `debug.log`:
---
2019-02-10T15:18:11Z UpdateTip: new best=00000000000000249597632a2fe08578cd1d2c0f620342ca91c3611786fe464f height=232591 version=0x00000002 log2_work=69.838772 tx=16550595 date='2013-04-22T14:31:02Z' progress=0.044502 cache=597.4MiB(5216340txo)
2019-02-10T15:18:12Z Error: Out of memory. Terminating.
---
I rebooted the raspi and it went straight to recovery mode... I will start from scratch again and do the hardware checks mentioned above.
---
2019-02-10T15:18:11Z UpdateTip: new best=00000000000000249597632a2fe08578cd1d2c0f620342ca91c3611786fe464f height=232591 version=0x00000002 log2_work=69.838772 tx=16550595 date='2013-04-22T14:31:02Z' progress=0.044502 cache=597.4MiB(5216340txo)
2019-02-10T15:18:12Z Error: Out of memory. Terminating.
---
I rebooted the raspi and it went straight to recovery mode... I will start from scratch again and do the hardware checks mentioned above.
Re: Bitcoind stops while syncing - "Failed to open mempool file from disk"
delete the blocks and chainstate folders and restart bitcoind.
It restarted from the first block already, but i'm trying this one more time.
@darosior I changed ownership to `pi` and chmod-ed the hard drive mount. Does bitcoind use a specific user that I need to change to?
Also, note that I didn't specify a path to save the block chain to bitcoind - instead, the folder .bitcoin links to my drive.
Bitcoind stops while syncing - "Failed to open mempool file from disk"
⭐ Merited by LoyceV (1)
I installed Bitcoin Core on a Raspberry Pi and tried to sync the block chain using bitcoind.
The data is written on an external hard drive (1TB) mounted on the machine.
After I run the `bitcoind -daemon` command, the block chain starts syncing, but after a few hours it stops.
This is what I have at the end of the debug.log file:
----
2019-02-10T05:41:04Z UpdateTip: new best=00000000727339b1f121c82ad73e522d8e83d7ed4b1b3473aa10f26029f2b046 height=12774 version=0x00000001 log2_work=45.641058 tx=12882 date='2009-04-30T12:58:37Z' progress=0.000035 cache=2.4MiB(12863txo)
2019-02-10T05:41:04Z Failed to open mempool file from disk. Continuing anyway.
2019-02-10T05:41:04Z tor: Thread interrupt
2019-02-10T05:41:04Z Shutdown: In progress...
2019-02-10T05:41:04Z addcon thread exit
2019-02-10T05:41:04Z opencon thread exit
2019-02-10T05:41:04Z torcontrol thread exit
2019-02-10T05:41:04Z net thread exit
2019-02-10T05:41:04Z msghand thread exit
2019-02-10T05:41:04Z scheduler thread interrupt
2019-02-10T05:41:06Z [default wallet] Releasing wallet
2019-02-10T05:41:06Z Shutdown: done
----
Does anyone have an idea? Thank you!
The data is written on an external hard drive (1TB) mounted on the machine.
After I run the `bitcoind -daemon` command, the block chain starts syncing, but after a few hours it stops.
This is what I have at the end of the debug.log file:
----
2019-02-10T05:41:04Z UpdateTip: new best=00000000727339b1f121c82ad73e522d8e83d7ed4b1b3473aa10f26029f2b046 height=12774 version=0x00000001 log2_work=45.641058 tx=12882 date='2009-04-30T12:58:37Z' progress=0.000035 cache=2.4MiB(12863txo)
2019-02-10T05:41:04Z Failed to open mempool file from disk. Continuing anyway.
2019-02-10T05:41:04Z tor: Thread interrupt
2019-02-10T05:41:04Z Shutdown: In progress...
2019-02-10T05:41:04Z addcon thread exit
2019-02-10T05:41:04Z opencon thread exit
2019-02-10T05:41:04Z torcontrol thread exit
2019-02-10T05:41:04Z net thread exit
2019-02-10T05:41:04Z msghand thread exit
2019-02-10T05:41:04Z scheduler thread interrupt
2019-02-10T05:41:06Z [default wallet] Releasing wallet
2019-02-10T05:41:06Z Shutdown: done
----
Does anyone have an idea? Thank you!
My PGP key:
https://mercier.link/pgp
https://mercier.link/pgp
Code:
-----BEGIN PGP PUBLIC KEY BLOCK-----
mQENBFqtOkcBCADT2ByBGE/E+wsmSyHLWT1nkyF1eYoCTvRuWQSWjKBaCJdTrmxG
KnIQRGLaM4iUaBMrErEqVdbhPlTsD8sv1YR9OUhwJa7CS3XSDXrAdP+mysd4BUrj
oCT7hS/iMrTgZIgPPRX0/PMrNmgVhALWTgYikRFcwZNXvIaXObzbCk4VXvxuaOsN
uUhR4KTyb9BNPrHZ19jIeI0OVdNpH0kmpT7zxf0QnheOVvHE4wq22dVzNiXh+Siy
Bq2XPlV4LH8H+ff6kgqAleLAViOpO0ZbUUG9udmcZEVGud/RHSCtfx4tOBKupMkZ
IprqSSawt+zX1PhjDjwbYDxGESer6QcyAkhlABEBAAG0KENvcmVudGluIE1FUkNJ
RVIgPGNvcmVudGluQG1lcmNpZXIubGluaz6JAVQEEwEIAD4WIQTx5X+BEzfkOnYR
U9c52kR+zVg8/QUCWq06RwIbAwUJA8JnAAULCQgHAgYVCgkICwIEFgIDAQIeAQIX
gAAKCRA52kR+zVg8/bdSB/9WAO1Aqr1Rm9Um1UbESJPYptSWDTxXyr014xX6NcE8
mvovSBVntiXWjuB7e7utI7cV7QQ3MZMnGoXVrtYpTIb0qklzB/kikZ+eoOREMKI9
fL5ipZut+deaRLbQl5UYLa9wHuGwKpY6cilByGtCzFltMutrJFZ9YEdKV4Q0A/8a
cPlLCeqWj9g0tTZ0KdToivDPtWsYS6irs5beTOAegaFa0oNZSludwu4ZcQaq1dbM
+OzddCRFFyHSotcOUFgR2+jzmViJYUvXjUcQvmsKBKMS08ExLzo/Qbj5YjmJFMS8
CDw6zVAweC5+nT3oEuQV0VWYqoHO1nhlTsrsL0bCMH0kuQENBFqtOkcBCADRIcza
VKZy+cMWx+75btZ/5Fl3FtVwGmCkWUgHj1+tV0XaNLITjQwJyRO6G7ZIUbXE+dNf
ZCh/p9E2zAYo+7PnAlU4/vCC3iDVxN/47dQFSMt2s7zWxe+ZsRR1xHnu1y4uTtJP
6wgP5pw1Zjnpg7yvJdM/G1V8Ac37oxVO8gnuxWf+lQ+1gTk8P5BeK8IGX4MN46Jd
XocXX8BL5sP53nm0e0sZDjm3KYU4tDg0VSO4vDJW5OQq2+lRAR8slB1lFf2nViW/
8ny44ddcyUDPpj9gELEdvZzpCnR6Y3W+p2fSC2vLpoqAzgmqvWSSaEzt4W6BeTzF
H+NpRXqlnR0eUCQNABEBAAGJATwEGAEIACYWIQTx5X+BEzfkOnYRU9c52kR+zVg8
/QUCWq06RwIbDAUJA8JnAAAKCRA52kR+zVg8/dgxB/4zx2p1Bb7xnxtawNnrwect
0E0m8MYG1HVK5ZlVPNcozdEXUK3tz4ST2oxx3MxHKh24+PUhtDH5DoUjtE8YkpY4
xdv776/ps4dMeQWfK4e11ok1jLP8LhHEU57ABUCJxIzI85w2iaqxGge3169+u3TR
IQ71gg901uyL7cJpOzy9WZF3P9Ual2/LJHHlZxZCj8UMb17orG3a7Ddl62v3WZu5
6pw6V4P76XvzfTJ200lDI/ZmxIyzD5vtofKQN9yMmacK4BVM1oA1SQxnSq0HRCgb
cU7U67pnkjZfFyiwKjaoIFd4lK+ouSLVpVSlbXyyXr3SWMqZY8h4UqDQanw+InpI
=LMGP
-----END PGP PUBLIC KEY BLOCK-----
mQENBFqtOkcBCADT2ByBGE/E+wsmSyHLWT1nkyF1eYoCTvRuWQSWjKBaCJdTrmxG
KnIQRGLaM4iUaBMrErEqVdbhPlTsD8sv1YR9OUhwJa7CS3XSDXrAdP+mysd4BUrj
oCT7hS/iMrTgZIgPPRX0/PMrNmgVhALWTgYikRFcwZNXvIaXObzbCk4VXvxuaOsN
uUhR4KTyb9BNPrHZ19jIeI0OVdNpH0kmpT7zxf0QnheOVvHE4wq22dVzNiXh+Siy
Bq2XPlV4LH8H+ff6kgqAleLAViOpO0ZbUUG9udmcZEVGud/RHSCtfx4tOBKupMkZ
IprqSSawt+zX1PhjDjwbYDxGESer6QcyAkhlABEBAAG0KENvcmVudGluIE1FUkNJ
RVIgPGNvcmVudGluQG1lcmNpZXIubGluaz6JAVQEEwEIAD4WIQTx5X+BEzfkOnYR
U9c52kR+zVg8/QUCWq06RwIbAwUJA8JnAAULCQgHAgYVCgkICwIEFgIDAQIeAQIX
gAAKCRA52kR+zVg8/bdSB/9WAO1Aqr1Rm9Um1UbESJPYptSWDTxXyr014xX6NcE8
mvovSBVntiXWjuB7e7utI7cV7QQ3MZMnGoXVrtYpTIb0qklzB/kikZ+eoOREMKI9
fL5ipZut+deaRLbQl5UYLa9wHuGwKpY6cilByGtCzFltMutrJFZ9YEdKV4Q0A/8a
cPlLCeqWj9g0tTZ0KdToivDPtWsYS6irs5beTOAegaFa0oNZSludwu4ZcQaq1dbM
+OzddCRFFyHSotcOUFgR2+jzmViJYUvXjUcQvmsKBKMS08ExLzo/Qbj5YjmJFMS8
CDw6zVAweC5+nT3oEuQV0VWYqoHO1nhlTsrsL0bCMH0kuQENBFqtOkcBCADRIcza
VKZy+cMWx+75btZ/5Fl3FtVwGmCkWUgHj1+tV0XaNLITjQwJyRO6G7ZIUbXE+dNf
ZCh/p9E2zAYo+7PnAlU4/vCC3iDVxN/47dQFSMt2s7zWxe+ZsRR1xHnu1y4uTtJP
6wgP5pw1Zjnpg7yvJdM/G1V8Ac37oxVO8gnuxWf+lQ+1gTk8P5BeK8IGX4MN46Jd
XocXX8BL5sP53nm0e0sZDjm3KYU4tDg0VSO4vDJW5OQq2+lRAR8slB1lFf2nViW/
8ny44ddcyUDPpj9gELEdvZzpCnR6Y3W+p2fSC2vLpoqAzgmqvWSSaEzt4W6BeTzF
H+NpRXqlnR0eUCQNABEBAAGJATwEGAEIACYWIQTx5X+BEzfkOnYRU9c52kR+zVg8
/QUCWq06RwIbDAUJA8JnAAAKCRA52kR+zVg8/dgxB/4zx2p1Bb7xnxtawNnrwect
0E0m8MYG1HVK5ZlVPNcozdEXUK3tz4ST2oxx3MxHKh24+PUhtDH5DoUjtE8YkpY4
xdv776/ps4dMeQWfK4e11ok1jLP8LhHEU57ABUCJxIzI85w2iaqxGge3169+u3TR
IQ71gg901uyL7cJpOzy9WZF3P9Ual2/LJHHlZxZCj8UMb17orG3a7Ddl62v3WZu5
6pw6V4P76XvzfTJ200lDI/ZmxIyzD5vtofKQN9yMmacK4BVM1oA1SQxnSq0HRCgb
cU7U67pnkjZfFyiwKjaoIFd4lK+ouSLVpVSlbXyyXr3SWMqZY8h4UqDQanw+InpI
=LMGP
-----END PGP PUBLIC KEY BLOCK-----
PGP key without BTC address? look at here
Oh right, moving post right now.