BTCD is no more

[Cassius]

Hey guys, I'm new to these forums, but I've been investing in BTC for a couple years now. I've been following this thread since the beginning and I'm happy to say that I'm a large investor in BTCD now as well Just wanted to say hi to everyone and a big thanks to James and all the helpers for their hard work. I'll be donating 200 BTCD. Have a good one guys!

Welcome!
I'm curious to know what counts as a big holder. As this is a coin with a market cap of $2-3 million, that a couple of weeks ago was $1 million, a lot of people will presumably own 0.1-1% of the total supply for just a few bitcoins. 1-10% isn't inconceivable by any stretch.

[1713585407]

1713585407

[1713585407]

1713585407

[1713585407]

1713585407

[1713585407]

1713585407

[1713585407]

1713585407

[1713585407]

1713585407

[jl777]

I seem to have problems in getting github setup correctly...
Anyway, I made a new repository libjl777, but it wasnt updating and somehow it was happiest replacing pNXT. I guess it's OK, as I have put all my stuff into libjl777 anyway. So now that it works with Mac. I will test it on ubuntu. I hope someone can test building this on Windows.

https://github.com/jl777/libjl777

I know i said it would take a couple days, but I am not so good at this type of work so my time estimating is off.
Now I think I will just link it with BitcoinDarkd and see what happens

James

P.S. Once I removed the Mac specific files from the linking, it worked find in Ubuntu

[whitegold15]

Hey guys, I'm new to these forums, but I've been investing in BTC for a couple years now. I've been following this thread since the beginning and I'm happy to say that I'm a large investor in BTCD now as well Just wanted to say hi to everyone and a big thanks to James and all the helpers for their hard work. I'll be donating 200 BTCD. Have a good one guys!

Welcome!
I'm curious to know what counts as a big holder. As this is a coin with a market cap of $2-3 million, that a couple of weeks ago was $1 million, a lot of people will presumably own 0.1-1% of the total supply for just a few bitcoins. 1-10% isn't inconceivable by any stretch.

Thanks for the welcome Cassius! I would consider 5-10% of total supply as a big investor for now until the coin gets more distributed, is that a fair assumption?

[crackfoo]

is there a guide to setting up a privacy server on debian/ubuntu anywhere?
Posted from Bitcointa.lk - #3IkMOkiPGm6DWIBy

It will be just to install BitcoinDarkd and make the appropriate entries in the .conf file, also will need a NXT core running and whatever other coin daemons you want your tradebots to have access to.

Now I think the build process might become a bit more complicated as you will need to get:
libcurl, libwebsockets, libnacl, and gzip but for ubuntu these are pretty standard and probably:
-lcurl -lwebsockets -lnacl -lz -luv

The above link extras will allow it to link libjl777

James

Can the wallets be shared with other applications or will they need to be didicated to the NXT core?

Thanks

[jl777]

is there a guide to setting up a privacy server on debian/ubuntu anywhere?
Posted from Bitcointa.lk - #3IkMOkiPGm6DWIBy

It will be just to install BitcoinDarkd and make the appropriate entries in the .conf file, also will need a NXT core running and whatever other coin daemons you want your tradebots to have access to.

Now I think the build process might become a bit more complicated as you will need to get:
libcurl, libwebsockets, libnacl, and gzip but for ubuntu these are pretty standard and probably:
-lcurl -lwebsockets -lnacl -lz -luv

The above link extras will allow it to link libjl777

James

Can the wallets be shared with other applications or will they need to be didicated to the NXT core?

Thanks

I dont understand the question. NXT doesnt use wallets, the account is linked to the password and I am using the privkey for a BTCD address as the password, so a public BTCD address automatically maps to a NXT address. In a sense the NXT "wallet" is contained in your BTCD wallet. You can choose any address to use as your public address

Maybe you can describe your use case and I can explain better

James

[jl777]

I just defined the libjl777 interface, might as well post it for the record.

extern "C" int32_t libjl777_start(void **coinptrs,char *JSON_or_fname);

