BTCD is no more

[paulthetafy]

well that was fun!

I like "beg for changepod"

[1715605672]

1715605672

[1715605672]

1715605672

[1715605672]

1715605672

[1715605672]

1715605672

[id10tothe9]

I want to share my pain with you


0 pNXT_json_commands sender.(8989816935121514892) valid.1 | size.20 | command.(select)
attempt privacyServer 1a79aa467ed1 209.126.70.170/6777 connect.0x0 tcp.0x0 udp.0x0
SETTING PRIVACY SERVER IPADDR.(209.126.70.170)
CONNECTED to 209.126.70.170/6777 connect.0x100f00430 tcp.0x100f01060
nxt.8989816935121514892
connect.0x100f00430 -> 0x0
udp.0x102600a60 tcp.0x100f01060 got bytes.0x100f00430 (connect) >>>>>>>>>>>>>>>>>>> got 299 bytes at 0x107000000.([{"NXT":"1700913285397123524","pubkey":"a942e1a4edb99401354eeea61ee0aad827d6ec524aa5257025a6fa0e8b91e75e","time":1407295599},{"token":"vb5lpi57ea2pb4cvjn7g1i2ffrso4j7p7ban3vfmhv7ftcbp9ur2u4etbem70501qq1mjlkn34f32cp 9osikj9qaf8ujamir90gp51511img005mpvkdqtal9al0tqcon96b03gb49cuunpn775koskakmctsk au"}]) from 209.126.70.170/6777
got crc of e4d1014e vx packet_crc 4e227b5b
signed by valid NXT.1700913285397123524 valid.1 diff.1
np.0x10380aa00 created.1 NXT.1700913285397123524 pubkey.a942e1a4edb99401354eeea61ee0aad827d6ec524aa5257025a6fa0e8b91e75e (len.32) connect.0x100f01060 sendresponse.0
process_intro got NXT.(1700913285397123524) np.0x10380aa00 <- I_am_server.0 UDP 0x0 TCP.0x100f01060 209.126.70.170/6777
set TCP.0x100f01060 209.126.70.170/6777
SETTING PRIVACY SERVER NXT ADDR.(1700913285397123524) (1700913285397123524)
json_handler returns.([{"NXT":"1700913285397123524","pubkey":"a942e1a4edb99401354eeea61ee0aad827d6ec524aa5257025a6fa0e8b91e75e","time":1407295599},{"token":"vb5lpi57ea2pb4cvjn7g1i2ffrso4j7p7ban3vfmhv7ftcbp9ur2u4etbem70501qq1mjlkn34f32cp 9osikj9qaf8ujamir90gp51511img005mpvkdqtal9al0tqcon96b03gb49cuunpn775koskakmctsk au"}])
on_client_udprecv 209.126.70.170/6777 nread.299 flags.0 | total 0
got crc of e4d1014e vx packet_crc 4e227b5b
signed by valid NXT.1700913285397123524 valid.1 diff.1
np.0x10380aa00 created.0 NXT.1700913285397123524 pubkey.a942e1a4edb99401354eeea61ee0aad827d6ec524aa5257025a6fa0e8b91e75e (len.32) connect.0x0 sendresponse.0
process_intro got NXT.(1700913285397123524) np.0x10380aa00 <- I_am_server.0 UDP 0x102600a60 TCP.0x0 209.126.70.170/6777
set UDP.0x102600a60 209.126.70.170/6777
SETTING PRIVACY SERVER NXT ADDR.(1700913285397123524) (1700913285397123524)
testforms len 16806
29109850111697 pNXT_json_commands sender.() valid.-1 | size.20 | command.(teleport)
verification valid.-1 missing for teleport sender.() vs NXT.()
replace NXT.(8989816935121514892)
29109850111697 pNXT_json_commands sender.(8989816935121514892) valid.1 | size.20 | command.(teleport)
amount.(0.10000000) minage.(10) 10
8989816935121514892 -> teleport 0.10000000 BTCD -> 8989816935121514892 minage.10
(backups/telepods/BTCD.0) update    0.10000000 height.46983    BTCD RPG2zwo3byN1EoG5U9Esgz76Pjtr2Jw1AY a4c6e70c6cce13a6986fca1b9ebdbdd209099680dd4ad9b6c82b41a630d61d15/vout_0
  load    0.10000000 height.46983    BTCD RPG2zwo3byN1EoG5U9Esgz76Pjtr2Jw1AY a4c6e70c6cce13a6986fca1b9ebdbdd209099680dd4ad9b6c82b41a630d61d15/vout_0
(backups/telepods/BTCD.1) update    0.10000000 height.46983    BTCD RFaHNNQmog8XBj7iuYnT9zJdR3ju36inBJ 8ab8b6416728596986cff9a2d5930f52017ac3ec569195a4be4a41d54f3cc19a/vout_0
  load    0.10000000 height.46983    BTCD RFaHNNQmog8XBj7iuYnT9zJdR3ju36inBJ 8ab8b6416728596986cff9a2d5930f52017ac3ec569195a4be4a41d54f3cc19a/vout_0
beg for changepod
after loaded 2 telepods
reject telepod.1 height.47400 - pod->height.46983 minage.10, ischange.1
evolve maxiters.0 with n.1
   hwm    0.10000000 height.46983    BTCD RFaHNNQmog8XBj7iuYnT9zJdR3ju36inBJ 8ab8b6416728596986cff9a2d5930f52017ac3ec569195a4be4a41d54f3cc19a/vout_0
-> evolved with bestn.1 0x106a00970
need to implement query (and propagation) mechanism for pubkeys
json_handler returns.({"error":"no pubkey for 8989816935121514892, request sent"})
testforms len 16806
NXTprotocol_json_handler.({"requestType":"teleport","secret":"xxx","dest":"8989816935121514892","amount":".1","coin":"BTCD","minage":"10"})
29109850111697 pNXT_json_commands sender.() valid.-1 | size.20 | command.(teleport)
verification valid.-1 missing for teleport sender.() vs NXT.()
replace NXT.(8989816935121514892)
29109850111697 pNXT_json_commands sender.(8989816935121514892) valid.1 | size.20 | command.(teleport)
amount.(0.10000000) minage.(10) 10
8989816935121514892 -> teleport 0.10000000 BTCD -> 8989816935121514892 minage.10
reject telepod.1 height.47400 - pod->height.46983 minage.10, ischange.1
evolve maxiters.0 with n.1
   hwm    0.10000000 height.46983    BTCD RFaHNNQmog8XBj7iuYnT9zJdR3ju36inBJ 8ab8b6416728596986cff9a2d5930f52017ac3ec569195a4be4a41d54f3cc19a/vout_0
-> evolved with bestn.1 0x102003fc0
start evolving at 28378.965000
reject telepod.1 height.47400 - pod->height.46983 minage.10, ischange.1
evolve maxiters.100000 with n.1
metric.1.998803 youngest.417 agesum 417 n 1, (10000000 - 10000000)
i.0 of 100000, replacei.0 j.0 inhwm.1
i.1 of 100000, replacei.0 j.0 inhwm.1
...
i.99 of 100000, replacei.0 j.0 inhwm.1
   hwm    0.10000000 height.46983    BTCD RFaHNNQmog8XBj7iuYnT9zJdR3ju36inBJ 8ab8b6416728596986cff9a2d5930f52017ac3ec569195a4be4a41d54f3cc19a/vout_0
