API tools faq
paste
Guest User

cryptsy

a guest
Oct 12th, 2013
355
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 33.55 KB | None | 0 0
raw download clone embed print report
  1. [quote]
  2. [9/27/2013 10:21:55 AM] r3wt: well, my request was this. i need someone on linux to attempt to connect and download blocks from me. i have verns block chain installed on my linux machine. my windows machine connects, but won't download any blocks. the debug log says "connection refused". i'm thinking maybe its because my two machines are on the same subnet and share external ips, making the client think they are the same host. i need someone to try to cnnect to me from external ip to see if they can dl blocks. mullick is unreachable and shake is at work. has to be someone trustworthy, cuz the next block is got 250,000 coins in it. whoever mines it will be responsible for distributing/covering the coins lost in the fork if there is one. i was hoping that you guys could maybe mine this block and distribute the coins to the chinese people and whoever that lost coins. i can't mine it because i don't have scrypt mining hardware
  3. [9/27/2013 10:22:21 AM] r3wt: oh and if vern decides to help, he will need to get the latest source from me.
  4. [9/27/2013 10:22:30 AM] r3wt: https://github.com/r3wt/nanotoken.git
  5. [9/27/2013 10:22:49 AM] r3wt: muddafudda's github should be disregarded, he is no longer a part of the project
  6. [9/27/2013 10:24:43 AM] Bit John: ok I will ask him when he gets in
  7. [9/27/2013 10:26:58 AM] r3wt: ok. tell him we need to talk specifics about the forking issues. i'm thinking that whatever is left over from the "reparations block" should probably be publicly destroyed. wouldn't you agree?
  8. [9/27/2013 10:27:39 AM] Bit John: works for me or we try to cover the folks that got screwed big time
  9. [9/27/2013 10:28:10 AM] r3wt: yeah thats what i'm saying, 250,000 should more than cover it.
  10. [9/27/2013 10:29:10 AM] r3wt: wait what do you mean cover the folks that got screwed big time? is there others i don't know about?
  11. [9/27/2013 10:29:37 AM] r3wt: so far i have only about 90,000 coins missing from 4 users that have contacted me at bctalk.
  12. [9/27/2013 10:29:48 AM] r3wt: biter, h4xxor, qwep, and blazr
  13. [9/27/2013 10:29:50 AM] Bit John: no that is who I am talking about
  14. [9/27/2013 10:30:27 AM] r3wt: oh. he told me he only had 60,000 missing
  15. [9/27/2013 10:31:30 AM] Bit John: your probably rght
  16. [9/27/2013 10:31:51 AM] r3wt: well jcoin is pretty much dead. the lack of source code was the nail in the coffin.
  17. [9/27/2013 10:32:07 AM] r3wt: but osc isn't :)
  18. [9/27/2013 10:32:13 AM] r3wt: i finally got one right
  19. [9/27/2013 10:40:52 AM] Bit John: I have been watching OSC
  20. [9/27/2013 10:44:14 AM] r3wt: cool.
  21. [9/27/2013 10:44:43 AM] r3wt: the past two days i've been working on it some
  22. [9/27/2013 10:45:04 AM] r3wt: i got the checkpointing server up already )
  23. [9/27/2013 10:45:11 AM] r3wt: no forkage for this coin
  24. [9/27/2013 10:45:21 AM] Bit John: haha CAPs just got its up
  25. [9/27/2013 10:46:08 AM] r3wt: sweet
  26. [9/27/2013 11:51:29 AM] r3wt: guess what...
  27. [9/27/2013 11:51:55 AM] r3wt: mullick compiled windows binary and... it connects and syncs up to the cryptsy chain!
  28. [9/27/2013 11:52:01 AM] r3wt: still got a few things to work out.
  29. [9/27/2013 11:52:49 AM] r3wt: like a diff switch to allow the diff to retarget in this special circumstance. then once the reparation block is mined i will have to update the source to checkpoint that block so no one can reverse it.
  30. [9/27/2013 11:53:03 AM] r3wt: but that is all simple stuff
  31. [9/27/2013 12:03:23 PM] Bit John: sweet
  32. [9/27/2013 12:43:23 PM] r3wt: ok here is the deal. dyoungii is setting up a pool for nano relaunch. using his pool we will mne the reparation block and then we will need you to send your address so that you may receive the reparation coins as we discussed. have you talked to vern yet? i'd like to get htis done today if possible
  33. [9/27/2013 12:43:45 PM] Bit John: I havent talked to vern yet
  34. [9/27/2013 12:43:58 PM] Bit John: so what do you need on our end now just the address?
  35. [9/27/2013 12:45:50 PM] r3wt: well yeah, if you need a client specify your os and i will send you the new client. we have linux/windows ready to roll
  36. [9/27/2013 12:46:07 PM] r3wt: it is imperative that cryptsy follow my instructions this time
  37. [9/27/2013 12:46:19 PM] r3wt: you will not be able to connnect to the new network without the new clients
  38. [9/27/2013 12:47:03 PM] Bit John: yip lets wait for vern when he gets on
  39. [9/27/2013 12:47:50 PM] r3wt: ok thats fine
  40. [9/27/2013 12:47:59 PM] r3wt: gives me time to compile a windows daemon
  41. [9/27/2013 12:48:08 PM] r3wt: so that all clients are available on launch
  42. [9/27/2013 4:32:09 PM] r3wt: ok, be on the lookout for someone trying to deposit large sums of nanotokens
  43. [9/27/2013 4:32:15 PM] r3wt: the info i have is
  44. [9/27/2013 4:32:16 PM] r3wt: addr" : "38.96.134.197:17578",
  45. "services" : "00000001",
  46. "lastsend" : 1380317234,
  47. "lastrecv" : 1380317234,
  48. "conntime" : 1380313478,
  49. "version" : 65009,
  50. "subver" : "/Nanotoken:3.0.0.3/",
  51. "inbound" : false,
  52. "releasetime" : 0,
  53. "startingheight" : 28902,
  54. "banscore" : 0
  55. [9/27/2013 4:32:20 PM] r3wt: mined the block
  56. [9/27/2013 4:34:32 PM] r3wt: that address is the only connection on the network and it must have mined the large reparation block. be on the lookout for this ip address
  57. [9/27/2013 4:41:53 PM] r3wt: i found the dude who mined it, his username is nyclogan. he said he submitted a support ticket.i asked him to contact you so that he could transfer the coins to you guys as we discussed.
  58. [9/27/2013 4:42:59 PM] r3wt: if you think it is ok let him keep a small bit of the coins, but that is up to you. i just want to get it done and everyone happy so that i can finally lose the stigma of not supporting my coins
  59. [9/27/2013 4:51:15 PM] r3wt: the finder of block 28,902 has come forward. support ticket number 3918. thank you
  60. [9/27/2013 7:41:31 PM] r3wt: wow, this is b/s
  61. [9/27/2013 7:41:41 PM] r3wt: wher did you all dissapeare to?
  62. [9/28/2013 9:14:27 AM] r3wt: dude, i can't login to crispy
  63. [9/28/2013 9:14:48 AM] r3wt: it says "A security error has occured" when i login
  64. [9/28/2013 11:59:30 AM] Bit John: means you have another session open usually
  65. [9/28/2013 12:00:38 PM] r3wt: oh ok. i went ahead and changed my password for fear that someone had hacked my account
  66. [9/28/2013 1:13:08 PM] r3wt: lots of requests for NAN to be re activated...
  67. [9/29/2013 3:12:16 PM] r3wt: whats going on
  68. [9/29/2013 3:24:13 PM] Bit John: nodda
  69. [9/29/2013 3:24:35 PM] r3wt: wheres vern? mired in the problems of star coin still?
  70. [9/29/2013 3:24:55 PM] Bit John: he just got on working on the CGB issue
  71. [9/29/2013 3:25:54 PM] r3wt: whats the cgb issue?
  72. [9/29/2013 3:26:08 PM] Bit John: the had commited an error
  73. [9/29/2013 3:26:13 PM] Bit John: which caused withdraw issues
  74. [9/29/2013 3:26:17 PM] Bit John: we had to update to the fix
  75. [9/29/2013 3:27:08 PM] r3wt: they had commited an error?
  76. [9/29/2013 3:29:05 PM] Bit John: yeah on github
  77. [9/29/2013 3:29:08 PM] Bit John: that they later fixed
  78. [9/29/2013 3:29:26 PM] r3wt: lol, i fixed it for them...
  79. [9/29/2013 3:29:38 PM] r3wt: http://github.com/r3wt/CGB.git
  80. [9/29/2013 3:30:31 PM] r3wt: i don't see how the problems with their github caused a deposit problem. unless perhaps it was a db error you're trying to cover up :P
  81. [9/29/2013 3:31:07 PM] Bit John: whateva
  82. [9/29/2013 3:31:15 PM] r3wt: i haven't decided whether i will fix ADT. personally i don't like shitcoins...
  83. [9/29/2013 3:31:31 PM] Bit John: me either :P
  84. [9/29/2013 3:31:33 PM] r3wt: so when can we talk about nanotokens
  85. [9/29/2013 3:31:45 PM] Bit John: haha whatcha want to talk about
  86. [9/29/2013 3:32:11 PM] r3wt: i give you my word that i will support it 100 percent from now on.
  87. [9/29/2013 3:32:33 PM] Bit John: I thought you were all in on your new coin
  88. [9/29/2013 3:32:41 PM] r3wt: i'm all in on both coins.
  89. [9/29/2013 3:32:57 PM] r3wt: you can ask mullick i fixed nanotokens 100 percent by myself
  90. [9/29/2013 3:33:14 PM] r3wt: he helped me test and he compiled windows for me
  91. [9/29/2013 3:33:25 PM] Bit John: well if we save nanotokens at this point its yet another coin we didnt delist
  92. [9/29/2013 3:33:52 PM] r3wt: but nanotokens has actual support.
  93. [9/29/2013 3:34:00 PM] r3wt: its not just some random shitcoin
  94. [9/29/2013 3:34:08 PM] r3wt: the chinese love it
  95. [9/29/2013 3:34:20 PM] r3wt: i promise you volume
  96. [9/29/2013 3:34:24 PM] Bit John: yeah I have seen it
  97. [9/29/2013 3:34:39 PM] Bit John: Id prefer to just add your new one
  98. [9/29/2013 3:34:39 PM] r3wt: and i promise you i will never let it hang in limbo again
  99. [9/29/2013 3:35:10 PM] r3wt: please, just give nan one more chance.
  100. [9/29/2013 3:35:15 PM] r3wt: i'm supporting both of them
  101. [9/29/2013 3:35:41 PM] r3wt: the clients issues are 100 percent fixed man, just give it a try
  102. [9/29/2013 3:35:58 PM] r3wt: i made some serious modifications
  103. [9/29/2013 3:36:12 PM] r3wt: just diff it against muddafuddas github and you will see how much has changed
  104. [9/29/2013 3:36:26 PM] Bit John: I dont doubt its changed at all
  105. [9/29/2013 3:36:43 PM] r3wt: https://github.com/r3wt/nanotoken.git
  106. [9/29/2013 3:36:55 PM] r3wt: new network id, new protocol, new version
  107. [9/29/2013 3:37:03 PM] r3wt: plus the block rewards are fixed
  108. [9/29/2013 3:37:20 PM] Bit John: ill see what vern says
  109. [9/29/2013 3:37:27 PM] r3wt: the old clients can't connect and cause a fork anymore.
  110. [9/29/2013 3:37:30 PM] Bit John: hes gonna say its on me
  111. [9/29/2013 3:37:35 PM] Bit John: haha
  112. [9/29/2013 3:37:41 PM] r3wt: and you say no huh.
  113. [9/29/2013 3:37:44 PM] r3wt: shit
  114. [9/29/2013 3:37:50 PM] Bit John: no Im in the air at the moment
  115. [9/29/2013 3:38:01 PM] r3wt: well just ask vern to look at the new github
  116. [9/29/2013 3:38:01 PM] Bit John: if I do it its because your asking
  117. [9/29/2013 3:38:11 PM] r3wt: i promise i won't burn you
  118. [9/29/2013 3:38:32 PM] Bit John: if I bring it back its gonna go to LTC markets
  119. [9/29/2013 3:39:03 PM] r3wt: why, it did fine in btc market
  120. [9/29/2013 3:39:15 PM] r3wt: worth more than mec, even with all its problems
  121. [9/29/2013 3:39:42 PM] Bit John: because I want more LTC markets and then Im not just yanking chains about delisting coins
  122. [9/29/2013 3:40:23 PM] r3wt: both markets :P
  123. [9/29/2013 3:40:35 PM] r3wt: delist kgc and all the junkcoins
  124. [9/29/2013 3:40:36 PM] r3wt: lol
  125. [9/29/2013 3:40:46 PM] Bit John: there are more on the list
  126. [9/29/2013 3:41:42 PM] r3wt: what happend to jester?
  127. [9/29/2013 3:41:50 PM] r3wt: he jus disapeared
  128. [9/29/2013 3:41:51 PM] Bit John: good question
  129. [9/29/2013 3:42:30 PM] r3wt: what about horus? don't see him anymore either
  130. [9/29/2013 3:42:48 PM] Bit John: hes active your just mising him
  131. [9/29/2013 3:42:55 PM] r3wt: i dare you to make Hydroponica a mod for a day
  132. [9/29/2013 3:42:56 PM] Bit John: he spends more time on his useraccount
  133. [9/29/2013 3:43:00 PM] Bit John: haha
  134. [9/29/2013 3:43:02 PM] Bit John: no
  135. [9/29/2013 3:43:11 PM] r3wt: so how is pr9me working out as a mod?
  136. [9/29/2013 3:44:42 PM] Bit John: great
  137. [9/29/2013 3:45:07 PM] r3wt: good to hear it. i knew he'd be trustworthy in the position of power
  138. [9/29/2013 4:04:11 PM] r3wt: pr9me makes good graphics
  139. [9/29/2013 4:09:23 PM] r3wt: please tell me you are not going to add TIX
  140. [9/29/2013 4:14:07 PM] Bit John: who knows haha
  141. [9/29/2013 4:14:46 PM] r3wt: i'm sick of all these junk coins. they only devalue the coins that are actually interesting.
  142. [9/29/2013 4:35:21 PM] Bit John: whats the good nano node
  143. [9/29/2013 4:38:15 PM] r3wt: did you get my source or muddafuddas?
  144. [9/29/2013 4:38:40 PM] r3wt: addnode=http://173.216.107.57/
  145. [9/29/2013 4:38:43 PM] r3wt: oops
  146. [9/29/2013 4:38:53 PM] r3wt: addnode=173.216.107.57
  147. [9/29/2013 4:38:56 PM] Bit John: the github you sent me
  148. [9/29/2013 4:39:05 PM] r3wt: addnode=nan.dencoinpools.com
  149. [9/29/2013 4:39:45 PM] r3wt: there are only like 3 or 4 connections atm. it might take awhile for you to connect
  150. [9/29/2013 4:40:28 PM] Bit John: so that other ip is good too?
  151. [9/29/2013 4:40:33 PM] Bit John: [Sunday, September 29, 2013 4:38 PM] r3wt:
  152.  
  153. <<< addnode=173.216.107.57
  154. [9/29/2013 4:41:01 PM] r3wt: yeah thats my computer lol. i got 3 clients running atm. one linux, one windows, one daemon
  155. [9/29/2013 4:41:11 PM] r3wt: but they all at the same ip address.
  156. [9/29/2013 4:41:43 PM] r3wt: it may take a while to find connections, especially if vern built without pnp
  157. [9/29/2013 4:42:00 PM] r3wt: if he wants i have the daemon built for linux with pnp
  158. [9/29/2013 4:46:54 PM] r3wt: wait, are you talking about OSC or NAN?
  159. [9/29/2013 4:46:56 PM] r3wt: NAN right?
  160. [9/29/2013 4:47:10 PM] r3wt: OSC has plenty of connections, NAN only has 1 or 2
  161. [9/29/2013 4:47:16 PM] Bit John: NAN
  162. [9/29/2013 4:47:24 PM] r3wt: ok, did you get a connection yet?
  163. [9/29/2013 4:47:40 PM] Bit John: think so
  164. [9/29/2013 4:48:19 PM] r3wt: good deal
  165. [9/29/2013 4:48:48 PM] r3wt: ps, do you want my cell number so you can text me in the event of problems? its really the best way to get ahold of me.
  166. [9/29/2013 4:49:14 PM] Bit John: sure send it to us
  167. [9/29/2013 4:49:18 PM] Bit John: Ill put it on our dev list
  168. [9/29/2013 4:49:26 PM] r3wt: 479-647-0135
  169. [9/29/2013 4:49:33 PM] r3wt: and my email is stuckinabox@live.com
  170. [9/29/2013 4:50:21 PM] r3wt: btw, i'm working on adding a new alert system for nanotokens to alert users to updates
  171. [9/29/2013 4:51:52 PM] r3wt: you like my chat handle "iGotPot"
  172. [9/29/2013 4:55:38 PM] Bit John: lol
  173. [9/29/2013 4:55:46 PM] r3wt: https://www.cryptsy.com/markets/view/64
  174. [9/29/2013 4:55:50 PM] r3wt: sneaky sneaky
  175. [9/29/2013 5:00:12 PM] r3wt: i just got an incoming transaction from cryptsy
  176. [9/29/2013 5:00:24 PM] r3wt: Status: 1/unconfirmed
  177. Date: 9/29/2013 16:59
  178. From: unknown
  179. To: MqfgXUHUJ8bTqdQqsQYNgoRjsDndE81Cds (own address)
  180. Credit: 9.79999999 NAN
  181. Net amount: +9.79999999 NAN
  182. Transaction ID: a1528ac838f9d9e06843a30fdd5717483607418f1483f4dac6df573abfa110e7
  183. [9/29/2013 5:00:33 PM] r3wt: can you find the user who sent them to me?
  184. [9/29/2013 5:00:41 PM] r3wt: i think his name was Paks or something
  185. [9/29/2013 5:01:49 PM] Bit John: haha I cant with my interface
  186. [9/29/2013 5:02:03 PM] r3wt: ah, its too bad.
  187. [9/29/2013 5:02:12 PM] r3wt: so is nan still going to be delisted in OCT?
  188. [9/29/2013 5:02:27 PM] r3wt: i won't give you to much grief about it, just curious as to where it stands
  189. [9/29/2013 5:02:38 PM] Bit John: not sure haha
  190. [9/29/2013 5:02:53 PM] r3wt: well atleast you're honest
  191. [9/29/2013 5:03:26 PM] r3wt: well, i've got some funds to move into cryptsy. time to capitalize on this cheap nan
  192. [9/29/2013 5:03:43 PM] r3wt: btw, did you run an audit to make sure there aren't any coins missing
  193. [9/29/2013 5:15:43 PM] r3wt: please please please never add TIX. igotspots has enough coins on the exchange
  194. [9/29/2013 5:17:12 PM] r3wt: my trust score is super low now huh
  195. [9/29/2013 5:18:26 PM] Bit John: haha might be
  196. [9/29/2013 5:18:44 PM] r3wt: damn you and your poker face
  197. [9/29/2013 5:19:28 PM] r3wt: remove the delisting message, watch trading soar
  198. [9/29/2013 5:24:00 PM] r3wt: i can only imagine your headaches.
  199. [9/29/2013 5:29:52 PM] Bit John: haha
  200. [9/29/2013 6:05:25 PM] r3wt: hey, would you give nyclogan some of the coins for finding the block and turning it in to you like i asked him. most people would have just dumped it on exchange...
  201. [9/29/2013 6:06:48 PM] Bit John: yip hell get a cut
  202. [9/29/2013 6:06:57 PM] Bit John: want to make sure they are paid out to the lost folks first
  203. [9/29/2013 6:08:06 PM] r3wt: oh ok. so should i instruct users to contact you about it or what? whats the practice here? because i only know of 4 people, 1 of them on the exchange the other 3 on the forum. what should i tell them? biter is driving me crazy about it
  204. [9/29/2013 6:09:24 PM] Bit John: yeah have the 4 you know contact me
  205. [9/29/2013 6:11:32 PM] r3wt: ok, on skype the forum or what?
  206. [9/29/2013 6:12:54 PM] r3wt: do i get a cut lol j/k
  207. [9/29/2013 6:13:04 PM] r3wt: but seriously should they just pm you on the forum?
  208. [9/29/2013 6:13:54 PM] Bit John: put in a ticket works
  209. [9/29/2013 6:14:06 PM] r3wt: okie dokie
  210. [9/29/2013 6:14:14 PM] r3wt: what if they don't have a cryptsy account?
  211. [9/29/2013 6:16:30 PM] Bit John: oh then they should email me
  212. [9/29/2013 6:23:27 PM] r3wt: email address?
  213. [9/29/2013 6:23:34 PM] r3wt: paul@cryptsy.com
  214. [9/29/2013 6:23:36 PM] r3wt: ??
  215. [9/29/2013 6:24:13 PM] Bit John: bitjohn@cryptsy.com
  216. [9/29/2013 6:29:30 PM] r3wt: ok, thanks
  217. [9/29/2013 6:34:10 PM] r3wt: one problem, how can i determine if they are lying or not?
  218. [9/29/2013 6:35:02 PM] r3wt: like should we just give biter, qwep and h4xx0r their coins back? the other guy just showed up out of nowhere and said he lost 1000 coins. i asked him to prove it and never heard from him again
  219. [9/29/2013 6:39:05 PM] Bit John: yeah they should have some proof lol
  220. [9/29/2013 6:39:36 PM] r3wt: are you able to contact the chinese guy(biter)
  221. [9/29/2013 6:40:08 PM] r3wt: him qwep and h4xxor are all chinese.
  222. [9/29/2013 6:40:13 PM] r3wt: their pms all look like this
  223. [9/29/2013 6:40:28 PM] r3wt: bla;kja;lsjblajdkslfl NAN blaklbjal 20,000 alsdjfalsdfj cryptsy!!!
  224. [9/29/2013 6:40:36 PM] Bit John: haha yeah painful haha
  225. [9/29/2013 6:41:33 PM] r3wt: h4xxor claims 14,000 coins missing qwep claims 1,500 and biter claims 60,000. think they are lying?
  226. [9/29/2013 6:42:03 PM] Bit John: biter isnt
  227. [9/29/2013 6:42:18 PM] Bit John: more than likely they used cryptsy
  228. [9/29/2013 6:42:33 PM] Bit John: even more interesting they likely have the coins now if they updated yes?
  229. [9/29/2013 6:43:12 PM] r3wt: yes, i contacted all 3 of them and no reply.
  230. [9/29/2013 6:43:31 PM] r3wt: i think biter was the one woh bought at cryptsy.
  231. [9/29/2013 6:44:39 PM] r3wt: h4xxor said he bought 14,000 from coins e and withdrew to his wallet and only 1,000 coinfirmed. the other guy i couldn't really understand what he said. i've made repeated tries to contact him but he just replies "when nan relist cryptsy"
  232. [9/29/2013 6:45:17 PM] Bit John: lol
  233. [9/29/2013 6:59:56 PM] r3wt: lol, h4xx0r had me to email him for you. his message makes no since but i sent it anyway
  234. [9/29/2013 7:04:31 PM] r3wt: hello?
  235. [9/29/2013 7:04:51 PM] Bit John: yip just sent it to him
  236. [9/29/2013 7:05:24 PM] r3wt: lol did you google translate his message. i know i shouldn't laugh about it but i did
  237. [9/29/2013 7:05:57 PM] Bit John: haha yeah I laugh at them all the time
  238. [9/29/2013 7:06:02 PM] Bit John: its painful
  239. [9/29/2013 7:06:25 PM] r3wt: we're going to hell haha
  240. [9/29/2013 7:06:46 PM] r3wt: did biter and qwep message you? i can't get either one to respond to me
  241. [9/29/2013 7:07:23 PM] Bit John: nope not yet
  242. [9/29/2013 7:08:32 PM] r3wt: well i sent them your email address. i bet you they just send support tickets agian
  243. [9/29/2013 7:09:40 PM] r3wt: wow buy support plummeted on nanotoken
  244. [9/29/2013 7:10:21 PM] Bit John: haha I saw that
  245. [9/29/2013 7:10:52 PM] r3wt: that big red message isn't very inviting lol
  246. [9/29/2013 7:11:24 PM] r3wt: odd how it had so much support. must have been muddafudda
  247. [9/29/2013 7:11:51 PM] r3wt: which scifi coins are you adding
  248. [9/29/2013 7:11:59 PM] Bit John: yeah I can honestly say the only guy who complained about nan was Biter lol
  249. [9/29/2013 7:12:01 PM] Bit John: all three
  250. [9/29/2013 7:12:27 PM] r3wt: ah, right on
  251. [9/29/2013 7:33:51 PM] r3wt: bcx just tried to attack nan again.
  252. [9/29/2013 7:34:40 PM] r3wt: he spammed the network with 600 block time travel. all my transactions went unconfirmed, wallet went out of balance. of course they were immediately orphaned and everything went back to normal. good to see that my changes are working.. for now atleast
  253. [9/29/2013 7:37:44 PM] Bit John: haha
  254. [9/29/2013 7:37:48 PM] Bit John: well it least it didnt break
  255. [9/29/2013 7:38:14 PM] r3wt: yeah, but now there are no connections to the network. BCX is up to his nonsense again
  256. [9/29/2013 7:41:12 PM] r3wt: ah, nevermind i got a connection again. all is good for now. i think this is definitely BCX. either that or someone tried to import their old blockchain to the new client.
  257. [9/29/2013 7:50:09 PM] Bit John: the 250k reversed
  258. [9/29/2013 7:50:43 PM] r3wt: wait about 5 minutes
  259. [9/29/2013 7:50:51 PM] r3wt: someone is trying to reverse it.
  260. [9/29/2013 7:51:06 PM] r3wt: but their blocks orphaned on my end
  261. [9/29/2013 7:51:21 PM] r3wt: the 250k shows confirmed here.
  262. [9/29/2013 7:52:38 PM] r3wt: what the hell...
  263. [9/29/2013 7:53:14 PM] Bit John: verns pulling it again until it calms down
  264. [9/29/2013 7:54:48 PM] r3wt: wtf, who is doing this shit.
  265. [9/29/2013 7:56:52 PM] Bit John: your buddy I am sure
  266. [9/29/2013 7:57:36 PM] Bit John: or another guy being a douche
  267. [9/29/2013 7:59:19 PM] r3wt: someone forked the network again i think. are you sure i'm in your addnode list?
  268. [9/29/2013 7:59:46 PM] Bit John: yes
  269. [9/29/2013 7:59:52 PM] Bit John: your the node we added
  270. [9/29/2013 7:59:59 PM] Bit John: the two you gave us
  271. [9/29/2013 8:00:07 PM] r3wt: unable to contact the pool operator.
  272. [9/29/2013 8:02:26 PM] r3wt: odd thing is that 13k is still showing up in the wallet...
  273. [9/29/2013 8:02:52 PM] Bit John: the 13k I sent that guy?
  274. [9/29/2013 8:02:58 PM] r3wt: that guy lol
  275. [9/29/2013 8:03:43 PM] r3wt: lol yep, he said he keeps getting kicked out of the network but the transaction is still confirmed
  276. [9/29/2013 8:39:07 PM] r3wt: muddafudda spamming the network. i think it will pass
  277. [9/29/2013 9:02:15 PM] r3wt: i'm trying to regain control of the network. not sure how much hash the dude who forked it has
  278. [9/29/2013 9:39:11 PM] r3wt: nyclogan is the one who did it.
  279. [9/29/2013 9:39:18 PM] r3wt: 99 percent sure.
  280. [9/29/2013 9:39:25 PM] r3wt: he pm'd me right before it happened.
  281. [9/30/2013 11:28:37 AM] r3wt: still unconfirmed?
  282. [9/30/2013 11:32:08 AM] r3wt: i figured itout. fortunately my linux machine was offline during the attack and its blockchain remains unaltered. i'm going to use it to rpc connect to my windows machine and over write the chain. then i'm going to hardode in as many blocks as i can into the source, recompile and redistribute. i think it will work
  283. [9/30/2013 3:44:52 PM] r3wt: yo
  284. [9/30/2013 3:51:21 PM] r3wt: yo yo yo
  285. [9/30/2013 3:51:44 PM] r3wt: i'm about to have NAN back up. my linux machine was offline during the attack and i was able to checkpoint the block.
  286. [9/30/2013 5:10:45 PM] r3wt: helllo!!!!
  287. [9/30/2013 5:11:29 PM] Bit John: yo
  288. [9/30/2013 5:12:19 PM] r3wt: y'all ready for round to i'm bout to update g/hub
  289. [9/30/2013 5:12:37 PM] Bit John: verns not in he will be a tad later
  290. [9/30/2013 5:13:40 PM] r3wt: ok gives me awhile to hardcode roadblocks into the source. attacker will have to work to attack nan again.
  291. [9/30/2013 5:16:16 PM] r3wt: so this is what i did...
  292. [9/30/2013 5:16:22 PM] r3wt: i created a class called nSerial
  293. [9/30/2013 5:16:32 PM] r3wt: during sanity tests it initiates two tests
  294. [9/30/2013 5:16:41 PM] r3wt: first it tests peers for nSerial
  295. [9/30/2013 5:16:49 PM] r3wt: then it tests its self for nSerial
  296. [9/30/2013 5:17:06 PM] r3wt: if nSerial is wrong for a peer, that peer is banned for 1 hour.
  297. [9/30/2013 5:17:17 PM] r3wt: if nSerial fails the selftest, the program is terminated
  298. [9/30/2013 5:17:42 PM] r3wt: now nSerial is required to build a program capable of connecting to the network, but it is not included in the source
  299. [9/30/2013 5:17:54 PM] r3wt: the only way to get nSerial is for me to give it to you personally.
  300. [9/30/2013 5:18:35 PM] r3wt: the sanity test executes in every object so its not just as simple as cutting the lines and pasting, besides 99% of clients will run the test.
  301. [9/30/2013 5:19:05 PM] r3wt: this allows network hash rate to take the back seat to the serial number, meaning that 51% hashrate is not enough to override nSerial
  302. [9/30/2013 6:10:24 PM] r3wt: there is nothing i can do about NAN until miners support it. it will just keep failing. i feel like this is unjust reason to bar OSC from the exchange. i want you to know that.
  303. [9/30/2013 6:10:30 PM] r3wt: cause thats how i feel about it
  304. [9/30/2013 6:10:41 PM] r3wt: doesn't mean i'm giving up on NAN, not by damn site
  305. [9/30/2013 6:11:47 PM] r3wt: i can't help but feel like you guys won't list OSC because you are judging me based on NAN which is unfair. each coin has its own merits, and NAN is based on provably exploitable and insecure litecoin .6.3 code.
  306. [9/30/2013 9:46:01 PM] r3wt: check this out bro
  307. [9/30/2013 9:46:03 PM] r3wt: http://opensourcecoin.org/
  308. [9/30/2013 9:52:19 PM] r3wt: can i borrow some btc to pay for my website design? i'll pay you back
  309. [9/30/2013 9:53:56 PM] Bit John: lol Im not a bank
  310. [9/30/2013 9:54:01 PM] r3wt: haha, i know.
  311. [9/30/2013 9:54:03 PM] Bit John: Im actually pretty BTC poor at the moment
  312. [9/30/2013 9:54:28 PM] r3wt: yeah me too. i promised zelles OSC would be on the exchange soon and well now i kinda got my foot in my mouth
  313. [9/30/2013 10:30:51 PM] r3wt: 3 iGotSpots coins on the exchange!!!!
  314. [9/30/2013 10:31:00 PM] r3wt: da fuq man?
  315. [9/30/2013 10:34:42 PM] Bit John: your coin wasnt fit for XPM or it woulda been yours to be honest lol
  316. [9/30/2013 10:35:29 PM] r3wt: lol, not fit for xpm? is that a insult?
  317. [9/30/2013 10:35:37 PM] r3wt: oh i see what you mean now, nevermind
  318. [9/30/2013 10:36:08 PM] r3wt: should i make a junk coin so it can be traded in xpm market lol
  319. [9/30/2013 10:37:18 PM] Bit John: haha no your coin is probably a BTC pairing
  320. [9/30/2013 10:38:38 PM] r3wt: definitely...
  321. [9/30/2013 10:38:44 PM] r3wt: r3wt strokes ego.
  322. [9/30/2013 10:38:50 PM] r3wt: lol
  323. [10/1/2013 8:50:03 PM] r3wt: you guys are killing my coin by refusing to add it to cryptsy. thanks
  324. [10/1/2013 8:54:14 PM] r3wt: [Tuesday, October 1, 2013 8:53 PM] r3wt:
  325.  
  326. <<< cryptsy is killing OSC by refusing to add it. i might be the 1 dev thats actually wants to create services. sure i'm in it to make money, i won't lie but i'm also in it to start a revolution. adding a few services to OSC and getting a few legit services is all it takes to supplant LTC as the second best Cryptocoin, and i intend for OSC to take its place[Tuesday, October 1, 2013 8:53 PM] r3wt:
  327.  
  328. <<< cryptsy is killing OSC by refusing to add it. i might be the 1 dev thats actually wants to create services. sure i'm in it to make money, i won't lie but i'm also in it to start a revolution. adding a few services to OSC and getting a few legit services is all it takes to supplant LTC as the second best Cryptocoin, and i intend for OSC to take its place
  329. [10/2/2013 4:21:28 PM] r3wt: yo
  330. [10/2/2013 4:21:53 PM] r3wt: i withrdrew some bitcoins hours ago. it still hasn't been processed and i haven't got my coins. whats going on?
  331. [10/3/2013 1:11:04 PM] r3wt: sup boi boi
  332. [10/8/2013 2:48:10 PM] r3wt: https://bitcointalk.org/index.php?topic=307958.0
  333. [10/8/2013 11:45:14 PM] r3wt: i've developed an amazing idea for the OSC online wallet
  334. [10/8/2013 11:46:11 PM] r3wt: we're gonna have it connect directly with cryptsy api so users can sell osc directly from their wallet
  335. [12:22:33 PM] r3wt: hey
  336. [12:22:52 PM] Bit John: yo
  337. [12:22:58 PM] r3wt: i just saw your poll
  338. [12:23:08 PM] Bit John: I knew you would hit me up
  339. [12:23:43 PM] r3wt: why?
  340. [12:24:43 PM] Bit John: because OSC wasnt on the list
  341. [12:24:57 PM] r3wt: ok
  342. [12:25:48 PM] r3wt: why?
  343. [12:25:59 PM] r3wt: so that means OSC will never be on cryptsy correct?
  344. [12:29:08 PM] Bit John: never said that but the NAN issue makes us resistant to add another of your coins we have already discussed that
  345. [12:30:18 PM] r3wt: muddafudda made nan though...
  346. [12:30:33 PM] Bit John: for you
  347. [12:30:48 PM] r3wt: yeah, he sabotaged it on purpose.
  348. [12:31:18 PM] r3wt: now matter how i fix it, BCX is always there to 51% it or kill it.
  349. [12:32:04 PM] Bit John: still its a coin your considered the developer and owner that has cost the exchange money. So whos to say if we add another of your coins BCX doesnt destroy that and you dont fix it? Then it costs us more money and you walk away
  350. [12:32:23 PM] Bit John: so the only leverage I have to get it fixed is for you to fix the first coin you walked from
  351. [12:32:32 PM] r3wt: he has no attack vector for OSC
  352. [12:32:52 PM] r3wt: all he has is the old litecoin hack artforz invented
  353. [12:33:17 PM] r3wt: every block is checkpointed, he can't time travel it
  354. [12:33:51 PM] Bit John: not the point your other coin is broken we have unhappy customers unless you can support your product we have issues supporting your products.
  355. [12:34:38 PM] r3wt: that's a bunch of bullshit
  356. [12:35:16 PM] Bit John: how do you figure?
  357. [12:35:27 PM] Bit John: there are other exchanges
  358. [12:35:43 PM] r3wt: i see you're iGotSpots bitch now
  359. [12:36:12 PM] r3wt: yeah, i don't like them though
  360. [12:36:17 PM] Bit John: why we havent lost money supporting his coins see this is what I am talking about you get emotional and fly off the handle
  361. [12:36:26 PM] Bit John: this is a business
  362. [12:36:53 PM] Bit John: if you cant conduct business professionally then again supporting your coins is just more risk to us
  363. [12:37:52 PM] Bit John: changing room names flying off the handle spamming chat are not ways to conduct yourself when doing business
  364. [12:37:54 PM] r3wt: well i'm stuck between a rock and a hardplace. i can resurrect nanotokens again, but BCX will used his hahsrate to 51% it again
  365. [12:38:11 PM] Bit John: lots of other coins have managed to find a way out
  366. [12:38:30 PM] Bit John: yours is the only one we have that is not fixed by the developer
  367. [12:38:54 PM] r3wt: they didn't have BCX attacking them though
  368. [12:39:19 PM] Bit John: so why does BCX attack you?
  369. [12:39:20 PM] r3wt: i fixed the fork, thats the easy part
  370. [12:39:31 PM] r3wt: i don't know
  371. [12:39:47 PM] Bit John: well you have obviously made something personal with him
  372. [12:39:59 PM] Bit John: and its your feud to resolve.
  373. [12:40:07 PM] r3wt: he's from texas, i'm from arkansas
  374. [12:40:20 PM] r3wt: it's already personal
  375. [12:40:24 PM] Bit John: look its all about risk adding one of your coins is risky based on past performance
  376. [12:41:19 PM] r3wt: so pretty much there is nothing i can do but hope bcx gives up?
  377. [12:42:59 PM] Bit John: fix your coin or find a way to pay back the losses in BTC to those affected I suppose
  378. [12:43:54 PM] r3wt: i fixed it, then bcx 51'd
  379. [12:44:36 PM] Bit John: I understand but its still broken
  380. [12:51:09 PM] r3wt: i guess i could try to implement the kimoto gravity well and put another one of those monster blocks. mine it. then checkpoint the block and release. i'll hit you up or something
  381. [12:53:04 PM] Bit John: if you do then I will definitley consider OSC :) I like the coin after all
  382. [12:53:14 PM] Bit John: just need you to fix what you started first is all
  383. [12:59:49 PM] *** r3wt sent OSC_concept.jpg ***
  384. [1:00:47 PM] Bit John: I like it
  385. [1:01:37 PM] r3wt: as soon as the open source initiative signs off on my request to reproduce their oficial logo, it will go in the "coin" being held by the hand
  386. [1:33:01 PM] r3wt: just finished the gravity well addition.
  387. [1:33:14 PM] r3wt: now i'm going to cook something up to lock out and start over
  388. [2:20:20 PM] r3wt: well its totally fucked
  389. [2:20:28 PM] Bit John: lol why now?
  390. [2:21:51 PM] r3wt: i don't have enough hash to take over the network
  391. [2:22:16 PM] Bit John: why is anyone mining it?
  392. [2:22:39 PM] r3wt: the chinese never stopped mining it
  393. [2:22:51 PM] Bit John: lol wtf what are they doing with it
  394. [2:23:34 PM] r3wt: can you do me a favor on nanotokens requests you receive? have them email me stuckinabox@live.com
  395. [2:23:46 PM] r3wt: i wanna find out who still is owed coins and who got theirs back
  396. [2:25:57 PM] Bit John: well only guy who got paid out was the 13k guy that all got reversed
  397. [2:26:41 PM] r3wt: i know, but don't you think that the guy who lost 60,000 all of his coins probably got them back already?
  398. [2:26:52 PM] r3wt: i asked him to message you did he ever contact you?
  399. [2:26:57 PM] Bit John: nope
  400. [2:27:29 PM] r3wt: the way i see it the only issue you have is the transaction that got reversed
  401. [2:27:57 PM] r3wt: let me worry about paying back anyone who might come forward with actual evidence they have coins missing.
  402. [2:28:23 PM] Bit John: works for me
  403. [2:33:00 PM] r3wt: so can you clear that 13k from the database and then forward all questions about nanotoken to me?
  404. [2:33:23 PM] Bit John: haha I have been waiting for vern to fix my negative :P
  405. [2:35:30 PM] r3wt: ya, well if nanotokens isn't being added to the excchange again anyway, whats the issue with OSC then?
  406. [2:35:49 PM] r3wt: would that mean i would have to get NAN relisted for OSC to even have a shot?
  407. [2:36:21 PM] Bit John: nope Il talk to vern and see what comes of it
  408. [2:38:44 PM] r3wt: thank's i'll hold my breath
  409. [2:42:25 PM] r3wt: kind of funny how blunder abandoned HBN and no one says shit about that when considering tek
  410. [2:42:41 PM] r3wt: but OSC? nah we can't have that
  411. [2:44:03 PM] Bit John: Again your getting emotional about business decisions
  412. [2:44:27 PM] r3wt: no i just pointed out your obvious bias, thats all
  413. [2:44:55 PM] Bit John: not really worth dicussing if your going down that road aain
  414. [2:44:57 PM] Bit John: again*
  415. [2:45:55 PM] r3wt: well whats the difference? he abandoned HBN, no penalty?
  416. [2:46:40 PM] Bit John: HBN is still being taken care of and still functioning and he has caused us no losses
  417. [2:47:28 PM] r3wt: how did i cause you any losses?
  418. [2:47:47 PM] r3wt: and is NAN not still being taken care of?
  419. [2:49:14 PM] Bit John: well not to long ago I told you we would put OSC back on the table
  420. [2:49:23 PM] Bit John: now your arguing with me about just that
  421. [2:50:07 PM] r3wt: could you please answer the question
  422. [2:50:40 PM] Bit John: several of the customers affected by nan no longer trade here
  423. [2:51:07 PM] r3wt: oh
  424. [2:51:24 PM] Bit John: anyhow your reinforcing my point about being emotional on the issue Cryptsy is a business
  425. [2:52:06 PM] r3wt: no i'm not, i'm asking the necessary questions so that i can fix the problem to both of our benefit. take your third grade logic elsewhere. i wasn't born yesterday you prick
  426. [2:52:24 PM] Bit John: I guess the discussion is over then
  427. [2:53:03 PM] r3wt: if you could give me the straight dobe instead of your teleprompted bubblegum bullshit we wouldn't have to keep having the same discussion over and over again.
  428. [2:54:08 PM] Bit John: anyhow Im moving on
  429. [2:54:52 PM] r3wt: ok be a punk then[/quote]
Add Comment
Please, Sign In to add comment
Public Pastes
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!