stacking.club 2.1 (#741)

[will-corcoran]

@aulneau

This discussion thread should be used for all payment requests for your grant.

Please follow these steps:

• Create a Gitbook for your project. If you are not familiar with this process, please watch this video for details on how to set your Gitbook up.
• Once you complete a milestone, update your Gitbook and post a message below summarizing which milestone was completed and the updates you made to your Gitbook.
• When you post your request please tag @will-at-stacks
• Once we have had a chance to review your deliverables and feel they match your pre-approved roadmap, we will begin the process of disbursing the associated payment.

[will-corcoran]

Link to grant issue

[will-corcoran]

Hi @aulneau -

Just checking in. Can you please provide an update on the status of your grant here?

Thanks,
Will

[aulneau]

Hi @will-at-stacks, yes absolutely!

We have the initial scaffold done for the new stacking.club project and most of the API work is completed:

• the api is now chainhooks based, will rely on Hiros chainhooks deployment to start
• has much better support for being more resilient to new contracts that support stacking
• just doing some final testing this week
• looking to launch the oss project with api implementation early next week
• with a fast follow of an updated stacking.club to make use of the new api

I've been in talks with anyone who has relied on the previous API and will help onboard them once we have the new service online.

[will-corcoran]

@aulneau - excellent. Thanks for the update! I'll ask Shakti to process your next payment.

[aulneau]

Hi everyone!

Wanted to provide a status update on the project:

We have most of the API completed and we're currently working on wrapping up the updated frontend. We opted for fleshing out a new application based on the improved API, which is taking a bit longer that we had hoped (lots of life stuff has come up recently, but things are settling down :) )

We are also working closely with Ludo to get hooked up with a Hiro deployed chainhooks instance which will power the new api and frontend.

Will keep everyone posted here!

[will-corcoran]

thanks for the update @aulneau !

[will-corcoran]

@aulneau just checking in to see how things are going. Can you provide an update soon? Thanks, Will

[friedger]

I hope @aulneau is doing well.

Does it make sense to hand over the project to a new lead? @will-at-stacks

[aulneau]

Hi there!

Thanks for the well wishes @friedger. I think long term if there is someone who is interested in working on stacking.club that would work out really well.

I want to thank everyone for their patience, I know that stacking.club has become a core property and service to much of the folks in the ecosystem. Without going into too much detail, things came up that have prevented me from shipping the project in the timeframe I had hoped and promised.

To give an update on status: I was waiting to gain access to a production deployment of chainhooks, and have been working closely with Ludo from hiro on that. Due to the network issues that came up, much of the focus on chainhooks was diverted to more pressing needs. Things have calmed down again, and I'm meeting next week with him to work together on anything left in that context.

I have a bit more UI related work, and some changes related to pox 3 to implement, but please know that I am still working on the project and plan to have a release that restores much of the functionality the ecosystem expects 🙏

Thanks everyone! happy to chat directly with anyone if you have concerns or suggestions :)

[aulneau]

Hey everyone! just wanted to provide an update: working to wrap up the few remaining components that existed previously, along with some new features (block-by-block updates!)

While most of the UI is completed, there are some minor data consistency issues I've been dealing with in trying to replicate the internal state of the pox contract. Been chatting with core devs to help understand what might be missing.

I'm shooting to have a beta version out soon so I can get feedback from the community around the data consistency issues -- it'll be helpful for folks to report if their data reflects what they understand to be true or not.

As always, thanks for your patience!

[Fingerpost77]

Thank you so much for the update and the work you are doing to bring stacking.club back to life after the STX upgrade. I'm really looking forward to the new site.

[jonastgerber]

Thx for all of your work, Thomas! We all love stacking.club and it's dearly missed : ) Much appreciated!

[muneeb-ali]

Amazing to see this coming along! Thanks, @aulneau 🚀

[aulneau]

Hey everyone! just wanted to provide a quick update here: planning on launching the new version of stacking.club on or before September 6. I've got our indexing situation working via the new Hiro platform and Chainhooks (great work team), just working on some additional data consistency checks and a few remaining UI components.

[Fingerpost77]

Very good news. Thank you for the update and thanks again for all the work you are doing. I have really missed stacking.club these past couple of months. Will be nice to see it up and running again.

[jonastgerber]

Woohoo! Thx @aulneau! 🙌

[aulneau]

Of course! I am very excited for when it can be live again. A status update:

I am working to get the production database and chainhooks set up for a release of beta.stacking.club for folks to test and provide feedback associated with stacking data. However, I'm running into issues with our database provider neon.tech. I'm working with their support to resolve the issues.

Will continue to provide updates

[aulneau]

Hey everyone!

I am happy to announce that there is a beta version of stacking club v2 available here: https://beta.stacking.club/

We still have a bit of work to do before pushing to production, but I wanted to get it out here for folks to dig into. We're aware of some minor performance issues, along with some improvements we want to do around mobile, open graph data, etc.

If you run into any issues, please feel free to comment here or reach out to me directly. I'm planning on keeping this beta site up for a week or so, and then hopefully pushing it live to production. Please note: the data doesn't currently go back before when pox2 was introduced. We'll be updating it with historic data once we've ironed out the current issues we have.

Thanks!

[will-corcoran]

Great news! Thanks for the update @aulneau

[jonastgerber]

Thx Thomas!

[friedger]

The number of stackers seems not correct. I see 1000 pool members and 45.4m STX locked at https://pool.friedger.de/cycles/70/
Based on data from https://app.statsonchain.com/dashboards/Fast-Pool/276

