Advertisement
Guest User

Untitled

a guest
Aug 25th, 2014
826
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 26.22 KB | None | 0 0
  1. <aaaaaa> Welcome miester jl777
  2. <aaaaaa> So whats the news is this a trustless system?
  3. <bbbbbb_> is this were the btcd talk is at? :D
  4. <aaaaaa> No this is the pokemon channel?
  5. <aaaaaa> Jokes. Yep
  6. <jl777> yes I hear some claims that surprise me
  7. <bbbbbb_> lol
  8. <bbbbbb_> I get jokes
  9. <aaaaaa> Ok so
  10. <ccccc> Jl777 gggggg's concern is that the BTCD system is not truustless
  11. <aaaaaa> Shal we commence
  12. <sdgsdg> i heard bitcoin is a scam
  13. <jl777> where is the trust point?
  14. <eee> who is jl777 i hear many people like him
  15. <ccccc> he may be a bit distracted right now he said he is reading the thread
  16. <aaaaaa> gggggg how can you throw around such horrible accusations
  17. <bbbbbb_> So here's whats going on. I'm in talk with investors right
  18. now. We were leaning towards buying an asic farm to mine/rent. If we
  19. can get a project together I would have no problem getting an llc
  20. wrote up. So far we have around 200k usd ready to invest.
  21. <fffffffff> no poiint in fearing ascics, coins that do will fail
  22. <bbbbbb_> Just throwing that out there for this new project
  23. <jl777> now I am adding trusted teleporting, this actually really
  24. improves privacy levels, but it is only for usage between people that
  25. trust each other.
  26. <gggggg> as far as i can see, its a diversion of the basic coinjoin
  27. concept, just instead of transporting coins through a node, you
  28. transport them through a pod
  29. <eee> is jl777 a btcd dev
  30. <jl777> I am still working to improve the entry into the teleport
  31. system, I am expecting there will be vendors of aged telepods who wont
  32. care that they are identified as injecting funds into the teleport
  33. economy
  34. <4456456> eee: seems so, and his ip hosts the darkpaper pdf.
  35. <eee> noice
  36. <ccccc> it is def jl777 : -)
  37. <jl777> hello gggggg! long time
  38. <gggggg> jl777: so its a trusted system.. entry and exit are traceable
  39. <jl777> teleport is not coinjoin at all
  40. <gggggg> yeah long time no see btw jl777 :-p
  41. <jl777> you are not needing to trust the creator of a telepod
  42. <jl777> now there are cloning events visible on the blockchain
  43. <jl777> however, it all traces back to the creator
  44. <jl777> so extraction from teleport system is another vulnerability,
  45. that is why we are making anon debit card, just send funds out to
  46. debit card
  47. <jl777> they can trace it to a debit card number, but nobody knows who
  48. has the debit card
  49. <jl777> alternatively you can sell it back to the original creator,
  50. this would create a transaction loop that goes back to the one that
  51. created it
  52. <gggggg> so, the transportation is for moving coins off the
  53. blockchain, and onto debit cards?
  54. <jl777> the people who had it during the loop are not linked
  55. <jl777> Imagine a poker game
  56. <jl777> you make chips (telepods)
  57. <4456456> But they must be linked if they want to spend on-chain, right ?
  58. <gggggg> yes
  59. <jl777> you are winning and losing chips and this is all happening off chain
  60. <jl777> you can spend a telepod without going on chain if you can find
  61. someone who will accept it!
  62. <jl777> I think this is the key, to create efficient offchain
  63. tradings, eg. gambling, market swaps, etc
  64. <gggggg> so there is the trick
  65. <jl777> of course eventually you will want to use it in the "real"
  66. crypto universe or even the "real" world, so there is the anon card
  67. for real world and tradebots for public crypto
  68. <4456456> jl777: imagine I want to use your telepod system to mask my
  69. transaction of BTC.
  70. <gggggg> use the pods for moving things out of chain, to be spendable
  71. on other places, debit cards etc... then when the coins are moved
  72. back, they belong to someone different
  73. <gggggg> correct*?
  74. <4456456> How is using your system different from me buying LTC,
  75. transacting on the LTC blockchain with someone, and that someone
  76. selling for BTC ?
  77. <jl777> it is different
  78. <jl777> let me try to explain
  79. <jl777> ok, currently when you spend it creates public record on the blockchain
  80. <jl777> the moment you spend
  81. <jl777> so this is subject to timing analysis
  82. <jl777> it is found out you sent X amount of BTC at noon
  83. <jl777> look on the blockchain and there is the X BTC at noon, so now
  84. we found out both your acct # and the destination acct#
  85. <jl777> teleport avoids this timing analysis attack
  86. <gggggg> because they will stay off the chain until someone brings
  87. them back, either the owner, or the new owner..
  88. <4456456> So, as a recipient, you can choose when to redeem, or
  89. alternatively respend it as teleport to someone else. Right ?
  90. <jl777> they are actually verified using the blockchain (other than
  91. trusted teleports) but there is no linkage of the cloned telepod to
  92. you
  93. <eee> i can see this working well with tumblers
  94. <jl777> yes! that's right. the timing of the public event (cloning) is
  95. up to the receiver. there is a clonesmear parameter that you set and
  96. it happens randomly in that timeframe
  97. <eee> ex a service that has a lot of btcd and acts as anonymization
  98. <jl777> yes
  99. <eee> it will be proprietery but it will be 100% anon
  100. <jl777> combining existing anon coins, mixers, etc. to fund the
  101. creation of the telepod is perfect!
  102. <eee> unless jl777 you ahve a plan to fix that?
  103. <jl777> even if it is unraveled, then all the clonings are private
  104. <4456456> jl777: how do you prevent double spending ? "handshakes"
  105. were mentioned.
  106. <jl777> I do have plans to improve the telepod creation with automated tradebots
  107. <jl777> well if the sender spends before the receiver clones, the
  108. receiver first off gets a bit upset, but more importantly just doesnt
  109. credit the acct. it is like writing a check to someone, then putting a
  110. stop payment. not nice, but no money lost
  111. <jl777> eee: anybody can create telepods, I think that makes it
  112. non-proprietary and decentralized
  113. <4456456> How so ? If you put a stop after taking whatever you were
  114. buying... Fail, no ?
  115. <eee> noice
  116. <jl777> 4456456: the seller should not deliver until all funds
  117. transferred. that is common sense isnt it?
  118. <gggggg> you need a mathematical proof to create money that depends on
  119. the original
  120. <jl777> or maybe partial delivery as the telepods are cloned
  121. <4456456> Funds transferred, here, meaning redeemed to the coin
  122. blockchain (eg, BTC) ?
  123. <jl777> gggggg: I think BTC blockchain is proof good enough for most people
  124. <gggggg> it still depends on trust
  125. <aaaaaa> Uh oh
  126. <jl777> 4456456: yes cloning transfers the value to 100% destination
  127. control, it is a public event on blockchain, but only links back all
  128. the way to the original creator, which maybe used mixers, etc
  129. <4456456> Then, imagine hte following scenario:
  130. <jl777> gggggg: where is the trust point?
  131. <4456456> Alice wants to buy something from Bob using your system, and BTC.
  132. <4456456> Alice makes a teleport payment to Bob. But Bob in turn
  133. decides not to redeem, but to keep this teleport for future reuse.
  134. <gggggg> when you take the coin of the block chain.. then either the
  135. reciever that your buying something from, or yourself can transfer the
  136. coin back into the chain... so i could in theory spend it before you
  137. do
  138. <4456456> So Bob gives this teleport to Charlie, etc.
  139. <4456456> Alice then has to wait for hte chain to finish before her
  140. payment is confirmed, and she can get whatever she was buying off Bob
  141. ?
  142. <jl777> 4456456: this is called trusted teleport, so if bob is going
  143. to trust alice to not double spend, then he needs to credit her when
  144. he decides to trust her
  145. <4456456> This is not allowed :p
  146. <jl777> trusted teleports are only for between people that trust each
  147. other and limited by amount of trust defined for each user
  148. <4456456> It has to not be based on "ok, I trust you won't double spend"
  149. <gggggg> so thats where the trust issue is
  150. <jl777> but trusted teleports are OPTIONAL
  151. <jl777> do you trust your family?
  152. <gggggg> so are you using group signatures for the trustless option?
  153. <jl777> does one group in a corporation trust another group?
  154. <4456456> So in order to use your system trustlessly, you can trade
  155. teleports ? You have to redeem at each step ?
  156. <4456456> I mean you can't, not you can, sorry.
  157. <jl777> 4456456: yes cloning each step for trustless
  158. <jl777> gggggg: higher authority to enforce things for trusted teleports
  159. <4456456> OK. So your claim for improvement in that case is just
  160. resistance to timing attacks, right ?
  161. <jl777> like CFO at company, smacks any guy that double spends intra
  162. company payment,
  163. <4456456> I mean resistance to correlation of payer/payee based on timing ?
  164. <gggggg> but, who is that higher authority then... the network?
  165. <jl777> 4456456: also resistant to packet monitoring via onion routing
  166. and M of N (254) shared secret fragments that are randomly routed or
  167. not routed
  168. <4456456> So, from now on I will only consider the case where you
  169. redeem without re-trading a teleport.
  170. <jl777> gggggg: if the two parties trust each other, they trust each
  171. other, this is not an issue. 90%+ of teleports are expected to be the
  172. trustless version
  173. <gggggg> yes, thats what i figured, but the part im having a hard time
  174. understanding is, who enforces the trustless version
  175. <jl777> yes cloning each time is the mainstream case, but the small
  176. number of trusted teleports makes it impossible to do much statistical
  177. correlations
  178. <4456456> In order for the BTC blockchain to be able to adjust the
  179. balances, there must be at least one transaction from the payer, and
  180. at least one transaction to the payee. Is that the case when using
  181. your system, or do you have a way out ?
  182. <jl777> gggggg: if johnny teleports to his sister and double spends,
  183. the mom punishes. higher authority is needed for trusted teleports.
  184. <gggggg> but who is that autority?
  185. <gggggg> the network, e specific node.. several nodes?
  186. <eee> escrow?
  187. <aaaaaa> I think trusted teleports arent very good. Would be hardly used
  188. <jl777> chaostec: if you teleport to me X and then double spend, then
  189. your honor is the authority
  190. <ccccc> jl777 Chaos is asking about the trustless i think
  191. <jl777> let us forget trusted teleports for now
  192. <gggggg> the trusted part i understand
  193. <jl777> the cloning validates the funds
  194. <jl777> now the receiver has 100% control
  195. <gggggg> its the trustless im having a hard time with
  196. <jl777> then credits the sender with whatever
  197. <jl777> So, let us pretend we are the attacker
  198. <jl777> What we see is a bunch of cloning events on the blockchain.
  199. <jl777> we trace it back to the creator, who is just some automated
  200. mixer service, or maybe you use Coinbase to send to your "transporter"
  201. account, so it comes from Coinbase big wallet
  202. <iiiii> nice
  203. <iiiii> i want some btcd hehe
  204. <4456456> You need to define what a cloning event is. A transaction ?
  205. <ikikik> ^
  206. <jl777> ideally it works with something like DRK to fund the intial
  207. telepod. BTCD is not aiming to replace any coin!!
  208. <jl777> teleport works in conjunction with all other coins and gains
  209. privacy by teleporting other coins
  210. <jl777> 4456456: yes cloning is a normal spend
  211. <gggggg> so, i create a pod lets for the sake of argument say, im
  212. transfering 1 bitcoin
  213. <gggggg> so, now i have the pod, with 1 bitcoin, and i send it to you
  214. <jl777> well not so fast
  215. <4456456> It is a spend from the payer's address (I assume) to what
  216. address on the blockchain ? A new one created for that purpose ? Or..
  217. ?
  218. <jl777> 4456456: one time addresses, one time keypairs, never reused
  219. <gggggg> and also i send it back to the bitcoin blockchain what would
  220. make sure i couldnt reintroduce the bitcoin into my wallet, while im
  221. paying you
  222. <4456456> That receiving address/key is created by... the payee ?
  223. <jl777> gggggg: if you double spend, then when I clone I get an error
  224. and dont credit you
  225. <jl777> 4456456: cloning is done by destination
  226. <gggggg> so, the transaction is written into btcds chain?
  227. <4456456> Sorry, I do not understand what you mean by this ?
  228. <jl777> BTC clonings are on BTC blockchain, DRK clonings on DRK blockchain, etc.
  229. <jl777> I think you need to read darkpaper first
  230. <4456456> Right. I assume we are using BTC in that example. Who
  231. creates that one time address ? The payee, the payer, or another party
  232. ?
  233. <jl777> cloning is done by the receiver, only they know the address
  234. and they dont even know until they start the cloning
  235. <jl777> so you wonder how does the telepod get from sender to destination?
  236. <4456456> No.
  237. <4456456> At hte moment, it looks very much like BTC.
  238. <4456456> I want to get paid, I generate an address, give it to you, you pay me.
  239. <jl777> by fully encryption and optionally fragmented M of N (254) onion routing
  240. <ikikik> >>[22:34] <jl777> I think you need to read darkpaper first<<
  241. <ikikik> i think all this talk is just fud
  242. <jl777> 4456456: well of course BTC telepods look a lot like BTC
  243. because it is BTC!
  244. <tesla666> jl777: this means the different blockchains will be flooded
  245. with clone transactions?
  246. <ikikik> i only watched btcd for 2 days and i understand it perfectly
  247. <jl777> ???????: if people are transacting in a currency that
  248. currencies blockchain is used
  249. <eee> please dont talk about anything other than btcd right now, there
  250. is no fud dev is just saying the facts
  251. <gggggg> ikikik: im really sorry you feel its fud, but i am REALLY
  252. trying to understand how the trustless part functions
  253. <4456456> So the remaining part is the clonesmear. I assume this is
  254. about the payee paying from that one time address to his/her main
  255. address (or wherever chosen) ?
  256. <Feedthemcake> So far all I'm seeing regarding BTCD is that JL777
  257. knows his shit and it's legitimate.
  258. <jl777> lets take a step back
  259. <eee> im going to put +m if dev cant answer all the questions
  260. <jl777> when teleport idea came to me, at first I thought it was too simple
  261. <jl777> if it worked why nobody else did it before?
  262. <fdgdgdfgdg5> reddit ama
  263. <jl777> after I start implementing, I realized it is quite complex for
  264. all the cases
  265. <jl777> so we imagine we are the attacker
  266. <zzzzz> where can i buy this shitcoin
  267. <jl777> what we have is a public record of all the clonings
  268. <fdgdgdfgdg5> https://bittrex.com/Market/Index?MarketName=BTC-BTCD
  269. <jl777> we say, aha!, lets see who controls those accts
  270. <rrrr> lol zzzzz
  271. <4456456> This public record is the blockchain of the chain you're
  272. using, right ?
  273. <jl777> we then find out each acct was only ever used once and to just
  274. transfer the value to the next one
  275. <jl777> 4456456: yes of course, BTC cloning on BTC blockchain
  276. <fdgdgdfgdg5> zzzzz: https://nxtforum.org/lite-multigateway-releases/mgw-v1-4-4/
  277. <jl777> so, the attacker can trace all the way back to the creator of
  278. the telepod
  279. <jl777> this is where I think teleport can use the help of other anon coins
  280. <jl777> to fund the initial telepod, it is a public thing, but if that
  281. was already anon via mixer or DRK or XMR, it is even better
  282. <jl777> ok back to attacker
  283. <jl777> he traces back all the tx to the creator and ends up in dead
  284. end of mixer, coinbase, some XMR or DRK xfer, etc.
  285. <jl777> lets try something else
  286. <jl777> we now go back to the list of cloning events
  287. <zzzzdddz> eee, /mode #CryptoTA +q *!*@*666666
  288. <jl777> however we have to look at all blockchains! as you can use
  289. InstantDEX to swap telepods from one currency to another
  290. <jl777> still we are determined attacker, now we have all the
  291. different coins cloning events
  292. <4456456> But this is a part that needs trust, right ?
  293. <eee> zzzzdddz, thanks
  294. <jl777> we now somehow find out you did a tx at noon
  295. <uuuu> ./mode -q eee
  296. <jl777> so we just go to the matrix of cloning events we made and go
  297. to noon, except we dont know what clonesmear time you used, so we have
  298. to guess as to how wide a window to look at
  299. <eee> let the dev talk please, if i see a fudder ill quiet him
  300. <jl777> the anon set is all the cloning events for all the coins for
  301. the clonesmear time (that is unknown to the attacker)
  302. <jl777> if the clonesmear time is one hour (I use that for default)
  303. then as overall teleporting increases, the anon set keeps increasing!
  304. <oooooo> 4456456: theres is a trustless and a trusted teleporting -
  305. i.e. take a 0 conf btc transaction or a 10 conf btc transaction
  306. <jl777> this is for receiver
  307. <jl777> for the sender it is even better!
  308. <jl777> you can age a telepod. This is time from cloning and the older
  309. it is the more private because the anon set is from the time of
  310. cloning to the time the destination clones
  311. <jl777> after a few generations of teleports there is extreme doubt as
  312. to who controls any given teleopod, so tracing back becomes harder and
  313. harder
  314. <jl777> just to make the attacker quit his job for the private sector,
  315. we toss in <10% trusted teleports
  316. <4456456> Do you agree that it is fair to ignore Tor, or debit cards,
  317. etc, since they're outside your teleport system ?
  318. <jl777> we are assuming trusted teleports are small minority and only
  319. among people that trust each other. The purpose of this is to add
  320. uncertainity to WHERE the telepod is. We not only dont know who has
  321. the telepod, with trusted teleports we dont even know where it is
  322. <oooooo> jl777: could you try to explain what you mean with aging
  323. telepods? why does it make the transaction more private?
  324. <rrrr> how do you intend on converting between the teleported coins?
  325. <jl777> so even a small amount of trusted teleports makes a
  326. mathematical model very hard to make, I cant think of how
  327. <jl777> rrrr: using InstantDEX peer to peer exchanging for trading
  328. telepods, probably need to do it using subatomic trades that are
  329. synchronized overlapped micropayment channels, or at least something
  330. like that
  331. <jl777> guest___: if you just clone a telepod and dont use it for 4
  332. months and then send it, how is the attacker going to correlate that
  333. to you? The anon set is all clonings for 4 months, isnt it?
  334. <rrrr> never heard of intantdex before. looking into it now...
  335. <jl777> rrrr: it is not done yet, will be part of supernetwork
  336. <oooooo> jl777: ah ok i understand what you mean
  337. <jl777> I am wanting to revenue share with all other coins that join
  338. supernetwork so everybody can get part of trading commissions
  339. <4456456> The clone action is a transaction from your BTC address to a
  340. one time BTC address, right ? Then it is trivially linkable to you.
  341. <gggggg> jl777: so if i understand it correctly, i transfer 1 bitcoin
  342. (or whatever coin) to an exchanging host (dont know what to call them)
  343. they hold the btc with multisig, and holds one of the keys, while to
  344. pod holds the other key, and that key is moved along with the pod?
  345. <jl777> instead of using centralized MtGox, etc., we can all trade
  346. among ourselves directly and cut fees way down
  347. <rrrr> dont say the G word, man
  348. <vvvvvv> g word?
  349. <vvvvvv> hue
  350. <true_capitalist> so are you telling me its just another shitcoin?
  351. <vvvvvv> oh gox
  352. <rrrr> :(
  353. <vvvvvv> mount gox
  354. <jl777> 4456456: it is from a telepod address to a telepod address,
  355. how do you link it to me?
  356. <vvvvvv> lelelel
  357. <jl777> it goes back to the creator of the telepod
  358. <jl777> not me
  359. <4456456> You had not defined telepod addresses before. A clone event
  360. was on the blockchain, I thought you'd said ?
  361. <bbbbbb_> ok I'm sold buying in now
  362. <rrrr> but how do you deal with exchange rate volatility?
  363. <mmmmmmm> jl777: If it is the initial transfer from transporter to
  364. telepod it is traceable
  365. <oooooo> ( the darkpaper has nearly 50 pages )
  366. <jl777> mmmmm: yes the injection into teleport economy is traceable
  367. and all clonings trace back to that address
  368. <pppppppp> My app has over 9000 code lines
  369. <pppppppp> Doesn't make it nice though
  370. <jl777> so I think most people wont be creating telepods due to the risk
  371. <jl777> once you get a telepod though, it will be linked to someone
  372. else, so you have privacy
  373. <jl777> think of it like this
  374. <jl777> if you go to airport, then there is all the id, passport,
  375. cavity search, confiscating the dangerous bottle of water, etc.
  376. <jl777> also same on exiting from the airport, with customs, etc.
  377. <jl777> this cannot be avoided and it is the same for using public blockchain
  378. <jl777> so what if midflight, you can teleport in and out of the airplane?
  379. <jl777> as many times as you want?
  380. <h6h6h6> to diferent planes?
  381. <bbbbbb_> ^ to the moon idiot
  382. <4456456> :D
  383. <oooooo> lol
  384. <gggggg> jl777: so the coin is held as a form of escrow.. but who owns
  385. the right to the coin is untraceable, since you cannot link the coin
  386. to the pod.. am i correct?
  387. <aaaaaa> Will it be first class? Or economy?
  388. <jl777> some hired guy goes through all the security, but during the
  389. flight, all sorts of teleporting can happen
  390. <ghjghjggg> Lol
  391. <jl777> gggggg: you are understanding
  392. <jl777> blockchain is used to confirm payment and prevent double spend
  393. <jl777> at least double spend is detected before crediting acct, so just as good
  394. <jl777> the creator of telepod is linked, but all subsequent tx is private
  395. <jl777> teleport needs other anon coins to seed the telepods!
  396. <gggggg> jl777: i can see the idea now, cool but where do you register
  397. the owner of a pod, in bctds blockchain, or as a simple string of bits
  398. send between clients?
  399. <aaaaaa> Will it be first class? Or economy?
  400. <jl777> some hired guy goes through all the security, but during the
  401. flight, all sorts of teleporting can happen
  402. <gghjghj> Lol
  403. <jl777> gggggg: you are understanding
  404. <jl777> blockchain is used to confirm payment and prevent double spend
  405. <jl777> at least double spend is detected before crediting acct, so just as good
  406. <jl777> the creator of telepod is linked, but all subsequent tx is private
  407. <jl777> teleport needs other anon coins to seed the telepods!
  408. <gggggg> jl777: i can see the idea now, cool but where do you register
  409. the owner of a pod, in bctds blockchain, or as a simple string of bits
  410. send between clients?
  411. <quuuu> is there someone that had a bad day? you can instatly feel you
  412. better! i have a bad year lost my wallet: jjjjjjjjjjjjjjj -_-
  413. <jl777> if the guy going through the airport is anon, then that would be great
  414. <Feedthemcake> JL777...this is pretty good
  415. <mmmmmmm> jl777: yes but who are we getting the pods from? it is only
  416. anonymous while someone leaves the pods in hyperspace, they cannot
  417. easily withdraw to a wallet without being linked
  418. <jl777> gggggg: there is also no permanent blockchain that is
  419. vulnerable to Quantum Computers from the future
  420. <mmmmmmm> it is the same as just getting BTC sent to a wallet you have not used
  421. <jl777> mmmm: I am working to make it easy to withdraw to anon debit card
  422. <rrrr> so, if you use other anon coins
  423. <ccccc> jl777 several times you have mentioned that it will not be
  424. attractive to create telepods.under what circumstances do u see
  425. creation as attractive / safe, and won' there be a bit of a market for
  426. these telepods?
  427. <jl777> then you can get cash from ATM
  428. <rrrr> why not just use an anon coin in the first place?
  429. <gggggg> basically your trading 1 of 2 keys for the escrowed coin
  430. <gggggg> and the current holder can take the coin out of escrow
  431. <jl777> maybe it is easy to crack all the anon tx, maybe not, but with
  432. teleport there is no permanent record, at least it all goes back to
  433. the telepod creator
  434. <oooooo> basicly like a vpn?
  435. <jl777> gggggg: something like that, the strength of teleport is the
  436. anon set grows with network activity. not fixed like others, so as
  437. overall activity grows anon level grows
  438. <jl777> this is why I want to work with all other coins!
  439. <jl777> the enemy is not each other, it is the existing fiat guys
  440. <aaaaaa> So what incentive do I have to be telepod creator?
  441. <gggggg> see, now i get it :-p
  442. <oooooo> aaaaaa: i guess you will be able to sell them?
  443. <jl777> by combining all our anon tx together into one giant
  444. supernetwork, within months it will be impossible for any govt to ever
  445. unravel things
  446. <jl777> ikikik: I have lab tests working, I am finalizing the accounting
  447. <jl777> there is one way the govt can deanonymize teleports
  448. <ikikik> nice ! looks like daddy gets new xmas toys :D
  449. <jl777> it is with massive simultaneous confiscation of all teleport
  450. nodes, globally
  451. <aaaaaa> How
  452. <gggggg> jl777: hehe sometimes things comes to you and the strangest
  453. moments... good thinking, and im looking forward to seeing it in
  454. action :-p
  455. <gggggg> and=at
  456. <aaaaaa> You cant take my nodes
  457. <aaaaaa> There my nodes
  458. <rrrr> lol
  459. <mmmmmmm> jl777: is there anyway for transporters to be reused? to
  460. mask the originator identity
  461. <aaaaaa> And you have to find me first
  462. <jl777> there is not blockchain, but each computer has a
  463. "privatechain" of all his tx, so if govt can get all the computers and
  464. crack the encrypted files they can recreate the entire blockchain
  465. <ikikik> GL with that
  466. <gggggg> jl777: look at mmmmmmm's comment, might be a good idea
  467. <jl777> gggggg: thanks! I dont want to be enemy of DRK or any coin, we
  468. work together, everybody wins
  469. <aaaaaa> That sounds fun
  470. <gggggg> jl777: i never see anyone as enemy, i see everyone trying to
  471. do something different, and the best ideas will go forward..
  472. <jl777> mmmm: reusing transporters would require trusting, but a group
  473. of people that trust each other could share a single transporter
  474. address!
  475. <gggggg> its the only healthy way to get digital coins to go forward
  476. <aaaaaa> But what if the popo come around to all of our houses and
  477. uninstall our btcd wallets?
  478. <jl777> I am just one guy who got lucky with idea and I hope to get
  479. many helps to make it better
  480. <gggggg> so now i also know why your been so busy lol
  481. <jl777> I will be offering revenue sharing to people so not just
  482. from altruism, but also you can make some money
  483. <jl777> the creation of telepods is definitely a business
  484. opportunity for some people
  485. <sss> +jl777 were gonna get everyone here to start buying your coin
  486. <jl777> I also make tradebots, which os
  487. <jl777> +-9/*/-
  488. <eee> sss, do not impersonate me please :)
  489. <jl777> sorry keyboardbattery died
  490. <tttttt> jl777: have you been able to do any work with the crypti team yet?
  491. <sss> what im the real eee
  492. <gggggg> lol jl777 been there
  493. <xxxxx> Yo Jl777 i got my coins from cryptsy! finally
  494. <gggggg> jl777: ill be checking in on you from time to time... :-p
  495. <ccccc> big thx to xxcv, xcvxcv and jl777 for a good convo!
  496. <jl777> i make turing complete tradebots that can run scripts
  497. written in C, so you can do crossmarket arbitrage, telepod trading,
  498. well anything as it is turing complete
  499. >jl777< tell me if you are done explaining ill publish this convo in
  500. a pastebin on twitter
  501. <eee> check pm jl777
  502. <4456456> Indeed, thanks for chatting here with us. I will read the dark paper
  503. <jl777> thank you for being of open minds! I need to get batteries,
  504. this old keyboard is horrible
  505. <gggggg> just needed to understand his thinking, its always better
  506. to understand the thinking, because then you understand the
  507. implementation
  508. <eee> thank you for joining us jl777 !
  509. <gggggg> awesome evening guys/gals
  510. <gggggg> :-p
  511. <jl777> ok, now i gofinish the accounting stuff
  512. <jl777> bye
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement