Michael Diamant

@kael-shipman Thanks for offering a contribution! Let us know if the above note + this note help provide a stating point. > @michaeldiamant anything to add? Linking to a recent...

@kael-shipman Thanks for the update. I appreciate you took a look at the testing methodology and totally understand that it's a greater time investment than you have available now. Closing...

I can't approve my own PR, so I leave a comment instead: As of https://github.com/algorand/pyteal/pull/439/commits/5282726f675b65498b04fe9f608694d94414b57e, the integration branch looks ready to merge once AVM 8 release kicks off.

> just one question on acct_params_get op code, and the related fields. Do we want them included in AVM8 release? @ahangsu Thanks for flagging it to ensure we cover all...

Leaving pointers to branches making progress towards the story's request: * https://github.com/barnjamin/pyteal-utils/blob/fp-class/pytealutils/math/fixed_point.py * https://github.com/CiottiGiorgio/pyteal/tree/feature/int

@ahangsu I think the ticket had a stale description based. Like you're suggesting, there's no exposed go-algorand functionality to extend in pyteal. So, I updated to remove the line item.

Summarizing outcomes from a group brainstorm: * Philosophically, it feels most correct to change fields from `number` to `bigint` everywhere that go-algorand defines a `uint64` data type. In practice, it...

For more complete context, here's the commit changing Go behavior: https://github.com/golang/go/commit/a218b3520a500254cc82b996b79ad6f5a355021c.

Marked as draft to prevent accidental merge because we've agreed to hold on merging until _after_ the upcoming consensus upgrade. https://github.com/algorand/go-algorand/issues/4344 exists as visual reminder to revisit for merging.

Closing in favor of https://github.com/algorand/go-algorand/issues/3973 because we agreed it's sufficient to start with an algod-only approach. Rationale: * Indexer does _not_ support _rewind_ capabilities for existing Application state (local +...