Author Topic: Cryptofresh Block Explorer + MUSE now available  (Read 96355 times)

0 Members and 1 Guest are viewing this topic.

Offline hybridd

  • Full Member
  • ***
  • Posts: 164
    • View Profile
  • BitShares: hybr1d
I've actually found this site useful as a debugging tool as well, nice job.
#btstip roadscape 100
http://sharebits.io - #sharebits "person" amount asset - Start tipping on bitsharestalk today!
Developer @ Freebie

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Is there a block explorer that shows info on a particular address, eg its balance & whether its claimed or not? This should be possible as most people arent using stealth addresses anymore.
You can only see account balances .. address don't hold funds except for those addresses in the genesis block .. I would suggest to take a look at the genesis block if you want to see your unclaimed balance:
https://github.com/bitshares/bitshares-2/blob/bitshares/genesis.json

Offline speedy

  • Hero Member
  • *****
  • Posts: 1160
    • View Profile
  • BitShares: speedy
Is there a block explorer that shows info on a particular address, eg its balance & whether its claimed or not? This should be possible as most people arent using stealth addresses anymore.

Offline maqifrnswa

  • Hero Member
  • *****
  • Posts: 661
    • View Profile
update on worker budget.
tl;dr: daily worker budget is the minimum of
worker_budget_per_day (from get_global_properties)
and
24*worker_budget (from the most recent get_object 2.13.X)

It currently is 360k BTS, not 500k BTS

Full write up:
every hour the worker budget is processed, but the budget isn't 500k BTS like i said, that is just the maximum. How it works:

Every second, [ 17/(2^32) * reserve fund ] is allocated for witnesses and workers where reserve fund is how many BTS are currently not distributed. This is defined in:
https://github.com/cryptonomex/graphene/blob/f85dec1c23f6bf9259ad9f15311b2e4aac4f9d44/libraries/chain/include/graphene/chain/config.hpp

Every hour the total available reserve fund is calculated by finding how many BTS are available to be distributed and how many BTS will be returned to the reserve fund (i.e., "burnt") during the next maintenance interval.

First find how many BTS have not been distributed:
Code: [Select]
from_initial_reserve = max_supply - current supply of BTS
from:
max_supply: get_object 1.3.0
current_supply: get_object 2.3.0


then modify it by adding the accumulated fees and witness budget remaining (i.e., 1.5 BTS per block is budgeted, so budget remaining is 1.5 BTS * (number of blocks left in maintenance period+blocks missed by witnesses))  in this maintenance cycle (they will be added to the "reserve fund" permanently at maintenance)

Code: [Select]
updated reserve fund = from_initial_reserve +  from_accumulated_fees + from_unused_witness_budgetvariables all from: get_object 2.13.* (choose the most recent one, for example)
for example:
Code: [Select]
new >>> get_object 2.13.361
get_object 2.13.361
[{
    "id": "2.13.361",
    "time": "2015-10-28T15:00:00",
    "record": {
      "time_since_last_budget": 3600,
      "from_initial_reserve": "106736452914941",
      "from_accumulated_fees": 15824269,
      "from_unused_witness_budget": 2250000,
      "requested_witness_budget": 180000000,
      "total_budget": 1520913100,
      "witness_budget": 180000000,
      "worker_budget": 1340913100,
      "leftover_worker_funds": 0,
      "supply_delta": 1502838831
    }
  }
]


then calculate how much is available to be spent on workers and witnesses is:

Code: [Select]
total_budget = (updated reserve fund)*(time_since_last_budget)*17/(2^32)
rounded up to the nearest integer

Ok, now to find how much workers will get in this budget period (1 hour), you find the smaller of the available pay AFTER subtracting witness budget from the total_budget OR the worker_budget_per_day/24 from "get_global_properties"

Code: [Select]
worker_budget=min(total_budget-witness_budget,worker_budget_per_day/24)

That is how much per hour allocated for all workers. NOW you rank each worker and pay them one hours worth of pay in order or # votes.

