Bitcoin full node and query server

October 2023

Archive of the libbitcoin Slack #general channel.

Thursday, October 5, 2023

Topic: Dev Weekly Status Time: October 5, 2023 01:00pm Pacific Time (US and Canada) Join Zoom Meeting https://us05web.zoom.us/j/87666370902?pwd=bEZDUlJ0MGJ5V3dVMUhVdHl5QzdFdz09 Meeting ID: 876 6637 0902 Passcode: 85U0bF

evoskuil19:32

I’m out today unless there’s something pressing.

pmienk19:36

Nothing pressing, no. Catch you next week

✅ 1👍🏻 1

Saturday, October 7, 2023

John Doe20:49

Hi all, I've been studying Eric's writing for awhile now and I had some questions about Libbitcoin I was wondering if folks could answer. I have a surface level understanding of the project, but really like the goal of multiple implementations. Is it currently possible for Core and Libbitcoin to interoperate? Could there be a future where multiple implementations exist? Sorry if this has already been answered. I have a bit of apprehension about core, as it's an iteration of the original satoshi code (yikes!). The development process strikes me as rather confusing at times. Thanks a bunch

(edited)

Slackbot20:49

👻

pmienk20:56

Libbitcoin is meant to allow common communication between itself and any compliant bitcoin network protocol implementation.

👍 1

21:00

The network project provides an implementation necessary for developers to plug into the bitcoin network. The node project implements a bitcoin node using the network and additional blockchain persistence libraries. The server project extends the node with an additional protocol allowing for queries not capable or convenient in the bitcoin network itself.

John Doe21:01

Gotcha and the system project is an SDK of sorts?

pmienk21:02

A base layer for the other projects, yes. It provides many common datatypes and other useful utilities shared by the 9 other projects

👍 1

21:03

They are all an sdk of sorts

👍 1

John Doe21:04

Interesting, so I can today send actual transactions using the node project? I guess maybe where libbitcoin differs from core is that it segregates these different functions into different libraries, where as core is a monolith?

pmienk21:06

Well, the node project is a node. It would relay transactions. But server or explorer could generate new transactions to be submitted.

👍 1

21:09

Libbitcoin differs in a number of ways, but you've identified at least two. Core was never intended as an SDK, whereas it's been a goal of libbitcoin since inception. Additionally the segregation allows developers to scope the functionality. No point in pulling in our server to build your own wallet

👍 1

John Doe21:14

Interesting, I wonder how many people are running alt implementations. It seems seldom discussed. I wonder if it could adversely affect the p2p network at all?

pmienk21:21

There a number of different implementations and versions in the wild. Running a node the log can show you advertised identifiers.

👍 1

21:23

As for adverse effects, detected violations of protocol can be disconnected from automatically. Blacklisting or whitelisting is possible as well. However, a bad actor implementation is completely possible.

👍 1

pmienk21:29

The protocol is designed with certain bad actor mitigations. The mechanism of determining the proper blockchain is itself a means of filtering some form of 'bad' blocks

21:30

All network protocols have to envision some attack vectors

John Doe21:31

Thanks @pmienk

pmienk21:31

Glad to help

👍 2🙏 1👍🏻 1

Thursday, October 12, 2023

pmienk16:00

Topic: Dev Weekly Status Time: October 12, 2023 01:00pm Pacific Time (US and Canada) Join Zoom Meeting https://us05web.zoom.us/j/87666370902?pwd=bEZDUlJ0MGJ5V3dVMUhVdHl5QzdFdz09 Meeting ID: 876 6637 0902 Passcode: 85U0bF