-> evolved with bestn.1 0x102601200
finished evolving at 28379.517000
set np <- NXT.1700913285397123524
ONIONIZE: np.0x107019000 NXT.8989816935121514892 8989816935121514892 pubkey.d4f90774a020df13 encode len.315 -> new len.371 + 42 = 413
sendmessage ([{"requestType":"transporter","coin":"BTCD","height":47400,"minage":10,"value":"0.10000000","telepods":["1489107942"],"totalcrc":3700449792},{"token":"d79fth95u83cu087m4js5pr7oqktvg537dctmf7sclmv3thq9ur40bpgi2bit301md2ijtcqb6g01tg d8fmsklgccgere9j8au65d3skqop0hm9nntm9o14uaocg6ft0ibdna069fkvimrfj2991dcah753nr7 3c"}]) len.316 to 8989816935121514892
np.0x10380aa00 NXT.1700913285397123524 np->udp 0x102600a60 | destnp.0x107019000 destnp_udp.0x0
Must use indirection
ONIONIZE: np.0x10380aa00 NXT.1700913285397123524 1700913285397123524 pubkey.194b9eda4e142a9 encode len.413 -> new len.469 + 42 = 511
udpsend finalbuf.515
sendandfree_jsonmessage.({"status":"8989816935121514892 sends via 1700913285397123524 encrypted sendmessage.([{"requestType":"transporter","coin":"BTCD","height":47400,"minage":10,"value":"0.10000000","telepods":["1489107942"],"totalcrc":3700449792},{"token":"d79fth95u83cu087m4js5pr7oqktvg537dctmf7sclmv3thq9ur40bpgi2bit301md2ijtcqb6g01tg d8fmsklgccgere9j8au65d3skqop0hm9nntm9o14uaocg6ft0ibdna069fkvimrfj2991dcah753nr7 3c"}]) [[{"requestType":"transporter","coin":"BTCD","height":47400,"minage":10,"value":"0.10000000","telepods":["1489107942"],"totalcrc":3700449792},{"token":"d79fth95u83cu087m4js5pr7oqktvg537dctmf7sclmv3thq9ur40bpgi2bit301md2ijtcqb6g01tg d8fmsklgccgere9j8au65d3skqop0hm9nntm9o14uaocg6ft0ibdna069fkvimrfj2991dcah753nr7 3c"}]] to 8989816935121514892 pending"})
json_handler returns.({"error":"sendandfree_jsonmessage telepod bundle failure for 0.10000000 BTCD to 8989816935121514892"})
on_client_udprecv 209.126.70.170/6777 nread.515 flags.0 | total 299
got crc of 6bb3c525 vx packet_crc 6bb3c525
deonionize >>>>> pubkey.194b9eda4e142a9 vs mypubkey.d4f90774a020df13 (40) -> 469 1d5
payload_len.469 err.0 new len.413
decrypted len.413 dest.(8989816935121514892)
deonionize >>>>> pubkey.d4f90774a020df13 vs mypubkey.d4f90774a020df13 (40) -> 371 173
payload_len.371 err.0 new len.315
decrypted2 len.315 dest.(8989816935121514892)
set UDP.0x102600a60 209.126.70.170/6777
29109850111697 pNXT_json_commands sender.(8989816935121514892) valid.1 | size.20 | command.(transporter)
make_traceable_telepod 0.10000000
got podaddr.(RHEXHztke1hZ5NSAxKHCproTsind934Sjc) privkey.0x102600640
args.(["transporter","RHEXHztke1hZ5NSAxKHCproTsind934Sjc",0.10000000])
check (backups/telepods/BTCD.2)
(backups/telepods/BTCD.2) update    0.10000000 height.47400    BTCD RHEXHztke1hZ5NSAxKHCproTsind934Sjc f166d4711537702a46994d1a78b01d2c7d083e668264b3efe6fc83f6fda2bbf9/vout_0
create    0.10000000 height.47400    BTCD RHEXHztke1hZ5NSAxKHCproTsind934Sjc f166d4711537702a46994d1a78b01d2c7d083e668264b3efe6fc83f6fda2bbf9/vout_0
make_traceable_telepod 0.10000000
got podaddr.(RKbPodL1GaBeyHydaAhvX286FAPDLw8ZhJ) privkey.0x106a01e40
args.(["transporter","RKbPodL1GaBeyHydaAhvX286FAPDLw8ZhJ",0.10000000])
check (backups/telepods/BTCD.3)
(backups/telepods/BTCD.3) update    0.10000000 height.47400    BTCD RKbPodL1GaBeyHydaAhvX286FAPDLw8ZhJ 07d22536a9869cac5d856c127893e89c2194f6c5bf22440c05f91f1c55f24fdb/vout_0
create    0.10000000 height.47400    BTCD RKbPodL1GaBeyHydaAhvX286FAPDLw8ZhJ 07d22536a9869cac5d856c127893e89c2194f6c5bf22440c05f91f1c55f24fdb/vout_0
set np <- NXT.1700913285397123524
ONIONIZE: np.0x107019000 NXT.8989816935121514892 8989816935121514892 pubkey.d4f90774a020df13 encode len.107 -> new len.163 + 42 = 205
sendmessage ({"requestType":"transporter_status","status":-1,"coin":"BTCD","crc":3700449792,"value",0.10000000,"num":1}) len.107 to 8989816935121514892
np.0x10380aa00 NXT.1700913285397123524 np->udp 0x102600a60 | destnp.0x107019000 destnp_udp.0x102600a60
Must use indirection
ONIONIZE: np.0x10380aa00 NXT.1700913285397123524 1700913285397123524 pubkey.194b9eda4e142a9 encode len.205 -> new len.261 + 42 = 303
udpsend finalbuf.307
send_transporter_ACK.({"status":"3791936988034107349 sends via 1700913285397123524 encrypted sendmessage.({"requestType":"transporter_status","status":-1,"coin":"BTCD","crc":3700449792,"value",0.10000000,"num":1}) [{"requestType":"transporter_status","status":-1,"coin":"BTCD","crc":3700449792,"value",0.10000000,"num":1}] to 8989816935121514892 pending"})
json_handler returns.(transporter_received from NXT.8989816935121514892 totalcrc.dc906200 n.1 height.47400 0.10000000 <<<<< ERROR changepod.0x0)
respond.(transporter_received from NXT.8989816935121514892 totalcrc.dc906200 n.1 height.47400 0.10000000 <<<<< ERROR changepod.0x0) to np.0x107019000 NXT.8989816935121514892
on_client_udprecv 209.126.70.170/6777 nread.404 flags.0 | total 814
got crc of 408c954b vx packet_crc 408c954b
deonionize >>>>> pubkey.194b9eda4e142a9 vs mypubkey.d4f90774a020df13 (40) -> 358 166
payload_len.358 err.0 new len.302
decrypted len.302 dest.(8463496752511744859)
deonionize >>>>> pubkey.30303731223a2273 vs mypubkey.d4f90774a020df13 (40) -> 25970 6572
mismatched len expected 26012 got 302
set UDP.0x102600a60 209.126.70.170/6777
29109850111697 pNXT_json_commands sender.(1700913285397123524) valid.1 | size.20 | command.()
respond.({"result":"pNXT_jsonhandler returns null from ([{"status":"1700913285397123524 sends direct encrypted sendmessage.(<encrypted>) [<encrypted>] to 8989816935121514892 pending"},{"token":"vb5lpi57ea2pb4cvjn7g1i2ffrso4j7p7ban3vfmhv7ftcbp9ur3s4etspfn9cg1ho7us4ptd9196rc 8qbh9sv9280ko5rvr2jnr3bjovii0562a34pfflce6d27bm7k9b8vr14h8kt596avurnduq642dq26f vq"}])"}) to np.0x10380aa00 NXT.1700913285397123524
on_client_udprecv 209.126.70.170/6777 nread.307 flags.0 | total 1218
got crc of 17cda099 vx packet_crc 17cda099
deonionize >>>>> pubkey.194b9eda4e142a9 vs mypubkey.d4f90774a020df13 (40) -> 261 105
payload_len.261 err.0 new len.205
decrypted len.205 dest.(8989816935121514892)
deonionize >>>>> pubkey.d4f90774a020df13 vs mypubkey.d4f90774a020df13 (40) -> 163 a3
payload_len.163 err.0 new len.107
decrypted2 len.107 dest.(8989816935121514892)
on_client_udprecv 209.126.70.170/6777 nread.404 flags.0 | total 1525
got crc of 81cd703a vx packet_crc 81cd703a
deonionize >>>>> pubkey.194b9eda4e142a9 vs mypubkey.d4f90774a020df13 (40) -> 358 166
payload_len.358 err.0 new len.302
decrypted len.302 dest.(8463496752511744859)
deonionize >>>>> pubkey.30303731223a2273 vs mypubkey.d4f90774a020df13 (40) -> 25970 6572
mismatched len expected 26012 got 302
set UDP.0x102600a60 209.126.70.170/6777
29109850111697 pNXT_json_commands sender.(1700913285397123524) valid.1 | size.20 | command.()
respond.({"result":"pNXT_jsonhandler returns null from ([{"status":"1700913285397123524 sends direct encrypted sendmessage.(<encrypted>) [<encrypted>] to 8989816935121514892 pending"},{"token":"vb5lpi57ea2pb4cvjn7g1i2ffrso4j7p7ban3vfmhv7ftcbp9ur4e4et8vgdjvg1t2197c3nr3ud56d 8bgl73evdcjv76a0tkmgs2tl7upk0khpqd0u73pru6m1j7fg73avdn0o20tk9chfpc3j676lgiagrdn um"}])"}) to np.0x10380aa00 NXT.1700913285397123524
testforms len 16806

