Guest User

Untitled

a guest
May 4th, 2014
244
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.87 KB | None | 0 0
  1. <tf2honeybadger> Hey
  2. <cryptowest> something wrong?
  3. <tf2honeybadger> Yes
  4. <tf2honeybadger> ************************
  5. <tf2honeybadger> EXCEPTION: St13runtime_error
  6. <tf2honeybadger> CDB() : can't open database file wallet.dat, error 12
  7. <tf2honeybadger> Whitecoin in AppInit()
  8. <tf2honeybadger> This has been happening with the Whitecoin walet
  9. <tf2honeybadger> wallet*
  10. <tf2honeybadger> MintPal also reported issues
  11. <tf2honeybadger> as did others when I asked originally
  12. <cryptowest> still? mp said things were ok
  13. <tf2honeybadger> Mindfox and I determined it was because of invalid transactions being inserted due to buggy PoS code
  14. <cryptowest> i think had to rescan
  15. <tf2honeybadger> I asked them days ago
  16. <tf2honeybadger> This isn't a blockchain error
  17. <tf2honeybadger> This is a wallet.dat problem
  18. <cryptowest> yeah run repairwallet
  19. <cryptowest> it might be confused because there is a checkpointing server now
  20. <cryptowest> and never was before
  21. <tf2honeybadger> no....that's not it, but I'll do it for you
  22. <cryptowest> AFAIK weve been talking with MP and they resolved it
  23. <tf2honeybadger> This has been happening for a long time
  24. <tf2honeybadger> Cryptsy also had this issue a while back
  25. <cryptowest> wish someone told me that, i just started pos and ended pow
  26. <cryptowest> lel
  27. <tf2honeybadger> Please do not repeat this to anyone else, by the way.
  28. <cryptowest> ok
  29. <cryptowest> thx
  30. <tf2honeybadger> If they ask what I needed, say we had a question about the new wallet and PoS
  31. <cryptowest> yeah i really had no idea about that
  32. <cryptowest> nobody ever mentioned it
  33. <cryptowest> even mp jason and mullick the coin guy from cryptsy
  34. <tf2honeybadger> Well, yeah.
  35. <cryptowest> they asked for proof of checkpoint server
  36. <tf2honeybadger> Exchange staff don't want to talk about it because it involves coins being inaccessible, so it makes people scared.
  37. <tf2honeybadger> I know
  38. <cryptowest> well they wouldve told me
  39. <tf2honeybadger> I talked to them every day now
  40. <tf2honeybadger> and bitjohn too
  41. <cryptowest> weird
  42. <tf2honeybadger> ************************
  43. <tf2honeybadger> EXCEPTION: St13runtime_error
  44. <tf2honeybadger> CDB() : can't open database file wallet.dat, error 12
  45. <tf2honeybadger> Whitecoin in AppInit()
  46. <tf2honeybadger> ************************
  47. <tf2honeybadger> EXCEPTION: St13runtime_error
  48. <tf2honeybadger> CDB() : can't open database file wallet.dat, error 12
  49. <tf2honeybadger> Whitecoin in AppInit()
  50. <tf2honeybadger> terminate called after throwing an instance of 'std::runtime_error'
  51. <tf2honeybadger> what(): CDB() : can't open database file wallet.dat, error 12
  52. <tf2honeybadger> That was with -repairwallet
  53. <cryptowest> it seems like a common problem when i google it
  54. <cryptowest> even in bitcoin
  55. <cryptowest> people saying to re-import private keys or -salvagewallet after backup
  56. <tf2honeybadger> Not really an option
  57. <tf2honeybadger> We use accounts extensively
  58. <cryptowest> alright well
  59. <cryptowest> can you just try moving the wallet.dat out, resyncing everything brand new, and then putting the wallet.dat back in
  60. <tf2honeybadger> It works.
  61. <tf2honeybadger> Well
  62. <tf2honeybadger> no
  63. <tf2honeybadger> I'll try that again
  64. <tf2honeybadger> yo
  65. <tf2honeybadger> bittrex-richie is reporting the same issue as us
  66. <cryptowest> ugh
  67. <cryptowest> did you get it resolved?
  68. <cryptowest> :(
  69. <tf2honeybadger> No
  70. <tf2honeybadger> It's pretty bad.
  71. <cryptowest> ha
  72. <cryptowest> well those fucking derps in charge shouldve told me the wallet had other issues
  73. <cryptowest> i had no idea i dont even know where to start with it other than the suggestions on google and such
  74. <tf2honeybadger> The client mindfox and I worked on solved this issue I think
  75. <tf2honeybadger> He said it would work
  76. <tf2honeybadger> but I can't get in contact with him right now
  77. <cryptowest> he never mentioned that issue
  78. <cryptowest> he wanted to add coin control and all this stuff
  79. <cryptowest> is all he told me
  80. <tf2honeybadger> Yeah, like I said, we don't like talking about it because it means exchanges can't access coins.
  81. <cryptowest> hes been working on it still
  82. <cryptowest> well if you guys knew about it and didnt tell me then its pretty much sabotage so im not sure what to say
  83. <cryptowest> ill try and contact mindfox asap hes still working on it
  84. <tf2honeybadger> lolwut?
  85. <tf2honeybadger> Mindfox and I were working on it
  86. <tf2honeybadger> and we both knew
  87. <tf2honeybadger> Then I left because of the foundation hiding shit
  88. <tf2honeybadger> Not my fault you didn't know dude
  89. <cryptowest> well you left
  90. <tf2honeybadger> Yeah
  91. <cryptowest> if mindfox knew he forgot
  92. <tf2honeybadger> And?
  93. <cryptowest> hes trying to do other things, add features
  94. <cryptowest> dunno if he even knew it was an issue
  95. <tf2honeybadger> So why is it our fault?
  96. <cryptowest> i dont care whos fault it is, i dont bicker
  97. <cryptowest> i will ask mindfox asap if he did know about it and knows a resolution
Add Comment
Please, Sign In to add comment