janniks
janniks
👋 wanted to check in here - is there something I could help out with?
I released stacks.js + connect, will now create a wallet-web PR that updates to the latest versions...
https://github.com/hirosystems/stacks-wallet-web/pull/2333 updates to current stacks.js (4.0.0)
https://github.com/hirosystems/stacks.js/tree/master/packages/network#use-the-built-in-api-key-middleware ☝️ Here's an example of adding the api key middleware for stacks.js methods (e.g. `makeSTXTokenTransfer`), since not all network requests are done via the api-client. For stacks.js we pass...
Thanks, good catch!
👋 Great PR, thanks for the contribution — we do currently require signing a CLA for legal reasons. Should be possible via [CLA Assistant](https://cla-assistant.io/hirosystems/connect?pullRequest=269)
Thanks, it might be possible that CLA can't connect the email to the GitHub user. Maybe try [updating the commit email](https://www.git-tower.com/learn/git/faq/change-author-name-email#chapter_using+git+filter-branch) to the same as the GitHub user. Sorry about...
Thanks 🙏🏻
Is this a connect or explorer bug?
This should not be a problem anymore with the latest Stacks.js >=`5.0.1` or connect >=`7.0.0`