coinptrs, are just passed back to any C++ services I need, eg. libjl777_broadcast
the JSON_or_fname is what it says, either the JSON string itself (it wont be freed) or the full path to a file that contains the JSON string that configures libjl777. This way, it can all be in the BitcoinDark.conf file or any other file

Once you do a libjl777_start it will block waiting for commands, so make sure to do it in another thread.

Once it is running, you can submit commands via http://127.0.0.1:7777/{json command}, but this is probably best for webpages to use, for internal software use:

extern "C" char *libjl777_JSON(char *JSONstr);

This will run the command embedded in the JSONstr and return a string (or NULL), you need to free it after you dont need it anymore.

There needs to be a way to broadcast a packet, so there needs to be the following function:

extern "C" int32_t libjl777_broadcast(void **coinptrs,uint8_t *packet,int32_t len,uint64_t txid,int32_t duration);

The coinptrs are what was passed in before and the packet + len is the binary data. The txid is a (hopefully!) unique id for the packet. duration is the number of seconds it should stay around. Not critical to purge it if that is hard to do, but this allows a bit of resource management. When the node receives a broadcast packet, you call:

extern "C" char *libjl777_gotpacket(uint8_t *packet,int32_t len,uint64_t txid,int32_t duration);

The gotpacket function will return a JSON string (or NULL). Not sure what sort of info yet, probably just error or success.

James

[crackfoo]

is there a guide to setting up a privacy server on debian/ubuntu anywhere?
Posted from Bitcointa.lk - #3IkMOkiPGm6DWIBy

It will be just to install BitcoinDarkd and make the appropriate entries in the .conf file, also will need a NXT core running and whatever other coin daemons you want your tradebots to have access to.

Now I think the build process might become a bit more complicated as you will need to get:
libcurl, libwebsockets, libnacl, and gzip but for ubuntu these are pretty standard and probably:
-lcurl -lwebsockets -lnacl -lz -luv

The above link extras will allow it to link libjl777

James

Can the wallets be shared with other applications or will they need to be didicated to the NXT core?

Thanks

I dont understand the question. NXT doesnt use wallets, the account is linked to the password and I am using the privkey for a BTCD address as the password, so a public BTCD address automatically maps to a NXT address. In a sense the NXT "wallet" is contained in your BTCD wallet. You can choose any address to use as your public address

Maybe you can describe your use case and I can explain better

James

Sorry I meant to say coin daemons. For example, I already 30 or so coin daemons at my disposal. Can I utilize those for currencies I would use trade bots with or do I need an all new set, specifically for the privacy server.

[jl777]

is there a guide to setting up a privacy server on debian/ubuntu anywhere?
Posted from Bitcointa.lk - #3IkMOkiPGm6DWIBy

It will be just to install BitcoinDarkd and make the appropriate entries in the .conf file, also will need a NXT core running and whatever other coin daemons you want your tradebots to have access to.

Now I think the build process might become a bit more complicated as you will need to get:
libcurl, libwebsockets, libnacl, and gzip but for ubuntu these are pretty standard and probably:
-lcurl -lwebsockets -lnacl -lz -luv

The above link extras will allow it to link libjl777

James

Can the wallets be shared with other applications or will they need to be didicated to the NXT core?

Thanks

I dont understand the question. NXT doesnt use wallets, the account is linked to the password and I am using the privkey for a BTCD address as the password, so a public BTCD address automatically maps to a NXT address. In a sense the NXT "wallet" is contained in your BTCD wallet. You can choose any address to use as your public address

Maybe you can describe your use case and I can explain better

James

Sorry I meant to say coin daemons. For example, I already 30 or so coin daemons at my disposal. Can I utilize those for currencies I would use trade bots with or do I need an all new set, specifically for the privacy server.

Wow 30 daemons running stable on one server! You can use the same ones, just need to add a JSON entry for each coin:

{"name":"BTC","conf":"/home/root/.bitcoin/bitcoin.conf","asset":"4551058913252105307","rpc":"127.0.0.1:8332","minconfirms":3,"estblocktime":600},

This will allow the tradebot to know how to communicate with each coin's daemon

[xyzzyx]