***********
Wasnt that fun!

That was an edited down sequence of the SIMPLEST teleport. Well at least it was at least an attempt. The problem was that I didnt have a minipod as I am teleporting the smallest unit to myself (loopback test) and this avoids all issues of connecting to another node and hopefully simplifies the test case. It even has a mini-genetic algorithm to find the optimal set of telepods to use for the teleport request, though I am far from having an optimal metric function, at least it should give decent results to give preference to the fewer telepods with the most age.

Anyway, when I teleport to myself, I have to allocate an extra minipod, at least in this scenario. So, just as the teleporter was about to zap the white rabbit across the room, it powers down.

At least I am one step away from finding all the bugs after the telepod gets to the other side.

Just thought you would like to see why I hate debugging. I can code for literally 24+ hours straight, but debugging I usually start to lose focus after just 12 hours. So, now things have to go really well tomorrow to get the rest of the way to complete the teleport, especially as all the partial completion cases need to be dealt with. What to do with half a white rabbit on each side?

James

we feel your pain man, though most of us can only offer mental support
but I would like to read the latest paper draft too!

[CTRLX]

I want to share my pain with you


0 pNXT_json_commands sender.(8989816935121514892) valid.1 | size.20 | command.(select)
attempt privacyServer 1a79aa467ed1 209.126.70.170/6777 connect.0x0 tcp.0x0 udp.0x0
SETTING PRIVACY SERVER IPADDR.(209.126.70.170)
CONNECTED to 209.126.70.170/6777 connect.0x100f00430 tcp.0x100f01060
nxt.8989816935121514892
connect.0x100f00430 -> 0x0
udp.0x102600a60 tcp.0x100f01060 got bytes.0x100f00430 (connect) >>>>>>>>>>>>>>>>>>> got 299 bytes at 0x107000000.([{"NXT":"1700913285397123524","pubkey":"a942e1a4edb99401354eeea61ee0aad827d6ec524aa5257025a6fa0e8b91e75e","time":1407295599},{"token":"vb5lpi57ea2pb4cvjn7g1i2ffrso4j7p7ban3vfmhv7ftcbp9ur2u4etbem70501qq1mjlkn34f32cp 9osikj9qaf8ujamir90gp51511img005mpvkdqtal9al0tqcon96b03gb49cuunpn775koskakmctsk au"}]) from 209.126.70.170/6777
got crc of e4d1014e vx packet_crc 4e227b5b
signed by valid NXT.1700913285397123524 valid.1 diff.1
np.0x10380aa00 created.1 NXT.1700913285397123524 pubkey.a942e1a4edb99401354eeea61ee0aad827d6ec524aa5257025a6fa0e8b91e75e (len.32) connect.0x100f01060 sendresponse.0
process_intro got NXT.(1700913285397123524) np.0x10380aa00 <- I_am_server.0 UDP 0x0 TCP.0x100f01060 209.126.70.170/6777
set TCP.0x100f01060 209.126.70.170/6777
SETTING PRIVACY SERVER NXT ADDR.(1700913285397123524) (1700913285397123524)
json_handler returns.([{"NXT":"1700913285397123524","pubkey":"a942e1a4edb99401354eeea61ee0aad827d6ec524aa5257025a6fa0e8b91e75e","time":1407295599},{"token":"vb5lpi57ea2pb4cvjn7g1i2ffrso4j7p7ban3vfmhv7ftcbp9ur2u4etbem70501qq1mjlkn34f32cp 9osikj9qaf8ujamir90gp51511img005mpvkdqtal9al0tqcon96b03gb49cuunpn775koskakmctsk au"}])
on_client_udprecv 209.126.70.170/6777 nread.299 flags.0 | total 0
got crc of e4d1014e vx packet_crc 4e227b5b
signed by valid NXT.1700913285397123524 valid.1 diff.1
np.0x10380aa00 created.0 NXT.1700913285397123524 pubkey.a942e1a4edb99401354eeea61ee0aad827d6ec524aa5257025a6fa0e8b91e75e (len.32) connect.0x0 sendresponse.0
process_intro got NXT.(1700913285397123524) np.0x10380aa00 <- I_am_server.0 UDP 0x102600a60 TCP.0x0 209.126.70.170/6777
set UDP.0x102600a60 209.126.70.170/6777
SETTING PRIVACY SERVER NXT ADDR.(1700913285397123524) (1700913285397123524)
testforms len 16806
29109850111697 pNXT_json_commands sender.() valid.-1 | size.20 | command.(teleport)
verification valid.-1 missing for teleport sender.() vs NXT.()
replace NXT.(8989816935121514892)
29109850111697 pNXT_json_commands sender.(8989816935121514892) valid.1 | size.20 | command.(teleport)
amount.(0.10000000) minage.(10) 10
8989816935121514892 -> teleport 0.10000000 BTCD -> 8989816935121514892 minage.10
(backups/telepods/BTCD.0) update    0.10000000 height.46983    BTCD RPG2zwo3byN1EoG5U9Esgz76Pjtr2Jw1AY a4c6e70c6cce13a6986fca1b9ebdbdd209099680dd4ad9b6c82b41a630d61d15/vout_0
  load    0.10000000 height.46983    BTCD RPG2zwo3byN1EoG5U9Esgz76Pjtr2Jw1AY a4c6e70c6cce13a6986fca1b9ebdbdd209099680dd4ad9b6c82b41a630d61d15/vout_0
