Updates

RT @mcuevasm: Another one: @StacksOrg leads listing with @transak_finance, Hiros @jtgerbingtons and @markymark integrate the fiat onramp into the @hirosystems web wallet making getting $STX so buttery beautiful. Just in time for holiday NFT SZN.🔥 ❤️ https://t.co/h7SyFdnnYf

RT @danheld: 1/ I've been writing about Bitcoin DeFi over the last 8 months which includes a variety of protocols including @lightning @Stacks @RSKsmart and @SovrynBTC. In this thread, I'm going to cover @ArkadikoFinance, which is a new stablecoin built on the @stacks ecosystem👇

@jasperjansz @aulneau_ nice rounded rectangles

@aulneau_ Here's some great analysis from @AaronBlankstein of fee estimates vs. median-fee rates that sheds light on our experience with estimates in the wallet last week https://t.co/MVGZ01O0XW

@BradMitchell_ @hirosystems This fix is now live in Firefox as v2.21.3

@BradMitchell_ @hirosystems Yep we're pushing the same v2.21.5 fix to Firefox today

@cryptoyipster Thanks for the kind words! And sorry for the bumpy release re: gas. We'll keep working until we get this right 💪

@cryptoyipster We pushed a new version to Chrome yesterday that caps standard fee recommendations to 0.75 STX as we iron out the underlying algorithm

@alexrudloff @aulneau_ Right now the fees only reflect distributions seen in the last block. At some point we may get them to reflect timing trends across several blocks, we which point we could indicate estimated time to confirmation by fee level

@alexrudloff @aulneau_ Of course, if the suggested value is miscalculated, it will take some time for users to figure out they should adjust around it. But also vice-versa as they get used to trusting a properly calculated value vs. prior experience

@alexrudloff @aulneau_ If users on balance opt to pay more than the standard suggestion, fees should increase until they reach an optimal equilibrium since it suggests they value their transactions more

@BitcoinBullz @hirosystems @Stacks @muneeb Heads up we're going to cap fees at lower values until we can iron out the estimation algorithm more: https://t.co/9lH1ktAEeN

@aulneau_ I just spot-checked a bunch of transactions from the more popular contracts and see mostly sub-1 STX as well. So to answer my own question, I do think our math here is off 😄 I'll push a new release that caps a lot lower for now until we can iron the algo out 🙏

@BitcoinBullz @hirosystems @Stacks @muneeb Here's a more recent piece in which we previewed the wallet's new fee estimates and other related work: https://t.co/3cLfRdZp30

@BitcoinBullz @hirosystems @Stacks @muneeb I'm truly sorry this is coming as a surprise, but we *are* trying to talk about this as much as possible. This was the post we made the first time there was an increase e.g.: https://t.co/SR2tvysF6N

@aulneau_ If the wallet is showing 5+ STX as a standard fee for any given transaction, then (theoretically) the last block saw 5+ STX paid in fees as the 50th percentile for similarly confirmed transactions. Do you suspect that's not the case i.e. we have a bug in the math somewhere?

@BitcoinBullz @hirosystems @Stacks @muneeb What kind of transparency here would be helpful here? We plan to publish a blog post about these wallet changes next week, to complement the FAQ I've linked. Would a pre-announcement help next time we expect to modify the wallet's fee functionality, as a heads up?

@BitcoinBullz @hirosystems @Stacks @muneeb I'm seeing 0.38048 STX for claiming with Byzantion at the moment since traffic appears to have eased since your screenshot (assuming its the same contract function) https://t.co/h2TeVnnyQZ

@BitcoinBullz @hirosystems @Stacks @muneeb See this FAQ for more details about how the fee suggestions now work: https://t.co/H22pGOFWuR

@BitcoinBullz @hirosystems @Stacks @muneeb The fee shown by wallet several days ago were static in that they didn’t take network conditions into account. They’re now prone to go up during especially busy periods