stacking.club shows 46 pool members and 45.9m STX:

[friedger]

pool.friedger.de has a bug that it can only handle 1000 pool members. The question is why it should 46 stackers.

[aulneau]

will dig into it -- this is an example of some data consistency issues I've been running into, will compare with statssonchain

[friedger]

Could you add a data field for total rewards in a cycle? Next to the stackers or so?

https://beta.stacking.club/cycles/69/rewards

[aulneau]

yes! will add

[314159265359879]

Impressive upgrade. I like it!

I miss the "all cycles" button in the navbar, even if it is only convenient to show the ones in PoX-3 I would love the option.

On mobile the "current cycle, and next cycle" buttons do not show in the navbar.

Will you also show APR's for finished cycles and/or per reward address in the future?

[jonastgerber]

+1, "all cycles" feature is key if doable 🙏

[aulneau]

Yes! there will be an all cycles tab, including historic cycles and future cycles. With the update to pox-2/3, the querying is a bit more complex and so it wasn't ready yet. But it's coming soon:tm:

[aulneau]

APR's for finished cycles and/or per reward address in the future?

Yes!

[jonastgerber]

Yeah that was what I was looking for in the beta, the latest APY's - thx again Thomas!

[friedger]

I see a difference in total amount of stacked stx for cycle 71. Any ideas which one is the correct one?

[aulneau]

I'm working on doing better calculations and screens to confirm total stacked based on the pox contract, and my indexing, should be live next week, and we can use that to better compare. The calculations to get the total stacked on the new stacking club take into consideration:

• raw stack stx
• stack increase
• stack extend
• aggregate stack commit
• aggregate stack increase

does the statsonchain handle all of those, too?

[friedger]

In https://app.statsonchain.com/dashboards/Fast-Pool/276 we only look at aggregate-stack* events

[friedger]

You are showing start of the next cycle as start of reward phase. Shouldn't we communicate the end of the period where stacking is allowed? See stacks-network/stacks-core#3775
@aulneau

[aulneau]

Yeah, this was confusing to me as well. In the original stacking.club, the prepare phase started at the beginning of N+1, but based on data from https://api.hiro.so/v2/pox, it shows that even though we're in the prepare phase, it's still technically cycle 70 (not 71)

{
  "contract_id": "SP000000000000000000002Q6VF78.pox-3",
  "pox_activation_threshold_ustx": 70960613753312,
  "first_burnchain_block_height": 666050,
  "current_burnchain_block_height": 815146,
  "prepare_phase_block_length": 100,
  "reward_phase_block_length": 2000,
  "reward_slots": 4000,
  "rejection_fraction": 25,
  "total_liquid_supply_ustx": 1419212275066257,
  "current_cycle": {
    "id": 70,
    "min_threshold_ustx": 120000000000,
    "stacked_ustx": 448267409278888,
    "is_pox_active": true
  },
  "next_cycle": {
    "id": 71,
    "min_threshold_ustx": 100000000000,
    "min_increment_ustx": 70960613753,
    "stacked_ustx": 363047370043271,
    "prepare_phase_start_block_height": 815050,
    "blocks_until_prepare_phase": -96,
    "reward_phase_start_block_height": 815150,
    "blocks_until_reward_phase": 4,
    "ustx_until_pox_rejection": 354803068766550
  },
  "min_amount_ustx": 100000000000,
  "prepare_cycle_length": 100,
  "reward_cycle_id": 70,
  "reward_cycle_length": 2100,
  "rejection_votes_left_required": 354803068766550,
  "next_reward_cycle_in": 4,
  "contract_versions": [
    {
      "contract_id": "SP000000000000000000002Q6VF78.pox",
      "activation_burnchain_block_height": 666050,
      "first_reward_cycle_id": 0
    },
    {
      "contract_id": "SP000000000000000000002Q6VF78.pox-2",
      "activation_burnchain_block_height": 781552,
      "first_reward_cycle_id": 56
    },
    {
      "contract_id": "SP000000000000000000002Q6VF78.pox-3",
      "activation_burnchain_block_height": 791551,
      "first_reward_cycle_id": 60
    }
  ]
}

[friedger]

Yes, that is confusing. The prepare phase is the end of the cycle. We should maybe call it transfer phase N/N+1

[aulneau]

Something else I'm curious about but don't have answers for:

The cycles stop paying rewards out very early than they have historically, which you can see from the new histogram chart I've added:

There also isn't PoB anymore -- @friedger do you know why this is the case?

[friedger]

All STX locked during the prepare phase won't get any slots. See https://app.statsonchain.com/dashboards/Fast%20Pool/276

[friedger]

This only explains a few empty slots

[friedger]

I don't see a big change in reward slots:
https://app.statsonchain.com/query?query=select%2520%28burn_block_height%2520-%2520666050%29%252F2100%2520as%2520cycle%252C%2520count%28*%29%2520as%2520slots%2520from%2520reward_slot_holders%250A--where%2520address%2520%253D%2520%27bc1qs0kkdpsrzh3ngqgth7mkavlwlzr7lms2zv3wxe%27%250Agroup%2520by%25201%250Aorder%2520by%25201%2520desc

[friedger]

burn amounts are only in the burnchain_rewards DB when there are also rewards in the same block.

[friedger]

[friedger]

The stacking amount for the current cycle for fast pool is not correct:
https://beta.stacking.club/cycles/72/delegators

it should be more like 46m STX

[friedger]

Is the source code available somewhere already? I am happy to look into it.

[friedger]

More updates? @aulneau