Did I get it right - mining is going on despite there is an error?
What to do to get rid of the error? Who's succeed in solving the problem? I am a lit bit panic, sorry
Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 2106. (Read 4671105 times)
If I reclone and recompile in linux it should fix this bug correct?
It should work, yes
If I reclone and recompile in linux it should fix this bug correct?
Lame, still getting this stupid extra parse error...
half a month, without a miner, a pool and GUI.
How can i play with this coin?
I really want to get in, but it's so difficult to me!
How can i play with this coin?
I really want to get in, but it's so difficult to me!
half a month? it's been 5 days only
The block chain says it started about 19 days ago.
When synching, there's a bug that doubles the estimated time to the last synced block. This blockchain started on April 18 at 10:50 GMT, which you can check through timestamps. That puts the age at 13 days.
half a month, without a miner, a pool and GUI.
How can i play with this coin?
I really want to get in, but it's so difficult to me!
How can i play with this coin?
I really want to get in, but it's so difficult to me!
half a month? it's been 5 days only
The block chain says it started about 19 days ago.
If I reclone and recompile in linux it should fix this bug correct?
Thank you
looks like the problem is still occuring despite merged mining having stopped 1 hour ago.
You could try my build till the official one is released: https://www.dropbox.com/s/zb5ch99jlbgp5pv/simplewallet.exe
I built simplewallet.exe for Windows from the new source code. It's working. Here is a link: https://www.dropbox.com/s/zb5ch99jlbgp5pv/simplewallet.exe
Tip me some MRO: 4AyRmUcxzefB5quumzK3HNE4zmCiGc8vhG6fE1oJpGVyVZF7fvDgSpt3MzgLfQ6Q1719xQhmfkM9Z2u NXgDMqYhjJVmc6KX
Tip me some MRO: 4AyRmUcxzefB5quumzK3HNE4zmCiGc8vhG6fE1oJpGVyVZF7fvDgSpt3MzgLfQ6Q1719xQhmfkM9Z2u NXgDMqYhjJVmc6KX
looks like the problem is still occuring despite merged mining having stopped 1 hour ago.
You need to replace the wallet binary if you want to send, receive, or check an updated balance. Mining continued to work all this time.
looks like the problem is still occuring despite merged mining having stopped 1 hour ago.
So are we able to continue mining while a fix is finalized? I'm in no rush to go through the process of updating to a beta wallet if a final one is going to be released soon anyway. I still seem to be synced to the network in the daemon, it's just that obviously the wallet cannot currently receive any new transactions.
Everybody can continue mining and sending money with an updated simplewallet software.
All daemons are ok without any updates because daemons don't care about "extra" field.
Buggy merged mining network is stopped an hour ago.
Please ask your friend not to test incompatible changes on the mainnet, that is what testnet is for
So are we able to continue mining while a fix is finalized? I'm in no rush to go through the process of updating to a beta wallet if a final one is going to be released soon anyway. I still seem to be synced to the network in the daemon, it's just that obviously the wallet cannot currently receive any new transactions.
Mining is still fine even with the old wallet using the daemon
Here are some new x64 linux binaries though: https://mega.co.nz/#!N5dxzZAC!_FOWi9gML1eeSNliyZ4Ihcp6C6tIFdj2xUslnLcNsMQ
win64 binaries are building
Thank you!
So are we able to continue mining while a fix is finalized? I'm in no rush to go through the process of updating to a beta wallet if a final one is going to be released soon anyway. I still seem to be synced to the network in the daemon, it's just that obviously the wallet cannot currently receive any new transactions.
Everybody can continue mining and sending money with an updated simplewallet software.
All daemons are ok without any updates because daemons don't care about "extra" field.
Buggy merged mining network is stopped an hour ago.
So are we able to continue mining while a fix is finalized? I'm in no rush to go through the process of updating to a beta wallet if a final one is going to be released soon anyway. I still seem to be synced to the network in the daemon, it's just that obviously the wallet cannot currently receive any new transactions.
Mining is still fine even with the old wallet using the daemon
Here are some new x64 linux binaries though: https://mega.co.nz/#!N5dxzZAC!_FOWi9gML1eeSNliyZ4Ihcp6C6tIFdj2xUslnLcNsMQ
win64 binaries are building
1st day:
(2^64 - 1 - 1) * (2^-20) * (10^-12)
=(18,446,744,073,709,551,616 -1 -1)*2^(-20)*10^(-12)
=18,446,744,073,709,551,614 * 0.00000095367431640625 * 0.000000000001
=17.592186044415999998092651367188
1 year(365 days):
(2^64 - 1 - 365) * (2^-20) * (10^-12)
=18,446,744,073,709,551,250 * 0.00000095367431640625 * 0.000000000001
=17.592186044415999650955200195313
Am I do the math reght?
(2^64 - 1 - 1) * (2^-20) * (10^-12)
=(18,446,744,073,709,551,616 -1 -1)*2^(-20)*10^(-12)
=18,446,744,073,709,551,614 * 0.00000095367431640625 * 0.000000000001
=17.592186044415999998092651367188
1 year(365 days):
(2^64 - 1 - 365) * (2^-20) * (10^-12)
=18,446,744,073,709,551,250 * 0.00000095367431640625 * 0.000000000001
=17.592186044415999650955200195313
Am I do the math reght?
This block reward formula is recursive so you need to write some code to compute it at a certain date. The "A" parameter is not the number of days but the number of coins in circulation so far in atomic units (rather than decimal shifted value).
1st day:
(2^64 - 1 - 0) * (2^-20) * (10^-12)
= 17.5922
365th day:
(2^64 - 1 - 7.2722*10^18) * (2^-20) * (10^-12)
= 10.6569
how many coins are in existence right now?
Around 300k.
So are we able to continue mining while a fix is finalized? I'm in no rush to go through the process of updating to a beta wallet if a final one is going to be released soon anyway. I still seem to be synced to the network in the daemon, it's just that obviously the wallet cannot currently receive any new transactions.
how many coins are in existence right now?
It doesn't fail in this case but there is no reason to parse it futher because there is no way to understand it. Your version of wallet that continues to parse unknown data is vulnerable to some possible attacks.
Okay, I will make it return on my master then.
Bug is fixed. Please update from git.
I'm going to ask Takotime to build binaries for Windows.
I'm going to ask Takotime to build binaries for Windows.
Your fix is wrong. There is no need to disable all error checking. Simply commenting out the line works fine, I just tested it.
https://github.com/monero-project/bitmonero/commit/cf8fe2867654f0061a17ca4780e736a170a8f87b
In this case the rest of transation can't be parsed by wallet. This means that wallet has to stop parsing this tx. The proper fix will be issued later after talking to Amphibian who created this tx.
There are no issues so far with implementing the fix as in my commit, but yes, this is improper error handling
It further parses after without error
It doesn't fail in this case but there is no reason to parse it futher because there is no way to understand it. Your version of wallet that continues to parse unknown data is vulnerable to some possible attacks.
Bug is fixed. Please update from git.
I'm going to ask Takotime to build binaries for Windows.
I'm going to ask Takotime to build binaries for Windows.
Your fix is wrong. There is no need to disable all error checking. Simply commenting out the line works fine, I just tested it.
https://github.com/monero-project/bitmonero/commit/cf8fe2867654f0061a17ca4780e736a170a8f87b
In this case the rest of transation can't be parsed by wallet. This means that wallet has to stop parsing this tx. The proper fix will be issued later after talking to Amphibian who created this tx.
There are no issues so far with implementing the fix as in my commit, but yes, this is improper error handling
It further parses after without error
Jump to: