BTCD is no more

[madalo]

just picked up a handful of BTCD. I hope I wont regret

[1714025759]

1714025759

[1714025759]

1714025759

[1714025759]

1714025759

[1714025759]

1714025759

[PondSea]

A1: more nodes is better, unless some of the additional nodes are giving conflicting info, then it would make it take longer to sync up. I think the best is to start with a few and then add some more little by little if it isnt syncing with the few.

A2: txindex is not actually supported, you can leave that out, I just have it out of habit from other coins

A3: I do not know if the Mac version is changed. I dont think so, my version is v1.0.0.0-g32a928e
As long as you have the wallet.dat (make backups!!) then your coins are on the blockchain and regardless of version you will be able to get the coins. To be safe, you can do:

dumpprivkey <address>

in the debug console. <address> is of course the BTCD address. This will give you a bunch of random letters/numbers. This is the magic that allows access to your funds! Keep it super safe. If you are dealing with large amounts, making a print out, or take a pic with enough resolution so you can always recover it. Then make sure you keep super safe the image with your private key

James

You rock. Thanks for getting us less code savvy people running smoothly. It is greatly appreciated.

I have a few different addresses in the same wallet. Do i need to dumpprivkey on every address?

[vipgelsi]

just picked up a handful of BTCD. I hope I wont regret

Me also.

[jl777]

A1: more nodes is better, unless some of the additional nodes are giving conflicting info, then it would make it take longer to sync up. I think the best is to start with a few and then add some more little by little if it isnt syncing with the few.

A2: txindex is not actually supported, you can leave that out, I just have it out of habit from other coins

A3: I do not know if the Mac version is changed. I dont think so, my version is v1.0.0.0-g32a928e
As long as you have the wallet.dat (make backups!!) then your coins are on the blockchain and regardless of version you will be able to get the coins. To be safe, you can do:

dumpprivkey <address>

in the debug console. <address> is of course the BTCD address. This will give you a bunch of random letters/numbers. This is the magic that allows access to your funds! Keep it super safe. If you are dealing with large amounts, making a print out, or take a pic with enough resolution so you can always recover it. Then make sure you keep super safe the image with your private key

James

You rock. Thanks for getting us less code savvy people running smoothly. It is greatly appreciated.

I have a few different addresses in the same wallet. Do i need to dumpprivkey on every address?

only the addresses that you want a paper backup for in case the computer blows up or EMP
you can check with the coin control from the send funds to see which addresses have the most funds

James

P.S. you just make a couple USB backups of the wallet.dat and not bother with printing out the key, just depends on your backup preferences

[PondSea]

A1: more nodes is better, unless some of the additional nodes are giving conflicting info, then it would make it take longer to sync up. I think the best is to start with a few and then add some more little by little if it isnt syncing with the few.

A2: txindex is not actually supported, you can leave that out, I just have it out of habit from other coins

A3: I do not know if the Mac version is changed. I dont think so, my version is v1.0.0.0-g32a928e
As long as you have the wallet.dat (make backups!!) then your coins are on the blockchain and regardless of version you will be able to get the coins. To be safe, you can do:

dumpprivkey <address>

in the debug console. <address> is of course the BTCD address. This will give you a bunch of random letters/numbers. This is the magic that allows access to your funds! Keep it super safe. If you are dealing with large amounts, making a print out, or take a pic with enough resolution so you can always recover it. Then make sure you keep super safe the image with your private key

James

You rock. Thanks for getting us less code savvy people running smoothly. It is greatly appreciated.

I have a few different addresses in the same wallet. Do i need to dumpprivkey on every address?

only the addresses that you want a paper backup for in case the computer blows up or EMP
you can check with the coin control from the send funds to see which addresses have the most funds

James

P.S. you just make a couple USB backups of the wallet.dat and not bother with printing out the key, just depends on your backup preferences

I already have that in place but i think might be worth getting the private key just in case, sucks though i have 12 addresses with the same amount of coins roughly.

[Boobsy]

Any idea on how to get past block 100675 in the Windows Version of the wallet?

I allready tried to delete all files but wallet.dat to make a full re-sync yet it again stopps syncing at 100675

Help please!

[jl777]

