Rafał Kiełbus
Rafał Kiełbus
That's the ``` return: '0x50e7caa7' ``` part of error message
I do realize, that activating SW under 95% is risky. Maybe when this code roll it get so much support, that reaching this limit will be possible.
You can use addnode `namecoin-cli addnode testnet.node.ip.address add` ``` testnet.namecoin.org 31.45.121.24 45.33.65.68 51.68.251.200 ``` Last one is mine :) I`m not aware about dns-seeder for namecoin, it would be best...
@domob1812 you probably need point some peers that seeder can start with, we also need add it (seeder) to code.
@domob1812 sorry, I was sure that this testnet seed is yours :)
Testnet nodes currently connected to me: ``` 139.180.143.165 45.33.65.68 94.23.252.190 31.45.104.147 51.75.22.122 47.244.156.37 23.129.64.160 47.244.58.44 51.68.251.200 ``` (last is mine) ``` namecoin-cli --testnet getblockchaininfo { "chain": "test", "blocks": 230297, "headers":...
Agree. It would be nice to translate easily.
> Would a power user such as yourself be ok with loss of atomicity if the old scheme were resurrected as an opt-in option? **Yes, definitely.** My ZFS setup with...
To answer your question: I am **already running Fulcrum v2** (specifically, building frequently from the git master branch). The issue with filling up the SSD became apparent after migrating. Since...
* **`cf_paths` Solution:** Yes, **one directory per CF fully solves** the ZFS `special_small_blocks` issue. It allows assigning different ZFS datasets and properties (like disabling `special_small_blocks` for `shist`). * **RocksDB `block_size`:**...