This multisig is really fun. After taking all this time to get working, now I just cant stop trying many combinations. All looking quite stable and very solid, but of course it is using localhost, so no real networking errors.
UDP sometimes is pretty finicky, but that is another advantage of the shared secret multisig. It essentially acts as an error correcting code, well at least as long I dont mix in packets that are corrupted. If even one bit gets changed, it will not match the packet crc and so just get ignored, then the decryption will also fail, so I would say the odds of bad data getting processed is ignorable, even using UDP path.

Have you considered doing reed-solomon on the data to correct any corrupt packets?  It would add some redundant overhead, but you'd gain reliability in noisy networks.

http://www.drdobbs.com/cpp/reed-solomon-error-correction/184410107

[jl777]

This multisig is really fun. After taking all this time to get working, now I just cant stop trying many combinations. All looking quite stable and very solid, but of course it is using localhost, so no real networking errors.
UDP sometimes is pretty finicky, but that is another advantage of the shared secret multisig. It essentially acts as an error correcting code, well at least as long I dont mix in packets that are corrupted. If even one bit gets changed, it will not match the packet crc and so just get ignored, then the decryption will also fail, so I would say the odds of bad data getting processed is ignorable, even using UDP path.

Have you considered doing reed-solomon on the data to correct any corrupt packets?  It would add some redundant overhead, but you'd gain reliability in noisy networks.

http://www.drdobbs.com/cpp/reed-solomon-error-correction/184410107

I think M of N has the same effect, though nowhere near as efficient as rs codes. I am not sure how big a problem it is, so if it does turn out to be a real issue, then I will certainly consider such solutions. For now, I have enough code to write so I want to finish what I know must be done first

[jl777]

I built a BitcoinDarkd with libjl777 linked in. Still not actually hooked up yet, but just getting all the linker errors out makes me happy!

I had to copy:

these external libraries: libnacl.a randombytes.o libuv.a libwebsockets.a
and: libjl777.a libothers.a

to the bitcoindark/src directory

Then add "libjl777.a libothers.a libwebsockets.a libnacl.a libuv.a randombytes.o -lcurl -lz -ldl -lm"
to the linker line and it builds without errors.

Now, just have hookup the four functions and so if things go well I could be testing teleports from within BitcoinDarkd tonight. I think the above changes are also adequate to make it link with the QT wallet, but i leave that to somebody else to verify

James

[jl777]

Since instead of taking two days, I finished the libjl777 in half a day, this caused a bit of scheduling surprise for the other devs...
I will switch back to things I had planned to do this weekend while the connections to libjl777 are made.

James

P.S. I changed it so libjl777_start() doesnt block and it starts its own thread. This way the calling side doesnt have to mess with threads

[jl777]

Code:

#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
//#include "libjl777.h"
#include <stdint.h>

int libjl777_start(void **coinptrs,char *JSON_or_fname);
char *libjl777_JSON(char *JSONstr);
int32_t libjl777_broadcast(void **coinptrs,uint8_t *packet,int32_t len,uint64_t txid,int32_t duration);
char *libjl777_gotpacket(uint8_t *packet,int32_t len,uint64_t txid,int32_t duration);

char *confjson = "{\
\"MAINNET\":1,\"MIN_NXTCONFIRMS\":3,\
\"active\":[\"BTCD\"],\
\"coins\":[\
{\"name\":\"BTCD\",\"maxevolveiters\":10,\"useaddmultisig\":1,\"nohexout\":1,\"conf\":\"/Users/username/Library/Application Support/BitcoinDark/BitcoinDark.conf\",\"backupdir\":\"/Users/username/backups\",\"asset\":\"11060861818140490423\",\"minconfirms\":10,\"estblocktime\":60,\"rpc\":\"127.0.0.1:14632\",\"ciphers\":[{\"skipjack\":\"LA98Vs3sS6UtdiSaAYwvfgt5GseCVkAJ\"},{\"aes\":\"RUFrkuGAUuv8wsoiNwCvXenjxAfAgsTdAt\"},{\"blowfish\":\"RVHigwQquJR9cA6R6M143H6ZiPep7S9Udt\"}],\"clonesmear\":1,\"pubaddr\":\"RUHAPSpJDHeFgFd1J34WHJ69TpkMBsWtBt\",\"privacyServer\":\"127.0.0.1\"}]\
}";