(backups/telepods/BTCD.1) update    0.10000000 height.46983    BTCD RFaHNNQmog8XBj7iuYnT9zJdR3ju36inBJ 8ab8b6416728596986cff9a2d5930f52017ac3ec569195a4be4a41d54f3cc19a/vout_0
  load    0.10000000 height.46983    BTCD RFaHNNQmog8XBj7iuYnT9zJdR3ju36inBJ 8ab8b6416728596986cff9a2d5930f52017ac3ec569195a4be4a41d54f3cc19a/vout_0
beg for changepod
after loaded 2 telepods
reject telepod.1 height.47400 - pod->height.46983 minage.10, ischange.1
evolve maxiters.0 with n.1
   hwm    0.10000000 height.46983    BTCD RFaHNNQmog8XBj7iuYnT9zJdR3ju36inBJ 8ab8b6416728596986cff9a2d5930f52017ac3ec569195a4be4a41d54f3cc19a/vout_0
-> evolved with bestn.1 0x106a00970
need to implement query (and propagation) mechanism for pubkeys
json_handler returns.({"error":"no pubkey for 8989816935121514892, request sent"})
testforms len 16806
NXTprotocol_json_handler.({"requestType":"teleport","secret":"xxx","dest":"8989816935121514892","amount":".1","coin":"BTCD","minage":"10"})
29109850111697 pNXT_json_commands sender.() valid.-1 | size.20 | command.(teleport)
verification valid.-1 missing for teleport sender.() vs NXT.()
replace NXT.(8989816935121514892)
29109850111697 pNXT_json_commands sender.(8989816935121514892) valid.1 | size.20 | command.(teleport)
amount.(0.10000000) minage.(10) 10
8989816935121514892 -> teleport 0.10000000 BTCD -> 8989816935121514892 minage.10
reject telepod.1 height.47400 - pod->height.46983 minage.10, ischange.1
evolve maxiters.0 with n.1
   hwm    0.10000000 height.46983    BTCD RFaHNNQmog8XBj7iuYnT9zJdR3ju36inBJ 8ab8b6416728596986cff9a2d5930f52017ac3ec569195a4be4a41d54f3cc19a/vout_0
-> evolved with bestn.1 0x102003fc0
start evolving at 28378.965000
reject telepod.1 height.47400 - pod->height.46983 minage.10, ischange.1
evolve maxiters.100000 with n.1
metric.1.998803 youngest.417 agesum 417 n 1, (10000000 - 10000000)
i.0 of 100000, replacei.0 j.0 inhwm.1
i.1 of 100000, replacei.0 j.0 inhwm.1
...
i.99 of 100000, replacei.0 j.0 inhwm.1
   hwm    0.10000000 height.46983    BTCD RFaHNNQmog8XBj7iuYnT9zJdR3ju36inBJ 8ab8b6416728596986cff9a2d5930f52017ac3ec569195a4be4a41d54f3cc19a/vout_0
