Anyone?

I'll be happy to guide through the process.

Will make extremely good use of the 2.5 years old "net/bitcoin" OpenBSD-WIP port.

(Alternatively possibly I could try to do it myself and then document where things seriously break here, and ask for your followup. Maybe that followup basically would require you to go through my instructions anyhow though so might be same ..)



Pascal:

BitcoinD is the reference quality Bitcoin network router software. The routing function is the central function in the network.

* Your suggestion that a BitcoinD port in OpenBSD would be a waste of time because its wallet functionality not works out of the box now, would be like saying that Unix machine is useless because it's not running X.

* Also, BitcoinD's installer warns of LibreSSL not be cause any issue has been found ever, but simply because LibreSSL is the only OpenSSL alternative that is not vanilla OpenSSL -

There is not one simple example of when BitcoinD has misbehaved when running with LibreSSL, and it will stop using OpenSSL in some version soon.

For this reason I think it's motivated for the OpenBSD port of BitcoinD to simply use LibreSSL for now. If it would break the routing function, someone would notice soon.

   Problem solved.



On 2015-12-16 19:05, poweru...@openmailbox.org wrote:
On 2015-12-16 19:04, poweru...@openmailbox.org wrote:
..
For this reason I suggest that OpenBSD is included into the ports tree!

Err - for this reason I suggest that *BitcoinD* is included into the ports tree.


That it's precompiled with "--disable-wallet" is all fine. If anyone
wants to fix that later it's fine. Now let's get the router working!



On 2015-12-16 18:50, Pascal Stumpf wrote:
I think this needs some serious work, at least an updated
databases/db/v4 and some solution to that ugly LibreSSL problem.

I'm not really using this in any way, so I won't spend that kind of
effort on it.

On Wed, 16 Dec 2015 18:26:04 +0800, poweru...@openmailbox.org wrote:
Guys,

What do you say, do you feel this is a relevant port?

Reply via email to