Alexander Graebe
Alexander Graebe
Developers often try to understand best practices (or techniques) to solve common goals. It would be great to collect and document them all cc @lgalabru
Let's figure out how to add the client library to the stacks.js monorepo. This goal should ideally include both an integration into the monorepo but also the being released in...
It would be great if there would be an API endpoint that would take an STX address (of a delegator) and return what accounts delegated how much (and until what...
Currently, the client requires contract call arguments to be manually serialized: ```js await smartContracts.callReadOnlyFunction({ contractAddress, contractName, functionName, readOnlyFunctionArgs: { sender: stxAddress, arguments: [ `0x${serializeCV( tupleCV({ hashbytes, version, }) ).toString("hex")}`, `0x${serializeCV(uintCV(microSTXoLockup)).toString("hex")}`,...
It is unclear which endpoints are proxied to the Node API. To make the project relationship clear, we should categorize or mark proxied endpoints appropriately.
As part of the OpenAPI spec review, we realized that there is a lack of naming conventions. It would be useful to extend our contributions guidelines with some initial conventions...
irt to [this chat](https://discord.com/channels/621759717756370964/691807526118883418/768472165166612550). we should document supported event types 
Currently, the API response for a contract call needs to deserialized manually: ```js const isEligible = await ; const response = deserializeCV(Buffer.from(isEligible.result.slice(2), "hex")); ``` It would be better if the...
Right now, the app uses GMaps as the main mapping provider. Users are asking for Leaflet or MapBox support
This should enable setting the following by path: - opened view - if contract call view, load provided contract