int main(int argc,const char *argv[])
{
    void **coinptrs;
    coinptrs = calloc(1,sizeof(*coinptrs));
    libjl777_start(coinptrs,confjson);
    while ( 1 )
        sleep(60);
    return(0);
}

The above is a pretty small test program. It starts the libjl777 and just sleeps, but the :7777 page appears and I am able to test teleporting, which means I can now go back to adding features and debugging within the framework that will automatically be inside the BTCD core and QT

James

[crackfoo]

is there a guide to setting up a privacy server on debian/ubuntu anywhere?
Posted from Bitcointa.lk - #3IkMOkiPGm6DWIBy

It will be just to install BitcoinDarkd and make the appropriate entries in the .conf file, also will need a NXT core running and whatever other coin daemons you want your tradebots to have access to.

Now I think the build process might become a bit more complicated as you will need to get:
libcurl, libwebsockets, libnacl, and gzip but for ubuntu these are pretty standard and probably:
-lcurl -lwebsockets -lnacl -lz -luv

The above link extras will allow it to link libjl777

James

Can the wallets be shared with other applications or will they need to be didicated to the NXT core?

Thanks

I dont understand the question. NXT doesnt use wallets, the account is linked to the password and I am using the privkey for a BTCD address as the password, so a public BTCD address automatically maps to a NXT address. In a sense the NXT "wallet" is contained in your BTCD wallet. You can choose any address to use as your public address

Maybe you can describe your use case and I can explain better

James

Sorry I meant to say coin daemons. For example, I already 30 or so coin daemons at my disposal. Can I utilize those for currencies I would use trade bots with or do I need an all new set, specifically for the privacy server.

Wow 30 daemons running stable on one server! You can use the same ones, just need to add a JSON entry for each coin:

{"name":"BTC","conf":"/home/root/.bitcoin/bitcoin.conf","asset":"4551058913252105307","rpc":"127.0.0.1:8332","minconfirms":3,"estblocktime":600},

This will allow the tradebot to know how to communicate with each coin's daemon

Yup actually, way underestimated that, I'm at 62 now. It's my coin master and dedicated for providing the daemons/wallets for my pools. So looks like the privacyserver would have to be local to the wallets. Would there be any way to provide authentication details for remote access? I say remote, but simply another machine on the same private network.

[jl777]

is there a guide to setting up a privacy server on debian/ubuntu anywhere?
Posted from Bitcointa.lk - #3IkMOkiPGm6DWIBy

It will be just to install BitcoinDarkd and make the appropriate entries in the .conf file, also will need a NXT core running and whatever other coin daemons you want your tradebots to have access to.

Now I think the build process might become a bit more complicated as you will need to get:
libcurl, libwebsockets, libnacl, and gzip but for ubuntu these are pretty standard and probably:
-lcurl -lwebsockets -lnacl -lz -luv

The above link extras will allow it to link libjl777

James

Can the wallets be shared with other applications or will they need to be didicated to the NXT core?

Thanks

I dont understand the question. NXT doesnt use wallets, the account is linked to the password and I am using the privkey for a BTCD address as the password, so a public BTCD address automatically maps to a NXT address. In a sense the NXT "wallet" is contained in your BTCD wallet. You can choose any address to use as your public address

Maybe you can describe your use case and I can explain better

James

Sorry I meant to say coin daemons. For example, I already 30 or so coin daemons at my disposal. Can I utilize those for currencies I would use trade bots with or do I need an all new set, specifically for the privacy server.

Wow 30 daemons running stable on one server! You can use the same ones, just need to add a JSON entry for each coin:

{"name":"BTC","conf":"/home/root/.bitcoin/bitcoin.conf","asset":"4551058913252105307","rpc":"127.0.0.1:8332","minconfirms":3,"estblocktime":600},

This will allow the tradebot to know how to communicate with each coin's daemon

