回复：比特币 API
首次公开证据
打开首次公开证据查看 1 个交叉存档
来源说明
Published on GitHub in February 2024 as part of Martti Malmi's testimony in the COPA v. Wright trial
有没有办法查出缺少的是哪些共享库？知道这一点会有帮助。
可能需要 gtk 库，那样的话，64 位版本也会遇到同样的问题。我希望能有一个也可在没有 UI 的系统上运行的单一可执行文件，但我不确定在 Linux 上该怎样链接这些东西，同时又能在库不存在时照常运行而不使用它们。也许我们应该静态链接 GTK。从许可证角度看，它是 LGPL，但因为它只在 Unix 上使用，所以这样没问题。（我们不能在 Windows 上链接 LGPL 的东西，因为我们提供了 OpenSSL DLL，但在 Linux 上，OpenSSL 随操作系统提供。）
随信附上我的 64 位（已剥离调试信息）可执行文件。它包含尚未进入 SVN 的未经测试的改动：UI 改动和钱包 fSpent 标志重新同步方面的内容。
我一直在研究进程间调用的方案。我希望找到一种便于各种服务器端语言调用的方式，尤其是 PHP。能够跨平台支持 Windows 是个加分项。
我不确定是否想让它可以通过网络访问。那会引入安全问题。如果它只能在本地系统上访问，那么本地安全认证就足以保护它，而且它不可能被远程入侵。
就表面来看，目前还没有研究任何细节，现阶段最有希望的是： D-Bus： 仅限本地系统 qt、gnome 和 skype 都在使用 绑定：c、python、java、c++， php 被列为“开发中” .net 被列为无人维护 不确定它在 Windows 上的成熟程度 XML-RPC： 使用广泛，PHP 中有内置库 它更适合 Web 客户端与服务器通信，传输方式是 http，所以存在安全问题
能否打开一个只能在本地访问的套接字？
你决定好比特币 API 的进程间调用方式了吗？一个简单的解决方案是使用 wxWidgets 提供的套接字接口：http://docs.wxwidgets.org/trunk/overview_ipc.html。这样，运行 wxServer 的比特币程序就可以通过从命令行调用 bitcoin 可执行文件，或编写自己的 wxClient 应用来访问。
另一个选择是直接使用普通的 BSD 套接字。
如果你有比特币的 64 位 Linux 二进制文件，可以发给我吗？我试过在 VPS 上编译，但内存耗尽了。也试过 32 位版本（配合 ia32-libs），但它找不到共享库。
英文原文
展开英文原文
Is there any way to find out what the missing shared libraries are? It would help to know.
It probably needs the gtk libraries, in which case you'll have the same problem with the 64-bit version. I would like to have a single executable that can also run on a UI-less system, but I'm not sure how on linux to link to things but still be able to run and not use them if the library is not present. Maybe we should statically link the GTK. Licensewise, it's LGPL, but since it's only used on unix, that would be OK. (we can't link LGPL stuff on windows because we provide the OpenSSL DLL, but on linux OpenSSL comes with the OS)
My 64-bit (debug stripped) executable is attached. It includes untested changes that are not in SVN yet: UI changes and the wallet fSpent flag resync stuff.
I've been researching options for interprocess calling. I want something that will be easy for a variety of server side languages to call, particularly PHP. Cross-platform to windows is a plus.
I'm not sure if I want it to be something that can be accessed across the network. That would introduce security issues. If it can only be accessed on the local system, then local security authentication covers it, and it is incapable of being hacked remotely.
At surface level, not looking into any details yet, the current front runners are: D-Bus: local system only used by qt, gnome and skype bindings: c, python, java, c++, php listed as "in progress" .net listed as unmaintained not sure how ready it is on windows XML-RPC: widely used, built in libraries on PHP it's more for web clients to talk to server, transport is http, so its a security question
Is it possible to open a socket that can only be accessed locally?
Have you decided upon the inter-process calling method of the Bitcoin API yet? An easy solution would be the socket interface provided by wxWidgets: http://docs.wxwidgets.org/trunk/overview_ipc.html. The Bitcoin program running a wxServer could be then accessed by calling the bitcoin executable from the command line or by coding your own wxClient app.
Another option would be to just use the plain BSD sockets.
Can you send me a 64-bit Linux binary of Bitcoin if you have one? I tried compiling on the VPS, but it ran out of memory. Tried the 32-bit version (with ia32-libs) also, but it didn't find the shared libraries.