references:
https://github.com/cryptonomex/graphene/blob/4c09d6b8ed350ff5c7546e2c3fd15d0e6699daf2/libraries/chain/db_maint.cpp
maintains an Ubuntu PPA: https://launchpad.net/~showard314/+archive/ubuntu/bitshares [15% delegate] wallet_account_set_approval maqifrnswa true [50% delegate] wallet_account_set_approval delegate1.maqifrnswa true

Offline Louis

Wow, very informative.  +5%

Offline ebit

  • Committee member
  • Hero Member
  • *
  • Posts: 1866
    • View Profile
  • BitShares: ebit
telegram:ebit521
https://weibo.com/ebiter

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4641
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
BitShares committee member: abit
BitShares witness: in.abit

Offline wallace

  • Sr. Member
  • ****
  • Posts: 215
    • View Profile
give me money, I will do...

Offline Shentist

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 1601
    • View Profile
    • metaexchange
  • BitShares: shentist
i like the site more and more - very useful!

Offline tonyk

  • Hero Member
  • *****
  • Posts: 3308
    • View Profile
Interesting.

Bewildering, some might say.


So, you have found something that you are better at , compared to traveling and not producing videos??


 + 1

The plus one is only if you do not intend to have a worker doing nothing the next 12 mo., and  just using this as a sales pitch.
« Last Edit: October 28, 2015, 05:13:22 am by tonyk »
Lack of arbitrage is the problem, isn't it. And this 'should' solves it.

Offline roadscape

Great! Can we have top voter list?

For this I need to build user index.. but that would give us interesting referral data too :) maybe ready in a few days..
http://cryptofresh.com  |  witness: roadscape

Offline clayop

  • Hero Member
  • *****
  • Posts: 2033
    • View Profile
    • Bitshares Korea
  • BitShares: clayop
Great! Can we have top voter list?
Bitshares Korea - http://www.bitshares.kr
Vote for me and see Korean Bitshares community grows
delegate-clayop

Offline roadscape

Added a basic proposal explorer:

http://cryptofresh.com/p/1.10.9 - here's puppies' proposal to reduce account registration fees

Pretty cool to see it laid out like this, I think.. what a fun blockchain to explore!

One thing that concerns me is that old proposals are inacessible.. i.e. there is no record of proposal 1.10.8 using get_object.
http://cryptofresh.com  |  witness: roadscape

Offline maqifrnswa

  • Hero Member
  • *****
  • Posts: 661
    • View Profile
Super useful.. thank you! I've got the daily funding logic in place now :)

Excellent! You have the best way of visualizing worker proposals in the whole world as of now, literally.
If you want to improve the display, here are some other hints:
1) Worker objects never expire. Also some workers are not valid yet. You probably should filter out your worker list to only show active and valid ones.
2) However, it is important that upcoming proposals get visibility. Perhaps a separate table of "pending proposals" ranked in order of votes for proposals which have not started yet.

1) I thought work_end_date was the expiration date, and a worker will be paid daily for the period of work_begin_date --> work_end_date, no?
2) For now I've distinguished active/upcoming using colors.. when we have a few more workers and funding starts to be limited I'll add a better indicator of active vs unfunded vs upcoming :)

Thanks!
1) Yes, but I think the object remains in memory, just is NULL (I could be wrong) -- I guess we'll see in a few days!
2) great!
maintains an Ubuntu PPA: https://launchpad.net/~showard314/+archive/ubuntu/bitshares [15% delegate] wallet_account_set_approval maqifrnswa true [50% delegate] wallet_account_set_approval delegate1.maqifrnswa true

Offline roadscape

Super useful.. thank you! I've got the daily funding logic in place now :)

Excellent! You have the best way of visualizing worker proposals in the whole world as of now, literally.
If you want to improve the display, here are some other hints:
1) Worker objects never expire. Also some workers are not valid yet. You probably should filter out your worker list to only show active and valid ones.
2) However, it is important that upcoming proposals get visibility. Perhaps a separate table of "pending proposals" ranked in order of votes for proposals which have not started yet.

1) I thought work_end_date was the expiration date, and a worker will be paid daily for the period of work_begin_date --> work_end_date, no?
2) For now I've distinguished active/upcoming using colors.. when we have a few more workers and funding starts to be limited I'll add a better indicator of active vs unfunded vs upcoming :)
http://cryptofresh.com  |  witness: roadscape