Serious business developers, not wasting time on promotion, only doing serious business sh*t!
Even Bitcoin does not have some features Bytecoin has. Maaan, i love Bytecoin!
Topic: [BCN] Bytecoin. Secure, private, untraceable since 2012 - page 240. (Read 1070171 times)
We are betatesters in real-time. Why do not you do betatesting before releasing of such important update? I think it worked fine with previous major update. ... At least from my view.
From my view this is a minor mistake of out devs, but c'mon, give them credit for the biggest update in CN coins history!
This is what I am talking about "minor mistake" which should be discovered before releasing. I am not affected too much personally but maybe pool's admins have more headache. I know that devs do great job but these small issues are maybe pity because this is something which do not show BCN in good light... in short time. I trust that the future will be shiny.
Message for DEVS please do not be pushed by us.. users. :-) Take time what you need.
Problem solved
you must erase wallet.bin (or whatever your walle name is" and make new sync
DONT ERASE WALLET.BIN.KEYS , you will lost everthing
So safest is to zip all three files and make backup and then make changes
DONT ERASE WALLET.BIN.KEYS , you will lost everthing
So safest is to zip all three files and make backup and then make changes
Worked, thank you.
you must erase wallet.bin (or whatever your walle name is" and make new sync
DONT ERASE WALLET.BIN.KEYS , you will lost everthing
So safest is to zip all three files and make backup and then make changes
DONT ERASE WALLET.BIN.KEYS , you will lost everthing
So safest is to zip all three files and make backup and then make changes
I cant open my wallet with the new version, but in the older version everything works fine.
This is the error.
EDIT:
The same wallet in the older version.
thanks
This is the error.
Code:
2014-Aug-13 22:16:20.851338 bytecoin wallet v1.0.0.312()
2014-Aug-13 22:16:43.923779 Loaded wallet keys file, with public address: 28pquteWfPqY2Pj3pzoexLFV8o5CH7Soqd6Pr81b6esB61dMsUPJrRxgsdhwMJmFn9jMpMmS3Dv4wQaVzaWMX19sNJd93dL
2014-Aug-13 22:16:44.251379 ERROR C:\projects\sorrybigbro\src\common/boost_serialization_helper.h:104 Exception at [unserialize_obj_from_file], what=unsupported version
2014-Aug-13 22:16:44.251379 ERROR ..\..\src\wallet\wallet2.cpp:683 !r. THROW EXCEPTION: error::file_read_error
2014-Aug-13 22:16:44.251379 ..\..\src\wallet\wallet2.cpp:683:struct tools::error::file_error_base<2>: failed to read file "testewallet.bin"
2014-Aug-13 22:16:44.251379 Error: failed to load wallet: failed to read file "testewallet.bin"
2014-Aug-13 22:16:44.266979 ERROR ..\..\src\simplewallet\simplewallet.cpp:431 could not open account
2014-Aug-13 22:16:44.266979 ERROR ..\..\src\simplewallet\simplewallet.cpp:1121 Failed to initialize wallet
EDIT:
The same wallet in the older version.
Code:
2014-Aug-13 22:32:57.060028 bytecoin wallet v0.8.11.65()
2014-Aug-13 22:33:07.270042 Loaded wallet keys file, with public address: 28pquteWfPqY2Pj3pzoexLFV8o5CH7Soqd6Pr81b6esB61dMsUPJrRxgsdhwMJmFn9jMpMmS3Dv4wQaVzaWMX19sNJd93dL
2014-Aug-13 22:33:07.420043 Opened wallet: 28pquteWfPqY2Pj3pzoexLFV8o5CH7Soqd6Pr81b6esB61dMsUPJrRxgsdhwMJmFn9jMpMmS3Dv4wQaVzaWMX19sNJd93dL
2014-Aug-13 22:33:07.440043 Starting refresh...
2014-Aug-13 22:33:07.450043 Block is already in blockchain: eeb8781a59aab14017b1a2ec0c80cb0d26ce94e5232380c5860a1678f4070778
2014-Aug-13 22:33:07.450043 Processed block: <4834e7e64f076dac7f90600882e8d1dc6041d2fa53e63faf12cfc1e81186da4a>, height 544794, 0(0/0)ms
2014-Aug-13 22:33:07.470043 Block is already in blockchain: 4834e7e64f076dac7f90600882e8d1dc6041d2fa53e63faf12cfc1e81186da4a
2014-Aug-13 22:33:07.470043 Refresh done, blocks received: 1, balance: **************, unlocked: **************
2014-Aug-13 22:33:07.470043 Refresh done, blocks received: 1
2014-Aug-13 22:33:07.480043 balance: **************, unlocked balance: **************
2014-Aug-13 22:33:07.480043 **********************************************************************
Use "help" command to see the list of available commands.
**********************************************************************
2014-Aug-13 22:33:19.020059 Read command: exit
thanks
We are betatesters in real-time. Why do not you do betatesting before releasing of such important update? I think it worked fine with previous major update. ... At least from my view.
From my view this is a minor mistake of out devs, but c'mon, give them credit for the biggest update in CN coins history!
This is what I am talking about "minor mistake" which should be discovered before releasing. I am not affected too much personally but maybe pool's admins have more headache. I know that devs do great job but these small issues are maybe pity because this is something which do not show BCN in good light... in short time. I trust that the future will be shiny.
Message for DEVS please do not be pushed by us.. users. :-) Take time what you need.
We are betatesters in real-time. Why do not you do betatesting before releasing of such important update? I think it worked fine with previous major update. ... At least from my view.
From my view this is a minor mistake of out devs, but c'mon, give them credit for the biggest update in CN coins history!
I see your problem is finally solved, good for you.
So with this new update Bytecoin apparently has the safest transactions now.
Good stuff...
So with this new update Bytecoin apparently has the safest transactions now.
Good stuff...
The way this bug is created:
1. You've sent a transaction some time ago which was included in the tx pool and stuck their for some time.
2. You've downloaded a buggy version of simplewallet this morning.
3. To fix the bug you deleted "wallet.bin" that contains all the info regarding already used inputs.
4. While refreshing, the wallet analyzed the blockchain and found all the used inputs there but it knows nothing about tx pools transactions waiting to be included into the blocks.
5. When trying to send a new transfer the wallet randomly chooses the inputs that are awaiting in the tx pool and therefore detects a double-spending attack.
Good news, it is solvable and we'll fix the wallet asap.
Bad news, it seems that you should wait up to 24 hours so that the transaction is either accepted by the network or is returned from tx pool.
1. You've sent a transaction some time ago which was included in the tx pool and stuck their for some time.
2. You've downloaded a buggy version of simplewallet this morning.
3. To fix the bug you deleted "wallet.bin" that contains all the info regarding already used inputs.
4. While refreshing, the wallet analyzed the blockchain and found all the used inputs there but it knows nothing about tx pools transactions waiting to be included into the blocks.
5. When trying to send a new transfer the wallet randomly chooses the inputs that are awaiting in the tx pool and therefore detects a double-spending attack.
Good news, it is solvable and we'll fix the wallet asap.
Bad news, it seems that you should wait up to 24 hours so that the transaction is either accepted by the network or is returned from tx pool.
We are betatesters in real-time. Why do not you do betatesting before releasing of such important update? I think it worked fine with previous major update. ... At least from my view.
Ok I will wait latest binaries and then start solomining
The way this bug is created:
1. You've sent a transaction some time ago which was included in the tx pool and stuck their for some time.
2. You've downloaded a buggy version of simplewallet this morning.
3. To fix the bug you deleted "wallet.bin" that contains all the info regarding already used inputs.
4. While refreshing, the wallet analyzed the blockchain and found all the used inputs there but it knows nothing about tx pools transactions waiting to be included into the blocks.
5. When trying to send a new transfer the wallet randomly chooses the inputs that are awaiting in the tx pool and therefore detects a double-spending attack.
Good news, it is solvable and we'll fix the wallet asap.
Bad news, it seems that you should wait up to 24 hours so that the transaction is either accepted by the network or is returned from tx pool.
1. You've sent a transaction some time ago which was included in the tx pool and stuck their for some time.
2. You've downloaded a buggy version of simplewallet this morning.
3. To fix the bug you deleted "wallet.bin" that contains all the info regarding already used inputs.
4. While refreshing, the wallet analyzed the blockchain and found all the used inputs there but it knows nothing about tx pools transactions waiting to be included into the blocks.
5. When trying to send a new transfer the wallet randomly chooses the inputs that are awaiting in the tx pool and therefore detects a double-spending attack.
Good news, it is solvable and we'll fix the wallet asap.
Bad news, it seems that you should wait up to 24 hours so that the transaction is either accepted by the network or is returned from tx pool.
It looks like I found problem
When I made full backup and start it after sync I have 0 BCN
When I delete wallet, put in new binaries then I have ( after sync) 8000 BCN
Can someone send me just few BCN to test it: since it is clear that I cannot send any if I dont have any
Is it safe now to do solomining? I would not like to lost block ot two when I found with new binaries
When I made full backup and start it after sync I have 0 BCN
When I delete wallet, put in new binaries then I have ( after sync) 8000 BCN
Can someone send me just few BCN to test it: since it is clear that I cannot send any if I dont have any
Is it safe now to do solomining? I would not like to lost block ot two when I found with new binaries
2014-Aug-13 20:37:31.011531 Starting...
2014-Aug-13 20:37:31.017532 bytecoin v0.8.11.65()
2014-Aug-13 20:37:31.019532 Module folder: D:\COINS\BYTECOIN\bytecoind.exe
2014-Aug-13 20:37:31.017532 bytecoin v0.8.11.65()
2014-Aug-13 20:37:31.019532 Module folder: D:\COINS\BYTECOIN\bytecoind.exe
v0.8 is old
the latest i have now is v1.0.0.312 is that the proper latest version?
Yes, it is.
From the first glance, everything should be working fine within 24 hours when the tx pool transactions would be either included into the blocks or returned back. This is likely a behavior associated with the change in tx pool algorithm made in this update.
BTW, the working link for Windows Full Kit is https://mega.co.nz/#!kZQm0R7Y!2Q9FA2cFbUWHlrmBldYBuQZSPrF3AJzJH2YxoK2KU4c - Mega is buggy sometimes.
2014-Aug-13 20:37:31.011531 Starting...
2014-Aug-13 20:37:31.017532 bytecoin v0.8.11.65()
2014-Aug-13 20:37:31.019532 Module folder: D:\COINS\BYTECOIN\bytecoind.exe
2014-Aug-13 20:37:31.017532 bytecoin v0.8.11.65()
2014-Aug-13 20:37:31.019532 Module folder: D:\COINS\BYTECOIN\bytecoind.exe
v0.8 is old
the latest i have now is v1.0.0.312 is that the proper latest version?
2014-Aug-13 20:37:31.011531 Starting...
2014-Aug-13 20:37:31.017532 bytecoin v0.8.11.65()
2014-Aug-13 20:37:31.019532 Module folder: D:\COINS\BYTECOIN\bytecoind.exe
2014-Aug-13 20:37:31.017532 bytecoin v0.8.11.65()
2014-Aug-13 20:37:31.019532 Module folder: D:\COINS\BYTECOIN\bytecoind.exe
I do that at least three times. I am bored of that : downloading full set: I will let you know result
We're investigating the issue.
I must apologize but it seems that Full Kit for windows was not updated. I've just uploaded a new link to the website. Here it is:
https://mega.co.nz/#!YIRXUD5Z!LTHZeY2HVc9AnIIgNcChxFNYUh7DsdHaLY4WwiEn16Q
You are really "good guys"
I downloaded "LATEST DATA" from your website and got what?
Old version of daemon and wallet with blockchain older then 15 day!
BEATIFULL
Could you not update it with newer block chain and latest binaries
I downloaded "LATEST DATA" from your website and got what?
Old version of daemon and wallet with blockchain older then 15 day!
BEATIFULL
Could you not update it with newer block chain and latest binaries
Our bad, the link was not updated on the website. Now it is.
I do that at least three times. I am bored of that : downloading full set: I will let you know result
We're investigating the issue.
I must apologize but it seems that Full Kit for windows was not updated. I've just uploaded a new link to the website. Here it is:
https://mega.co.nz/#!YIRXUD5Z!LTHZeY2HVc9AnIIgNcChxFNYUh7DsdHaLY4WwiEn16Q
You are really "good guys"
I downloaded "LATEST DATA" from your website and got what?
Old version of daemon and wallet with blockchain older then 15 day!
BEATIFULL
Could you not update it with newer block chain and latest binaries
I downloaded "LATEST DATA" from your website and got what?
Old version of daemon and wallet with blockchain older then 15 day!
BEATIFULL
Could you not update it with newer block chain and latest binaries
Our bad, the link was not updated on the website. Now it is.
This new link give me temporary error.
So I made full backup of blockchain and wallet.
And when new version be ready, let us know
Be happy to try it
I do that at least three times. I am bored of that : downloading full set: I will let you know result
We're investigating the issue.
I must apologize but it seems that Full Kit for windows was not updated. I've just uploaded a new link to the website. Here it is:
https://mega.co.nz/#!kZQm0R7Y!2Q9FA2cFbUWHlrmBldYBuQZSPrF3AJzJH2YxoK2KU4c
You are really "good guys"
I downloaded "LATEST DATA" from your website and got what?
Old version of daemon and wallet with blockchain older then 15 day!
BEATIFULL
Could you not update it with newer block chain and latest binaries
I downloaded "LATEST DATA" from your website and got what?
Old version of daemon and wallet with blockchain older then 15 day!
BEATIFULL
Could you not update it with newer block chain and latest binaries
Our bad, the link was not updated on the website. Now it is.
You are really "good guys"
I downloaded "LATEST DATA" from your website and got what?
Old version of daemon and wallet with blockchain older then 15 day!
BEATIFULL
Could you not update it with newer block chain and latest binaries
I downloaded "LATEST DATA" from your website and got what?
Old version of daemon and wallet with blockchain older then 15 day!
BEATIFULL
Could you not update it with newer block chain and latest binaries
1. I now use v.0.0.312
2014-Aug-13 19:35:48.502760 Starting...
2014-Aug-13 19:35:48.507760 bytecoin v1.0.0.312()
2014-Aug-13 19:35:48.509760 Module folder: D:\COINS\BYTECOIN\bytecoind.exe
2. wallet is same version
I overwrite daemon and wallet with new version.
Only thing I didnot change is blockchain.
3. I use same syntax as 33zer0wolf and got this in wallet
[wallet 2AspAR]: transfer 0 25cZNQYVAi3issDCoa6fWA2Aogd4FgPhYdpX3p8KLfhKC6sN8s6Q9WpcW4778TPwcUS5jEM25JrQvjD 3XjsvXuNHSWhYUsu 500 -p aac3
3b339d3e4a6758b596cdeaab5fd524dc8bbc5d4bea8c804794b7cf97f230
Error: transaction <96d15c74eca21a354bdb8849e6c1a4676cb485865e021b2c52ffb74e066c4ed1> was rejected by daemon with status "Failed"
[wallet 2AspAR]:
and in daemon
...
2014-Aug-13 19:35:48.502760 Starting...
2014-Aug-13 19:35:48.507760 bytecoin v1.0.0.312()
2014-Aug-13 19:35:48.509760 Module folder: D:\COINS\BYTECOIN\bytecoind.exe
2. wallet is same version
I overwrite daemon and wallet with new version.
Only thing I didnot change is blockchain.
3. I use same syntax as 33zer0wolf and got this in wallet
[wallet 2AspAR]: transfer 0 25cZNQYVAi3issDCoa6fWA2Aogd4FgPhYdpX3p8KLfhKC6sN8s6Q9WpcW4778TPwcUS5jEM25JrQvjD 3XjsvXuNHSWhYUsu 500 -p aac3
3b339d3e4a6758b596cdeaab5fd524dc8bbc5d4bea8c804794b7cf97f230
Error: transaction <96d15c74eca21a354bdb8849e6c1a4676cb485865e021b2c52ffb74e066c4ed1> was rejected by daemon with status "Failed"
[wallet 2AspAR]:
and in daemon
...
Could you please delete your "wallet.bin" file (not the .keys file as your money will be lost then), then refresh the wallet and try transferring again?
I do that at least three times. I am bored of that : downloading full set: I will let you know result
Jump to: