Razvan Gabriel Apostu
Razvan Gabriel Apostu
Did you find a possible fix for this issue in the end?
> > create a guideline for frontend integrations > > Yep. A front-end template that shows how to use Permit2 with Ethers.js would go a long way. The [permit2-sdk](https://github.com/Uniswap/permit2-sdk) library...
Looks like it works if you remove the events, custom errors and `receive` (so only functions and constructor are left).
Got the same issue - it has to do with the way web3-react [expects](https://github.com/Uniswap/web3-react/blob/505e164e156854e7a82bc56520ae0fab3129746d/packages/walletconnect-v2/src/index.ts#L95) the `desiredChainId` to be included in the `chains` array (which afaik is now an antipattern due...
Thank you @tmm. Sorry for missing the "allow edits" checkbox.
Shouldn't this feature reside in a periphery?
I still think there's a need to separate the ERC721 "token" from the ERC20 "token" it is entitled to. > we realized that the 'token' terminology is ubiquitous for ERC-20s...
Fair points from both! Let's go with `token` then.
Yes, good idea! Could go in the "Queries" area in our docs: https://docs.sablier.com/api/subgraphs/protocol/queries.
This new version auto-generates queries in the API section. The idea behind the **Queries** page under **Indexers** was to provide popular queries stemming from user requests over time. It was...