-> evolved with bestn.1 0x102601200
finished evolving at 28379.517000
set np <- NXT.1700913285397123524
ONIONIZE: np.0x107019000 NXT.8989816935121514892 8989816935121514892 pubkey.d4f90774a020df13 encode len.315 -> new len.371 + 42 = 413
sendmessage ([{"requestType":"transporter","coin":"BTCD","height":47400,"minage":10,"value":"0.10000000","telepods":["1489107942"],"totalcrc":3700449792},{"token":"d79fth95u83cu087m4js5pr7oqktvg537dctmf7sclmv3thq9ur40bpgi2bit301md2ijtcqb6g01tg d8fmsklgccgere9j8au65d3skqop0hm9nntm9o14uaocg6ft0ibdna069fkvimrfj2991dcah753nr7 3c"}]) len.316 to 8989816935121514892
np.0x10380aa00 NXT.1700913285397123524 np->udp 0x102600a60 | destnp.0x107019000 destnp_udp.0x0
Must use indirection
ONIONIZE: np.0x10380aa00 NXT.1700913285397123524 1700913285397123524 pubkey.194b9eda4e142a9 encode len.413 -> new len.469 + 42 = 511
udpsend finalbuf.515
sendandfree_jsonmessage.({"status":"8989816935121514892 sends via 1700913285397123524 encrypted sendmessage.([{"requestType":"transporter","coin":"BTCD","height":47400,"minage":10,"value":"0.10000000","telepods":["1489107942"],"totalcrc":3700449792},{"token":"d79fth95u83cu087m4js5pr7oqktvg537dctmf7sclmv3thq9ur40bpgi2bit301md2ijtcqb6g01tg d8fmsklgccgere9j8au65d3skqop0hm9nntm9o14uaocg6ft0ibdna069fkvimrfj2991dcah753nr7 3c"}]) [[{"requestType":"transporter","coin":"BTCD","height":47400,"minage":10,"value":"0.10000000","telepods":["1489107942"],"totalcrc":3700449792},{"token":"d79fth95u83cu087m4js5pr7oqktvg537dctmf7sclmv3thq9ur40bpgi2bit301md2ijtcqb6g01tg d8fmsklgccgere9j8au65d3skqop0hm9nntm9o14uaocg6ft0ibdna069fkvimrfj2991dcah753nr7 3c"}]] to 8989816935121514892 pending"})
json_handler returns.({"error":"sendandfree_jsonmessage telepod bundle failure for 0.10000000 BTCD to 8989816935121514892"})
on_client_udprecv 209.126.70.170/6777 nread.515 flags.0 | total 299
got crc of 6bb3c525 vx packet_crc 6bb3c525
deonionize >>>>> pubkey.194b9eda4e142a9 vs mypubkey.d4f90774a020df13 (40) -> 469 1d5
payload_len.469 err.0 new len.413
decrypted len.413 dest.(8989816935121514892)
deonionize >>>>> pubkey.d4f90774a020df13 vs mypubkey.d4f90774a020df13 (40) -> 371 173
payload_len.371 err.0 new len.315
decrypted2 len.315 dest.(8989816935121514892)
set UDP.0x102600a60 209.126.70.170/6777
29109850111697 pNXT_json_commands sender.(8989816935121514892) valid.1 | size.20 | command.(transporter)
make_traceable_telepod 0.10000000
got podaddr.(RHEXHztke1hZ5NSAxKHCproTsind934Sjc) privkey.0x102600640
args.(["transporter","RHEXHztke1hZ5NSAxKHCproTsind934Sjc",0.10000000])
check (backups/telepods/BTCD.2)
(backups/telepods/BTCD.2) update    0.10000000 height.47400    BTCD RHEXHztke1hZ5NSAxKHCproTsind934Sjc f166d4711537702a46994d1a78b01d2c7d083e668264b3efe6fc83f6fda2bbf9/vout_0
create    0.10000000 height.47400    BTCD RHEXHztke1hZ5NSAxKHCproTsind934Sjc f166d4711537702a46994d1a78b01d2c7d083e668264b3efe6fc83f6fda2bbf9/vout_0
make_traceable_telepod 0.10000000
got podaddr.(RKbPodL1GaBeyHydaAhvX286FAPDLw8ZhJ) privkey.0x106a01e40
args.(["transporter","RKbPodL1GaBeyHydaAhvX286FAPDLw8ZhJ",0.10000000])
check (backups/telepods/BTCD.3)
(backups/telepods/BTCD.3) update    0.10000000 height.47400    BTCD RKbPodL1GaBeyHydaAhvX286FAPDLw8ZhJ 07d22536a9869cac5d856c127893e89c2194f6c5bf22440c05f91f1c55f24fdb/vout_0
create    0.10000000 height.47400    BTCD RKbPodL1GaBeyHydaAhvX286FAPDLw8ZhJ 07d22536a9869cac5d856c127893e89c2194f6c5bf22440c05f91f1c55f24fdb/vout_0
set np <- NXT.1700913285397123524
ONIONIZE: np.0x107019000 NXT.8989816935121514892 8989816935121514892 pubkey.d4f90774a020df13 encode len.107 -> new len.163 + 42 = 205
sendmessage ({"requestType":"transporter_status","status":-1,"coin":"BTCD","crc":3700449792,"value",0.10000000,"num":1}) len.107 to 8989816935121514892
np.0x10380aa00 NXT.1700913285397123524 np->udp 0x102600a60 | destnp.0x107019000 destnp_udp.0x102600a60
Must use indirection
ONIONIZE: np.0x10380aa00 NXT.1700913285397123524 1700913285397123524 pubkey.194b9eda4e142a9 encode len.205 -> new len.261 + 42 = 303
udpsend finalbuf.307
send_transporter_ACK.({"status":"3791936988034107349 sends via 1700913285397123524 encrypted sendmessage.({"requestType":"transporter_status","status":-1,"coin":"BTCD","crc":3700449792,"value",0.10000000,"num":1}) [{"requestType":"transporter_status","status":-1,"coin":"BTCD","crc":3700449792,"value",0.10000000,"num":1}] to 8989816935121514892 pending"})
json_handler returns.(transporter_received from NXT.8989816935121514892 totalcrc.dc906200 n.1 height.47400 0.10000000 <<<<< ERROR changepod.0x0)
respond.(transporter_received from NXT.8989816935121514892 totalcrc.dc906200 n.1 height.47400 0.10000000 <<<<< ERROR changepod.0x0) to np.0x107019000 NXT.8989816935121514892
on_client_udprecv 209.126.70.170/6777 nread.404 flags.0 | total 814
got crc of 408c954b vx packet_crc 408c954b
deonionize >>>>> pubkey.194b9eda4e142a9 vs mypubkey.d4f90774a020df13 (40) -> 358 166
payload_len.358 err.0 new len.302
decrypted len.302 dest.(8463496752511744859)
deonionize >>>>> pubkey.30303731223a2273 vs mypubkey.d4f90774a020df13 (40) -> 25970 6572
mismatched len expected 26012 got 302
set UDP.0x102600a60 209.126.70.170/6777
29109850111697 pNXT_json_commands sender.(1700913285397123524) valid.1 | size.20 | command.()
respond.({"result":"pNXT_jsonhandler returns null from ([{"status":"1700913285397123524 sends direct encrypted sendmessage.(<encrypted>) [<encrypted>] to 8989816935121514892 pending"},{"token":"vb5lpi57ea2pb4cvjn7g1i2ffrso4j7p7ban3vfmhv7ftcbp9ur3s4etspfn9cg1ho7us4ptd9196rc 8qbh9sv9280ko5rvr2jnr3bjovii0562a34pfflce6d27bm7k9b8vr14h8kt596avurnduq642dq26f vq"}])"}) to np.0x10380aa00 NXT.1700913285397123524
on_client_udprecv 209.126.70.170/6777 nread.307 flags.0 | total 1218
got crc of 17cda099 vx packet_crc 17cda099
deonionize >>>>> pubkey.194b9eda4e142a9 vs mypubkey.d4f90774a020df13 (40) -> 261 105
payload_len.261 err.0 new len.205
decrypted len.205 dest.(8989816935121514892)
deonionize >>>>> pubkey.d4f90774a020df13 vs mypubkey.d4f90774a020df13 (40) -> 163 a3
payload_len.163 err.0 new len.107
decrypted2 len.107 dest.(8989816935121514892)
on_client_udprecv 209.126.70.170/6777 nread.404 flags.0 | total 1525
got crc of 81cd703a vx packet_crc 81cd703a
deonionize >>>>> pubkey.194b9eda4e142a9 vs mypubkey.d4f90774a020df13 (40) -> 358 166
payload_len.358 err.0 new len.302
decrypted len.302 dest.(8463496752511744859)
deonionize >>>>> pubkey.30303731223a2273 vs mypubkey.d4f90774a020df13 (40) -> 25970 6572
mismatched len expected 26012 got 302
set UDP.0x102600a60 209.126.70.170/6777
29109850111697 pNXT_json_commands sender.(1700913285397123524) valid.1 | size.20 | command.()
respond.({"result":"pNXT_jsonhandler returns null from ([{"status":"1700913285397123524 sends direct encrypted sendmessage.(<encrypted>) [<encrypted>] to 8989816935121514892 pending"},{"token":"vb5lpi57ea2pb4cvjn7g1i2ffrso4j7p7ban3vfmhv7ftcbp9ur4e4et8vgdjvg1t2197c3nr3ud56d 8bgl73evdcjv76a0tkmgs2tl7upk0khpqd0u73pru6m1j7fg73avdn0o20tk9chfpc3j676lgiagrdn um"}])"}) to np.0x10380aa00 NXT.1700913285397123524
testforms len 16806

***********
Wasnt that fun!

That was an edited down sequence of the SIMPLEST teleport. Well at least it was at least an attempt. The problem was that I didnt have a minipod as I am teleporting the smallest unit to myself (loopback test) and this avoids all issues of connecting to another node and hopefully simplifies the test case. It even has a mini-genetic algorithm to find the optimal set of telepods to use for the teleport request, though I am far from having an optimal metric function, at least it should give decent results to give preference to the fewer telepods with the most age.

Anyway, when I teleport to myself, I have to allocate an extra minipod, at least in this scenario. So, just as the teleporter was about to zap the white rabbit across the room, it powers down.

At least I am one step away from finding all the bugs after the telepod gets to the other side.

Just thought you would like to see why I hate debugging. I can code for literally 24+ hours straight, but debugging I usually start to lose focus after just 12 hours. So, now things have to go really well tomorrow to get the rest of the way to complete the teleport, especially as all the partial completion cases need to be dealt with. What to do with half a white rabbit on each side?

