lets say I wanted my node to support bip148. What do I need to configure in order to allow this? I am currently running bitcoin core 0.14.2 am I just ammending a line of code into the config file? I just need a reference if possible or is it advised to just wait for a release from bitcoin core?. I do not know if this is the proper channel for this so I apologize in advance. Thank you very much for the help.
Bitcoin Core at this point does not support BIP148
There are forks of the codebase that do.
Understood my question was hypethical. My main concern is if I am running my node how can I test BIP148 suppost. I found a link that allows me to download bitcoin core with BIP148 support, but I did not know if this was trustworthy. Thank you
Hmm... isn't the whole wallet endpoint URI encoding really required if we only allow "CHARS_ALPHA_NUM + ".-_"" for wallet filenames?!
I guess it's not. Ping ryanofsky
jonasschnelli: i wondered about that as well. I tried (unsuccessfully) to get wallets containing sneaky characters to load, and it failed as expected (though sometimes with a segfault that needs to be fixed). I fail to see why it's necessary
jonasschnelli: i assumed it was for more robust usage in the future
cfields: yes. That makes sense.
jonasschnelli: well that theory is based on absolutely nothing :)
url encoding was suggested when there were still wallet ids. if you want to check for CHARS_ALPHA_NUM in bitcoin-cli instead of percent encoding, that seems fine, though a little more fragile (because maybe we will allow another class of characters in bitcoind and bitcoin-cli will break)
i'd rather leave it this way
wumpus: #10817 is not really a bug fix, but its ready for merge and adds a couple strings
perhaps you can help. communication is hard
jtimon: you to provide the outpoint with the address?
it seems I missunderstood this comment "The checksum should not contain any salted data. Otherwise with 30bits of non-cryptographic checksum one can easily calculate a TxID that is valid for more than one Network"
he means that since it's only 30 bits of checksum, with 2^15 tries you can create a collision that is valid for more than 1 network.