Quote
22. AFAIK weve been talking with MP and they resolved it
23. This has been happening for a long time
24. Cryptsy also had this issue a while back
25. wish someone told me that, i just started pos and ended pow
26. lel
27. Please do not repeat this to anyone else, by the way.
28. ok
29. thx
30. If they ask what I needed, say we had a question about the new wallet and PoS
31. yeah i really had no idea about that
32. nobody ever mentioned it
33. even mp jason and mullick the coin guy from cryptsy
34. Well, yeah.
35. they asked for proof of checkpoint server
36. Exchange staff don't want to talk about it because it involves coins being inaccessible, so it makes people scared.
37. I know
38. well they wouldve told me
39. I talked to them every day now
40. and bitjohn too
41. weird
42. ************************
43. EXCEPTION: St13runtime_error
44. CDB() : can't open database file wallet.dat, error 12
45. Whitecoin in AppInit()
46. ************************
47. EXCEPTION: St13runtime_error
48. CDB() : can't open database file wallet.dat, error 12
49. Whitecoin in AppInit()
50. terminate called after throwing an instance of 'std::runtime_error'
51. what(): CDB() : can't open database file wallet.dat, error 12
52. That was with -repairwallet
53. it seems like a common problem when i google it
54. even in bitcoin
55. people saying to re-import private keys or -salvagewallet after backup
56. Not really an option
57. We use accounts extensively
58. alright well
59. can you just try moving the wallet.dat out, resyncing everything brand new, and then putting the wallet.dat back in
60. It works.
61. Well
62. no
63. I'll try that again
64. yo
65. bittrex-richie is reporting the same issue as us
66. ugh
67. did you get it resolved?
68. 
69. No
70. It's pretty bad.
71. ha
72. well those fucking derps in charge shouldve told me the wallet had other issues
73. i had no idea i dont even know where to start with it other than the suggestions on google and such
74. The client mindfox and I worked on solved this issue I think
75. He said it would work
76. but I can't get in contact with him right now
77. he never mentioned that issue
78. he wanted to add coin control and all this stuff
79. is all he told me
80. Yeah, like I said, we don't like talking about it because it means exchanges can't access coins.
81. hes been working on it still
82. well if you guys knew about it and didnt tell me then its pretty much sabotage so im not sure what to say
83. ill try and contact mindfox asap hes still working on it
84. lolwut?
85. Mindfox and I were working on it
86. and we both knew
87. Then I left because of the foundation hiding shit
88. Not my fault you didn't know dude
89. well you left
90. Yeah
91. if mindfox knew he forgot
92. And?
93. hes trying to do other things, add features
94. dunno if he even knew it was an issue
95. So why is it our fault?
96. i dont care whos fault it is, i dont bicker
97. i will ask mindfox asap if he did know about it and knows a resolution
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
33.
34.
35.
36.
37.
38.
39.
40.
41.
42.
43.
44.
45.
46.
47.
48.
49.
50.
51.
52.
53.
54.
55.
56.
57.
58.
59.
60.
61.
62.
63.
64.
65.
66.
67.
68.
69.
70.
71.
72.
73.
74.
75.
76.
77.
78.
79.
80.
81.
82.
83.
84.
85.
86.
87.
88.
89.
90.
91.
92.
93.
94.
95.
96.
97.
Guys, If you don't want this repeated to anyone else, maybe don't make it into a public pastebin?
PROOF cryptowest IS NOT Mindfox.
cryptowest chatting with tf2honeybadger proves nothing about anything.
So, is ccryptcoin really gldcoin?
Maybe try at least reading what's posted.
BUT it's clearly evident you ARE NOT Interested in FACTS.
Respond anyway you wish...
You are now on our "ignore list"...
96.
97.