James

Somehow this post reminded me of this : https://www.youtube.com/watch?v=6wn1T_JUJMY Keep on trucking James, I admire your work.

[XNext]

I want to share my pain with you
James

What is the matter?

[pvnamk19]

I am addicted to read James's "sci-fi" posts.
I don't understand most of his tech-ideas, just guess and decide to buy, hold or sell     

[Trinibits]

I am addicted to read James's "sci-fi" posts.
I don't understand most of his tech-ideas, just guess and decide to buy, hold or sell     

Me too but it makes me keep buying 

[jeezy]

OK, a bit ahead of schedule. I issued the the anon card asset today!

Current price ratio BTCD/NXT is ~27:1 so 25000 BTCD is matched by 675000 NXT, which makes its sale price = 1.35 NXT per asset

The following is the asset description, very short and generic:
Issuer ID: NXT-KKNV-8EPK-W2S4-96VTK Asset number 7110939398145553585

###
NXTprivacy is proud to issue the cryptocard asset which will distribute 1% of processed transaction volumes to the assetholders. This card does not require any personal information. All of the processing and handling is outsourced to coinomat.com. Please check NXTprivacy.org for the latest details on fees and limits. Standard ATM fees will apply for cash withdrawals.
###

The initial text for the NXTprivacy.org site is:

###
We're launching debit card program for easy withdrawal of NXT and BitcoinDark funds through ATM's worldwide and online payments.

Key facts:

- The card is issued by a European bank with a good card programs track record
- This a no-name card; we would need your address for card shipment though
- Card issuance and delivery cost $40 and naturally can be paid in NXT or BTCD
- The monthly transaction volume with one card is limited by $10,000. Multiple cards can be ordered
- Online payments using the card are free, withdrawal fee through ATM is charged by the issuing bank and is 3%
- NXT and BTCD conversion is made according to the current respective exchange rates.
- Processing is carried out by coinomat.com exchange service.

The card will be launched in September 2014.

Our goal in making this card program is to provide an easy bridge for crypto to fiat conversion. In future withdrawal of other cryptos, including Bitcoin, will be possible.
###

So, what we need is to get the NXT account #'s that correspond to the people that donated. And noashh (who has helped me before) has volunteered to coordinate this to save me time. So get your NXT acct (make sure to use high entropy password) to icecoldtommy.

Once it is distributed, then it could start trading on NXT AE, actually nobody can stop this, so it should have some immediate liquidity. Plz dont complain the NXTprivacy.org site is not ready yet, this all came together much faster than expected thanks to awesome BTCD community!

James

P.S. For those worried about the need for postal address, we will also be arranging having the cards available at tradeshows for a cash basis, so you can meetup with the NXT booth and pay cash and grab a random card from the box of pre-issued cards. Then register the number at public internet shop.

This is so awesome, thanks for your hard work guys! You really are doing great things for cryptocoins around the world.

[clovis A.]

Updated darkpaper available for any BTCD regulars to preview

James

I'll take a look, please. 

Edit:  very sneaky what you did there

Hope you like the pirates

Tried to make it both understandable to normal peoples, but still have technical depth

And that's not always easy to do.... Going to have to read this in more detail, but I like what I'm reading.  Unfortunately, I just got called out to work.... time to go fix some cellular LTE technology.....  too bad I can't teleport there 

Do you work for a carrier?
I am in the same industry.

Sure do, I'm a Field Engineer with Sprint and Clearwire

[jl777]

Some of you probably have wondered how to use NXT in the context of the BTCD functions. In order to use NXT you need to just install the standard NXT software (from nxtforum.org or nxt.org), but after that you need a NXT acct number and with NXT your password is your account. So you must have a high entropy password.

It just so happens that there is a way to bind a BTCD address to a NXT address and to know you have a high entropy password.

I suggest to make a new BTCD address just to keep things compartmentalized. This will be your public address and maybe you never even use it, that way it is only tied to you as the "post office box" number that people send to you, but with Teleport it doesnt arrive at your published address, you will get telepods.

So, back to the NXT linkage. Just do a:
dumpprivkey <BTCD public address>

This will spit out a bunch of letters and numbers. If you have any significant amount of value associated with that address, guard this number carefully! It will allow anybody that gets it to access your BTCD funds, but if it is just a public address with no funds, then not much to worry about. However, if you cut and paste from the debug window of your wallet into the NXT wallet and login, you will get a NXT acct number. This will be your <NXT public address> and you can use it for a normal NXT account without worry that it can be directly linked to your BTCD public acct (unless of course you publish both)

So, if you end up using the NXT account for signficant value, then dont be saving the password in a text file!
Since you can always generate it from your wallet's debug window via "dumpprivkey" as long as you have regular backups of your BTCD wallet, your NXT password is always there.
Nothing prevents you from making private addresses that are never published and having them also linked.

James

[cloudboy]

Some of you probably have wondered how to use NXT in the context of the BTCD functions. In order to use NXT you need to just install the standard NXT software (from nxtforum.org or nxt.org), but after that you need a NXT acct number and with NXT your password is your account. So you must have a high entropy password.

It just so happens that there is a way to bind a BTCD address to a NXT address and to know you have a high entropy password.

I suggest to make a new BTCD address just to keep things compartmentalized. This will be your public address and maybe you never even use it, that way it is only tied to you as the "post office box" number that people send to you, but with Teleport it doesnt arrive at your published address, you will get telepods.

So, back to the NXT linkage. Just do a:
dumpprivkey <BTCD public address>

This will spit out a bunch of letters and numbers. If you have any significant amount of value associated with that address, guard this number carefully! It will allow anybody that gets it to access your BTCD funds, but if it is just a public address with no funds, then not much to worry about. However, if you cut and paste from the debug window of your wallet into the NXT wallet and login, you will get a NXT acct number. This will be your <NXT public address> and you can use it for a normal NXT account without worry that it can be directly linked to your BTCD public acct (unless of course you publish both)

So, if you end up using the NXT account for signficant value, then dont be saving the password in a text file!
Since you can always generate it from your wallet's debug window via "dumpprivkey" as long as you have regular backups of your BTCD wallet, your NXT password is always there.
Nothing prevents you from making private addresses that are never published and having them also linked.

James

Good idea, I suggest everyone do this. I installed NXT client last night and am loving it. This effectively makes your BTCD private key the private key for your NXT address as well.

[jl777]

Some of you probably have wondered how to use NXT in the context of the BTCD functions. In order to use NXT you need to just install the standard NXT software (from nxtforum.org or nxt.org), but after that you need a NXT acct number and with NXT your password is your account. So you must have a high entropy password.

It just so happens that there is a way to bind a BTCD address to a NXT address and to know you have a high entropy password.

I suggest to make a new BTCD address just to keep things compartmentalized. This will be your public address and maybe you never even use it, that way it is only tied to you as the "post office box" number that people send to you, but with Teleport it doesnt arrive at your published address, you will get telepods.

So, back to the NXT linkage. Just do a:
dumpprivkey <BTCD public address>

