algoanne

Results 39 comments of algoanne

need to look at the other SDKs as well, probably same issue & fix.

To support this would require algod to potentially do a lot of work for every such request (the data is not organized in the DB in a way to efficiently...

My current thought (a controversial opinion, I'm sure...) is that maybe the algod should only be used for submitting transactions and getting the state deltas for data. These are the...

@pbennett Indexer no longer requires an archival node ever since Conduit release. You remind me of this issue: https://github.com/algorand/indexer/issues/1343 which asks for basically an indexer that just queries current state....

Thanks @fergalwalsh , I was wondering if someone would bring up latency as a factor in favor of algod serving current state. > In the dApps and wallets I've worked...

Looking at this now - We can add the proposer to the block in the indexer. This will require a DB migration to add the column. We can do this....

I went through the list, here are names that are confusingly different (there are others that have some variation but semantically the same): from - Sender to - Receiver or...

yes @shubhamshd, contributions are welcome here!

> Some things will still require Buffer usage in node (like base64 encoding), but we can investigate ways to have an alternative code path for browsers. @jasonpaulos why does base64...

one concern: boxes don't have an associated round in indexer (unlike all the accounts data), so we'll have to consider maybe we'll need more retries or something.