Yup actually, way underestimated that, I'm at 62 now. It's my coin master and dedicated for providing the daemons/wallets for my pools. So looks like the privacyserver would have to be local to the wallets. Would there be any way to provide authentication details for remote access? I say remote, but simply another machine on the same private network.

I think you could put the requesting server's IP address in the rpcallow field, so only your server can access the daemon's remotely.
If that wont work, I could add some authentication JSON fields to the .conf file, just let me know what you need

[crackfoo]

is there a guide to setting up a privacy server on debian/ubuntu anywhere?
Posted from Bitcointa.lk - #3IkMOkiPGm6DWIBy

It will be just to install BitcoinDarkd and make the appropriate entries in the .conf file, also will need a NXT core running and whatever other coin daemons you want your tradebots to have access to.

Now I think the build process might become a bit more complicated as you will need to get:
libcurl, libwebsockets, libnacl, and gzip but for ubuntu these are pretty standard and probably:
-lcurl -lwebsockets -lnacl -lz -luv

The above link extras will allow it to link libjl777

James

Can the wallets be shared with other applications or will they need to be didicated to the NXT core?

Thanks

I dont understand the question. NXT doesnt use wallets, the account is linked to the password and I am using the privkey for a BTCD address as the password, so a public BTCD address automatically maps to a NXT address. In a sense the NXT "wallet" is contained in your BTCD wallet. You can choose any address to use as your public address

Maybe you can describe your use case and I can explain better

James

Sorry I meant to say coin daemons. For example, I already 30 or so coin daemons at my disposal. Can I utilize those for currencies I would use trade bots with or do I need an all new set, specifically for the privacy server.

Wow 30 daemons running stable on one server! You can use the same ones, just need to add a JSON entry for each coin:

{"name":"BTC","conf":"/home/root/.bitcoin/bitcoin.conf","asset":"4551058913252105307","rpc":"127.0.0.1:8332","minconfirms":3,"estblocktime":600},

This will allow the tradebot to know how to communicate with each coin's daemon

Yup actually, way underestimated that, I'm at 62 now. It's my coin master and dedicated for providing the daemons/wallets for my pools. So looks like the privacyserver would have to be local to the wallets. Would there be any way to provide authentication details for remote access? I say remote, but simply another machine on the same private network.

I think you could put the requesting server's IP address in the rpcallow field, so only your server can access the daemon's remotely.
If that wont work, I could add some authentication JSON fields to the .conf file, just let me know what you need

Yes that's what I do now, but just looking at the json you posted, the credentials are expected in a file location?

[jl777]

is there a guide to setting up a privacy server on debian/ubuntu anywhere?
Posted from Bitcointa.lk - #3IkMOkiPGm6DWIBy

It will be just to install BitcoinDarkd and make the appropriate entries in the .conf file, also will need a NXT core running and whatever other coin daemons you want your tradebots to have access to.

Now I think the build process might become a bit more complicated as you will need to get:
libcurl, libwebsockets, libnacl, and gzip but for ubuntu these are pretty standard and probably:
-lcurl -lwebsockets -lnacl -lz -luv

The above link extras will allow it to link libjl777

James

Can the wallets be shared with other applications or will they need to be didicated to the NXT core?

Thanks

I dont understand the question. NXT doesnt use wallets, the account is linked to the password and I am using the privkey for a BTCD address as the password, so a public BTCD address automatically maps to a NXT address. In a sense the NXT "wallet" is contained in your BTCD wallet. You can choose any address to use as your public address

Maybe you can describe your use case and I can explain better

James

Sorry I meant to say coin daemons. For example, I already 30 or so coin daemons at my disposal. Can I utilize those for currencies I would use trade bots with or do I need an all new set, specifically for the privacy server.

Wow 30 daemons running stable on one server! You can use the same ones, just need to add a JSON entry for each coin:

{"name":"BTC","conf":"/home/root/.bitcoin/bitcoin.conf","asset":"4551058913252105307","rpc":"127.0.0.1:8332","minconfirms":3,"estblocktime":600},

This will allow the tradebot to know how to communicate with each coin's daemon