This will spit out a bunch of letters and numbers. If you have any significant amount of value associated with that address, guard this number carefully! It will allow anybody that gets it to access your BTCD funds, but if it is just a public address with no funds, then not much to worry about. However, if you cut and paste from the debug window of your wallet into the NXT wallet and login, you will get a NXT acct number. This will be your <NXT public address> and you can use it for a normal NXT account without worry that it can be directly linked to your BTCD public acct (unless of course you publish both)

So, if you end up using the NXT account for signficant value, then dont be saving the password in a text file!
Since you can always generate it from your wallet's debug window via "dumpprivkey" as long as you have regular backups of your BTCD wallet, your NXT password is always there.
Nothing prevents you from making private addresses that are never published and having them also linked.

James

Good idea, I suggest everyone do this. I installed NXT client last night and am loving it. This effectively makes your BTCD private key the private key for your NXT address as well.

Now we just need a HTML5 GUI guy to reskin the NXT GUI into BTCD GUI and we can transparently deal with the NXT account. I am thinking the basic BTCD-qt can have a button to push that opens a browser to the right page and automatically logs in with the designated BTCD address.

I bit of a klunky two step, but at least it will be push button automated into a logged in NXT acct. You will need to beg for a few NXT before you can do anything, but there is a faucet and once you get even a few NXT you can use AE to sell stuff and get more NXT

I suggest a small bounty fund to pay for GUI dev as otherwise we will have Teleport working via commandline that most people wont be able to use. We need some mods to the QT and a reskin of the NXT GUI, the latter is more work I am sure. I have no idea of what sort of budget is required. But I think even 1000 BTCD will be enough to get some contractor to do the QT changes. Maybe 2500 BTCD for the reskinned NXT GUI?

So, now imagine BTCD having not only super awesome Teleport, but state of the art reskinned gen 2 GUI with all of NXT features! NXT will be under the hood for AE and other things, but this is like "white label" (I think that is the term), the brand that presents the features gets the user cred. Think about Intel CPU, customers might care a bit about the CPU and it is certainly important, but the big computer brands like Apple are using the CPU tech, but creating a user experience brand.

Any cut and paste monkey can make a NXT clone (and there are many!), but nobody has done this "white label" thing yet. This is a bit out of my expertise, I hope there are peoples here that can take on this task of designing the reskinned GUI and then we can find contractor to do it if nobody picks up the bounty.

All I know is we cant wait for this to happen. Somebody has to make it happen. With the darkpaper draft, you should be able to see what sorts of functions the GUI needs

volunteers for GUI team?

James

[cloudboy]

Some of you probably have wondered how to use NXT in the context of the BTCD functions. In order to use NXT you need to just install the standard NXT software (from nxtforum.org or nxt.org), but after that you need a NXT acct number and with NXT your password is your account. So you must have a high entropy password.

It just so happens that there is a way to bind a BTCD address to a NXT address and to know you have a high entropy password.

I suggest to make a new BTCD address just to keep things compartmentalized. This will be your public address and maybe you never even use it, that way it is only tied to you as the "post office box" number that people send to you, but with Teleport it doesnt arrive at your published address, you will get telepods.

So, back to the NXT linkage. Just do a:
dumpprivkey <BTCD public address>

This will spit out a bunch of letters and numbers. If you have any significant amount of value associated with that address, guard this number carefully! It will allow anybody that gets it to access your BTCD funds, but if it is just a public address with no funds, then not much to worry about. However, if you cut and paste from the debug window of your wallet into the NXT wallet and login, you will get a NXT acct number. This will be your <NXT public address> and you can use it for a normal NXT account without worry that it can be directly linked to your BTCD public acct (unless of course you publish both)

So, if you end up using the NXT account for signficant value, then dont be saving the password in a text file!
Since you can always generate it from your wallet's debug window via "dumpprivkey" as long as you have regular backups of your BTCD wallet, your NXT password is always there.
Nothing prevents you from making private addresses that are never published and having them also linked.

James

Good idea, I suggest everyone do this. I installed NXT client last night and am loving it. This effectively makes your BTCD private key the private key for your NXT address as well.

Now we just need a HTML5 GUI guy to reskin the NXT GUI into BTCD GUI and we can transparently deal with the NXT account. I am thinking the basic BTCD-qt can have a button to push that opens a browser to the right page and automatically logs in with the designated BTCD address.

I bit of a klunky two step, but at least it will be push button automated into a logged in NXT acct. You will need to beg for a few NXT before you can do anything, but there is a faucet and once you get even a few NXT you can use AE to sell stuff and get more NXT

I suggest a small bounty fund to pay for GUI dev as otherwise we will have Teleport working via commandline that most people wont be able to use. We need some mods to the QT and a reskin of the NXT GUI, the latter is more work I am sure. I have no idea of what sort of budget is required. But I think even 1000 BTCD will be enough to get some contractor to do the QT changes. Maybe 2500 BTCD for the reskinned NXT GUI?

So, now imagine BTCD having not only super awesome Teleport, but state of the art reskinned gen 2 GUI with all of NXT features! NXT will be under the hood for AE and other things, but this is like "white label" (I think that is the term), the brand that presents the features gets the user cred. Think about Intel CPU, customers might care a bit about the CPU and it is certainly important, but the big computer brands like Apple are using the CPU tech, but creating a user experience brand.

Any cut and paste monkey can make a NXT clone (and there are many!), but nobody has done this "white label" thing yet. This is a bit out of my expertise, I hope there are peoples here that can take on this task of designing the reskinned GUI and then we can find contractor to do it if nobody picks up the bounty.

All I know is we cant wait for this to happen. Somebody has to make it happen. With the darkpaper draft, you should be able to see what sorts of functions the GUI needs

volunteers for GUI team?

James

I'm a little confused. The QT designer will add Teleport button and form, etc. The HTML5 guy will do what? NXT GUI is designed in HTML?

[jl777]

Some of you probably have wondered how to use NXT in the context of the BTCD functions. In order to use NXT you need to just install the standard NXT software (from nxtforum.org or nxt.org), but after that you need a NXT acct number and with NXT your password is your account. So you must have a high entropy password.

It just so happens that there is a way to bind a BTCD address to a NXT address and to know you have a high entropy password.

I suggest to make a new BTCD address just to keep things compartmentalized. This will be your public address and maybe you never even use it, that way it is only tied to you as the "post office box" number that people send to you, but with Teleport it doesnt arrive at your published address, you will get telepods.

So, back to the NXT linkage. Just do a:
dumpprivkey <BTCD public address>

This will spit out a bunch of letters and numbers. If you have any significant amount of value associated with that address, guard this number carefully! It will allow anybody that gets it to access your BTCD funds, but if it is just a public address with no funds, then not much to worry about. However, if you cut and paste from the debug window of your wallet into the NXT wallet and login, you will get a NXT acct number. This will be your <NXT public address> and you can use it for a normal NXT account without worry that it can be directly linked to your BTCD public acct (unless of course you publish both)

So, if you end up using the NXT account for signficant value, then dont be saving the password in a text file!
Since you can always generate it from your wallet's debug window via "dumpprivkey" as long as you have regular backups of your BTCD wallet, your NXT password is always there.
Nothing prevents you from making private addresses that are never published and having them also linked.

James

Good idea, I suggest everyone do this. I installed NXT client last night and am loving it. This effectively makes your BTCD private key the private key for your NXT address as well.

