Quote from: nametooshort on January 21, 2014, 12:49:44 PM
Transactions in Bitcoin address 1B6Dg74sC8xDmpA9SQyQxQNZaEuZZsDtuT (http://www1.agsexplorer.com/balances/1B6Dg74sC8xDmpA9SQyQxQNZaEuZZsDtuT and http://angelshares.info/lookup.php?addr=1B6Dg74sC8xDmpA9SQyQxQNZaEuZZsDtuT) is inconsistent...
PTS donation amounton January 21 is inconsistent too...

While AngelShares.info is updating their database I am suspending this bounty.  Both AGS and AngelShares.info are resolving bugs and when they both have their fixes ready I will resume the bounty.    I will also increase the bounty and require an analysis of which one was doing it wrong.

I will check this and come back with result later. (agsexplorere.com)


Sent from my iPhone using Tapatalk

Angelshares.info currently has a database problem. Updating the database with new information has become slower and slower as the tables have gotten bigger, to the point where it was taking longer than the block timing. This is due to a design error which we are currently working on fixing. We will post here when the problem is fixed.

Bytemaster, this is why I haven't created your graph yet. However, this problem should be fixed soon, and I should still be able to create this before BTC Miami.

Transactions in Bitcoin address 1B6Dg74sC8xDmpA9SQyQxQNZaEuZZsDtuT (http://www1.agsexplorer.com/balances/1B6Dg74sC8xDmpA9SQyQxQNZaEuZZsDtuT and http://angelshares.info/lookup.php?addr=1B6Dg74sC8xDmpA9SQyQxQNZaEuZZsDtuT) is inconsistent...
PTS donation amounton January 21 is inconsistent too...

Would be nice to extend the bounty to find out the details of the inconsistency.

My API looks good and I checked it multiple times. So who wants to crawl block explorers and find out which displays the most accurate information?

Quote from: bytemaster on January 19, 2014, 04:29:28 AM

Quote from: HackFisher on January 19, 2014, 04:24:00 AM
PTS donation amount on January 18 is different between http://www1.agsexplorer.com/  (about 2331 )and http://www.enccoin.com/ (about 3082) , and http://angelshares.info/ (about 1373)

Which one is correct? due to PTS network lag?

If this inconsistency doesn't resolve itself within the next day then you will get 5 PTS

My PTS address is PdhV9ithAGJsgzR95UdjeS6ihqPqkuz9Cy
Thanks.

Quote from: lakerta06 on January 20, 2014, 05:36:32 PM
I know this bounty is about inconsistencies in the calculation. But anyway you should be aware of the following statement in http://www1.agsexplorer.com/ags101


"How do I find my hidden change addresses or what address actually sends out the donation?
The easiest way is double click the donation transaction in your wallet, in the pop-up window (Transaction Detail), find the Transation ID, look it up in blockchain explorer.

BTC: http://blockchain.info/tx/[your transation id]
PTS: http://coinplorer.com/PTS/Transactions/[your transation id]
The addresses shown in the "Inputs" section is actual address(es) your donation is sent from.

Note: sometimes it has multiple input addresses, they will be credited AGS proportionally by AGSExplorer.com. When AngelShares genesis block is generated, 3I will randomly pick one of these addresses to credit AGS [?]. To redeem AGS in the future, it's safe to import the whole wallet that contains all these addresses."

It appears AGSexplorer is not following the spec which says 100% should be credited to the first input to the transaction.

I know this bounty is about inconsistencies in the calculation. But anyway you should be aware of the following statement in http://www1.agsexplorer.com/ags101


"How do I find my hidden change addresses or what address actually sends out the donation?
The easiest way is double click the donation transaction in your wallet, in the pop-up window (Transaction Detail), find the Transation ID, look it up in blockchain explorer.

BTC: http://blockchain.info/tx/[your transation id]
PTS: http://coinplorer.com/PTS/Transactions/[your transation id]
The addresses shown in the "Inputs" section is actual address(es) your donation is sent from.

Note: sometimes it has multiple input addresses, they will be credited AGS proportionally by AGSExplorer.com. When AngelShares genesis block is generated, 3I will randomly pick one of these addresses to credit AGS [?]. To redeem AGS in the future, it's safe to import the whole wallet that contains all these addresses."

BTC donation amount on 15Th is also different between  www1.agsexplorer.com (53.96) and http://www.enccoin.com/ (35.86) too, this might need check, other days are slight different.

If we take a look at blockchain statistic, also have different result, but it seems blockchain statistic is quite rough and not accurate.
https://blockchain.info/charts/received-per-day?showDataPoints=true&show_header=true&daysAverageString=1&timespan=30days&scale=0&address=1ANGELwQwWxMmbdaSWhWLqBEtPTkWb8uDc

Quote from: HackFisher on January 19, 2014, 04:24:00 AM
PTS donation amount on January 18 is different between http://www1.agsexplorer.com/  (about 2331 )and http://www.enccoin.com/ (about 3082) , and http://angelshares.info/ (about 1373)

Which one is correct? due to PTS network lag?

If this inconsistency doesn't resolve itself within the next day then you will get 5 PTS

PTS donation amount on January 18 is different between http://www1.agsexplorer.com/  (about 2331 )and http://www.enccoin.com/ (about 3082) , and http://angelshares.info/ (about 1373)

Which one is correct? due to PTS network lag?

Quote from: donschoe on January 15, 2014, 10:44:57 PM

Quote from: bytemaster on January 15, 2014, 10:40:19 PM

Quote from: donschoe on January 15, 2014, 10:34:06 PM

Quote from: bytemaster on January 15, 2014, 10:22:20 PM

Quote from: donschoe on January 15, 2014, 10:06:48 PM
this thread is misleading, bytemaster.

you issued AGS, and you should define how donations from multiple input addresses are handled.

of course i could take the time to write down detailled documentation on the algorithm, but to be honest, it would be better to announce how it will be.

after that me and the fluxxer can adjust their algorithms to fit the defined allocation procedure.

The algorithm I defined was that the first input address of every transaction should be the one allocated the AGS.

Define "first". Isnt that too random? What about the input address with highest input?

If all addresses belong to the same person then it doesn't matter which one is picked so long as it is deterministic.  First is deterministic, there may be two addresses with the same input amount.

Okay, right, I will think about that. I got to rewrite the API to match this. I hope this wont cause confusion.

* donschoe pokes angelshares.info guys

The ags.info site must use the same algorithm too. How to ensure both sites pick the same first input address? Is the daemon always reporting the same input as "first"?

It is deterministic in the blockchain.

Quote from: bytemaster on January 15, 2014, 10:40:19 PM

Quote from: donschoe on January 15, 2014, 10:34:06 PM

Quote from: bytemaster on January 15, 2014, 10:22:20 PM

Quote from: donschoe on January 15, 2014, 10:06:48 PM
this thread is misleading, bytemaster.

you issued AGS, and you should define how donations from multiple input addresses are handled.

of course i could take the time to write down detailled documentation on the algorithm, but to be honest, it would be better to announce how it will be.

after that me and the fluxxer can adjust their algorithms to fit the defined allocation procedure.

The algorithm I defined was that the first input address of every transaction should be the one allocated the AGS.

Define "first". Isnt that too random? What about the input address with highest input?

If all addresses belong to the same person then it doesn't matter which one is picked so long as it is deterministic.  First is deterministic, there may be two addresses with the same input amount.

Okay, right, I will think about that. I got to rewrite the API to match this. I hope this wont cause confusion.


The ags.info site must use the same algorithm too. How to ensure both sites pick the same first input address? Is the daemon always reporting the same input as "first"?

Quote from: donschoe on January 15, 2014, 10:34:06 PM

Quote from: bytemaster on January 15, 2014, 10:22:20 PM

Quote from: donschoe on January 15, 2014, 10:06:48 PM
this thread is misleading, bytemaster.

you issued AGS, and you should define how donations from multiple input addresses are handled.

of course i could take the time to write down detailled documentation on the algorithm, but to be honest, it would be better to announce how it will be.

after that me and the fluxxer can adjust their algorithms to fit the defined allocation procedure.

The algorithm I defined was that the first input address of every transaction should be the one allocated the AGS.

Define "first". Isnt that too random? What about the input address with highest input?

If all addresses belong to the same person then it doesn't matter which one is picked so long as it is deterministic.  First is deterministic, there may be two addresses with the same input amount.

Quote from: bytemaster on January 15, 2014, 10:22:20 PM

Quote from: donschoe on January 15, 2014, 10:06:48 PM
this thread is misleading, bytemaster.

you issued AGS, and you should define how donations from multiple input addresses are handled.

of course i could take the time to write down detailled documentation on the algorithm, but to be honest, it would be better to announce how it will be.

after that me and the fluxxer can adjust their algorithms to fit the defined allocation procedure.

The algorithm I defined was that the first input address of every transaction should be the one allocated the AGS.

Define "first". Isnt that too random? What about the input address with highest input?