Yup actually, way underestimated that, I'm at 62 now. It's my coin master and dedicated for providing the daemons/wallets for my pools. So looks like the privacyserver would have to be local to the wallets. Would there be any way to provide authentication details for remote access? I say remote, but simply another machine on the same private network.

I think you could put the requesting server's IP address in the rpcallow field, so only your server can access the daemon's remotely.
If that wont work, I could add some authentication JSON fields to the .conf file, just let me know what you need

Yes that's what I do now, but just looking at the json you posted, the credentials are expected in a file location?

I parse the bitcoin.conf file to get the credentials, so specifying the location of the .conf file authorizes access

[crackfoo]

is there a guide to setting up a privacy server on debian/ubuntu anywhere?
Posted from Bitcointa.lk - #3IkMOkiPGm6DWIBy

It will be just to install BitcoinDarkd and make the appropriate entries in the .conf file, also will need a NXT core running and whatever other coin daemons you want your tradebots to have access to.

Now I think the build process might become a bit more complicated as you will need to get:
libcurl, libwebsockets, libnacl, and gzip but for ubuntu these are pretty standard and probably:
-lcurl -lwebsockets -lnacl -lz -luv

The above link extras will allow it to link libjl777

James

Can the wallets be shared with other applications or will they need to be didicated to the NXT core?

Thanks

I dont understand the question. NXT doesnt use wallets, the account is linked to the password and I am using the privkey for a BTCD address as the password, so a public BTCD address automatically maps to a NXT address. In a sense the NXT "wallet" is contained in your BTCD wallet. You can choose any address to use as your public address

Maybe you can describe your use case and I can explain better

James

Sorry I meant to say coin daemons. For example, I already 30 or so coin daemons at my disposal. Can I utilize those for currencies I would use trade bots with or do I need an all new set, specifically for the privacy server.

Wow 30 daemons running stable on one server! You can use the same ones, just need to add a JSON entry for each coin:

{"name":"BTC","conf":"/home/root/.bitcoin/bitcoin.conf","asset":"4551058913252105307","rpc":"127.0.0.1:8332","minconfirms":3,"estblocktime":600},

This will allow the tradebot to know how to communicate with each coin's daemon

Yup actually, way underestimated that, I'm at 62 now. It's my coin master and dedicated for providing the daemons/wallets for my pools. So looks like the privacyserver would have to be local to the wallets. Would there be any way to provide authentication details for remote access? I say remote, but simply another machine on the same private network.

I think you could put the requesting server's IP address in the rpcallow field, so only your server can access the daemon's remotely.
If that wont work, I could add some authentication JSON fields to the .conf file, just let me know what you need

Yes that's what I do now, but just looking at the json you posted, the credentials are expected in a file location?

I parse the bitcoin.conf file to get the credentials, so specifying the location of the .conf file authorizes access

figured as much. so if I'm running a privacy server on a different box, I could just copy all the .conf's over, but perhaps having them in the json would be more flexible?

[jl777]

figured as much. so if I'm running a privacy server on a different box, I could just copy all the .conf's over, but perhaps having them in the json would be more flexible?

For single server setups, I think it is better to not be putting passwords in the .conf file as it just creates chances to post it by accident. But for a remote setup, it is more risk to be making copies of the .conf files.

So, I added "rpcuserpass" field in the .conf JSON for you. It this one is set, it will ignore any bitcoin.conf file (so you dont need the "conf" field for that coin)

the format of the argument is "<user>:<password>"

James

P.S. I only coded it, so it is untested for now, maybe you can test it when it is released?

[crackfoo]

figured as much. so if I'm running a privacy server on a different box, I could just copy all the .conf's over, but perhaps having them in the json would be more flexible?

For single server setups, I think it is better to not be putting passwords in the .conf file as it just creates chances to post it by accident. But for a remote setup, it is more risk to be making copies of the .conf files.

So, I added "rpcuserpass" field in the .conf JSON for you. It this one is set, it will ignore any bitcoin.conf file (so you dont need the "conf" field for that coin)

the format of the argument is "<user>:<password>"

James

P.S. I only coded it, so it is untested for now, maybe you can test it when it is released?

sounds good, I'll give'r a go when it's out.

thanks