Now we just need a HTML5 GUI guy to reskin the NXT GUI into BTCD GUI and we can transparently deal with the NXT account. I am thinking the basic BTCD-qt can have a button to push that opens a browser to the right page and automatically logs in with the designated BTCD address.

I bit of a klunky two step, but at least it will be push button automated into a logged in NXT acct. You will need to beg for a few NXT before you can do anything, but there is a faucet and once you get even a few NXT you can use AE to sell stuff and get more NXT

I suggest a small bounty fund to pay for GUI dev as otherwise we will have Teleport working via commandline that most people wont be able to use. We need some mods to the QT and a reskin of the NXT GUI, the latter is more work I am sure. I have no idea of what sort of budget is required. But I think even 1000 BTCD will be enough to get some contractor to do the QT changes. Maybe 2500 BTCD for the reskinned NXT GUI?

So, now imagine BTCD having not only super awesome Teleport, but state of the art reskinned gen 2 GUI with all of NXT features! NXT will be under the hood for AE and other things, but this is like "white label" (I think that is the term), the brand that presents the features gets the user cred. Think about Intel CPU, customers might care a bit about the CPU and it is certainly important, but the big computer brands like Apple are using the CPU tech, but creating a user experience brand.

Any cut and paste monkey can make a NXT clone (and there are many!), but nobody has done this "white label" thing yet. This is a bit out of my expertise, I hope there are peoples here that can take on this task of designing the reskinned GUI and then we can find contractor to do it if nobody picks up the bounty.

All I know is we cant wait for this to happen. Somebody has to make it happen. With the darkpaper draft, you should be able to see what sorts of functions the GUI needs

volunteers for GUI team?

James

I'm a little confused. The QT designer will add Teleport button and form, etc. The HTML5 guy will do what? NXT GUI is designed in HTML?

The QT will add basic functions for Teleport and managing telepods, but for things like InstantDEX we need to use the NXT GUI as a starting point. NXT GUI is totally HTML and runs in a browser talking to localhost (127.0.0.1:7876) so it is totally client side, but it looks like an active website.

If you use the NXT GUI you will understand, it cannot be compared to any QT wallet. So I need people with user interface experience to look at what NXT GUI is now and then think through what it could be as a reskinned BTCD GUI with "NXT inside"

It is like HDTV bigscreen vs. old black and white TV, well the difference is even more. Words cant describe

James

[cloudboy]

Looks like yesterdays' Bittrex manipulator is back. Suddenly there are 450 BTCD buy orders in the top 50 orders...

[ralexvalex]

The QT will add basic functions for Teleport and managing telepods, but for things like InstantDEX we need to use the NXT GUI as a starting point. NXT GUI is totally HTML and runs in a browser talking to localhost (127.0.0.1:7876) so it is totally client side, but it looks like an active website.

If you use the NXT GUI you will understand, it cannot be compared to any QT wallet. So I need people with user interface experience to look at what NXT GUI is now and then think through what it could be as a reskinned BTCD GUI with "NXT inside"

It is like HDTV bigscreen vs. old black and white TV, well the difference is even more. Words cant describe

James

Thanks James, you'r the man.

How about contacting original NXT GUI guys? Can they help?

[jl777]

The QT will add basic functions for Teleport and managing telepods, but for things like InstantDEX we need to use the NXT GUI as a starting point. NXT GUI is totally HTML and runs in a browser talking to localhost (127.0.0.1:7876) so it is totally client side, but it looks like an active website.

If you use the NXT GUI you will understand, it cannot be compared to any QT wallet. So I need people with user interface experience to look at what NXT GUI is now and then think through what it could be as a reskinned BTCD GUI with "NXT inside"

It is like HDTV bigscreen vs. old black and white TV, well the difference is even more. Words cant describe

James

Thanks James, you'r the man.

How about contacting original NXT GUI guys? Can they help?

They are already helping as much as they can, one is doing InstantDEX GUI another Privatebet GUI, need more GUI guys. I seem to have too many magic API's that need them

[PilotofBTC]

The QT will add basic functions for Teleport and managing telepods, but for things like InstantDEX we need to use the NXT GUI as a starting point. NXT GUI is totally HTML and runs in a browser talking to localhost (127.0.0.1:7876) so it is totally client side, but it looks like an active website.

If you use the NXT GUI you will understand, it cannot be compared to any QT wallet. So I need people with user interface experience to look at what NXT GUI is now and then think through what it could be as a reskinned BTCD GUI with "NXT inside"

It is like HDTV bigscreen vs. old black and white TV, well the difference is even more. Words cant describe

James

Thanks James, you'r the man.

How about contacting original NXT GUI guys? Can they help?

They are already helping as much as they can, one is doing InstantDEX GUI another Privatebet GUI, need more GUI guys. I seem to have too many magic API's that need them

I'm happy to help with HTML5/CSS/Javascript coding for BTCD. Let me know what you need. you can contact my via PM if you want.

[jl777]

The QT will add basic functions for Teleport and managing telepods, but for things like InstantDEX we need to use the NXT GUI as a starting point. NXT GUI is totally HTML and runs in a browser talking to localhost (127.0.0.1:7876) so it is totally client side, but it looks like an active website.

If you use the NXT GUI you will understand, it cannot be compared to any QT wallet. So I need people with user interface experience to look at what NXT GUI is now and then think through what it could be as a reskinned BTCD GUI with "NXT inside"

It is like HDTV bigscreen vs. old black and white TV, well the difference is even more. Words cant describe

James

Thanks James, you'r the man.

How about contacting original NXT GUI guys? Can they help?

They are already helping as much as they can, one is doing InstantDEX GUI another Privatebet GUI, need more GUI guys. I seem to have too many magic API's that need them

I'm happy to help with HTML5/CSS/Javascript coding for BTCD. Let me know what you need. you can contact my via PM if you want.

First step get the reference NXT code from nxt.org and get familiar with the HTML
Then update with https://nxtforum.org/nxtservices-releases/multigateway-ui/
This has code that talks to my :7777 API

So with that, you can see how to go from universal webpage to my API
Then we need graphics peoples to see what sort of thing can be done with making it look BTCD
And GUI designer to come up with the right pages/buttons, etc. to be implemented

James

[jl777]

Looks like yesterdays' Bittrex manipulator is back. Suddenly there are 450 BTCD buy orders in the top 50 orders...

We are getting very close to alltime highs, so games are expected

what other coin has ever recovered back to pump level alltime highs within 2 weeks!?
We had volumes close to LTC volumes during that pump and dump. To get slammed down to one third of peak prices usually really hurts a coin.

It just let me get a bunch more BTCD

So, with anon card, Teleport, new QT, new HTML GUI, all still "insider" info to this thread and of course no recent press coverage at all, my prediction of Top 10 coinmarketcap appears to be not so crazy

James

[salsacz]

Don't forget about the Bitsofproof wallet. Create this and getting BTCD on the Trezor will be very easy

yes, Trezor already supports altcoins. the only reason why it is not working yet is a lazyness of the altcoin-devs.

There needs to be a client with BIP 32 support - https://bitsofproof.com/?page_id=323 / block explorer. This already works for Bitcoin so it should be easy to make it for BTCD and merge the Trezor/Card into one package