Comment
Author: Admin | 2025-04-28
My check list..I wouldn't kill yourself on x86 compatibility. Honestly who has a machine that is running .net which isn't x64 at this point. Even in QT devs started using x64 builds because of performance and memory issues. As the blockchain grows the memory demands will also grow with it. 5flags Full Member Offline Activity: 224 Merit: 100 Professional anarchist It isn't a client, it is a library.Aar, I see.For the benefit of other .Net developers, I'm currently using BitcoinJ in a .Net application (https://github.com/XCoinr/Metrobit) by using IKVM to create a .Net dll from a BitcoinJ bundled jar. I will be writing a how-to when I've nailed the very basic functionality, but happy to share tips with anyone interested. Nicolas Dorier (OP) What problem are you trying to solve here? What does your .Net implementation give us that that Bitcoin-QT or talking to bitcoind over RPC doesn't?I'm totally in favour of alternative clients, but all of them seem to solve a particular problem. Are you planning to simply keep up to date with the bitcoin-core changes? Are you planning to head in a different direction?It depends on if you are talking about the crypto part goal, the node implementation goal, or the overall goal.For the overall goal :Actually Bitcoin code is in C++. Compiling it on a windows computer, or even linux, and playing by debugging tests is a big battle that will cost you lots of time.In other words, you can't participate into the bitcoin code if you are not a linux wizard in C++.With NBitcoin, you clone the project, open with visual studio, and you can directly compile and run tests. There is no dependencies to compile and fetch on the net.To use the NBitcoin library, you just use the Nuget Package manager that will automatically download and
Add Comment