Topic: BTCD is no more - page 228. (Read 1328507 times)

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

do you have the latest version?

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

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!

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.

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

Me also.

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

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

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

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

in the debug console.

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

Holy Bjeezy, it's working!

Sorry, James. You might think I am a total idiot for asking so many questions. For some reason, I wasn't having a .conf file made by the terminal, but on the third try in terminal, it finally appeared.

Anyhow, THANK YOU for hanging in there with me!

Also, it took a while leaving it open to start synching, but it's finally synching.

IT'S ALIVE!!!

I will post a how-to tonight.

Three last questions:

Question 1: There are a LOT more nodes listed in the .conf code given on page 1 of this thread, however, mine appears to be working with the simpler code you gave me above with just two nodes added. Is it the more nodes listed the merrier (as in I should also add those other nodes), or will I be fine with the simpler version you gave me?

Question 2: Your simpler code you just gave me ends with the line "txindex=1," a line which is nowhere to be found in the original code on page 1 of this thread. Is that line important, and should it be added to the original code on page 1 of this thread?

Question 3: Is the Mac wallet link on page 1 of this thread the most recent Mac wallet available? I want to make sure if I start sending myself coins from exchanges that I actually get them.

James is too active again. Looks like its really near... Hodl on your breath...

the debugging went pretty smooth so far. after a few silly errors one node sent a UDP API to another, the other node got it, but it was a bit confused and the sending node crashed

not bad for first time test of new code, so hopefully all the onion layering is ported properly.

over the months the API tokenization has gotten a bit confusing, so it is time to clean that up and make it easy for debugging the application level state machines. This is routine work and requiring of no magic, but it still has to be done. So after some nice meal and latte I will get this done and hope to be able to announce later tonight some success of inter-node comms using SuperNET API protocol.

this is using the public IP disclosed privacyServers, so the probabilistic stuff is for after the easy routing is stable.

once BTCDdev gets me the few changes, then it should be ready for larger scale testing, but we need to verify that the packet traffic is under control first.

As soon as these system level issues are done, then while it is being tested, I can finalize the application level code, eg. Teleport.

James

copy means to use the mouse to select the text and do a copy command to get it in the clipboard

cat > BitcoinDark.conf



the control-d is to hold down the control key and press 'd' at the same time

James,

Here is what you said to do:

rpcuser=user
rpcpassword=password
rpcport=14632
port=14631
daemon=1
server=1
addnode=107.170.59.196
addnode=146.185.188.6
txindex=1

copy the above
open a terminal in the Mac
type
cat > BitcoinDark.conf

control-d

So, I opened a terminal and tried to follow your directions and nothing happened. I believe the issue might be with the directions.

Do I hit return anywhere?

Do I paste the command after hitting return?

Do I hold down the control key and then press the letter "d" (doing that just makes a "^d" appear in the pasted code).

Or do I type the words "control-d" after pasting the command and hitting return?

Could you please update your directions to include wherever you might hit return, as well as tell me where the file will be after doing all this?

Please assume the audience knows absolutely nothing about using the terminal.

How can I see how many btcd I have in my wallet address without looking in my wallet?
eg through block explorer.
I found 3 block explorers. 1 is not working and two do not show my address, only transactions etc.
I just want it to check "mined" btcd from staking while I am not at home

thanks

Okay, I will try that when I get back from a quick bite. I will let you know if it worked soon. Thanks for the help!

+1, better than vim

you might need a rpcusername and password


copy the above
open a terminal in the Mac
type
cat > BitcoinDark.conf

control-d

now you have a pure text file and this is exactly the .conf file I have that is working fine, other than the user/password
for testing you can even leave that
make sure the filename is exact