BitShares Forum
Other => Graveyard => Muse/SoundDAC => Topic started by: trytinysmart on October 11, 2014, 10:15:54 am
-
Now, music-tracker supports Linux, Mac OS X windows binary.
https://bintray.com/bts-utils/music-tracker/music-tracker/view/files
music-tracker https://github.com/bts-utils/music-tracker
BitShares Music Note pre-sale tracker.
$ ./music-tracker fetch
Day Date BTC Notes/BTC
1 2014-10-06 34.786598 143733.515422
2 2014-10-07 39.459149 126713.324696
3 2014-10-08 32.596869 153388.966563
4 2014-10-09 33.257446 150342.271546
5 2014-10-10 27.134661 184266.170015
6 2014-10-11 28.818317 173500.762096
7 2014-10-12 0.372000 13440860.215054
Total BTC AVG BTC AVG Notes
196.425040 28.060720 178185.021697
Sparkline:
██▇▇▆▆▁
-
great :)
-
ui .. we can use more cool tools like this .. +5%
-
Next, I will use Go language to refactor it. Cross platform is very important!
;D
-
very cool tool .. just checked it out .. works nice with linux too ..
never heard of textql .. but i REALLY love it .. awesome! +5%
can I tip you some btsx via "trytinysmart"?
-
Yes, my btsx ID is "trytinysmart", key is BTSX5MZKHUAp5C2z6ZtU5twJ6vTSVH8gAv9UEPpr1tQGbpsmTGZJuT
Thanks, :)
very cool tool .. just checked it out .. works nice with linux too ..
never heard of textql .. but i REALLY love it .. awesome! +5%
can I tip you some btsx via "trytinysmart"?
-
Good stuff @trytinysmart.
I noticed that the data source is from blockchain.info's history data API. The timestamp it uses is the time transaction is made instead of the time the block is produced which includes the transactions. For those transactions made close to the end of the day may be included in the block that is produced the next day. Therefore the totals and the ratio could be slightly different from the official calculation. But as for a quick ticker to know what the progress is, this is good enough. I think you might want to add this to your README to prevent confusion.
If you need, I can provide you a data source from agsexplorer.com which corrects that tx timestamp vs block timestamp issue.
Sent from my iPhone using Tapatalk
-
Thank you for your reminding me. I need it.
Good stuff @trytinysmart.
I noticed that the data source is from blockchain.info's history data API. The timestamp it uses is the time transaction is made instead of the time the block is produced which includes the transactions. For those transactions made close to the end of the day may be included in the block that is produced the next day. Therefore the totals and the ratio could be slightly different from the official calculation. But as for a quick ticker to know what the progress is, this is good enough. I think you might want to add this to your README to prevent confusion.
If you need, I can provide you a data source from agsexplorer.com which corrects that tx timestamp vs block timestamp issue.
Sent from my iPhone using Tapatalk
-
http://www1.agsexplorer.com/ticker/music/btc.json
I twisted the API a bit and it should suit your need.
-
Good stuff @trytinysmart.
I noticed that the data source is from blockchain.info's history data API. The timestamp it uses is the time transaction is made instead of the time the block is produced which includes the transactions. For those transactions made close to the end of the day may be included in the block that is produced the next day. Therefore the totals and the ratio could be slightly different from the official calculation. But as for a quick ticker to know what the progress is, this is good enough. I think you might want to add this to your README to prevent confusion.
If you need, I can provide you a data source from agsexplorer.com which corrects that tx timestamp vs block timestamp issue.
How is the official calculation? Is it upon one confirmation?
-
Yes. Only the block time matters. Transaction sent at time x and is included in block at time y. Time y is used as the time of donation.
Sent from my iPhone using Tapatalk
-
@boombastic: just noticed via osx and FF 32
(http://i.imgur.com/aitkKIU.png)
hope this helps ...
-
Yes. Only the block time matters. Transaction sent at time x and is included in block at time y. Time y is used as the time of donation.
Ahh.. then I have missed the inclusion for that good day. :(
-
@boombastic: just noticed via osx and FF 32
(http://i.imgur.com/aitkKIU.png)
hope this helps ...
Thanks for letting me know. It's fixed now.
-
Yes. Only the block time matters. Transaction sent at time x and is included in block at time y. Time y is used as the time of donation.
One more question. When you say "block time", how many BTC confirmations do you mean?
-
Yes. Only the block time matters. Transaction sent at time x and is included in block at time y. Time y is used as the time of donation.
One more question. When you say "block time", how many BTC confirmations do you mean?
that block that has that particular transaction included ... so basically a single confirmation is sufficient