got JSON.({"requestType":"sendmessage","dest":"8894667849638377372","msg":"hello"})
pNXT_json_commands sender.(482478496576188177) valid.1 | size.22 | command.(sendmessage) orig.([{"requestType":"sendmessage","dest":"8894667849638377372","msg":"hello","NXT":"482478496576188177"},{"token":"sc749qe0te0ln5417busj6453qnkfl5knuhev55ilij0jhqqh7jqq09h8hbqe08116u2r9totg04edv r2ia77c3f43pd8l6flk9m4q3hv8j0aomunkbeoh1puui7ssrgevae58f77jba9digp7n0dgvr27l621 2g"}])
sendmsg_func sender.(482478496576188177) valid.1 dest.(8894667849638377372) ([{"requestType":"sendmessage","dest":"8894667849638377372","msg":"hello","NXT":"482478496576188177"},{"token":"sc749qe0te0ln5417busj6453qnkfl5knuhev55ilij0jhqqh7jqq09h8hbqe08116u2r9totg04edv r2ia77c3f43pd8l6flk9m4q3hv8j0aomunkbeoh1puui7ssrgevae58f77jba9digp7n0dgvr27l621 2g"}])
ONIONIZE: np.0x7f3700010530 NXT.8894667849638377372 8894667849638377372 pubkey.f080a422dff8ed23 encode len.275 -> new len.331 + 42 = 373
sendmessage ([{"requestType":"sendmessage","dest":"8894667849638377372","msg":"hello","NXT":"482478496576188177"},{"token":"sc749qe0te0ln5417busj6453qnkfl5knuhev55ilij0jhqqh7jqq09h8hbqe08116u2r9totg04edv r2ia77c3f43pd8l6flk9m4q3hv8j0aomunkbeoh1puui7ssrgevae58f77jba9digp7n0dgvr27l621 2g"}]) len.275 to 8894667849638377372
np.0x7f3700000ea0 NXT.482478496576188177 | destnp.0x7f3700010530
add layer 1: NXT.13434315136155299987
ONIONIZE: np.0x7f37000025f0 NXT.13434315136155299987 13434315136155299987 pubkey.aeb37026ae0c3b45 encode len.373 -> new len.429 + 42 = 471
ONIONIZE: np.0x7f37000025f0 NXT.13434315136155299987 13434315136155299987 pubkey.aeb37026ae0c3b45 encode len.471 -> new len.527 + 42 = 569
DIRECT udpsend to 209.126.70.159/6777 finalbuf.573
portable_udpwrite 573 bytes to 209.126.70.159/6777
parms.({"requestType":"sendmessage","dest":"8894667849638377372","msg":"hello","NXT":"482478496576188177"}) valid.1
UDP RECEIVED
{"status":"482478496576188177 sends via p2p encrypted sendmessage to 8894667849638377372 pending"}
decrypted2 len.373 dest.(13434315136155299987)
[?wȄH5p{ߝ??u4#.?s/o?^
                        ?3???%<
@K?$A???F?$?%?e򘂮q["] argjson.(nil) udp.0x7f370802b5c0
DIRECT udpsend to 209.126.70.156/6777 finalbuf.377
portable_udpwrite 377 bytes to 209.126.70.156/6777
UDP RECEIVED


The above is the result of: ./BitcoinDarkd SuperNET '{"requestType":"sendmessage","dest":"8894667849638377372","msg":"hello"}'
on one server and:


UDP RECEIVED
mismatched len expected 13411 got 275
decrypted len.275 dest.(7310874250626366299)
[[{"requestType":"sendmessage","dest":"8894667849638377372","msg":"hello","NXT":"482478496576188177"},{"token":"sc749qe0te0ln5417busj6453qnkfl5knuhev55ilij0jhqqh7jqq09h8hbqe08116u2r9totg04edv r2ia77c3f43pd8l6flk9m4q3hv8j0aomunkbeoh1puui7ssrgevae58f77jba9digp7n0dgvr27l621 2g"}]] argjson.0x7f443c0109f0 udp.0x7f4454023000
pNXT_json_commands sender.(482478496576188177) valid.1 | size.22 | command.(sendmessage) orig.([{"requestType":"sendmessage","dest":"8894667849638377372","msg":"hello","NXT":"482478496576188177"},{"token":"sc749qe0te0ln5417busj6453qnkfl5knuhev55ilij0jhqqh7jqq09h8hbqe08116u2r9totg04edv r2ia77c3f43pd8l6flk9m4q3hv8j0aomunkbeoh1puui7ssrgevae58f77jba9digp7n0dgvr27l621 2g"}])
sendmsg_func sender.(482478496576188177) valid.1 dest.(8894667849638377372) ([{"requestType":"sendmessage","dest":"8894667849638377372","msg":"hello","NXT":"482478496576188177"},{"token":"sc749qe0te0ln5417busj6453qnkfl5knuhev55ilij0jhqqh7jqq09h8hbqe08116u2r9totg04edv r2ia77c3f43pd8l6flk9m4q3hv8j0aomunkbeoh1puui7ssrgevae58f77jba9digp7n0dgvr27l621 2g"}])
received message.([{"requestType":"sendmessage","dest":"8894667849638377372","msg":"hello","NXT":"482478496576188177"},{"token":"sc749qe0te0ln5417busj6453qnkfl5knuhev55ilij0jhqqh7jqq09h8hbqe08116u2r9totg04edv r2ia77c3f43pd8l6flk9m4q3hv8j0aomunkbeoh1puui7ssrgevae58f77jba9digp7n0dgvr27l621 2g"}])
add.1 Uaddr.(209.126.70.159/6777) to 0


A lot of back and forth just to send "hello", but this is the same path for any SuperNET API call between two nodes.

I had to make some shortcuts to get this to work, but now that I have it working for this command, it is a matter of propagating this to all the other API calls. I also need to check for any memory leaks, i have a feeling I put some in there as I changed to a more streamlined approach.

also, only one API call is differentiating between a locally generated API call and a remotely sent one. Clearly we need some sort of limits on what sort of API calls we allow remote nodes to do!

The messaging is not filtering and this needs to be fixed in the BTCDcore, but now I am able to solidify the SuperNET routing and get back to implementing the API calls themselves.

James

tl:dr making steady progress debugging the core of SuperNET functionality, once this is done I can complete the Teleport

[jl777]

Any idea on how to get past block 100675 in the Windows Version of the wallet?

I allready tried to delete all files but wallet.dat to make a full re-sync yet it again stopps syncing at 100675

Help please!

do you have the latest version?

[torshammer]

Any idea on how to get past block 100675 in the Windows Version of the wallet?

I allready tried to delete all files but wallet.dat to make a full re-sync yet it again stopps syncing at 100675

Help please!

do you have the latest version?

did u add the .conf file as explained earlier in the thread?

[torshammer]

tl:dr making steady progress debugging the core of SuperNET functionality, once this is done I can complete the Teleport

Rock on James!

[jeezy]

tl:dr making steady progress debugging the core of SuperNET functionality, once this is done I can complete the Teleport

Do you have a rough timeline for the modules/functionalities to be completed? e.g. Teleport End of Sept, SuperNET complete End of 2014...?

[Qwitnix]

Hi all,

I see quite some people having some troubles with the installation of the wallet.
I myself also had some issues with the new version after the last fork.

So I'm planning of making an installer for windows (.MSI) that will do:
1. Check if a previous version of this installer is installed, if so, uninstall the old one first / upgrade the old one.
2. If not (otherwise, in the future, this will be done by the uninstall of the old msipackage), check if wallet is running, if so kill process. Is there a way built into the wallet to close the wallet nicely from a commandline?
3. Place the .exe in a folder on C:\Program Files\BitcoinDark (location customizable in install wizard)
4. Place shortcut in startmenu (by default)
5. Place shortcut on desktop (Optional, not default, will be a checkbox on install)
6. Start .exe on windows startup (not the default option, will be a checkbox on install, will probably write a key in run under HKLM)
7. If exist, backup %appdata%\BitcoinDark to %appdata%\BitCoinDark_PrevVersion (if this already exsists, remove the old, create the new backup) and remove all in %appdata%\BitcoinDark, except wallet and .conf (Also optional, but default)
8. If not present create .conf in %appdata%\BitcoinDark
9. Start .exe when installation is finished (Optional, but default)

To make this there's a few more things I need to know:
If I include this .conf file as default, will that do for the general end-user (it is the one you can downloaded from OP)?

Code:

addnode=107.170.59.196
addnode=146.185.188.6
addnode=74.91.20.250:39997
addnode=54.85.50.15:50288
addnode=186.94.211.104:49543
addnode=107.170.148.50:14631
addnode=65.129.66.246:57762
addnode=31.220.4.41
addnode=98.226.66.65
addnode=193.219.117.63
addnode=62.210.141.204
addnode=128.199.172.165
addnode=192.99.143.114
addnode=178.20.169.208
addnode=195.34.100.2:42038
addnode=5.101.107.239:60056

Or would it need the version that's written in text on the OP?

Code:

rpcuser=user
rpcpassword=pass
rpcport=14632
port=14631
daemon=1
gen=1
server=1
addnode=107.170.59.196
addnode=146.185.188.6
addnode=74.91.20.250:39997
addnode=54.85.50.15:50288
addnode=107.170.148.50:14631
addnode=65.129.66.246:57762
addnode=31.220.4.41
addnode=98.226.66.65
addnode=193.219.117.63
addnode=62.210.141.204
addnode=128.199.172.165
addnode=192.99.143.114

Or maybe even a completely different one?
How do I make sure that the file I upload is 100% virus, malware, etc free? Is there a trusted site or something?
Is there a guide that I can follow to make a checksum thingy, so people can checkt it's the exact same thing I uploaded?
Anything else needed?

Grtz,
Qwitnix

tl;dr: Incoming windows installer, but need some input to make it work.

[Cassius]

Windows installer would be very helpful.

Interesting that BTCD has kept its value surprisingly well, given BTC's crash. Low volume, too. I guess BTCD people are natural born hodlers.

[alxx77]

Stainless steel balls 

[RichardT]

Interesting that BTCD has kept its value surprisingly well, given BTC's crash. Low volume, too. I guess BTCD people are natural born hodlers.

Yeah, it's one of the things that got me drawn to BTCD in the first place.  If you look at the history, BTCD has probably had the most stable price (even after big price jumps) out of any coin within the past 3 months.  Good community here and it doesn't seem like there are a bunch of people who are just looking to dump all their coins the first chance they get.  Or people could just be holding in anticipation for Teleport release, knowing the next big price jump will happen again.  But even after that happens, I predict price will continue to stay elevated because of SuperNET.  Lots of intertwining things that will help maintain the value.

[Juicemixer]

Stainless steel balls 

Purchased at 60k and still holding. If anything I want to see the dividend payouts. Could pay off my investment in only a few months leading to straight profit for years.

I have donated some so there has been a few let go of but I think I'm done giving out free BTCD. Don't want to leave myself with nothing to show.

[jl777]

tl:dr making steady progress debugging the core of SuperNET functionality, once this is done I can complete the Teleport

Do you have a rough timeline for the modules/functionalities to be completed? e.g. Teleport End of Sept, SuperNET complete End of 2014...?

SuperNET transport needs to come first as Teleport will use it
It is hard to estimate exact times when I am doing a lot of non-coding things
the SuperNET routing is being code reviewed now, i have small scale tests working, as things are scaled up there will be issues that need to be found and then fixed.

Considering this has never been done before and neither has Teleport, any exact prediction will likely be wrong, especially as I am not getting much help on the tech side at all.

I am willing and able to get all the tech done on my own, but I cannot be on a strict schedule and be doing all the non-tech stuff while doing never before done things.

I hope you can understand. I am working as hard as I can, one step at a time. The next step is to get the SuperNET routing solid so Teleport and all other SuperNET applications have a solid foundation. Once this is in place, then the pace will speed up a lot as application debugging is much faster than system debugging

James

[jl777]

Hi all,

I see quite some people having some troubles with the installation of the wallet.
I myself also had some issues with the new version after the last fork.

So I'm planning of making an installer for windows (.MSI) that will do:
1. Check if a previous version of this installer is installed, if so, uninstall the old one first / upgrade the old one.
2. If not (otherwise, in the future, this will be done by the uninstall of the old msipackage), check if wallet is running, if so kill process. Is there a way built into the wallet to close the wallet nicely from a commandline?
3. Place the .exe in a folder on C:\Program Files\BitcoinDark (location customizable in install wizard)
4. Place shortcut in startmenu (by default)
5. Place shortcut on desktop (Optional, not default, will be a checkbox on install)
6. Start .exe on windows startup (not the default option, will be a checkbox on install, will probably write a key in run under HKLM)
7. If exist, backup %appdata%\BitcoinDark to %appdata%\BitCoinDark_PrevVersion (if this already exsists, remove the old, create the new backup) and remove all in %appdata%\BitcoinDark, except wallet and .conf (Also optional, but default)
8. If not present create .conf in %appdata%\BitcoinDark
9. Start .exe when installation is finished (Optional, but default)

To make this there's a few more things I need to know:
If I include this .conf file as default, will that do for the general end-user (it is the one you can downloaded from OP)?

Code:

addnode=107.170.59.196
addnode=146.185.188.6
addnode=74.91.20.250:39997
addnode=54.85.50.15:50288
addnode=186.94.211.104:49543
addnode=107.170.148.50:14631
addnode=65.129.66.246:57762
addnode=31.220.4.41
addnode=98.226.66.65
addnode=193.219.117.63
addnode=62.210.141.204
addnode=128.199.172.165
addnode=192.99.143.114
addnode=178.20.169.208
addnode=195.34.100.2:42038
addnode=5.101.107.239:60056

Or would it need the version that's written in text on the OP?

Code:

rpcuser=user
rpcpassword=pass
rpcport=14632
port=14631
daemon=1
gen=1
server=1
addnode=107.170.59.196
addnode=146.185.188.6
addnode=74.91.20.250:39997
addnode=54.85.50.15:50288
addnode=107.170.148.50:14631
addnode=65.129.66.246:57762
addnode=31.220.4.41
addnode=98.226.66.65
addnode=193.219.117.63
addnode=62.210.141.204
addnode=128.199.172.165
addnode=192.99.143.114

Or maybe even a completely different one?
How do I make sure that the file I upload is 100% virus, malware, etc free? Is there a trusted site or something?
Is there a guide that I can follow to make a checksum thingy, so people can checkt it's the exact same thing I uploaded?
Anything else needed?

Grtz,
Qwitnix

tl;dr: Incoming windows installer, but need some input to make it work.

ths would be great!
you should build the binary to make sure it is not infected, assuming your computer isnt infected
i remember seeing checksum generating methods, but dont have the link

the .conf file details will be changing with the new release, so for now, just use the second one here, with changes to the rpcuser and rpcpassword. i am assuming it wont be hard to update the .conf template

[Qwitnix]

Code:

rpcuser=user
rpcpassword=pass
rpcport=14632
port=14631
daemon=1
gen=1
server=1
addnode=107.170.59.196
addnode=146.185.188.6
addnode=74.91.20.250:39997
addnode=54.85.50.15:50288
addnode=107.170.148.50:14631
addnode=65.129.66.246:57762
addnode=31.220.4.41
addnode=98.226.66.65
addnode=193.219.117.63
addnode=62.210.141.204
addnode=128.199.172.165
addnode=192.99.143.114

ths would be great!
you should build the binary to make sure it is not infected, assuming your computer isnt infected
i remember seeing checksum generating methods, but dont have the link

the .conf file details will be changing with the new release, so for now, just use the second one here, with changes to the rpcuser and rpcpassword. i am assuming it wont be hard to update the .conf template

So rpcuser and rpcpassword should not be in the default .config, people that will need it, will have to add it manually?
Or should the installer ask for it?
I haven't got a clue what it's for so if included in the installer wizard, I need a text to explain it to a user and/or a default value.

Grtz,
Qwitnix

[jl777]

Code:

rpcuser=user
rpcpassword=pass
rpcport=14632
port=14631
daemon=1
gen=1
server=1
addnode=107.170.59.196
addnode=146.185.188.6
addnode=74.91.20.250:39997
addnode=54.85.50.15:50288
addnode=107.170.148.50:14631
addnode=65.129.66.246:57762
addnode=31.220.4.41
addnode=98.226.66.65
addnode=193.219.117.63
addnode=62.210.141.204
addnode=128.199.172.165
addnode=192.99.143.114

ths would be great!
you should build the binary to make sure it is not infected, assuming your computer isnt infected
i remember seeing checksum generating methods, but dont have the link

the .conf file details will be changing with the new release, so for now, just use the second one here, with changes to the rpcuser and rpcpassword. i am assuming it wont be hard to update the .conf template

So rpcuser and rpcpassword should not be in the default .config, people that will need it, will have to add it manually?
Or should the installer ask for it?
I haven't got a clue what it's for so if included in the installer wizard, I need a text to explain it to a user and/or a default value.

Grtz,
Qwitnix

they are needed, if you can automatically generate some random values that would be perfect
keep it to letters and numbers, 16 to 32 chars for each