Delivery-date: Mon, 07 Oct 2024 05:17:43 -0700
Date: Mon, 7 Oct 2024 05:16:09 -0700 (PDT)
From: "'Dr. Craig S. Wrong' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Message-Id: <c8a0717f-4576-4fb7-ac5c-a2a1ab7a2eden@googlegroups.com>
Subject: [bitcoindev] Pure Swift Bitcoin Protocol implementation (largely experimental)
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_322154_1547947587.1728303369600"
Reply-To: "Dr. Craig S. Wrong" <toximaxi@proton.me>
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com

------=_Part_322154_1547947587.1728303369600
Content-Type: multipart/alternative; 
	boundary="----=_Part_322155_1104646991.1728303369600"

------=_Part_322155_1104646991.1728303369600
Content-Type: text/plain; charset="UTF-8"

Hello there!

I wanted to share with y'all a project that I've been working on for more 
than two years called Swift Bitcoin 
(https://github.com/swift-bitcoin/swift-bitcoin 
/ https://swift-bitcoin.github.io)

It started as a way for me to test my own knowledge about the way Bitcoin 
works internally and externally. I first took a stab at implementing the 
various BIPs including with their respective test vectors in my favorite 
language Swift. I then started porting over additional unit tests from the 
Bitcoin Core project which helped me understand a lot of what happens under 
the hood.

While far from complete, today the package offers a comprehensive set of 
idiomatic Swift APIs which covers ECC and Bitcoin cryptography (uses 
libsecp256k1), hash functions, codecs, a full SCRIPT interpreter, 
transaction composition, signature verification, wallet functionality 
(addresses, key derivation, mnemonic, transaction input signing), 
blockchain, mining, RPC and P2P transport (WIP).

About some the advantages of using Swift I can mention the use of actors 
for isolation of mutable state and structured concurrency which guarantees 
data race safety. These are particularly noticeable at the wire protocol 
level where I'm leveraging the SwiftNIO library for non-blocking I/O.

The code does not rely on third party dependencies and produces a very fast 
and small binary which could eventually be suitable for embedded systems 
(coming soon). For Apple platform of course this library fits right in but 
everything is developed and tested on Linux. Also with C / C++ 
interoperability it can also be integrated into any CMake-based project.

Anyway if anyone is interested in knowing more or becoming a contributor 
please reach out to me at toximaxi (at) proton.me. I'm not a protocols guy 
so progress in that area has been slow and I could use some help in that 
particular area as well as many others.

Aside from that let me know what you think. Could an 
experimental/educational project like this one evolve into something useful 
for others?

Thanks everyone for taking the time.

Cheers!

-- 
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bitcoindev/c8a0717f-4576-4fb7-ac5c-a2a1ab7a2eden%40googlegroups.com.

------=_Part_322155_1104646991.1728303369600
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hello there!<div><br /></div><div>I wanted to share with y'all a project th=
at I've been working on for more than two years called Swift Bitcoin (https=
://github.com/swift-bitcoin/swift-bitcoin /=C2=A0https://swift-bitcoin.gith=
ub.io)</div><div><br /></div><div>It started as a way for me to test my own=
 knowledge about the way Bitcoin works internally and externally. I first t=
ook a stab at implementing the various BIPs including with their respective=
 test vectors in my favorite language Swift. I then started porting over ad=
ditional unit tests from the Bitcoin Core project which helped me understan=
d a lot of what happens under the hood.</div><div><br /></div><div>While fa=
r from complete, today the package offers a comprehensive set of idiomatic =
Swift APIs which covers ECC and Bitcoin cryptography (uses libsecp256k1), h=
ash functions, codecs, a full SCRIPT interpreter, transaction composition, =
signature verification, wallet functionality (addresses, key derivation, mn=
emonic, transaction input signing), blockchain, mining, RPC and P2P transpo=
rt (WIP).</div><div><br /></div><div>About some the advantages of using Swi=
ft I can mention the use of actors for isolation of mutable state and struc=
tured concurrency which guarantees data race safety. These are particularly=
 noticeable at the wire protocol level where I'm leveraging the SwiftNIO li=
brary for non-blocking I/O.</div><div><br /></div><div>The code does not re=
ly on third party dependencies and produces a very fast and small binary wh=
ich could eventually be suitable for embedded systems (coming soon). For Ap=
ple platform of course this library fits right in but everything is develop=
ed and tested on Linux. Also with C / C++ interoperability it can also be i=
ntegrated into any CMake-based project.</div><div><br /></div><div>Anyway i=
f anyone is interested in knowing more or becoming a contributor please rea=
ch out to me at toximaxi (at) proton.me. I'm not a protocols guy so progres=
s in that area has been slow and I could use some help in that particular a=
rea as well as many others.</div><div><br /></div><div>Aside from that let =
me know what you think. Could an experimental/educational project like this=
 one evolve into something useful for others?</div><div><br /></div><div>Th=
anks everyone for taking the time.</div><div><br /></div><div>Cheers!</div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;Bitcoin Development Mailing List&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:bitcoindev+unsubscribe@googlegroups.com">bitcoind=
ev+unsubscribe@googlegroups.com</a>.<br />
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/d/msgid/bitcoindev/c8a0717f-4576-4fb7-ac5c-a2a1ab7a2eden%40googlegroups.=
com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msg=
id/bitcoindev/c8a0717f-4576-4fb7-ac5c-a2a1ab7a2eden%40googlegroups.com</a>.=
<br />

------=_Part_322155_1104646991.1728303369600--

------=_Part_322154_1547947587.1728303369600--